JPeX Client Socket Integration via XML Translation Facade

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The integration of external applications with the JPeX client has resulted in a chaotic jumble of specialized code due to independent choices of technologies and solutions, lacking a unified approach for facilitating interactive trading and end-user interaction activities.

Innovation Solution

A system and method that uses a socket server to establish connections between external applications and the JPeX client, employing XML for command execution, with a translation facade for parsing service requests and an authentication module for secure communication, enabling seamless integration and workflow management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If external applications are integrated with JPeX client using independent technology choices, then integration functionality is achieved, but code complexity and disorganization increase

Engineering Contradiction:
Improveintegration functionalityVSAvoidcode complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent segments the integration architecture into distinct layers: presentation layer (external applications), translation facade layer (XML parsing and protocol conversion), and core business logic layer (JPeX client). This segmentation allows each layer to be developed independently while maintaining organized, manageable code structures that reduce overall system complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a translation facade as an intermediary component between external applications and the JPeX client. This facade provides a standardized interface that mediates all communications, preventing direct coupling between external applications and core client code. The intermediary layer organizes integration logic centrally, reducing code complexity while maintaining versatility.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If multiple integration technologies are used independently, then diverse application support is achieved, but system uniformity and maintainability deteriorate

Engineering Contradiction:
Improveapplication supportVSAvoidsystem uniformity
Core Design Contradiction:
Adaptability or versatilityVSStability of the object's composition

Solution Approach 1:

The patent creates a universal translation facade that handles multiple integration technologies (DDE, HTTP, sockets, RPC) through a single standardized interface. This universal layer parses all incoming requests using consistent XML schemas and converts them to uniform internal protocols, maintaining system uniformity while supporting diverse applications.

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

Solution Approach 2:

The patent enforces homogeneity by requiring all external applications to communicate through standardized XML message formats regardless of their underlying technology. The translation facade ensures all requests are normalized to the same internal structure, creating uniform processing logic that improves maintainability while supporting application diversity.

Inventive Principle:
Principle #33Homogeneity

3Speed

If direct connections are established between external applications and JPeX client, then communication efficiency is improved, but security and authentication control are weakened

Engineering Contradiction:
Improvecommunication efficiencyVSAvoidsecurity control
Core Design Contradiction:
SpeedVSReliability

Solution Approach 1:

The translation facade serves as a security intermediary that all communications must pass through. It implements centralized authentication, authorization, and validation logic that maintains security controls while preserving communication efficiency. The intermediary verifies credentials and validates requests without adding significant overhead to the communication path.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements feedback mechanisms where the translation facade continuously monitors and validates communications between external applications and the JPeX client. Authentication tokens are verified, requests are validated against business rules, and responses are authenticated before being sent back, maintaining security control while enabling efficient communication through established protocols.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS7770184B2Integrated trading platform architecture
Publication Date: 2010.08.03 JPMORGAN CHASE BANK NA
  • US7770184B2 patent drawing
  • US7770184B2 patent drawing
  • US7770184B2 patent drawing

AI summary

A system and method that provides a JPeX client that opens up a socket on which it listens for connections from the local host. External applications on the desktop are able to connect to the server socket in the client and use XML to execute commands on the client.