WO2023273218A1

WO2023273218A1 - Json packet checking method and json packet checking apparatus

Info

Publication number: WO2023273218A1
Application number: PCT/CN2021/139563
Authority: WO
Inventors: 夏柱昌; 夏勇
Original assignee: 深圳前海微众银行股份有限公司
Priority date: 2021-06-30
Filing date: 2021-12-20
Publication date: 2023-01-05
Also published as: CN113489593A; CN113489593B

Abstract

The present application relates to the technical field of financial technology (Fintech), and discloses a JSON packet checking method and a JSON packet checking apparatus. The method comprises: acquiring a JSON packet to be checked and a preset packet checking rule, wherein the packet checking rule is obtained by configuring on the basis of the JSON packet to be checked; converting a first source packet in the JSON packet to be checked into a second source packet of a Map data structure, and converting a first target packet in the JSON packet to be checked into a second target packet of the Map data structure; if a MD5 value of the second source packet is inconsistent with a MD5 value of the second target packet after comparison, determining a source Value from the second source packet according to the packet checking rule, and determining a target Value from the second target packet according to the packet checking rule; and performing checking according to the source Value and the target Value to obtain a packet checking result of the JSON packet to be checked.

Description

Method for checking JSON message and device for checking JSON message

priority information

This application claims the priority of the Chinese patent application with application number 202110746878.X filed on June 30, 2021, the entire contents of which are incorporated in this application by reference.

technical field

This application relates to the technical field of financial technology (Fintech), in particular to a method for checking JSON messages and a device for checking JSON messages.

Background technique

With the development of computer technology, more and more technologies (big data, distributed, blockchain, artificial intelligence, etc.) The industry's security and real-time requirements also put forward higher requirements for the consistency check technology of JSON messages.

Nowadays, Json (Java Script Object Notation, JS object notation, a lightweight data exchange format, JS is called Java Script, which is a programming language) messages are used in scenarios such as API interface and front-end and back-end message transmission. All of them have a very wide range of applications, especially for Java (an object-oriented programming language) application development and data testing, check whether the JSON messages before and after the interface change are consistent, and whether the JSON messages of the same data source are processed by multiple parties Whether the returned data is consistent, etc., are all necessary and frequent operations.

The currently commonly used JSON message checking method is to use tools such as Beyond Compare (a text file comparison tool) or based on a simple Json open source package to compare data consistency. However, these checking methods cannot implement data consistency checks in situations where the data nesting level of the JSON message itself is deep, fields change, or there is an unsorted data list in the JSON message, resulting in low efficiency of the JSON message consistency check.

Contents of the invention

The main purpose of this application is to propose a JSON message checking method and a JSON message checking device, aiming at solving the existing technical problem of low checking efficiency for JSON message consistency checking.

In order to achieve the above object, the application provides a checking method of a JSON message, and the checking method of the JSON message includes the following steps:

Obtaining the JSON message to be checked and a preset message checking rule, wherein the message checking rule is configured based on the JSON message to be checked;

Converting the first source message in the JSON message to be checked into the second source message of the Map data structure, and converting the first target message in the JSON message to be checked into the first source message of the Map data structure Two target messages;

If the comparison shows that the MD5 values of the second source message and the second target message are inconsistent, then determine the source Value value from the second source message according to the message check rule, and according to the Determine the target Value value from the second target message according to the message checking rule;

Checking is performed according to the source Value and the target Value to obtain a message checking result of the to-be-checked JSON message.

In addition, in order to achieve the above object, the present application also provides a JSON message checking device, the JSON message checking device includes:

A message check preparation module, configured to obtain a JSON message to be checked and a preset message check rule, wherein the message check rule is configured based on the JSON message to be checked;

A message conversion module, configured to convert the first source message in the JSON message to be checked into the second source message of the Map data structure, and convert the first target message in the JSON message to be checked Be converted into the second target message of Map data structure;

A Value determination module, configured to determine the source Value from the second source message according to the message checking rules if the MD5 values of the second source message and the second target message are inconsistent after comparison value, and determine the target Value value from the second target message according to the message checking rule;

A checking module, configured to check according to the source Value and the target Value to obtain a message checking result of the to-be-checked JSON message.

Wherein, each functional module of the device for checking JSON messages in the present application implements the steps of the checking method for JSON messages as described above during operation.

In addition, in order to achieve the above object, the present application also provides a terminal device, which includes: a memory, a processor, and a check program for JSON messages stored on the memory and operable on the processor, When the checking program of the JSON message is executed by the processor, the above-mentioned steps of the checking method of the JSON message are realized.

In addition, in order to achieve the above purpose, the present application also provides a computer storage medium, the computer storage medium is stored with a check program for JSON messages, and when the check program for JSON messages is executed by a processor, the above-mentioned The steps of the verification method of the JSON message.

In addition, in order to achieve the above purpose, the present application also provides a computer program product, the computer program product includes a check program for JSON messages, and when the check program for JSON messages is executed by a processor, the above-mentioned JSON message is implemented. The steps of the verification method of the document.

The present application obtains the JSON message to be checked and the preset message checking rule, wherein, the message checking rule is configured based on the JSON message to be checked; the first in the JSON message to be checked The source message is converted into the second source message of the Map data structure, and the first target message in the JSON message to be checked is converted into the second target message of the Map data structure; The MD5 value of the second source message is inconsistent with the second target message, then determine the source Value value from the second source message according to the message checking rule, and determine the source Value value from the second source message according to the message checking rule Determining a target Value in the second target message; checking according to the source Value and the target Value to obtain a message check result of the unchecked JSON message.

Compared with the traditional method of using the Beyond Compare tool or based on the simple Json open source package for JSON message consistency comparison, this application converts the JSON message into a Map data structure, and according to the pre-configured message check rules based on The Map data structure determines the Value value to check the consistency of the message. In this way, it can realize convenient and accurate processing and checking of any field of the JSON message, effectively avoiding the situation that the traditional method cannot be checked, and improving the JSON report. The efficiency of document consistency check.

Description of drawings

Fig. 1 is the schematic structural diagram of the verification device of the JSON message of the hardware operating environment involved in the scheme of the embodiment of the present application;

Fig. 2 is the schematic flow chart of the checking method one embodiment of the JSON message of the present application;

Fig. 3 is the description of fields in the message checking rules involved in an embodiment of the checking method of the JSON message of the present application;

Fig. 4 is the data table associated with the preset checking application involved in an embodiment of the checking method of the JSON message of the present application;

Fig. 5 is a schematic diagram of the application process involved in an embodiment of the checking method of the JSON message of the present application;

FIG. 6 is a block diagram of an embodiment of a device for checking JSON messages of the present application.

The realization, functional features and advantages of the present application will be further described in conjunction with the embodiments and with reference to the accompanying drawings.

detailed description

It should be understood that the specific embodiments described here are only used to explain the present application, and are not intended to limit the present application.

As shown in FIG. 1 , FIG. 1 is a schematic structural diagram of a terminal device in a hardware operating environment involved in the solution of the embodiment of the present application.

The terminal device in this embodiment of the present application is a terminal device configured to check the consistency of the JSON message. The terminal device may be a PC, a smart phone, or a server device on which a virtual machine runs.

As shown in FIG. 1 , the terminal device may include: a processor 1001 , such as a CPU, a network interface 1004 , a user interface 1003 , a memory 1005 , and a communication bus 1002 . Wherein, the communication bus 1002 is used to realize connection and 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 and a wireless interface. Optionally, the network interface 1004 may include a standard wired interface and a wireless interface (such as a WI-FI interface). The memory 1005 can be a high-speed RAM memory, or a stable memory (non-volatile memory), such as a disk memory. Optionally, the memory 1005 may also be a storage device independent of the aforementioned processor 1001 .

Those skilled in the art can understand that the structure of the terminal device shown in FIG. 1 does not constitute a limitation on the device, and may include more or less components than those shown in the figure, or combine some components, or arrange different components.

As shown in FIG. 1 , the memory 1005 as a computer storage medium may include an operating system, a network communication module, a user interface module, and a checking program for JSON messages.

In the terminal equipment shown in Fig. 1, the network interface 1004 is mainly used to connect the background server and carry out data communication with the background server; the user interface 1003 is mainly used to connect the client (client) and carry out data communication with the client; The device 1001 can be used to call the verification program of the JSON message stored in the memory 1005, and perform the operations in the following JSON message verification method.

Based on the above hardware structure, an embodiment of the checking method for the JSON message of the present application is proposed.

It should be noted that, nowadays, Json (Java Script Object Notation, JS object notation, a lightweight data exchange format, JS is called Java Script, which is a programming language) messages between the API interface and the front-end and back-end of the application It is widely used in messaging and other scenarios, especially for development and testing, to check whether the JSON messages before and after interface changes are consistent, and whether the returned data of JSON messages from the same data source are consistent after multi-party processing, etc. , are all necessary and frequent operations.

In view of the above phenomenon, this application provides a method for checking JSON messages, please refer to Figure 2, Figure 2 is a schematic flow chart of the first embodiment of the method for checking JSON messages of this application, the method for checking JSON messages of this application is applied to For the above-mentioned terminal device, the checking method of the JSON message in this application includes:

Step S10, obtaining the JSON message to be checked and a preset message checking rule, wherein the message checking rule is configured based on the JSON message to be checked;

It should be noted that, in this embodiment, the preset message checking rules are pre-configured and generated based on the JSON message to be checked, and stored in the corresponding checking rule base, so as to perform consistent Specifically, the checking rule base may be MySQL (a relational database management system) or SQLite (a light database) maintained in the local storage space of the terminal device.

The terminal device obtains the JSON message to be checked that currently needs to be checked for consistency from the database storing the JSON message, and obtains the consistency check for the JSON message to be checked from the check rule library that stores message checking rules. Checked packet check rules.

Specifically, for example, please refer to the application process shown in Figure 5, assuming that the database storing JSON messages is a specific storage space independently configured on the terminal side in the local storage space and named "JSON message library". The space can also be maintained as MySQL or SQLite. The terminal device will write the JSON messages generated during development, testing and even operation into the "JSON message library". A request for consistency check of the source message and target message generated before and after a certain interface change, that is, the source message and target message are regarded as the JSON message to be checked, and the JSON message library is obtained from the "JSON message library". The JSON message to be checked is ready for subsequent consistency check.

Moreover, while the terminal device obtains the JSON message to be checked from the "JSON message library", it also synchronously obtains the pre-configured generation based on the JSON message to be checked in the "checking rule base" for use in Check the message checking rules to check whether the source message and the target message in the JSON message to be checked are consistent.

Further, in a feasible embodiment, the checking method of the JSON message of the present application may also include:

Step S50, generating a message checking rule for performing consistency check on the JSON message to be checked based on the configuration of the JSON message to be checked.

After the terminal device receives the request for consistency check on the JSON message and determines the JSON message to be checked pointed to by the request, it immediately generates a consistency check message based on the configuration of the JSON message to be checked. The message check rule of the sex check is used, and the message check rule is stored for calling.

It should be noted that, in this embodiment, after the terminal device generates a message checking rule for consistency checking of the JSON message to be checked based on the configuration of the JSON message to be checked, it can follow the received JSON message The time of the request for the consistency check of the message, and the message check rule is stored in the check rule base. In this way, when the terminal device starts to check the consistency of the JSON message to be checked, it can accurately extract the message checking rule from the checking rule base according to the requested time and use it to perform consistency check on the JSON message to be checked. gender check.

Alternatively, after the terminal device is configured to generate a message checking rule for consistency checking of the JSON message to be checked, it can also directly store the message checking rule in the checking rule base according to the current time, so that the terminal device When the consistency check for the JSON message to be checked is started immediately based on the request, the terminal device can extract the latest message check rule from the check rule base according to the current time for the consistency check of the JSON message to be checked gender check.

It should be noted that, in this embodiment, since no new request has been received after the current time, or the new request has not been responded to yet (the terminal device can be set to respond to the next new request after executing the current request Request), so that no other message checking rules are configured and generated after the current time, then the latest message checking rules generated by the current configuration are the rules used to check the consistency of the JSON message to be checked.

Further, in a feasible embodiment, the above step S50, based on the configuration of the JSON message to be checked, generates a message checking rule for performing consistency check on the JSON message to be checked, which may include:

Step S501, obtaining a preset message checking requirement, and analyzing the data structure of the JSON message to be checked;

In the process of determining the to-be-checked JSON message that currently needs to be checked for consistency, and thereby generating a message checking rule based on the configuration of the to-be-checked JSON message, the terminal device first obtains the report for the consistency check of the to-be-checked JSON message document verification requirements, and synchronously parse the data structure of the JSON message to be verified.

It should be noted that, in this embodiment, the terminal device can obtain the message checking requirements for consistency checking from the received request for consistency checking on JSON messages to be checked, and the message checking requirements include but Not limited to: comparing fields directly, comparing arrays, and comparing arrays within arrays.

Specifically, for example, the terminal device receives a request for consistency comparison between the source message and the target message before and after a certain interface change, and determines the source message and the target message together as the JSON to be checked After the message, the terminal device further determines from the request based on the mature command analysis technology that the current message check requirement for the consistency check of the JSON message to be checked is to directly compare fields, compare arrays, or compare arrays in arrays. Moreover, based on the mature data structure analysis technology, the terminal device analyzes and determines the data structures such as all the fields contained in the source message and the target message respectively.

Step S502, generate a message checking rule corresponding to the data structure according to the message checking requirement configuration and used for checking the consistency of the JSON message to be checked.

After the terminal device obtains the message verification requirement for the consistency check of the JSON message to be checked, and parses out the data structure of the JSON message to be checked, it configures and generates the corresponding data structure according to the message checking requirement. Therefore, it can be used as a message checking rule for accurately checking the consistency of the checking JSON message.

Specifically, for example, please refer to the field descriptions in the message checking rules shown in Figure 3, assuming that the terminal device obtains the message checking requirements from the request for consistency checking of JSON messages to be checked: The message and the target message are directly compared with each other to determine the required configuration. In the generated message check rule, from_path=source.a.b? , to_path=target.x.y, and after the terminal device parses and obtains all the fields contained in the source message and the target message, it can be configured to generate corresponding to all the fields so that it can be used to accurately check the source message and the target message The message check rule for target message consistency is: INSERT INTO sys_checkrule_def(id,group_id,compare_type,from_path,to_path,check_first_only_if_list,check_size_if_list,from_check_fields,to_check_fields,remark)VALUES('T3_ACCT_INFO_NEW_ALUE02','FO3_UEW_IN' 'custNumber','CUST_NUMBER','N','N',",",",'Compare T3accountInfos external content').

Or, assume that the terminal device obtains the message verification requirement from the request for consistency check of the JSON message to be checked: compare the arrays of the source message and the target message, so as to determine the message generated by the required configuration. In the text check rule, the name of the array needs to be configured, and the fields that do not want to be compared in the array can be configured in "sys_rmb_compare_def.ignore_field_from" and "sys_rmb_compare_def.ignore_fieldto", and the terminal device parses and obtains that the source message and the target message respectively contain After all the fields, you can configure and generate a packet check rule that corresponds to all the fields and can be used to accurately check the consistency between the source packet and the target packet: INSERT INTO sys_checkrule_def(id,group_id,compare_type,from_path ,to_path,check_first_only_if_list,check_size_if_list,from_check_fields,to_check_fields,remark)VALUES('T3_TRANS_NEW_01','T3_TRANS_NEW','LIST','output.TXN_ARRAY','TXN_ARRAY','N','N',",",' Compare T3 accountInfos').

Alternatively, assume that the terminal device obtains the message verification requirement from the request for consistency check of the JSON message to be checked: compare the array within the array for the source message and the target message, so as to determine the required configuration In the generated message checking rules, "#" needs to be used to separate the arrays of different nesting levels, and after the terminal device parses and obtains all the fields contained in the source message and the target message, it can be configured to generate and match all the fields. The message check rule that corresponds to the field and can be used to accurately check the consistency between the source message and the target message is: INSERT INTO sys_checkrule_def(id,group_id,compare_type,from_path,to_path,check_first_only_if_list,check_size_if_list,from_check_fields,to_check_fields,remark )VALUES('T3_ACCT_INFO_NEW_03','T3_ACCT_INFO_NEW','LIST_LIST','accountInfos#subAccountInfo','ACCOUNT_INFOS#SUB_ACCOUNT_INFO','N','N',

'accountBalance,accountStatus,acctNo,availableBalance,currencyCode,openChannelId,openDate,productId,subAccountSerialNo','ACCOUNT_BALANCE,ACCOUNT_STATUS,ACCT_NO,AVAILABLE_BALANCE,CURRENCY_CODE,OPEN_CHANNEL_ID,OPEN_DATE,PRODUCT_ID,SUB_ACCOUNT_SERIAL_NO','比较T3 subAccountInfo')。

In this embodiment, the data structure of the JSON message to be checked is synchronously analyzed by obtaining the message checking requirement for the consistency check of the JSON message to be checked, thereby configuring and generating the data according to the message checking requirement. The structure corresponds to the message checking rule that can be used to accurately check the consistency of the checked JSON message. In this way, compared to the traditional way of using the Beyond Compare tool or based on the simple Json open source package for JSON message consistency comparison, this application does not require additional development work, and only dynamically configures the corresponding message according to the message verification requirements. By using the text checking rules, the consistency checking of complex, customizable and multi-level JSON messages can be realized, which further improves the checking efficiency.

Step S20, converting the first source message in the JSON message to be checked into the second source message of the Map data structure, and converting the first target message in the JSON message to be checked into Map data the second target message of the structure;

After obtaining the to-be-checked JSON message that needs to be checked for consistency, the terminal device further converts the first source message in the to-be-checked JSON message into the second source message of the Map data structure, and also The first target message in the to-be-checked JSON message is also converted into the second target message of the Map data structure.

Specifically, for example, the terminal device receives a request for consistency check of the source message and the target message generated before and after a certain interface change in the "JSON message library", so that the source message and the target message As the JSON message to be checked, and after obtaining the JSON message to be checked from the "JSON message library" to prepare for the consistency check, the terminal device will use the source message as the first source message to use the second A source message is converted into a second source message of the Map data structure, and the terminal device also uses the target message as the first target message to convert the first target message into the second target of the Map data structure message, so that the value value can be conveniently determined and compared with the second source message and the second target message according to the Map data structure.

Further, in a feasible embodiment, the Map data structure includes: an ordinary Map data structure and a nested Map data structure, in step S20, "the first source in the JSON message to be checked The step of converting the message into the "second source message of the Map data structure" may include:

Step S201, determining the first message data in common form and/or the second message data in nested form in the first source message;

When the terminal device converts the first source message in the JSON message to be checked into the second source message of the Map data structure, it first determines the first message data and/or The second packet data in nested form.

It should be noted that, in this embodiment, the first message data in common form is the message content in the form of K-V in the JSON message, and the second message data in the nested form is the K-V form in the JSON message. Message content in the form of List or K-List (List).

Step S202, converting the first message data into the second source message of the common Map data structure, and/or converting the second message data into the nested Map data structure second source message;

After the first source message determines the first message data in common form and/or the second message data in nested form, the terminal device respectively performs Converting, that is, directly converting the first message data into a second source message of a common Map data structure, and/or correspondingly converting the second message data into a second source of a nested Map data structure message.

It should be noted that, in this embodiment, the common Map data structure is WeMap(K, V), and the message of the WeMap(K, V) can be obtained directly based on the value algorithm WeMap.get(K) to obtain the corresponding Value; while the nested Map data structure is WeMap(K,List(WeMap((K1,V1),(K2,V2),……))), the WeMap(K,List(WeMap((K1, V1), (K2, V2),...))) messages need the value algorithm corresponding to the nesting level to obtain the Value value of the corresponding nesting level, that is, get the corresponding value through WeMap.get(K.K1) V1, WeMap.get(K.K2) obtains the corresponding V2, and the List(WeMap((K1,V1),(K2,V2),…)) can be obtained through WeMap.get(K), where V1 , V2 respectively refer to the Value corresponding to the first level and the Value corresponding to the second level. By analogy, it can support the extraction of the corresponding Value value in any multi-level JSON message.

Further, in a feasible embodiment, in the above step S20, the step of "converting the first target message in the JSON message to be checked into the second target message of the Map data structure",

Step S203, determining the third message data in common form and/or the fourth message data in nested form in the first target message;

When the terminal device converts the first target message in the JSON message to be checked into the second target message of the Map data structure, it first determines the third message data in a common form in the first target message and/or Or the fourth message data in a nested form.

Step S204, converting the third message data into the second target message of the common Map data structure, and/or converting the fourth message data into the nested Map data structure Second target message.

After the terminal device determines the third message data in common form and/or the fourth message data in nested form in the first target message, it respectively performs Converting, that is, directly converting the third message data into a second target message of a common Map data structure, and/or correspondingly converting the fourth message data into a second target of a nested Map data structure message.

Further, in a feasible embodiment, in step S204, the step of "converting the fourth message data into the second target message of the nested Map data structure" may include:

Step S2041, cyclically detect the Value value type corresponding to the key value in each nesting level of the fourth message data, wherein the Value value type includes: ordinary Value value, JSON array and JSON object;

It should be noted that, in this embodiment, when the terminal device converts the message data in the nested form in the JSON message to be checked into a message of the nested Map data structure, it loops for each level to obtain the Key value , Obtain the Value value corresponding to the Key and determine the type of the Value value.

In the process of converting the fourth message data in the nested form into the second target message of the nested Map data structure, the terminal device performs, for each nesting level of the fourth message data, first obtaining the Key value, and then obtain the Value value corresponding to the Key, and determine whether the type of the Value value is a normal Value value, JSON array, or JSON object.

Step S2042, if it is detected that the type of the Value is the normal Value, record the key value as a Map data structure to obtain the second target message.

In the process of judging the type of the Value value for each nesting level of the fourth message data in the nested form, if the terminal device determines that the type of the Value value is a normal Value value, the terminal device directly sets the value of the nesting level The key value of the key is directly recorded as a Map data structure. In this way, after the key values of all nested levels are recorded as a Map data structure, the second goal of converting the fourth message data into a nested Map data structure is completed. message.

Specifically, for example, for each nested level in the JSON message to be checked, the terminal device loops through the operations of obtaining the Key value, obtaining the Value value corresponding to the Key, and judging the type of the Value value. When the type is a JSON array (Array), further use the Value value as a "List type" to enter the next level of loop processing, and write the value in the Map data: (Key,toList(Value)); When the type of the Value value is a JSON object (Object), further treat the Value value as a "Json object", and write the value in the Map data: (Key, toWeMap(Value)), so that it is called in subsequent processing After the "toWeMap", you can return to the step of "obtaining the Key value" to realize the recursive analysis of the Value value; finally, if it is judged that the type of the Value value is an ordinary Value value, then when the type is an ordinary value, The terminal device can directly write the Value value into the Map data, that is, write the value in the Map data: Map(Key, Value), so that the conversion of the JSON message to be checked into a Map data structure is completed.

It should be noted that, in this embodiment, the function of toList is to parse all the Key-Values in the List type and store them in the Map data structure.

After the terminal device judges that the type of the Value value is a JSON array (Array), it further uses the Value value as a "List type" to enter the next level of loop processing, and writes the value in the Map data: (Key,toList( Value)), further call the "toList" to start recirculation execution for each value in the List: the operation of obtaining the Value value and judging the type of the Value value, and, similarly, the terminal device is judging the type of the Value value , if it is judged that the type of the Value value is a Json array, then continue to use the Value value as a "List type" to enter the next level of loop processing, and the List writes the value: (toList(Value)), so, you can Recursively call "toList" to recursively process the value inside the List; and when it is judged that the type of the Value value is a Json object, the Value is treated as a Json object, and the value is written into the List: (toWeMap(Value)), so that , you can further call "toWeMap" to implement recursive parsing of the Value value and convert all the Value values in the JSON message into values in the Map data structure; finally, when it is judged that the type of the Value value is an ordinary value, that is, directly Write the Value value to List(Value).

In addition, the process that the terminal device converts the second message data in the nested form into the second source message of the nested Map data structure is the same as converting the fourth message data in the nested form into the nested Map data. The process of the second target packet of the structure is the same, and will not be repeated here.

Step S30, if the MD5 values of the second source message and the second target message are inconsistent according to the comparison, then determine the source Value value from the second source message according to the message checking rule, and determining a target Value from the second target message according to the message checking rule;

The terminal device converts the first source message and the first target message in the JSON message to be checked into the second source message and the second target message of the Map data structure, and then first targets the second source message The message and the second target message are compared with the MD5 value of the whole text, so that when the MD5 values of the second source message and the second target message are not the same, further according to the acquired Based on the message checking rule for consistency checking of the JSON message to be checked, the source Value is determined in the second source message, and the target Value is determined in the second target message for subsequent checking.

It should be noted that, in this embodiment, if the terminal device compares the MD5 value of the whole text of the second source message and the second target message, and compares the second source message and the second target message When the MD5 values of the two target messages are the same, the terminal device can directly obtain the message checking result of the successful consistency check between the source message and the target message in the JSON message to be checked.

Step S40, check according to the source Value and the target Value to obtain a message check result of the JSON message to be checked.

After determining the source value in the second source message and determining the target value in the second target message, the terminal device compares whether the source value and the target value are the same, and determines the corresponding Simultaneously, in the JSON message to be checked, the message checking result of the consistency check of the source message and the target message is obtained correspondingly; otherwise, when it is determined that they are different, correspondingly, in the JSON message to be checked, The check result of the message that the consistency check between the source message and the target message fails.

Specifically, for example, please refer to step 2 in the example of the terminal device performing a consistency check on the JSON message to be checked through the verification application (the verification APP shown in the figure) in the application process shown in Figure 5. If the terminal device passes the verification application After determining that the message check type is the Value type, the source Value corresponding to the same Key is determined from the second source message and the second target message directly according to the value path corresponding to the Value type in the message check rule value and the target Value value, after that, the terminal device compares whether the source Value value is the same as the target Value value, and if the source Value value is the same as the target Value value, it obtains the current verification according to the message The rule checks the consistency of the JSON message to be checked, and the message check result is successful. On the contrary, if the source value and the target value are not the same, the message check result is failed, and the failure is recorded s reason.

Further, in a feasible embodiment, the source value includes: an inner source value, and the target value includes: an inner target value. The above step S30 may include:

Step S301, determining the first value path corresponding to the preset Value message check type in the message check rule;

It should be noted that, in this embodiment, the terminal device may specifically acquire the preset Value message check type by parsing the received request for consistency check on the JSON message to be checked.

When the terminal device determines the source value and the target value from the second source message and the second target message respectively according to the obtained message check rule, if the value obtained for the consistency check of the JSON message to be checked is Message check type, then according to the Value message check type in the second source message and the second target message, it is determined to be corresponding to the Value type for extracting the inner layer source Value value and the inner layer target Value The first value path for the value.

Step S302, determining the inner source Value value from the second source message according to the first value path, and determining the inner layer value from the second target message according to the value path Target Value.

After the terminal device determines the first value path from the message verification rules according to the type of the Value message verification, it further obtains the innermost content in the multi-level second source message according to the first value path. The layer source Value value, and also obtain the innermost layer target Value value in the multi-level second target message according to the first value acquisition path.

Specifically, for example, it is assumed that the second source message of the Map data structure obtained by converting the first source message in the JSON message to be checked by the terminal device is: WeMap(K,List(WeMap(K1,List(WeMap( (K2,V2),(K3,V3),...))))). In this way, if the terminal device obtains the Value message check type, and uses the Value message check type to determine the first value path from the message check rules: Key is K.K1.K2, then the terminal device directly According to the Key is K.K1.K2 from the second source message: WeMap(K,List(WeMap(K1,List(WeMap((K2,V2),(K3,V3),...))))) , get the innermost V2 as the inner source Value. Similarly, the terminal device may obtain the innermost inner target Value from the second target packet.

Further, step S40 may include:

Step S401, comparing the inner source Value with the inner target Value to obtain a comparison result;

Step S402, if the comparison result is that the inner source Value and the inner target Value are the same, then obtain a message check result indicating that the consistency check of the to-be-checked JSON message is successful.

Specifically, for example, the terminal device follows the first value path: Key is K.K1.K2, and from the second source message: WeMap(K,List(WeMap(K1,List(WeMap((K2,V2),( In K3,V3),...))))), the innermost V2 is obtained as the inner source Value value, and, according to the first value path: Key is K.K1.K2, from the The second target message with the same Map data structure in the second source message obtains the innermost inner target Value value, and then the terminal device compares whether the inner source Value value is the same as the inner target Value value, And, when comparing the source value of the inner layer with the target value of the inner layer, it is obtained that the message checking result of the consistency checking of the JSON message to be checked according to the message checking rule is successful, and the opposite , if the source value is not the same as the target value, the message check result is failed, and the reason for the failure is recorded.

Further, in another feasible embodiment, the source Value includes: a first source field Value, and the target Value includes: a first target field Value, the above step S30 may also include:

Step S303, determining the second value path corresponding to the preset List message check type in the message check rule;

It should be noted that, in this embodiment, the terminal device may specifically obtain the preset List message check type by parsing the received request for consistency check on the JSON message to be checked.

When the terminal device determines the source value and the target value from the second source message and the second target message respectively according to the obtained message checking rules, if it obtains the List for consistency check for the JSON message to be checked Message check type, then according to the List message check type in the second source message and the second target message, determine that it is corresponding to the List type for extracting the first source field Value value and the first target The second path to obtain the value of the field Value.

Step S304: Determine the value of the first source field Value from each piece of source message data in the second source message according to the second value path, and determine the value of the first source field Value from the first value path according to the second value path. The value of the first target field Value is determined in each piece of source message data of the second target message.

After the terminal device determines the second value path from the message verification rules according to the type of the List message check, it further selects among the source message data of the multi-level second source message according to the second value path. , to obtain the first source field Value value of each level of source message data, and, also according to the second value path, among the source message data of the multi-level second target message, to obtain each Value of the first target field of hierarchical source packet data.

Specifically, for example, it is assumed that the second source message of the Map data structure obtained by the terminal device by converting the first source message in the JSON message to be checked is WeMap(K, List(WeMap((K1 ,V1),(K2,V2),...))). In this way, if the terminal device obtains the Value message check type, and uses the List message check type to determine the second value path from the message check rules: Key is K, then the terminal device directly follows the Key as K obtains the first source message data corresponding to the outermost List from the second source message: WeMap(K,List(WeMap((K1,V1),(K2,V2),...))) The source field Value value is: List(WeMap((K1,V1),(K2,V2),...)), and so on to obtain the first source field Value value of all the source message data corresponding to each level of List. Similarly, the terminal device may obtain the Value of the first target field of each level of source message data from each piece of source message data in the second target message.

Further, step S40 may also include:

Step S403, sorting each of the source message data and each of the target message data according to the sorting manner corresponding to the List type in the message checking rule;

It should be noted that, in this embodiment, the terminal device may configure a sorting field in the message checking rule based on the received request for consistency checking on the JSON message to be checked.

Specifically, for example, after the terminal device obtains the first source field Value value of the source message data corresponding to each layer List of the second source message, and the target message data corresponding to each layer List of the second target message After the value of the first target field Value, the terminal device first sorts the multiple pieces of message data in the List of each level according to the sorting field configured in the message checking rule to obtain the sorted message data.

Step S404, checking whether the number of the first data pieces of each of the sorted source message data and each of the target message data is consistent;

After the terminal device sorts each piece of source message data and each piece of target message data, the first data number of each piece of source message data and each piece of target message data after the sorting is according to the message checking rule Is it consistent.

Specifically, for example, after the terminal device respectively sorts the multiple pieces of message data in the List of each level according to the sorting field configured in the message checking rule to obtain the sorted message data, it detects the number of items in the message checking rule. Whether the check rule for the number of data items in the List is configured (assumed to be: check that the number of items in the source message data and the target message data are the same, or, check that the number of items in the source message data cannot be less than the number of target message data number of items, etc.), thus, if it is detected that the check rule is configured in the message check rule, the number of message data items in the List of each level corresponds to each target item after sorting the source message data. After the message data is sorted, compare the number of message data items in the list of each level to determine whether the numbers are the same. If they are not the same, return the verification failure and record the reason for the failure.

Step S405, if it is checked that the number of the first data items is consistent, then compare the value of the first source field Value with the value of the first target field;

Step S406, when the value of the first source field Value and the value of the first target field are the same after comparison, obtain a message check result indicating that the consistency check of the JSON message to be checked is successful.

When the terminal device checks that the number of first data pieces of each piece of source message data and each piece of target message data is consistent after sorting, it further performs the determined first source field Value value and the first target field Value value. Compare; and when comparing the first source field Value value and the first target field Value value, correspondingly obtain the message that the consistency check of the source message and the target message is successful in the JSON message to be checked. Text check results.

It should be noted that, in this embodiment, the process for the terminal device to check whether the first source field Value and the first target field Value are consistent is the same as the above-mentioned process for checking whether the source Value and the target Value are consistent. I won't go into too much detail here. In addition, before the terminal device checks the first source field Value value and the first target field Value value, it also checks whether there is a configuration that must check the first piece of data in the message check rule, and, similarly, if it exists but checks to The second source message and the second target message do not conform to the rules, and the result of the message check is failure, and the reason for the failure is recorded; and the terminal device checks for each source message data or target message in each layer List The data can be checked one by one according to the fields.

Further, in yet another feasible embodiment, the source Value includes: a second source field Value, and the target Value includes: a second target field Value. The above step S30 may also include:

Step S305, determining the third value path corresponding to the preset List_List message checking type in the message checking rule;

It should be noted that, in this embodiment, the terminal device may specifically obtain the preset List_List message check type by parsing the received request for consistency check on the JSON message to be checked.

When the terminal device determines the source value and the target value from the second source message and the second target message respectively according to the obtained message checking rules, if it obtains the List_List for consistency checking of the JSON message to be checked Message check type, then according to the List_List message check type in the second source message and the second target message, determine that it is corresponding to the List_List type for extracting the second source field Value value and the second target The third value path of the value of the field Value.

Step S306: Determine the value of the second source field Value from each piece of source message data in the second source message according to the third value path, and determine the value of the second source field Value from the first value path according to the third path. The value of the second target field Value is determined in each item of target message data of the second target message.

After the terminal device determines the third value-taking path from the message checking rules according to the message checking type of List_List, that is, further according to the third value-taking path, among the source message data of the multi-level second source message , to obtain the second source field Value value of each level of source message data, and, also according to the third value path, among the source message data of the multi-level second target message, to obtain each The value of the second target field Value of the hierarchical source message data.

Specifically, for example, it is assumed that the second source message of the Map data structure obtained by the terminal device by converting the first source message in the JSON message to be checked is WeMap(K, List(WeMap) in the form of K, List(List) (K1,List(WeMap((K2,V2),(K3,V3),...))))). In this way, if the terminal device obtains the List_List message check type, and uses the List_List message check type to determine the third value path from the message check rule: Key is K, then the terminal device directly follows the Key as K obtains the second source message data corresponding to the outermost List from the second source message: WeMap(K,List(WeMap((K1,V1),(K2,V2),...))). The Value value of the source field is: Value is List(K1,List(WeMap((K2,V2),(K3,V3),……))), and so on to get all the source message data corresponding to each level of List The value of the second source field. Similarly, the terminal device can obtain the value of the second target field of the source message data of each level from each piece of source message data in the second target message.

Further, the above step S40 may also include:

Step S407, checking the second number of data pieces of the source message data and the target message data layer by layer from outside to inside according to the hierarchical order;

It should be noted that, in this embodiment, the hierarchical order is the hierarchical order of the respective message data in the second source message and the second target message indicated by each layer of List in the Map data structure, for example , when the second source message is WeMap(K,List(WeMap(K1,List(WeMap((K2,V2),(K3,V3),...))))) in the form of K,List(List), The outermost source message data indicated by List is: WeMap(K,List(WeMap(K1,List(WeMap((K2,V2),(K3,V3),...))))), The innermost source message data indicated by the List is: WeMap((K2, V2), (K3, V3),...).

Specifically, for example, the terminal device detects whether a check rule for the number of data items in the List is configured in the message check rule, and when it detects that the check rule is configured in the message check rule, it checks each source message Data, according to the order of levels indicated by the List, the number of source message data in each level of List is compared with the number of target message data in each level of List to determine whether the numbers are the same, if If the number of checks is not the same, return check failure and record the reason for the failure.

Step S408, if it is checked that the number of the second data pieces is the same, compare the value of the second source field Value with the value of the second target field;

Step S409, when the value of the second source field Value and the value of the second target field are the same after comparison, obtain a message check result indicating that the consistency check of the JSON message to be checked is successful.

When the terminal device checks layer by layer that the number of data pieces of each piece of source message data and each piece of target message data is consistent, it further compares the determined value of the second source field with the value of the second target field ; and when the second source field Value value is consistent with the second target field Value value, correspondingly obtain the message check that the consistency check between the source message and the target message is successful in the JSON message to be checked result.

It should be noted that, in this embodiment, the process for the terminal device to check whether the value of the second source field is consistent with the value of the second target field is the same as the process for checking whether the value of the source value and the target value are consistent. I won't go into too much detail here. In addition, when the terminal device checks the data in the inner List according to the hierarchical order, it is based on List(WeMap(K1,List(Map((K2,V2),(K3,V3),...)))), Through the path configured in the message check rule: Key is K1, to determine the Value value is List(WeMap((K2,V2),(K3,V3),...)) to check, the check rule is the same as the above terminal equipment in determining The verification process when the message verification type is List type.

Further, in a feasible embodiment, in the above step S40, after checking according to the source Value value and the target Value value to obtain the message checking result of the JSON message to be checked, the application JSON The message checking method may also include:

Step S60, recording the message checking result in a data table associated with a preset checking application for output, wherein the running mode of the preset checking application is a background running mode; or,

Step S70, outputting the message checking result through a preset API.

It should be noted that, in this embodiment, as shown in the application flow shown in Figure 5, the terminal device can perform the process of performing the consistency check for the JSON message to be checked in the above steps by checking that the application is running in the background. Alternatively, the terminal device can also embed a functional business module, and the business module that performs the message checking function embedded in any application performs the above-mentioned steps to perform the process of consistency checking for the JSON message to be checked.

After the terminal device checks the consistency of the JSON message to be checked in the background operation mode through the checking application and obtains the message checking result, it will directly record the checking result of the message in the data table associated with the checking application, and based on Display the data table to output the verification result of the message.

Specifically, for example, after the terminal device performs the checking process of the JSON message to be checked based on the background operation mode through the checking application, and after obtaining the message checking result of the consistency check, the terminal device writes the message checking as shown in Figure 4 In the field "compare_status" of the message table (assumed to be named: sys_compare_payload) describing the checking application (when the message checking result is a failure, the checking exception information will be written in the field "error_msg", so that the message table When displaying, the verification result of the message can be output.

It should be noted that, in this implementation, the data table associated with the checking application can also be stored in MySQL or SQLLite like the checking rule library storing message checking rules or the JSON message library storing JSON messages.

After the terminal device checks the consistency of the JSON message to be checked and obtains the message checking result through the business module embedded in the application that performs the message checking function, it will obtain the JSON message to be checked and the message checking result through the business module. The application program interface enabled at the time of the rule directly feeds back the verification result of the message.

Specifically, for example, after the terminal device performs the above-mentioned checking process of the JSON message to be checked through the business module embedded in the application, and obtains the message checking result of the consistency check, it uses the business module again to obtain the JSON message to be checked The API interface, the application program interface enabled when checking the rules with the message, directly returns the message check (when the message check result is a failure, the exception information is also checked synchronously through the API interface.

It should be noted that, in this embodiment, when the terminal device outputs the message check result for the consistency check of the JSON message to be checked by checking the message table of the application or the application program interface of the business module, if the If the message verification result is failure, the terminal device can also synchronously issue an alarm for the inconsistency of the to-be-checked JSON message.

In this embodiment, the terminal device can perform the process of checking the consistency of the JSON message to be checked in the above steps by checking that the application is running in the background, or the terminal device can also be embedded in a functional business module. The business module that performs the message checking function embedded in any application executes the above-mentioned steps to check the consistency of the JSON message to be checked. Compared with the traditional way of using the Beyond Compare tool or based on the simple Json open source package to compare the consistency of JSON messages, this application implements running in the background as an application to directly check the source JSON message and the target JSON message , or embedded into other applications, and perform data verification through the API interface, which improves the flexibility of JSON message consistency verification.

The checking method of the JSON message provided by this application is to obtain the JSON message to be checked that currently needs to be checked for consistency from the database storing the JSON message through the terminal device, and obtain from the checking rule base storing the message checking rules. A message checking rule for consistency checking of the JSON message to be checked; the first source message in the JSON message to be checked is converted into a second source message of the Map data structure, and the The first target message in the JSON message to be checked is also converted into the second target message of the Map data structure; according to the message checking rule obtained for the consistency check of the JSON message to be checked, Determine the source Value value in the second source message, and determine the target Value value in the second target message for subsequent checking; by comparing whether the source Value value and the target Value value are the same, and determine the corresponding Simultaneously, in the JSON message to be checked, the message checking result of the consistency check of the source message and the target message is obtained correspondingly; otherwise, when it is determined that they are different, correspondingly, in the JSON message to be checked, The check result of the message that the consistency check between the source message and the target message fails.

In addition, the present application also provides a checking device for a JSON message, please refer to Figure 6, the checking device for the JSON message includes:

The message check preparation module 10 is used to obtain the JSON message to be checked and a preset message check rule, wherein the message check rule is configured based on the JSON message to be checked;

Message conversion module 20, for converting the first source message in the JSON message to be checked into the second source message of the Map data structure, and converting the first target message in the JSON message to be checked The text is converted into the second target message of the Map data structure;

Value determination module 30, configured to determine the source from the second source message according to the message checking rules if the MD5 values of the second source message and the second target message are inconsistent after comparison Value value, and determine the target Value value from the second target message according to the message checking rule;

A checking module 40, configured to check according to the source Value and the target Value to obtain a message checking result of the to-be-checked JSON message.

Further, the source Value value includes: an inner layer source Value value, and the target Value value includes: an inner layer target Value value, and the Value determination module 30 includes:

A first path determination unit, configured to determine a first value path corresponding to the preset Value message check type in the message check rule;

A first Value determination unit, configured to determine the inner source Value value from the second source message according to the first value path, and determine the inner source Value value from the second target message according to the value path determining the inner target Value;

Check module 40, including:

A first comparison unit, configured to compare the inner source Value with the inner target Value to obtain a comparison result;

The first result determination unit is configured to obtain a message that the consistency check of the JSON message to be checked is successful if the comparison result is that the inner source value and the inner target value are the same. Check the results.

Further, the source Value value includes: a first source field Value value, and the target Value value includes: a first target field Value value, and the Value determination module 30 includes:

A second path determination unit, configured to determine a second value path corresponding to the preset List message check type in the message check rule;

A second Value determination unit, configured to determine the value of the first source field Value from each piece of source message data in the second source message according to the second value path, and according to the second value path The path determines the value of the first target field Value from each piece of source message data in the second target message.

Further, the checking module 40 includes:

A sorting unit, configured to sort each of the source message data and each of the target message data according to the sorting manner corresponding to the List type in the message checking rule;

A first checking unit, configured to check whether the number of first pieces of data in each of the sorted source message data and each of the target message data is consistent;

The second comparison unit is configured to compare the value of the first source field with the value of the first target field if the number of the first data pieces is checked to be consistent;

The second result determination unit is configured to obtain a message check that the consistency check of the JSON message to be checked is successful when the value of the first source field is the same as that of the first target field. result.

Further, the source Value value includes: a second source field Value value, and the target Value value includes: a second target field Value value, and the Value determination module 30 includes:

A third path determination unit, configured to determine a third value path corresponding to the preset List_List message check type in the message check rule;

A third Value determination unit, configured to determine the value of the second source field Value from each piece of source message data in the second source message according to the third value path, and according to the third value path The path determines the value of the second target field Value from each item of target message data in the second target message.

Further, the checking module 40 includes:

The second checking unit is configured to check the second number of data pieces of the source message data and the target message data layer by layer from outside to inside according to the hierarchical order;

A third comparison unit, configured to compare the second source field Value with the second target field Value if the number of the second data pieces is found to be consistent;

The third result determination unit is configured to obtain a message check that the consistency check of the JSON message to be checked is successful when the value of the second source field Value and the value of the second target field are the same after comparison. result.

Further, the checking device of the JSON message of the present application also includes:

A generating module, configured to obtain a preset message checking requirement, and parse the data structure of the JSON message to be checked, so as to generate the data structure corresponding to the JSON message to be checked according to the message checking requirement. Packet checking rules for checking the consistency of the packets.

Further, after the checking according to the source Value and the target Value to obtain the message checking result of the JSON message to be checked, the device further includes:

The first output module is configured to record the message checking result in a data table associated with a preset checking application for output, wherein the running mode of the preset checking application is a background running mode; or,

The second output module is configured to output the message checking result through a preset application program interface.

Further, the Map data structure includes: a common Map data structure and a nested Map data structure,

The message conversion module 20 is also used for:

determining the first message data in normal form and/or the second message data in nested form in the first source message;

Converting the first message data into a second source message of the common Map data structure, and/or converting the second message data into a second source of the nested Map data structure message;

The message conversion module 20 is also used for:

determining the third message data in common form and/or the fourth message data in nested form in the first target message;

Converting the third message data into a second target message of the common Map data structure, and/or converting the fourth message data into a second target of the nested Map data structure message.

Further, the message conversion module 20 is also used for:

Circularly detect the Value value type corresponding to the key value in each nested level of the fourth message data, wherein the Value value type includes: ordinary Value value, JSON array and JSON object;

If it is detected that the type of the Value is the normal Value, then recording the key value as a Map data structure to obtain the second target message.

For the methods executed by the above program units, reference may be made to the various embodiments of the method for checking JSON messages in this application, which will not be repeated here.

The application also provides a checking device for a JSON message. The checking device for a JSON message includes: a memory, a processor, and a checking program for a JSON message stored on the memory and operable on the processor. For the methods implemented when the program is executed by the processor, reference may be made to the various embodiments of the method for checking JSON messages in this application, and details will not be repeated here.

The present application also provides a computer storage medium.

The checking program of the JSON message is stored on the computer storage medium of the application, and the checking program of the JSON message is implemented when the processor executes the steps of the checking method of the JSON message as described above.

Wherein, the method implemented when the JSON message checking program running on the processor is executed can refer to the various embodiments of the JSON message checking method in this application, and will not be repeated here.

The present application also provides a computer program product.

The computer program product of the present application includes a JSON message checking program, and when the JSON message checking program is executed by a processor, the steps of the JSON message checking method described above are implemented.

It should be noted that, as used herein, the term "comprises", "comprises" or any other variation thereof is intended to cover a non-exclusive inclusion such that a process, method, article or system comprising a set of elements includes not only those elements, It also includes other elements not expressly listed, or elements inherent in the process, method, article, or system. Without further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article or system comprising that element.

The serial numbers of the above embodiments of the present application are for description only, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus a necessary general-purpose hardware platform, and of course also by hardware, but in many cases the former is better implementation. Based on such an understanding, the technical solution of the present application can be embodied in the form of a software product in essence or the part that contributes to the prior art, and the computer software product is stored in a storage medium as described above (such as ROM/RAM , magnetic disk, optical disk), including several instructions to make a terminal device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) execute the methods described in various embodiments of the present application.

The above are only preferred embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structures or equivalent process transformations made by using the contents of the specification and drawings of this application, or directly or indirectly used in other related technical fields , are all included in the patent protection scope of the present application in the same way.

Claims

A checking method of JSON message, wherein, the checking method of described JSON message comprises:

Obtaining the JSON message to be checked and a preset message checking rule, wherein the message checking rule is configured based on the JSON message to be checked;

Converting the first source message in the JSON message to be checked into the second source message of the Map data structure, and converting the first target message in the JSON message to be checked into the first source message of the Map data structure Two target messages;

If the comparison shows that the MD5 values of the second source message and the second target message are inconsistent, then determine the source Value value from the second source message according to the message check rule, and according to the Determine the target Value value from the second target message according to the message checking rule;

Checking is performed according to the source Value and the target Value to obtain a message checking result of the to-be-checked JSON message.
The checking method of JSON message as claimed in claim 1, wherein, said source Value value comprises: inner layer source Value value, and said target Value value comprises: inner layer target Value value,

The steps of determining the source value from the second source message according to the message checking rule, and determining the target value from the second target message according to the message checking rule include:

Determine the first value path corresponding to the preset Value message check type in the message check rule;

determining the inner source value from the second source message according to the first value path, and determining the inner target value from the second target message according to the value path ;

The step of checking according to the source Value and the target Value to obtain the message checking result of the JSON message to be checked includes:

Comparing the inner source Value with the inner target Value to obtain a comparison result;

If the comparison result is that the inner source Value is the same as the inner target Value, a message check result indicating that the consistency check of the JSON message to be checked is successful is obtained.
The checking method of JSON message according to claim 1, wherein, the source Value value comprises: the first source field Value value, and the target Value value comprises: the first target field Value value,

The steps of determining the source value from the second source message according to the message checking rule, and determining the target value from the second target message according to the message checking rule include:

Determine the second value path corresponding to the preset List message check type in the message check rule;

Determine the value of the first source field Value from each source message data of the second source message according to the second value path, and determine the value of the first source field Value from the second target message according to the second value path. Determine the value of the first target field Value in each piece of source message data in the text.
The checking method of JSON message as claimed in claim 3, wherein, the step of checking according to the source Value value and the target Value value to obtain the message checking result of the JSON message to be checked includes :

sorting each of the source message data and each of the target message data according to the sorting manner corresponding to the List type in the message checking rule;

Check whether the number of the first data pieces of each of the source message data after sorting and each of the target message data is consistent;

If it is checked that the number of the first data pieces is consistent, then comparing the value of the first source field with the value of the first target field;

When the value of the first source field Value is the same as the value of the first target field, a message check result indicating that the consistency check of the JSON message to be checked is successful is obtained.
The checking method of JSON message according to claim 1, wherein, the source Value value comprises: the second source field Value value, and the target Value value comprises: the second target field Value value,

The steps of determining the source value from the second source message according to the message checking rule, and determining the target value from the second target message according to the message checking rule include:

Determine the third value path corresponding to the preset List_List message check type in the message check rule;

Determine the value of the second source field Value from each piece of source message data in the second source message according to the third value path, and determine the value of the second source field from the second target message according to the third value path. Determine the value of the second target field Value in each item of target message data in the text.
The checking method of JSON message as claimed in claim 5, wherein, the step of checking according to the source Value value and the target Value value to obtain the message checking result of the JSON message to be checked includes :

Checking the second number of data pieces of the source message data and the target message data layer by layer from outside to inside according to the hierarchical order;

If it is checked that the number of the second data pieces is consistent, then comparing the value of the second source field Value with the value of the second target field;

When the value of the second source field Value is the same as that of the second target field Value, a message check result indicating that the consistency check of the to-be-checked JSON message is successful is obtained.
The checking method of JSON message as claimed in claim 1, wherein, described method also comprises:

Obtaining the preset message checking requirements, and parsing the data structure of the JSON message to be checked, so as to generate the data structure corresponding to the message checking requirement for consistency of the JSON message to be checked Checked packet check rules.
The checking method of JSON message as claimed in claim 1, wherein, described Map data structure comprises: common type Map data structure and nested type Map data structure,

The step of converting the first source message in the JSON message to be checked into the second source message of the Map data structure includes:

determining the first message data in normal form and/or the second message data in nested form in the first source message;

Converting the first message data into a second source message of the common Map data structure, and/or converting the second message data into a second source of the nested Map data structure message;

The step of converting the first target message in the JSON message to be checked into the second target message of the Map data structure includes:

determining the third message data in common form and/or the fourth message data in nested form in the first target message;

Converting the third message data into a second target message of the common Map data structure, and/or converting the fourth message data into a second target of the nested Map data structure message.
The checking method of the JSON message as claimed in claim 8, wherein, the step of converting the fourth message data into the second target message of the nested Map data structure comprises:

Circularly detect the Value value type corresponding to the key value in each nested level of the fourth message data, wherein the Value value type includes: ordinary Value value, JSON array and JSON object;

If it is detected that the type of the Value is the normal Value, then recording the key value as a Map data structure to obtain the second target message.
A checking device of JSON message, wherein, the checking device of described JSON message comprises:

A message check preparation module, configured to obtain a JSON message to be checked and a preset message check rule, wherein the message check rule is configured based on the JSON message to be checked;

A message conversion module, configured to convert the first source message in the JSON message to be checked into the second source message of the Map data structure, and convert the first target message in the JSON message to be checked Be converted into the second target message of Map data structure;

A Value determination module, configured to determine the source Value from the second source message according to the message checking rules if the MD5 values of the second source message and the second target message are inconsistent after comparison value, and determine the target Value value from the second target message according to the message checking rule;

A checking module, configured to check according to the source Value and the target Value to obtain a message checking result of the to-be-checked JSON message.