FIX Protocol Service Platform Script Decoupling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The high costs associated with deploying and maintaining service environments for various FIX protocol versions on a service platform, due to the need for separate environments and transaction service logic for each version, increase with protocol upgrades and growing service types.
Innovation Solution
A service implementation method and apparatus that abstracts and encapsulates FIX packets into universal messages without detailed service logic, allowing service platforms to process service data using scripts that are decoupled from the FIX protocol code, enabling compatibility with any FIX protocol version by using dynamic configuration and loading of service scripts.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If the service platform sets up service environments for all FIX protocol versions to ensure compatibility, then the protocol version compatibility is improved, but the deployment and maintenance costs increase significantly
Solution Approach 1:
The patent implements a universal service environment that can handle multiple FIX protocol versions (FIX 4.2, FIX 4.3, FIX 4.4, FIX 5.0) through a single deployment. The service platform uses a common service environment with version-agnostic service logic that can process messages from different protocol versions without requiring separate environments for each version, thereby achieving multi-functionality and reducing deployment complexity
Solution Approach 2:
The patent introduces an intermediary layer (the service environment) that mediates between the incoming FIX messages of various versions and the underlying service logic. This intermediary handles protocol version detection and routing, translating different protocol versions into a unified internal representation that the service logic can process, thus eliminating the need for multiple separate service environments
2Adaptability or versatility
If separate transaction service logic is developed for different FIX protocol versions, then the protocol version compatibility is improved, but the development and maintenance workload increase
Solution Approach 1:
The patent develops a universal transaction service logic that can handle multiple FIX protocol versions through a single implementation. The service logic is designed to be version-agnostic, using a unified message structure and processing framework that works across FIX 4.2, 4.3, 4.4, and 5.0, thereby eliminating the need to develop and maintain separate service logic for each protocol version
Solution Approach 2:
The patent uses configuration files and templates to represent different protocol version handling rules, allowing the system to copy and adapt the same service logic template for different protocol versions. Instead of duplicating entire service logic implementations, the system copies and modifies configuration parameters to accommodate version-specific requirements, significantly reducing the volume of service logic needed
Data Source
AI summary
A message is received by a service platform. The message includes service data. A service script associated with the message is determined by the service platform from a script list. The service script is determined based on at least a service type of the service data. The service script includes service logic associated with a protocol version of the message. The service script is executed, by the service platform, to process the service data based on the service logic.