CN112532619B

CN112532619B - DEFIX protocol generation and analysis method, client, server and system

Info

Publication number: CN112532619B
Application number: CN202011353556.0A
Authority: CN
Inventors: 彭小龙
Original assignee: Shenzhen Qianhaijingyou Technology Co ltd
Current assignee: Shenzhen Qianhaijingyou Technology Co ltd
Priority date: 2020-11-26
Filing date: 2020-11-26
Publication date: 2022-01-25
Anticipated expiration: 2040-11-26
Also published as: CN112532619A

Abstract

The invention discloses a method for generating a DEFIX protocol, which comprises the steps of receiving data application demand information and confirming the information type of the data application demand information; generating DEFIX protocol information of the data application demand information by taking the information type as an information header, wherein the DEFIX protocol information comprises the information header, an information target, an information text field and an information end mark; and sending the generated DEFIX protocol information to a server to acquire corresponding application data. The invention also discloses a DEFIX protocol analysis method, a client and a server, namely a system. The invention designs a method for generating a DEFIX protocol, the internal structure of the DEFIX protocol is simpler, a Key corresponding to the form of a header is used for expressing, a header command does not need to be verified, login/logout is not needed, the speed of the protocol is improved, the effect of more intuitively presenting important information is realized, and the application efficiency of the DEFIX protocol is also improved.

Description

DEFIX protocol generation and analysis method, client, server and system

Technical Field

The invention relates to the technical field of data transmission formats, in particular to a DEFIX protocol generation and analysis method, a client, a server and a system.

Background

In data transmission application, the FIX protocol is widely applied to data transmission application of various large financial institutions at present, and although the existing FIX protocol as a real-time electronic communication protocol has some advantages of data communication, in practical application, financial services are formatted compared with the traditional service process, and a uniform exchange format is applied to each service function interface, so that each function module realizes communication connection. When the FIX protocol is used for data transmission, the FIX protocol is too complex in internal structure and slow in response speed, and is not convenient to use. And the header file of the existing FIX protocol header is unreadable, is in a binary format, and cannot better analyze service requirements.

The above is only for the purpose of assisting understanding of the technical aspects of the present invention, and does not represent an admission that the above is prior art.

Disclosure of Invention

The invention mainly aims to provide a DEFIX protocol generation and analysis method, a client server and a computer readable storage medium, and aims to solve the problems that the internal structure of the existing FIX protocol is too complex, the reaction speed is slow, the use is not simple enough, the header file of the FIX protocol is unreadable, the business requirement cannot be better analyzed, and the efficiency of data transmission application is influenced.

In order to achieve the above object, the present invention provides a method for generating a DEFIX protocol, including the following steps:

receiving data application demand information and confirming the information type of the data application demand information;

generating DEFIX protocol information of the data application demand information by taking the information type as an information header, wherein the DEFIX protocol information comprises the information header, an information target, an information text field and an information end mark;

and sending the generated DEFIX protocol information to a server to acquire corresponding application data.

Optionally, the step of generating the DEFIX protocol information of the data application requirement information by using the information type as a header includes:

analyzing the data application demand information, and confirming and generating information parameters of the DEFIX protocol information according to an analysis result, wherein the information parameters comprise information types, operation data and information contents;

adding the parsed information parameter to a preset DEFIX protocol generation format to generate the DEFIX protocol information.

Optionally, the method further comprises:

sending a data connection request to a server;

and creating a data connection channel with the server when receiving a confirmation instruction returned by the server.

Optionally, the step of creating a data connection channel with the server when receiving a confirmation instruction returned by the server includes:

a DEFIX protocol information generation format is deployed in the data connection channel.

In order to achieve the above object, the present invention provides a method for parsing a DEFIX protocol, including:

receiving DEFIX protocol information sent by a client, and reading a header of the DEFIX protocol information to confirm the information type of the DEFIX protocol information;

confirming target data of the DEFIX protocol information, and integrating feedback data by the information type and the target data;

returning the integrated feedback data to the client application.

Optionally, the step of confirming the target data of the DEFIX protocol information and integrating the feedback data with the information type and the target data includes:

reading an information target and an information text field of the DEFIX protocol information, and confirming corresponding target data by using the information target;

and performing data integration on the target data according to the data application purpose of the information text domain, and obtaining the feedback data according to an integration result.

Optionally, the method further comprises:

when a data connection request of a client is received, a confirmation instruction is returned to the client;

and establishing a data connection relation with the client according to the data connection channel established by the client.

In addition, to achieve the above object, the present invention further provides a client, including: the processor is used for storing the DEFIX protocol generation program, and the DEFIX protocol generation program is stored on the memory and can be operated on the processor, and when the DEFIX protocol generation program is analyzed by the processor, the steps of the DEFIX protocol generation method are realized.

The present invention also provides a server, comprising: a memory, a processor, and a DEFIX protocol parser stored on the memory and operable on the processor, the DEFIX protocol parser, when parsed by the processor, implementing the steps of the DEFIX protocol parsing method as described above.

The invention also provides a DEFIX protocol generation system comprising a client as claimed in the preceding claims and a server as described above.

The invention provides a method for generating a DEFIX protocol, which comprises the steps of receiving data application requirement information and confirming the information type of the data application requirement information; generating DEFIX protocol information of the data application demand information by taking the information type as an information header, wherein the DEFIX protocol information comprises the information header, an information target, an information text field and an information end mark; and sending the generated DEFIX protocol information to a server to acquire corresponding application data. According to the invention, by establishing a DEFIX protocol format, the internal structure of the DEFIX protocol is simpler, a header is not required to be encrypted, the acquisition form is simplified, a header command is not required to be checked again, login/exit is not required, and the syntax is simpler. A Key corresponding to the form of the header title is used for expressing, a header command does not need to be verified, most of numerical value generation configuration files of the Key are applied and stored to the local, login/logout is not needed, the speed of the protocol is improved, important information is displayed more visually, and the application efficiency of the DEFIX protocol is improved.

Drawings

FIG. 1 is a schematic diagram of a terminal \ device structure of a hardware operating environment according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of another terminal \ device in a hardware operating environment according to an embodiment of the present invention;

FIG. 3 is a schematic flow chart of a first embodiment of a DEFIX protocol generation method of the present invention;

FIG. 4 is a schematic flow chart of a second embodiment of a DEFIX protocol generation method of the present invention;

FIG. 5 is a flow chart illustrating a first embodiment of a DEFIX protocol parsing method according to the present invention;

fig. 6 is a flowchart illustrating a second embodiment of a DEFIX protocol parsing method according to the present invention.

The implementation, functional features and advantages of the objects of the present invention will be further explained with reference to the accompanying drawings.

Detailed Description

It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

The main solution of the embodiment of the invention is as follows: receiving data application demand information and confirming the information type of the data application demand information; generating DEFIX protocol information of the data application demand information by taking the information type as an information header, wherein the DEFIX protocol information comprises the information header, an information target, an information text field and an information end mark; and sending the generated DEFIX protocol information to a server to acquire corresponding application data.

Because the internal structure of the existing FIX protocol is too complex, the response speed is slow, the use is not simple enough, and the header file of the FIX protocol is unreadable, the business requirement can not be better analyzed, and the efficiency of data transmission application is influenced.

The invention provides a solution, which creates a DEFIX protocol format, so that the internal structure of the DEFIX protocol is simpler, a header is not required to be encrypted, the acquisition form is simplified, a head command is not required to be checked again, login/exit is not required, and the grammar is simpler. A Key corresponding to the form of the header title is used for expressing, a header command does not need to be verified, most of numerical value generation configuration files of the Key are applied and stored to the local, login/logout is not needed, the speed of the protocol is improved, important information is displayed more visually, and the application efficiency of the DEFIX protocol is improved.

As shown in fig. 1, fig. 1 is a schematic diagram of a terminal \ device structure of a hardware operating environment according to an embodiment of the present invention.

The terminal of the embodiment of the invention can be a PC, and can also be a mobile or non-mobile terminal device such as a smart phone, a tablet computer, an electronic book reader, a portable computer and the like.

As shown in fig. 1, the terminal may include: a processor 1001, such as a CPU, a network interface 1004, a user interface 1003, a memory 1005, a communication bus 1002. Wherein a communication bus 1002 is used to enable connective communication between these components. The user interface 1003 may include a Display screen (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 1003 may also include a standard wired interface, a wireless interface. The network interface 1004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 1005 may be a high-speed RAM memory or a non-volatile memory (e.g., a magnetic disk memory). The memory 1005 may alternatively be a storage device separate from the processor 1001.

Those skilled in the art will appreciate that the terminal structure shown in fig. 1 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components.

As shown in fig. 1, a memory 1005, which is a kind of computer storage medium, may include therein generation programs of an operating system, a network communication module, a user interface module, and a DEFIX protocol.

In the terminal shown in fig. 1, the network interface 1004 is mainly used for connecting to a backend server and performing data communication with the backend server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and the processor 1001 may be configured to call the generation procedure of the DEFIX protocol stored in the memory 1005 and resolve the following operations:

Further, the processor 1001 may call the generation program of the DEFIX protocol stored in the memory 1005, and also resolve the following operations:

sending a data connection request to a server;

As shown in fig. 2, fig. 2 is a schematic diagram of a terminal \ device structure of a hardware operating environment according to an embodiment of the present invention.

As shown in fig. 1, the terminal may include: a processor 2001 such as a CPU, a network interface 2004, a user interface 2003, a memory 2005, a communication bus 2002. The communication bus 2002 is used to implement connection communication between these components. The user interface 2003 may include a Display (Display), an input unit such as a Keyboard (Keyboard), and the optional user interface 2003 may also include a standard wired interface, a wireless interface. The network interface 2004 may optionally include a standard wired interface, a wireless interface (e.g., WI-FI interface). The memory 2005 may be a high-speed RAM memory or a non-volatile memory (e.g., a disk memory). The memory 2005 may alternatively be a storage device separate from the aforementioned processor 2001.

As shown in fig. 1, the memory 2005, which is a kind of computer storage medium, may include therein a generation program of an operating system, a network communication module, a user interface module, and a DEFIX protocol.

In the terminal shown in fig. 1, the network interface 2004 is mainly used for connecting to a backend server and performing data communication with the backend server; the user interface 1003 is mainly used for connecting a client (user side) and performing data communication with the client; and the processor 2001 may be used to invoke the parser program of the DEFIX protocol stored in the memory 2005 and parse the following operations:

returning the integrated feedback data to the client application.

Further, the processor 2001 may invoke a resolution procedure of the DEFIX protocol stored in the memory 2005, which also resolves the following operations:

Referring to fig. 3, fig. 3 is a schematic flow chart of a first embodiment of a DEFIX protocol generating method according to the present invention, where the DEFIX protocol generating method includes:

step S10, receiving data application requirement information and confirming the information type of the data application requirement information;

receiving data application demand information based on current data connection application, wherein the data application demand information is a data application demand based on current defix protocol data transmission, and in general, the data application demand information mainly points to a server to acquire/update operation data of target data, and is initiated by a user of a terminal where a client is located, wherein when the data application demand information is initiated based on the client, the data application demand information can be initiated based on related data application operation of the client. Further, according to the received data application requirement, an information type of the data application requirement information is determined, where the information type refers to an operation type based on data operation in the current data application requirement information, and in this embodiment, the information type may be defined as data updating operation such as data acquisition and updating, or data revocation operation such as data closing.

Step S20, generating DEFIX protocol information of the data application requirement information by using the information type as an information header, where the DEFIX protocol information includes an information header, an information target, an information body field, and an information end flag;

according to the method, the DEFIX protocol is a simplified improved version based on the existing FIX protocol, namely the DEFIX protocol is simplified and improved on the basis of the FIX protocol, and specific simplified and improved operations comprise removing a standard header and a standard tail and reducing unnecessary information length; inheriting a text domain structure, wherein the domain is in a form of 'Tag ═ Value', and since SOH is a non-printable character, a delimiters is changed into a vertical line ('|'), so that reading and writing are facilitated; the end of the message is indicated by a line break ("\ n").

In the method of the invention, there are 2 identities using the DEFIX protocol: a client (client) and a server (server); the client updates data and pulls the data to the server through the data request and the update instruction, and the server feeds the data back to the client through the data feedback information. And the server stores and maintains all data, and uses "symbol" to mark a piece of data information, each symbol data is a set of multiple fields (Tag ═ Value), and uses page (group) to represent the set of multiple symbols, and can use corresponding instruction to obtain and set.

As shown above, the step of generating the DEFIX protocol information of the data application requirement information with the information type as the header includes:

The method includes the steps of confirming an information type based on the data application requirement information, generating corresponding DEFIX protocol information, analyzing the data application requirement information to obtain an information parameter based on the DEFIX protocol information on the premise that the DEFIX protocol information includes an information header, an information target, an information body field and an information end mark, and based on an information format of the DEFIX protocol information, the information parameter of the DEFIX protocol information includes an information type, operation data and information content, so that specific contents based on a DEFIX protocol structure are as follows:

the DEFIX protocol information format is: information type, information target, information text domain and information end mark;

the information type is as follows: each piece of information begins with an information type name that identifies the type and purpose of the piece of information. The information type includes instruction information and data feedback information. The instruction information can be divided into a data request instruction and a data update instruction, and the information types are specifically classified as follows.

Information object: representing the target of information to be operated, generally using handle identification, each information type represents different specific meanings and roles:

the handle in the data request instruction information represents the request id of the request, and the server responds to the data feedback information of the request, wherein the request id is used as the handle, so that the client can distinguish a plurality of different request instructions. Handle in the data update instruction information generally indicates the symbol name or page name of the instruction requiring data update. And the handle in the data feedback information is the handle set in the request instruction of the response.

Information text field: the body of information is generally the specific content that the information is intended to represent, and is made up of a plurality of fields ("Tag" | ") spaced by delimiters (vertical lines" | "). The value of the field Tag in the data request instruction information represents the parameters of a specific instruction, and the value of the Tag in the data feedback information is generally specified in advance in the system, for example:

Get page by constant"EXCHANGE"

pageget|ref1|0＝EXCHANGES|1＝all|

Message feeback:

img|ref1|0＝1_20_0|1＝CFFEX|2＝DCE|

end of message flag: DEFIX uses the line break (\ n) as an end marker for each piece of information, which is easy to review and can be easily distinguished during development and operation.

Step S30, sending the generated DEFIX protocol information to a server to obtain corresponding application data.

And sending the generated default protocol information to a server through the data connection relation between the current client and the server according to the currently generated default protocol information so that the server feeds back the corresponding target data application according to the received default protocol information. Further, when the data relationship application between the client and the server is implemented, because the capture application of the related financial data is involved, based on the default protocol data, the related contract communication operation is also presented in the form of a code, and the specific content of the specific contract communication operation can be as follows:

DEFIX communication contract series information:

1. acquiring all exchanges

Get page by constant"EXCHANGE"

pageget|ref1|0＝EXCHANGES|1＝all|

Message feeback:

img|ref1|0＝1_20_0|1＝CFFEX|2＝DCE|

2. Obtaining exchange contract series from 1

pageget|ref2|0＝CFFEX|1＝all|

Message feeback:

img|ref2|0＝1_20_0|1＝CIF|

3. Subscribe all contract series from 2, then find whether the series is futures or options, judge contract type in defix

open|ref3|0＝CIF|1＝all|

Message feeback:

img|ref3|0＝CIF|103＝3|...

4. Two methods to subscribe all contract information from 2

By pageget:

pageget|ref4|0＝CIF|1＝all|

Message feeback:

img|ref4|0＝1_20_0|1＝IF1707|

Subscribe contract:

open|ref5|0＝IF1707|1＝all|

Message feeback:

img|ref5|0＝IF1707|1＝3500|10＝4000|11＝2000|14＝3550|20＝1|21＝3500|41＝3

500.2|100＝CFFEX|102＝CIF|103＝3|104＝300|105＝0.2|107＝0|109＝IF|110＝0|

111＝IF|200＝10|202＝5|

by page:

page|ref6|0＝CIF|1＝all|

Message feeback:

img|ref6_0|0＝IF1707|1＝3500|10＝4000|11＝2000|14＝3550|20＝1|21＝3500|41＝3500.2|100＝CFFEX|102＝CIF|103＝3|104＝300|105＝0.2|107＝0|109＝IF|110＝0|111＝IF|200＝10|202＝5|。

in addition, the DEFIX protocol is generally applied to financial data expression applications, and the change related to financial data also needs to be implemented by the relevant content of the DEFIX protocol information, and the expression of the DEFIX on the fluctuation rate can be as follows:

volatility (vollatity) is hereinafter referred to as: vol, there are three kinds of vol currently stored in DataEngine, bidvol, askvol, vol (referring to implicit fluctuation ratio), and the former two kinds of vol cannot be modified manually.

Wherein the bidvol and the askvol are stored in the market, and the keys are respectively: 80, and 84, only the market of the option contract may contain both keys.

VOL (implicit fluctuation ratio) is stored separately, and its pagename is VOL _ [ undersying ], whose format is: VOL _ [ undercut ] |0 ═ 1 ═ strike 1, VOL1|2 ═ strike 2, VOL2|3 ═ strike 3, and VOL3|.

1) DEFIX subscription/View contract form on dataengine order:

pageset|bu|0＝bu1909|

upd|bu|103＝3|0＝bu|111＝bu|100＝SHFE|

pageset|SHFE|0＝bu|

pageset|EXCHANGES|0＝SHFE|

upd|bu1909|0＝bu1909|100＝SHFE|101＝bu1909|301＝bu|302＝1|200＝30|201＝0|202＝500|203＝1|104＝10|105＝2|106＝20190916|306＝1|204＝0.06|205＝0.06|206＝1|107＝0|303＝0|109＝bu|103＝3|102＝bu|20＝1|111＝bu|

DEFIX subscription/View contract form on dataengine price (market quotation):

upd|HO1905-P-2800|18＝16:02:29900|19＝20190218|0＝HO1905-P-2800|1＝280.6|14＝280.6|12＝280.6|13＝0|2＝|3＝|4＝|6＝0|7＝0|8＝0|5＝280.6|9＝241.8|10＝532.2|11＝29|20＝1|307＝16:02:29 900|21＝|31＝0|41＝|51＝0|

2) DEFIX is looking at the contract form of the queuing state:

pageset|EXCHS_31112480000000032|0＝EXCH_2019021300609757|

pageset|EXCHA_CtpTradeA|0＝EXCH_2019021300609757|

img|EXCH_2019021300609757|401＝31112480000000032|402＝2019021300609757|452＝0|453＝|474＝2019-02-13 11:21:43.000|17＝2019-02-1300:00:00.000|404＝CTP|100＝CZCE|405＝CtpTradeA|0＝SR909|406＝1|407＝5091|408＝1|409＝2|410＝0|412＝0|413＝0|414＝0|20＝3|

3) DEFIX is in the form of a contract that looks at the status of a deal that has been returned from the exchange:

pageset|TRADES_2019021300609757|0＝TRADE_B2019021300044488|

pageset|TRADEA_CtpTradeA|0＝TRADE_B2019021300044488|

img|TRADE_B2019021300044488|402＝2019021300609757|403＝B2019021300044488|17＝2019-02-1313:35:21.000|404＝CTP|100＝CZCE|405＝CtpTradeA|0＝SR909|406＝1|407＝5091|408＝1|409＝2|20＝5|

pageset|EXCHS_31112480000000031|0＝EXCH_2019021300589204|

pageset|EXCHA_CtpTradeA|0＝EXCH_2019021300589204|

img|EXCH_2019021300589204|401＝31112480000000031|402＝2019021300589204|451＝5092|450＝1|452＝0|453＝|474＝2019-02-13

11:12:34.000|17＝2019-02-13

00:00:00.000|404＝CTP|100＝CZCE|405＝CtpTradeA|0＝SR909|406＝1|407＝5092|408＝1|409＝2|410＝0|412＝0|413＝0|414＝0|20＝5|

4) DEFIX is in the form of a contract that looks at the state of the contract order withdrawn by OMS:

pageset|EXCHS_30901220000000001|0＝EXCH_2019021300002622|

pageset|EXCHA_CtpTradeA|0＝EXCH_2019021300002622|

img|EXCH_2019021300002622|401＝30901220000000001|402＝2019021300002622|452＝0|453＝|474＝2019-02-1309:01:09.000|17＝2019-02-13

00:00:00.000|404＝CTP|100＝CZCE|405＝CtpTradeA|0＝SR907|406＝1|407＝5068|408＝1|409＝2|410＝0|412＝0|413＝0|414＝0|20＝4

the DEFIX protocol format created in this embodiment makes the internal structure of the DEFIX protocol simpler, and does not need to encrypt a header, simplifies the acquisition form, does not need to check a header command again, does not need to log in/log out, and has a simpler syntax. A Key corresponding to the form of the header title is used for expressing, a header command does not need to be verified, most of numerical value generation configuration files of the Key are applied and stored to the local, login/logout is not needed, the speed of the protocol is improved, important information is displayed more visually, and the application efficiency of the DEFIX protocol is improved.

Further, referring to fig. 4, fig. 4 is a schematic flowchart of a second embodiment of the method for generating a DEFIX protocol according to the present invention, and based on the first embodiment shown in fig. 3, the method for generating a DEFIX protocol further includes:

step S40, sending a data connection request to the server;

in step S50, a data connection channel with the server is created when a confirmation instruction returned by the server is received.

In this embodiment, according to the data usage of the current client, it is necessary to obtain related application data from a server, that is, it is necessary to create a data connection relationship with a corresponding server, and send a data connection request to the server, where the server is a data storage area based on the data usage of the client, and the server and the client have a corresponding data structure relationship. The method comprises the steps of receiving a confirmation instruction returned by a server after a data connection request sent by a client to the server is received, wherein the confirmation instruction is triggered by the server based on the data connection request sent by the client, verifying the user information of the client when the server returns the confirmation instruction, and returning the confirmation instruction to the client when the user information of the client is confirmed to be correct. The method comprises the following steps of creating a data connection channel with a server according to a confirmation instruction returned by the current server, deploying a defix protocol information generation format based on the created data connection channel to realize the generation of the current defix protocol information and send a requirement for realizing data acquisition, namely, the step of creating the data connection channel with the server when receiving the confirmation instruction returned by the server comprises the following steps:

Referring to fig. 5, fig. 5 is a schematic flow chart of a first embodiment of a DEFIX protocol parsing method according to the present invention, where the DEFIX protocol parsing method further includes:

step S60, receiving DEFIX protocol information sent by a client, and reading a header of the DEFIX protocol information to confirm an information type of the DEFIX protocol information;

the server stores and maintains all data, the data is data based on a client data application, in the server, a piece of data information is marked by 'symbol', each symbol data is a set of a plurality of fields (Tag ═ Value), when in application, a page (group) is used for representing the set of the plurality of symbols, and corresponding instruction acquisition and setting of the data can be defined based on the page group, namely, the page group can also comprise instruction information based on the data acquisition and setting. Based on the above contents, receiving the defix protocol information sent by the client, and according to the received defix protocol information, confirming the information type of the defix protocol information by using the information header of the defix protocol information, where the information type is the operation type based on data in the defix protocol information, and includes but is not limited to data-based operation contents such as data acquisition, update, editing, deletion, and revocation.

Step S70, confirming target data of the DEFIX protocol information, and integrating feedback data with the information type and the target data;

when the information type of the received DEFIX protocol information is confirmed, target data based on the DEFIX protocol information, namely corresponding operation data based on the DEFIX protocol information is confirmed, because the information parameters of the DEFIX protocol information comprise information types, operation data and information contents, and when the information type of the DEFIX protocol information is realized, different data integration steps are provided according to different information types, namely operation types based on data operation, data of a server, feedback data required by a client are integrated according to the information types and the target data, and in practical application, the content of the feedback data is integrated as follows, namely the step of confirming the target data of the DEFIX protocol information and integrating the feedback data according to the information types and the target data, the method comprises the following steps:

According to the type of the received defix protocol information, corresponding target data can be determined by reading an information target and an information text field of the defix protocol information, and an integration operation based on the type of the information and the target data is related to a corresponding processing step of the type of the information, wherein the specific operation steps of classifying and integrating feedback data based on the information of the defix protocol information are as follows:

1. a data update instruction:

1) command format: acute toxicity is acute in the early stage of acute toxicity syndrome > < key1> < value1> < key2> < value2> |

And (3) response flow: searching a corresponding smybol data object according to the name, and if the smybol data object does not exist, establishing a symbol object; and emptying the hash table of the storage content of the symbol object, and then sequentially inserting the tag-value values in the img command into the hash table.

2) Command format: uk, (upd | < symbol > | < key1> < value1> | < key2> < value2> |

And (3) response flow: searching a corresponding smybol data object according to the name, and if the smybol data object does not exist, establishing a symbol object; and updating the corresponding values of the Tag-Value values in the upd command according to the key values in sequence, and if the values do not exist, newly building an insert.

3) Command format: legesit | < pageName > |0 ═ symbol1> |1 ═ symbol2 |.

And (3) response flow: searching a corresponding page data object according to the name, and if the corresponding page data object does not exist, establishing a new page object; the hash table of the memory content of the symbol object is cleared, and then symbols to be added (starting from field 0) in the pageset command are added to the page object in sequence.

2. Data request instruction

And when the data command is confirmed to be the request command according to the received default protocol information, judging whether to send photo information of symbol/page and whether to associate the current connection with the corresponding subscription object according to the type of the request command and the type of the mode, wherein the specific process is shown in a request command response flow chart.

1) Command format: open | < handle > |0 ═ symbol > |1 ═ mode > <

In the open command format, an open instruction is used to request to obtain data specifying symbol, handle represents a client request id, symbol represents a requested data name, mode represents a request type, and a value may be: img, upd, all; img represents that photo information is requested only once, upd represents that subsequent updating information under the symbol is requested, and when the symbol data is updated, the server pushes data to the client side through the current connection to improve the performance of the client side; all indicates that img and upd are requested simultaneously.

2) Command format: page | < handle > |0 ═ pageName > |1 ═ mode > -gaming

In the page command format, a page command is used to request data specifying all symbols under a page. The pageName indicates the name of the requested page (group), and the meanings of handle and mode are consistent with the open instruction.

3) Command format: close | < handle > -ventilated hole

In the close command format, the close command closes the request subscription command previously associated with a handle by specifying the handle name.

4) Command format: pageget | < handle > |0 ═ pageName > |100 ═ pageNum > gaming

In the pageget command format, after receiving a pageget command, the server parses out a page name (pageName) and a lookup page number (pageNum), then looks up all symbol names of the specified pageName in the pageNum with the page number in the page data, and sends the page names in a specific format combination. The data format returned to the client after the server receives the instruction is as follows:

total number of symbols contained in total symbol count page

symbol CountPerNum the number of symbols contained per page

pageNum is the current page;

nextPageNum: next page (if the current page is the last page, there is no item in the returned data)

Step S80, returning the integrated feedback data to the client application.

And returning the feedback data to a value client for application according to the feedback data integrated by the currently read defix protocol information, wherein the client is a data end for sending the defix protocol information to the server, and the integrated feedback data is returned by taking the identification of the client as a reference under the general condition so that the client performs data application based on the feedback data.

In the embodiment, the corresponding defix protocol generation format is set according to the current data connection relation with the client, the defix protocol information is analyzed and data are fed back in the safety data connection with the client, and the internal structure of the defix protocol generation format is simple, so that the analysis speed of the defix protocol information is increased, and the data interaction efficiency with the client is further improved.

Referring to fig. 6, fig. 6 is a flowchart illustrating a second embodiment of a DEFIX protocol parsing method according to the present invention, based on the first embodiment shown in fig. 5, the DEFIX protocol parsing method further includes:

step S90, when receiving a data connection request of a client, returning a confirmation instruction to the client;

and step S100, establishing a data connection relation with the client according to the data connection channel established by the client.

In this embodiment, a data connection request of a client is received based on a current data storage premise, where the client is a user application program that has a data application requirement of currently stored data, and a data application structure of the user application program is consistent with a currently stored data structure, so that when the data connection request of the client is received, user information based on the client in the data connection request is verified, where the user information is currently registered user information with a data application authority, and when it is confirmed that the user information of the client is correct, a confirmation instruction is returned to the client, so that the client creates a data connection relationship with a server, and the client further deploys a defix protocol generation format based on the data connection relationship, and the application based on the server has a corresponding defix protocol parsing scheme, and the method is used for analyzing the defix protocol information sent by the client to realize the data application interaction with the client.

Further, the present invention also provides a DEFIX protocol generating system, which when executed implements the contents of the embodiments of the DEFIX protocol generating method described above and the DEFIX protocol parsing method described above.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or system. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or system that comprises the element.

The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.

Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner. Based on such understanding, the technical solution of the present invention may be substantially or partially embodied in the form of a software product, which is stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) as described above and includes instructions for enabling a terminal device (e.g. a mobile phone, a computer, a server, an air conditioner, or a network device) to analyze the method according to the embodiments of the present invention.

The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. A DEFIX protocol generation method, comprising:

receiving data application demand information, and confirming the information type of the data application demand information, wherein the information type comprises any one or more of data acquisition, data updating and data closing operation;

analyzing the data application demand information, and confirming and generating information parameters of the DEFIX protocol information according to an analysis result, wherein the information parameters comprise information types, operation data and information contents, the information types comprise instruction information and data feedback information, and the instruction information comprises a data request instruction and a data updating instruction;

adding the parsed information parameter to a preset DEFIX protocol generation format to generate DEFIX protocol information, wherein the DEFIX protocol information comprises an information header, an information target, an information body field and an information end mark, the information target comprises a handle identifier, and the information end mark comprises a DEFIX use line break (\ n) as an end mark of each piece of information;

sending the generated DEFIX protocol information to a server to acquire corresponding application data;

the method further comprises the following steps:

sending a data connection request to a server;

2. A method for resolving a DEFIX protocol, the method for generating the DEFIX protocol comprising the steps of:

returning the integrated feedback data to the client application.

3. The DEFIX protocol parsing method of claim 2, wherein the step of validating target data of the DEFIX protocol information and integrating feedback data with the information type and the target data comprises:

4. The DEFIX protocol parsing method of claim 3, wherein the method further comprises:

5. A client, the client comprising: a memory, a processor, and a DEFIX protocol generation program stored on the memory and operable on the processor, the DEFIX protocol generation program, when interpreted by the processor, implementing the steps of the DEFIX protocol generation method of claim 1.

6. A server, characterized in that the server comprises: a memory, a processor, and a DEFIX protocol parser stored on the memory and operable on the processor, the DEFIX protocol parser, when parsed by the processor, implementing the steps of the DEFIX protocol parsing method of any of claims 2-4.

7. A DEFIX protocol generation system, comprising the client of claim 5 and the server of claim 6.