Gateway Cluster Protocol Translation for NGN Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing gateway servers in NGN networks require customization to adapt between different communication protocols used by client nodes and provider servers, leading to inefficiencies in request and answer translation, load balancing, and scenario rule management.

Innovation Solution

A system comprising a cluster of gateway nodes with a database of scripts for scenario, routing, and transformation rules, an execution processing module, and peer-to-peer connections, which translates and balances requests and answers between client and server nodes, using routing and transformation scripts based on client profiles and session history to adapt protocols and manage events.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If gateway servers are customized for configuring the gateway for adapting between different protocols of client nodes and provider servers, then protocol compatibility is improved, but device complexity increases

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidgateway customization complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a protocol adapter as an intermediary component between the gateway server and the communication protocols. This adapter handles the complexity of protocol translation and adaptation, allowing the gateway to maintain simplicity while supporting multiple client node and provider server protocols without direct customization of the gateway itself.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The gateway server is designed with universal functionality to handle multiple protocols through a common architecture. By using a single gateway that can adapt to various protocols via the mediator mechanism, the system eliminates the need for multiple customized gateways, thereby reducing device complexity while maintaining protocol compatibility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Device complexity

If a single gateway server handles all client requests and server answers, then device complexity is reduced, but productivity decreases due to processing burden

Engineering Contradiction:
Improvegateway structure simplicityVSAvoidrequest processing efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The gateway server is segmented into multiple independent gateway nodes that form a cluster. Each gateway node handles a portion of the processing load, distributing requests and answers across multiple units. This segmentation maintains the simplicity of individual gateway structures while significantly improving overall productivity through parallel processing.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

Multiple gateway nodes are merged into a unified cluster that operates as a single logical unit. The cluster collectively handles all client requests and server answers, combining the processing power of multiple gateways to achieve high productivity while maintaining the architectural simplicity of each individual node.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If gateway servers translate and adapt all requests and answers, then protocol compatibility is improved, but loss of time increases due to translation processing

Engineering Contradiction:
Improveprotocol adaptation capabilityVSAvoidrequest translation time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

Transformation scripts are pre-configured in the gateway nodes before runtime operation. These scripts contain pre-computed translation rules and protocol adaptation logic that can be executed directly without delay. By preparing the translation mechanisms in advance, the system minimizes translation time during actual request processing while maintaining comprehensive protocol compatibility.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If gateway nodes are interconnected through peer to peer connections, then reliability is improved, but device complexity increases

Engineering Contradiction:
Improvenetwork service availabilityVSAvoidgateway interconnection structure
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The gateway nodes are designed to self-manage their peer-to-peer connections and interactions within the cluster. Each gateway node autonomously handles its own routing, load balancing, and communication with other nodes without requiring complex centralized control. This self-service capability improves reliability through distributed operation while keeping the interconnection structure relatively simple.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS8738700B2Method and system for providing network services
Publication Date: 2014.05.27 TRAFFIX SYST
  • US8738700B2 patent drawing
  • US8738700B2 patent drawing
  • US8738700B2 patent drawing

AI summary

The present invention provides a system for intermediating between client nodes and pools of server nodes in an NGN network where the server nodes provide network services to client nodes, wherein the client nodes use various communication protocols and at least part of said communication protocols are different from the communication protocol used by the server nodes. The system comprising: a cluster of associated gateway nodes providing an integrated service for the clients nodes, where each gateway provides services of at least one of: translations of request and answers between the client node and a provider server node, load balancing and managing scenario rules. Each gateway comprise: a database of scripts including, scenario rules, routing scripts and associated transformation scripts, an execution processing module for handling events of at least client requests and server answers according to scenario rules.