Service implementation method, apparatus, and system based on fix protocol

Patent metadata

Field	Value
Publication number	US-2018367482-A1
Application number	US-201816115313-A
Country	US
Kind code	A1
Filing date	Aug 28, 2018
Priority date	Feb 29, 2016
Publication date	Dec 20, 2018
Grant date	—

Abstract

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.

First claim

What is claimed is:

1 . A computer-implemented method, comprising:
receiving, by a service platform, a message, wherein the message includes service data; determining, by the service platform, a service script associated with the message from a script list, wherein the service script is determined based on at least a service type of the service data, and the service script includes service logic associated with a protocol version of the message; and executing, by the service platform, the service script to process the service data based on the service logic.

2 . The computer-implemented method of claim 1 , wherein the message is a Financial Information Exchange (FIX) message, the FIX message is an encapsulated universal FIX message, and the encapsulated universal FIX message is encapsulated to not include service logic associated with a FIX protocol version of the FIX message.

3 . The computer-implemented method of claim 2 , wherein the service data is in a character string format, the script list includes a plurality of service scripts, and each service script is associated with a particular FIX protocol version.

4 . The computer-implemented method of claim 2 , the method further comprising:
in response to a FIX service being added to the service platform, obtaining a service script including service logic of the added FIX service; and adding the obtained service script to the script list.

5 . The computer-implemented method of claim 2 , the method further comprising:
after receiving the FIX message, determining a message type of the FIX message based on message type information in the service data; in response to determining that the message type of the FIX message is an application layer type, invoking an application layer method to execute universal service logic at an application layer; and in response to determining that the message type of the FIX message is a session layer type, invoking a session layer method to execute universal service logic at a session layer.

6 . The computer-implemented method of claim 1 , further comprising determining the protocol version from the service data.

7 . The computer-implemented method of claim 6 , wherein the service script is determined based on the service type and the protocol version, and the script list includes a mapping relationship among the service type, the protocol version, and the determined service script.

8 . A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:
receiving, by a service platform, a message, wherein the message includes service data; determining, by the service platform, a service script associated with the message from a script list, wherein the service script is determined based on at least a service type of the service data, and the service script includes service logic associated with a protocol version of the message; and executing, by the service platform, the service script to process the service data based on the service logic.

9 . The non-transitory, computer-readable medium of claim 8 , wherein the message is a Financial Information Exchange (FIX) message, the FIX message is an encapsulated universal FIX message, and the encapsulated universal FIX message is encapsulated to not include service logic associated with a FIX protocol version of the FIX message.

10 . The non-transitory, computer-readable medium of claim 9 , wherein the service data is in a character string format, the script list includes a plurality of service scripts, and each service script is associated with a particular FIX protocol version.

11 . The non-transitory, computer-readable medium of claim 9 , the operations further comprising:
in response to a FIX service being added to the service platform, obtaining a service script including service logic of the added FIX service; and adding the obtained service script to the script list.

12 . The non-transitory, computer-readable medium of claim 9 , the operations further comprising:
after receiving the FIX message, determining a message type of the FIX message based on message type information in the service data; in response to determining that the message type of the FIX message is an application layer type, invoking an application layer method to execute universal service logic at an application layer; and in response to determining that the message type of the FIX message is a session layer type, invoking a session layer method to execute universal service logic at a session layer.

13 . The non-transitory, computer-readable medium of claim 8 , the operations further comprising determining the protocol version from the service data.

14 . The non-transitory, computer-readable medium of claim 13 , wherein the service script is determined based on the service type and the protocol version, and the script list includes a mapping relationship among the service type, the protocol version, and the determined service script.

15 . A computer-implemented system, comprising:
one or more computers; and one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising: receiving, by a service platform, a message, wherein the message includes service data; determining, by the service platform, a service script associated with the message from a script list, wherein the service script is determined based on at least a service type of the service data, and the service script includes service logic associated with a protocol version of the message; and executing, by the service platform, the service script to process the service data based on the service logic.

16 . The computer-implemented system of claim 15 , wherein the message is a Financial Information Exchange (FIX) message, the FIX message is an encapsulated universal FIX message, and the encapsulated universal FIX message is encapsulated to not include service logic associated with a FIX protocol version of the FIX message.

17 . The computer-implemented system of claim 16 , wherein the service data is in a character string format, the script list includes a plurality of service scripts, and each service script is associated with a particular FIX protocol version.

18 . The computer-implemented system of claim 16 , the operations further comprising:
in response to a FIX service being added to the service platform, obtaining a service script including service logic of the added FIX service; and adding the obtained service script to the script list.

19 . The computer-implemented system of claim 16 , the operations further comprising:
after receiving the FIX message, determining a message type of the FIX message based on message type information in the service data; in response to determining that the message type of the FIX message is an application layer type, invoking an application layer method to execute universal service logic at an application layer; and in response to determining that the message type of the FIX message is a session layer type, invoking a session layer method to execute universal service logic at a session layer.

20 . The computer-implemented system of claim 15 , the operations further comprising determining the protocol version from the service data.

Assignees

• Alibaba Group Holding Ltd

Inventors

• Li Xuyang

Classifications

• H04L69/06 Primary

  Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1] · CPC title

• G06F9/44521

  Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading · CPC title

• G06Q40/00

  Finance; Insurance; Tax strategies; Processing of corporate or income taxes · CPC title

• H04L2212/00

  Encapsulation of packets · CPC title

• H04L51/06

  Message adaptation to terminal or network requirements · CPC title