Tiered Affinity-Based Message Routing for Endpoint Integration

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing message routing systems face challenges in efficiently routing messages between client service applications and business service endpoints, particularly when new service endpoints are deployed, requiring hardware changes and complex reconfiguration, and struggle with load balancing and failover.

Innovation Solution

A tiered affinity-based message routing approach is implemented, where affinity rules are created and applied to select the appropriate service endpoint based on data partitioning strategies, geographic location, and partner associations, allowing for efficient routing changes and improved load balancing and failover.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If a load balancer reconfigures to accommodate a new service endpoint, then the new endpoint can be integrated into the system, but hardware changes are required which increases complexity and time for deployment

Engineering Contradiction:

Improveintegration of new service endpointVSAvoidhardware changes

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent replaces the mechanical hardware-based load balancer with a software-based routing system. The affinity rules processor and client service application use software configurations (affinity rules) to route messages to service endpoints, eliminating the need for hardware changes when integrating new endpoints. This substitution allows dynamic adaptation through software updates rather than physical reconfiguration.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Productivity

If traditional load balancing is used to route messages, then messages can be distributed across endpoints, but the system lacks flexibility in routing based on data characteristics and location

Engineering Contradiction:

Improvemessage routing efficiencyVSAvoidrouting flexibility based on data characteristics

Core Design Contradiction:

ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements local quality by making routing decisions based on local data characteristics. The affinity rules processor evaluates specific attributes of the requested data (such as data location, partner associations, and partitioning strategies) to determine the optimal service endpoint. This allows messages to be routed to the most appropriate endpoint based on the specific characteristics of each data request, improving both efficiency and adaptability.

Inventive Principle:

Principle #3Local quality

Solution Approach 2:

The system changes routing parameters dynamically based on data characteristics. Instead of using fixed load balancing rules, the affinity rules processor modifies routing decisions based on varying parameters such as data location, partner relationships, and partitioning schemes. This parameter-based approach enables flexible adaptation to different data types and access patterns while maintaining high routing efficiency.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If the load balancer operator manually reconfigures the system for each new endpoint, then routing can be updated, but this increases operational time and complexity

Engineering Contradiction:

Improverouting accuracyVSAvoidreconfiguration time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The system implements self-service through automated affinity rule processing. When a new service endpoint is deployed, the affinity rules processor automatically retrieves updated affinity rules from storage and applies them to route messages appropriately. This eliminates the need for manual operator intervention in the reconfiguration process, reducing both time and operational complexity while maintaining routing accuracy through rule-based automation.

Inventive Principle:

Principle #25Self-service

4Adaptability or versatility

If client applications are notified of each new endpoint, then they can update their routing information, but this increases network traffic and complexity

Engineering Contradiction:

Improveendpoint awarenessVSAvoidnotification and update mechanism

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces an intermediary affinity rules processor that acts as a mediator between service endpoints and client applications. Instead of directly notifying client applications of new endpoints, the system updates affinity rules in the intermediary processor, which then automatically handles routing decisions. This intermediary approach reduces network traffic and complexity by centralizing routing logic and eliminating the need for direct client application updates.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentUS9680925B2Methods and apparatus to route message traffic using tiered affinity-based message routing

Publication Date: 2017.06.13 AT&T INTELLECTUAL PROPERTY I L P

AI summary

Methods and apparatus to route network traffic using tiered affinity-based message routing are disclosed herein. An example method to select a destination endpoint for a message includes receiving a rule from a service provider, the rule specifying a set of destination endpoints associated with the service provider and the rule specifying a set of criteria to be used to select one of the destination endpoints for a message containing a data request. The method also includes sending the rule to a client service to be used to select the destination endpoint for the message based on a characteristic of the requested data.