A message processing method, system and storage medium

Abstract

The present invention discloses a message processing method, system and storage medium, the message processing method comprising: the front end sends a request message to the back end server; the back end server returns a response message to the front end, the response message is encapsulated in a HashtableMsg manner; the front end receives the response message, and parses all fields in the message by a parsing method of the ArrayListMsg type; the field content to be displayed is retained by a screening method and the field content is displayed to the front end user. The present invention encapsulates and parses multi-layer separator mode messages by using the data structures of ArrayListMsg and HashtableMsg, so that the parsing work does not need to be decomposed layer by layer, reducing the parsing workload of the coder; the message transmission steps are simplified, and it is convenient to add or reduce fields in the future.

Description

Technical Field

[0001] The present invention relates to the field of computer communications, and in particular to a message processing method, system and storage medium. Background Art

[0002] At present, when applications interact with each other, messages are assembled and parsed in a specific format agreed upon by both parties, and the application service interface is responsible for formulating the specific message assembly rules. In the process of message formulation, commas, equal signs, pound signs, and other symbols are often used as delimiters to distinguish string streams of different segments. After obtaining the required string stream according to the delimiter, it is necessary to determine the actual object type according to the specific type, such as string, encapsulated object, array, linked list, or key-value set, which brings difficulties to parsing, especially linked lists and key-value combinations.

[0003] Normally, a common list structure (such as ArrayList) is used to parse linked list data. For key-value collection data, the list must be parsed based on the nesting first, and then the common map structure (such as HashMap, Hashtable) is used to parse the key-value data. For the parsing of multi-layer nested linked lists, it is also necessary to recursively parse the layers one by one according to the specific nesting rules. It is necessary to know the assembly process of the entire message, and the encoding complexity is extremely high. For the parsing of key-value collections, in addition to knowing the names of the fields, it is necessary to care about the order of the fields. When adding or reducing fields during future expansion, it will be interfered by other fields, making the encoding extremely difficult to maintain.

[0004] Therefore, the prior art has the following problems:

[0005] 1. The parsing of the message requires layer-by-layer decomposition of the nested content, and the parsing process is too complicated;

[0006] 2. If the message adopts the key-value format, it becomes difficult to add or remove fields in the message in the future.

[0007] In order to solve the above problems, it is necessary to provide a message processing method, system and storage medium. Summary of the invention

[0008] The present invention discloses a message processing method, comprising:

[0009] The front end sends a request message to the back end server;

[0010] The backend server returns a response message to the frontend, and the response message is encapsulated in HashtableMsg mode;

[0011] The front end receives the response message and parses all fields in the message through the parsing method of the ArrayListMsg type;

[0012] The field contents to be displayed are retained by the screening method and displayed to the front-end user.

[0013] Furthermore, the response message is encapsulated in a HashtableMsg manner and includes:

[0014] The response message is encapsulated into two layers, the first layer is the field name description layer, and the second layer is the single record layer; the first layer and the second layer are separated by a first-level separator, the field names in the first layer are separated by a second-level separator, and the single records in the second layer are separated by a second-level separator.

[0015] Furthermore, the parsing method of the ArrayListMsg type to parse all fields in the message includes:

[0016] Determine the first delimiter and the last delimiter of the response message;

[0017] Determine the position of the first level delimiter in the field content between the first delimiter and the last delimiter;

[0018] Determine the position of the secondary delimiters in the field content between the first delimiter and the last delimiter;

[0019] Extracting the field contents between a plurality of second-level delimiters in the first two first-level delimiters of the response message as field names;

[0020] The field contents between several second-level delimiters in two first-level delimiters after the response message are extracted as a single record value.

[0021] Preferably, the screening method includes: receiving a query field value input by a user, matching the query field value with the field name of a response message one by one, and if they match, using the field name as a column name and displaying the single record under the field name in separate lines; if they do not match, returning an error prompt.

[0022] Preferably, the screening method includes: receiving a numerical value input by a user, matching the numerical value with a single record numerical value of a response message one by one, and if there is a match, using the field name corresponding to the single record numerical value as a column name, and displaying the single record separately; if there is no match, returning an error prompt.

[0023] On the other hand, the present invention provides a message processing system, including: a front end, a back end server, a HashtableMsg module, an ArrayListMsg module and a screening module;

[0024] The front end sends a request message to the back end server and receives an encapsulated response message;

[0025] The HashtableMsg module encapsulates the response message of the backend server;

[0026] The ArrayListMsg module parses all fields in the message;

[0027] The screening module retains the field content to be displayed and displays the field content to the front-end user.

[0028] Furthermore, the message processing system also includes a timestamp module. After receiving the request message sent by the front end, the background server calls the timestamp module to judge the validity of the request message through a time verification method. If the request message is valid, the message is sent to the HashtableMsg module; if it is invalid, the message is discarded.

[0029] Furthermore, the time verification method includes:

[0030] Extract the message identification number and time field of the request message;

[0031] Determine whether the generation time of the message identification number is earlier than a preset threshold value. If it is earlier than the preset value, the verification result of the request message is invalid;

[0032] The size relationship between the first timestamp and the second timestamp in the time field is determined. If the first timestamp is greater than the second timestamp, the request message is valid, otherwise it is invalid.

[0033] The system also includes a client, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and the processor implements the steps of the above method when executing the computer program.

[0034] The present invention also includes a computer-readable storage medium, which stores a computer program and is applied to a client. When the computer program is executed by a processor, the steps of the above method are implemented.

[0035] It can be seen from the above technical solution that the present invention has at least the following advantages and positive effects:

[0036] 1. The multi-layer separator mode message is encapsulated by using the ArrayListMsg data structure. The encapsulation uses the first-level separator and the second-level separator. When parsing, only the first-level and second-level separators need to be located, so that the parsing work does not need to be decomposed layer by layer, reducing the parsing workload of the coder.

[0037] 2. By adopting the custom type HasgtableMsg, the repeated combination of the first-level separator and the second-level separator makes it possible to assemble fields without redundant escape characters, thereby simplifying the message transmission steps, eliminating the need for coders to know the order of the fields, and facilitating the addition and removal of fields in the future. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for describing the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative work, among which:

[0039] Figure 1 It is a flowchart of a message processing method provided by an embodiment of the present invention;

[0040] Figure 2 It is a flow chart of the HashtableMsg message parsing method provided by the present invention;

[0041] Figure 3 It is a schematic diagram of the structure of ArrayListMsg provided by the present invention;

[0042] Figure 4 is a flow chart of a time validity verification method provided by another embodiment of the present invention;

[0043] Figure 5 is a structural diagram of a message processing system provided by another embodiment of the present invention;

[0044] Figure 6 It is a schematic diagram of a multi-layer separator mode message provided by the present invention;

[0045] Figure 7 This is an example diagram of the HashtableMsg message provided by the present invention. DETAILED DESCRIPTION

[0046] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0047] Embodiment 1

[0048] Figure 1A flowchart of a message processing method provided by an embodiment of the present invention. The method comprises the following steps:

[0049] S1: The front end sends a request message to the back end server;

[0050] S2: The backend server returns a response message to the frontend, and the response message is encapsulated in HashtableMsg mode;

[0051] S3: The front end receives the response message and parses all fields in the message through the parsing method of the ArrayListMsg type;

[0052] S4: retaining the field contents to be displayed through a screening method and displaying the field contents to a front-end user.

[0053] Users query data through client terminals, and the displayed content needs to be adjusted in a timely manner according to the user's ideas.

[0054] After the front-end inputs the query conditions, it assembles the request message and sends it to the back-end service. After the back-end service performs logical processing based on the received request, it encapsulates all the query result sets using the HashtableMsg method. The fields transmitted from the back-end to the front-end here are all the data fields loaded and responded to the front-end.

[0055] After receiving the response message, the front end parses the message content according to HashtableMsg and parses all the fields. Then, it filters according to the content checked in the user-defined "Table Field Display Settings", obtains the display value of the corresponding column according to the corresponding FieldName, and directly ignores other unnecessary FieldNames. This ensures the personalized needs of all customers and the normal operation of the system functions.

[0056] Specifically, the HashtableMsg method of encapsulation includes: dividing the response message into two layers for encapsulation, the first layer is the field name description layer, and the second layer is the single record layer; the first layer and the second layer are separated by a first-level separator, the field names in the first layer are separated by a second-level separator, and the single records in the second layer are separated by a second-level separator.

[0057] Further, the message is parsed according to HashtableMsg as follows Figure 2 As shown, including:

[0058] S20: Determine the first delimiter and the last delimiter of the response message;

[0059] S21: determining the position of the first level delimiter in the field content between the first delimiter and the last delimiter;

[0060] S22: determining the position of the secondary delimiter in the field content between the first delimiter and the last delimiter;

[0061] S23: extracting the field contents between a plurality of second-level delimiters in the first two first-level delimiters of the response message as field names;

[0062] S24: extracting the field contents between several second-level delimiters in the two first-level delimiters after the response message as a single record value.

[0063] Preferably, retaining the displayed field content by the screening method and displaying the field content to the front-end user comprises:

[0064] Receive the query field value input by the user, match the query field value with the field name of the response message one by one, if they match, use the field name as the column name, and display the single record under the field name in separate lines; if they do not match, return an error prompt;

[0065] Receive the value entered by the user, and match the value with the single record value of the response message one by one. If they match, use the field name corresponding to the single record value as the column name and display the single record separately; if they do not match, return an error prompt.

[0066] Furthermore, if Figure 3 As shown, the ArrayListMsgArrayListMsg described in step S3 inherits from the custom type of ArrayList, and is a custom collection type separated by a multi-layer separator pattern. The collection can include the String type or the ArrayListMsg type itself, but can only include one type at the same time. If the String type is included, it means that the layer is already the last layer. If the ArrayListMsg type is included, it means that there is a next layer structure.

[0067] ArrayListMsg is mainly used to encapsulate multi-layer separator mode messages, so that developers can use the collection method to process them during use without having to consider the message parsing process. When ArrayListMsg is serialized, it automatically generates the corresponding string format according to the rules and transmits it on the network. After the other party receives the string, the parsing function provided by the ArrayListMsg type can be used to generate an ArrayListMsg object to achieve deserialization, simplifying the coding difficulty for developers and increasing the flexibility of the system.

[0068] Furthermore, the HashtableMsg described in step S2 is similar to the ResultSet of JDBC, which is a two-dimensional table. The entire message is divided into two parts, the first part represents the field name, and the second part uses a two-layer separator pattern to represent the field values ​​of multiple records. The order of each field corresponds to the field name one by one. Since the message can be parsed to generate a Hashtable array, it is named HashtableMsg. When using the HashtableMsg type for message transmission, the coder does not need to worry about the order of the fields, as long as he knows the name of the field. When adding or reducing fields during future expansion, other fields can be undisturbed.

[0069] Embodiment 2

[0070] Figure 4 A flowchart of a time validity verification method provided by an embodiment of the present invention. The method comprises the following steps:

[0071] S30: extracting the message identification number and time field of the request message;

[0072] S31: determining whether the generation time of the message identification number is earlier than a preset threshold value, if earlier than the preset value, the verification result of the request message is invalid;

[0073] S32: Determine the size relationship between the first timestamp and the second timestamp in the time field. If the first timestamp is greater than the second timestamp, the request message is valid; otherwise, it is invalid.

[0074] The judgment of whether the generation time of the message identification number is earlier than the preset threshold value is firstly to store the message identification number of the request message in correspondence with the time field, and to judge whether the storage parameters of the stored message identification number meet the preset storage conditions when storing; if not, the stored message identification number is cleaned up based on the preset storage conditions. In practical applications, due to the limited storage space during use and the increase of cache, the processing speed may be reduced. Therefore, by setting the preset storage conditions, it is judged whether the storage parameters of the message identification number stored by the client meet the preset storage conditions. When it meets the preset storage conditions, the message identification number is stored at the user end. When it does not meet the preset storage conditions, the stored message identification number is cleaned up so that the stored message identification number meets the preset storage conditions to avoid memory overflow due to excessive data volume.

[0075] Further, the storage parameters include storage quantity and storage duration, and the determination of whether the storage parameters of the stored message identity identification number meet the preset storage conditions includes:

[0076] It is determined whether the number of stored message identity identification numbers is greater than a preset threshold, and / or it is determined whether the storage duration of the stored message identity identification numbers exceeds a preset duration.

[0077] Among them, the storage parameters and the preset storage conditions can be set according to the actual situation. For example, the storage parameters may include the storage quantity and the storage duration, and the corresponding preset storage conditions can be set to store data not greater than the preset threshold, and the storage duration not exceeding the preset duration. Based on this, when judging whether the storage parameters of the stored message identity identification number meet the preset storage conditions, it can be judged whether the storage quantity of the stored message identity identification number is greater than the preset threshold. If it is greater, it is determined that it is not satisfied, and the message identification needs to be cleaned up. If it is less than, it is determined that it is satisfied and it is directly stored in the cache. Alternatively, it can also be judged whether the storage duration of the stored message identity identification number exceeds the preset duration. If it is greater, it is determined that it is not satisfied, and the message identification needs to be cleaned up. If it is less than, it is determined that it is satisfied and it is directly stored in the cache. Among them, the preset threshold can be but not limited to 7500, and the preset duration can be but not limited to 8 minutes.

[0078] Furthermore, the timestamp uses data generated by digital signature technology, and the object of the signature includes information such as the original file information, signature parameters, and signature time. The timestamp system is used to generate and manage timestamps, and digitally sign the signature object to generate a timestamp to prove that the original file existed before the signature time. The timestamp is a complete and verifiable data that can indicate that a piece of data already existed at a specific time point. It is mainly proposed to provide users with an electronic evidence to prove the generation time of certain data of the user. In practical applications, it can be used in various aspects including e-commerce and financial activities, and can especially be used to support the "non-repudiation" service of the public key infrastructure. The essence of the timestamp service is to bind the user's data to the current accurate time, and on this basis, use the digital certificate of the timestamp to sign, and rely on the legally authoritative status of the timestamp to generate a timestamp that can be used as legal evidence to prove the generation time of the user data, so as to achieve the goal of "non-repudiation" or "non-repudiation". The composition of the timestamp mainly includes three parts: a trusted time source, a signature system, and a timestamp database. The main purpose of the timestamp is to authenticate the time when the data is generated through certain technical means. The first timestamp of the timestamp is the message timestamp, and the second timestamp is the processing timestamp. Then, the size relationship between the first timestamp and the second timestamp is determined, and the message to be processed is discarded or consumed. By setting a size comparison mechanism, messages can be processed quickly, avoiding a large backlog of messages.

[0079] In actual applications, the pending message data is discarded or followed up based on the size relationship between the first timestamp and the second timestamp, including: if the first timestamp is smaller than the second timestamp, the pending message data is discarded; if the first timestamp is greater than or equal to the second timestamp, the pending message content corresponding to the message identification number is obtained from the data platform, and the pending message content is followed up.

[0080] On the other hand, since the timestamps are generated by the timestamp service and are in an incremental form, the first timestamp and the second timestamp can be compared. If the first timestamp is smaller than the second timestamp, it means that the message data to be processed has been processed before, so it is discarded and not processed, avoiding repeated processing of the message data to be processed, thereby improving the processing efficiency of the user end. If the first timestamp is larger than the second timestamp, it means that the processed message data has been updated and needs to be processed again. Therefore, the client needs to obtain the content of the message to be processed corresponding to the message identification number from the data platform and further process the content of the message to be processed.

[0081] Embodiment 3

[0082] Figure 5 The structural diagram of a message processing system provided by another embodiment of the present invention includes a front end 100, a backend server 200, a HashtableMsg module 300, an ArrayListMsg module 400 and a screening module 500.

[0083] The front end 100 sends a request message to the backend server 200 and receives an encapsulated response message;

[0084] The request message adopts a data structure of ArrayListMsg type. The ArrayListMsg type is a custom type inherited from ArrayList. It is a custom collection type separated by a multi-layer separator pattern. The collection can include String type or ArrayListMsg type itself, but only one type can be included at the same time. If String type is included, it means that this layer is already the last layer. If ArrayListMsg type is included, it means that there is a next layer structure.

[0085] like Figure 6As shown, ArrayListMsg mainly encapsulates multi-layer separator mode messages, allowing developers to process them in a collection manner during use without having to consider the message parsing process. When ArrayListMsg is serialized, it automatically generates the corresponding string format according to the rules and transmits it on the network. After the other party receives the string, it can use the parsing function provided by the ArrayListMsg type to generate an ArrayListMsg object to achieve deserialization, simplifying the coding difficulty of developers and increasing the flexibility of the system.

[0086] like Figure 7 As shown, HashtableMsg is similar to JDBC ResultSet, which is a two-dimensional table. The entire message is divided into two parts. The first part represents the field name, and the second part uses a two-layer separator mode to represent the field values ​​of multiple records. The order of each field corresponds to the field name one by one.

[0087] Since the message can be parsed to generate a Hashtable array, it is named HashtableMsg. When using the HashtableMsg type for message transmission, the coder does not need to worry about the order of the fields, as long as he knows the name of the field. When adding or reducing fields in the future expansion, other fields will not be disturbed.

[0088] The HashtableMsg module 300 encapsulates the response message of the background server 200; the response message is encapsulated in the HashtableMsg method, including: the HashtableMsg method divides the response message into two layers for encapsulation, the first layer is the field name description layer, and the second layer is the single record layer; the first layer and the second layer are separated by a first-level separator, the field names in the first layer are separated by a second-level separator, and the single records in the second layer are separated by a second-level separator.

[0089] The ArrayListMsg module 400 parses all fields in the message; further, the ArrayListMsg module 400 parses through a parsing method, the parsing method including: determining the first delimiter and the last delimiter of the response message; determining the position of the first-level delimiter in the field content between the first delimiter and the last delimiter; determining the position of the second-level delimiter in the field content between the first delimiter and the last delimiter; extracting the field content between several second-level delimiters in the first two first-level delimiters of the response message as the field name; extracting the field content between several second-level delimiters in the last two first-level delimiters of the response message as the value of a single record.

[0090] The screening module 500 retains the displayed field content through a screening method and displays the field content to the front-end user. Preferably, the screening method includes: receiving the query field value input by the user, matching the query field value with the field name of the response message one by one, if it matches, using the field name as the column name, and displaying the single record under the field name in separate lines; if it does not match, returning an error prompt. The screening method can also be: receiving the numerical value input by the user, matching the numerical value with the numerical value of a single record in the response message one by one, if it matches, using the field name corresponding to the numerical value of the single record as the column name, and displaying the single record separately; if it does not match, returning an error prompt.

[0091] Furthermore, the present invention also includes a client, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program;

[0092] Furthermore, the present invention also includes a computer-readable storage medium, which stores a computer program and is applied to a client, and the computer program implements the steps of the above method when executed by a processor.

[0093] The above descriptions are merely embodiments of the present invention and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

Claims

1. A message processing method, characterized in that: The method comprises: The front end sends a request message to the back end server; The backend server returns a response message to the frontend, and the response message is encapsulated in HashtableMsg mode; The front end receives the response message and parses all fields in the message through the parsing method of the ArrayListMsg type; Retain the displayed field contents through the screening method and display the field contents to the front-end user; The response message is encapsulated in a HashtableMg manner, including encapsulating the response message in two layers, the first layer being a field name description layer, and the second layer being a single record layer; the first layer and the second layer are separated by a primary separator, the field names in the first layer are separated by a secondary separator, and the single records in the second layer are separated by a secondary separator; The parsing method comprises: determining a first delimiter and a last delimiter of a response message; Determine the position of the first level delimiter in the field content between the first delimiter and the last delimiter; Determine the position of the secondary delimiters in the field content between the first delimiter and the last delimiter; Extracting the field contents between a plurality of second-level delimiters in the first two first-level delimiters of the response message as field names; The field contents between several second-level delimiters in the two first-level delimiters after the response message are extracted as a single record value.

2. The method according to claim 1, characterized in that: The screening method includes receiving a query field value input by a user, matching the query field value with the field name of the response message one by one, and if there is a match, using the field name as a column name and displaying the single record under the field name in separate lines; if there is no match, returning an error prompt.

3. The method according to claim 2, characterized in that The screening method also includes receiving a numerical value input by a user, matching the numerical value with a single record numerical value of a response message one by one, and if there is a match, using the field name corresponding to the single record numerical value as a column name, and displaying the single record separately; if there is no match, returning an error prompt.

4. A message processing system, characterized in that: The message processing system includes a front-end, a back-end server, a HashtableMsg module, an ArrayListMsg module and a screening module; The front end sends a request message to the back end server and receives an encapsulated response message; The HashtableMsg module encapsulates the response message of the backend server; The ArrayListMsg module parses all fields in the message; The screening module retains the field content to be displayed and displays the field content to the front-end user; The encapsulation of the HashtableMsg module includes encapsulating the response message into two layers, the first layer is a field name description layer, and the second layer is a single record layer; the first layer and the second layer are separated by a first-level separator, the field names in the first layer are separated by a second-level separator, and the single records in the second layer are separated by a second-level separator; The ArrayListMsg module is parsed by a parsing method, the parsing method comprising: determining the first delimiter and the last delimiter of the response message; determining the position of the first delimiter in the field content between the first delimiter and the last delimiter; determining Determine the position of the secondary delimiter in the field content between the first delimiter and the last delimiter; extract the field content between several secondary delimiters in the first two primary delimiters of the response message as the field name; extract the field content between several secondary delimiters in the last two primary delimiters of the response message as the single record value.

5. The system according to claim 4, characterized in that The message processing system also includes a timestamp module. After receiving the request message sent by the front end, the background server calls the timestamp module to judge the validity of the request message through a time verification method. If the request message is valid, the message is sent to the HashtableMsg module. If it is invalid, the message is discarded.

6. The system according to claim 5, characterized in that The time validity verification method comprises: extracting a message identification number and a time field of a request message; Determine whether the generation time of the message identification number is earlier than a preset threshold value, if it is earlier than the preset threshold value, the verification result of the request message is invalid; The size relationship between the first timestamp and the second timestamp in the time field is determined. If the first timestamp is greater than the second timestamp, the request message is valid, otherwise it is invalid.

7. A client comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 3 are implemented.

8. A computer-readable storage medium storing a computer program and applied to a client, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 3 are implemented.

Images