CN107347048B - Data verification method, device and system - Google Patents
Data verification method, device and system Download PDFInfo
- Publication number
- CN107347048B CN107347048B CN201610290586.9A CN201610290586A CN107347048B CN 107347048 B CN107347048 B CN 107347048B CN 201610290586 A CN201610290586 A CN 201610290586A CN 107347048 B CN107347048 B CN 107347048B
- Authority
- CN
- China
- Prior art keywords
- json data
- standard
- server
- verification
- client
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
- H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
Abstract
The application discloses a method, a device and a system for data verification, wherein the method comprises the following steps: receiving JSON data from at least one remote server to obtain at least one JSON data; calling a corresponding standard file from a standard server for each JSON data to carry out verification to obtain a verification result, wherein the standard file is generated by the standard server in advance according to the client and an interface agreement document of the JSON data received by the client from one of at least one remote server; judging a verification result, and if the verification result is successful, transmitting JSON data to the client application; and if the verification result is failure, informing the client that the application verification result is failure. The method carries out verification according to the comparison of JSON data received from a remote server and a standard file called in a standard server, and can avoid abnormity or crash caused by non-standard JSON data of client application.
Description
Technical Field
The present disclosure generally relates to the field of data technologies, and in particular, to a method, an apparatus, and a system for data verification.
Background
At present, a large number of server interfaces in applications transmit data through a JSON format, wherein JSON (Java Script Object notification, Java Script Object identifier) is a lightweight data exchange format, and is a main data transmission format for current internet application data transmission due to the characteristics of small data size, fast network transmission, convenient conversion, and the like.
However, usually, due to the limitation of an interface of an upstream remote server or defects in some codes, JSON data transferred by the server may have an irregular format, so that an application program (APP) on a downstream client (such as an application program based on the Android/iOS mobile phone operating system at present) is prone to application crash when processing the irregular JSON data. For example: the remote server interface appoints that the data type of a JSON field is a String type, but the data sent by the actual server is an int type, so that the data of the int type is treated as the data of the String type in the application to cause abnormity and crash of the application.
Therefore, a new method, apparatus and system for data verification is needed.
The above information disclosed in this background section is only for enhancement of understanding of the background of the disclosure and therefore it may contain information that does not constitute prior art that is already known to a person of ordinary skill in the art.
Disclosure of Invention
The present disclosure provides a data checking method, device and system, so as to solve the technical problem of application breakdown caused by data abnormality in the prior art.
Additional features and advantages of the disclosure will be set forth in the detailed description which follows, or in part will be obvious from the description, or may be learned by practice of the disclosure.
According to an aspect of the present disclosure, there is provided a data verification method, including:
receiving JSON data from at least one remote server to obtain at least one JSON data;
calling a corresponding standard file from a standard server for verifying each JSON data to obtain a verification result;
judging the checking result, and if the checking result is successful, transmitting the JSON data to a client application; and if the verification result is failure, informing the client side that the application verification result is failure.
According to an embodiment of the present disclosure, before verifying that each JSON data calls a corresponding standard file from a standard server, the method further includes:
and carrying out preliminary verification on the JSON data, and if the preliminary verification is successful, continuing to call a corresponding standard file from a standard server for verifying each JSON data.
According to another embodiment of the present disclosure, the preliminary verification includes:
judging whether the object of the JSON data is empty or not; and
judging whether the JSON data contains illegal characters or not;
and when the object of the JSON data is not empty and the JSON data does not contain illegal characters, the preliminary verification is successful.
According to another embodiment of the present disclosure, the method further comprises:
after the standard file is generated, caching the standard file from the standard server to the client.
According to another embodiment of the present disclosure, the method further comprises:
and when the JSON data format of any remote server side is changed, updating the corresponding standard file in the standard server.
According to another aspect of the present disclosure, there is also provided an apparatus for data verification, including:
the receiving module is used for receiving the JSON data from at least one remote server to obtain at least one JSON data;
the first checking module is used for calling a corresponding standard file from a standard server for checking each JSON data to obtain a checking result;
the standard file generation module is used for generating the standard file by the standard server in advance according to a client and an interface agreement document of JSON data received by the client from one of the at least one remote server; and
the execution module is used for judging the checking result, and if the checking result is successful, the JSON data is transmitted to the client application; and if the verification result is failure, informing the client side that the application verification result is failure.
According to an embodiment of the present disclosure, the apparatus further comprises:
and the second checking module is used for preliminarily checking the JSON data before calling the corresponding standard file from the standard server for checking, and continuously executing the first checking module if the preliminary checking is successful, and calling the corresponding standard file from the standard server for checking the JSON data.
According to another embodiment of the present disclosure, the second check module includes:
the first judgment submodule is used for judging whether the object of the JSON data is empty or not; and
the second judgment submodule is used for judging whether the JSON data contains illegal characters or not;
and when the first judgment submodule judges that the object of the JSON data is not empty and the second judgment submodule judges that the JSON data does not contain illegal characters, the preliminary verification is successful.
According to another embodiment of the present disclosure, the apparatus further comprises:
and the cache module is used for caching the standard file from the standard server to the client after the standard server generates the standard file.
According to another embodiment of the present disclosure, the apparatus further comprises:
and the updating module is used for updating the corresponding standard file in the standard server when the JSON data format of any remote server side is changed.
According to another aspect of the present disclosure, there is also provided a system for data verification, including:
a processor; and
a memory for storing the processor-executable commands;
wherein the processor is to:
receiving JSON data from at least one remote server to obtain at least one JSON data;
calling a corresponding standard file from a standard server for each JSON data to carry out verification to obtain a verification result, wherein the standard file is generated by the standard server in advance according to a client and an interface agreement document of the JSON data received by the client from one of the at least one remote server;
judging the checking result, and if the checking result is successful, transmitting the JSON data to a client application; and if the verification result is failure, informing the client side that the application verification result is failure.
According to the technical scheme of the disclosure, the following technical effects can be obtained:
a set of unified JSON data verification method is set up by utilizing the prior public technology, verification is carried out according to the comparison of JSON data received from a far-end server and a standard file called in a standard server, and abnormity or breakdown caused by non-standard JSON data of client application can be avoided.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The above and other objects, features and advantages of the present disclosure will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.
Fig. 1 schematically illustrates a flowchart of steps of a method for data verification provided in an embodiment of the present disclosure.
Fig. 2 schematically shows a framework relationship diagram among the remote server, the client application and the standard server of the present disclosure.
Fig. 3 schematically illustrates a flowchart of steps of a method of data verification provided in another embodiment of the present disclosure.
Fig. 4 schematically shows a flowchart of the step of S40 in the verification method provided by the present disclosure.
Fig. 5 schematically illustrates a schematic diagram of an apparatus for data verification provided in an embodiment of the present disclosure.
Fig. 6 schematically illustrates a schematic diagram of an apparatus for data verification provided in another embodiment of the present disclosure.
Fig. 7 schematically illustrates a schematic diagram of a system for data verification provided in an embodiment in accordance with the present disclosure.
Detailed Description
Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art. The drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus their repetitive description will be omitted.
Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of embodiments of the disclosure. One skilled in the relevant art will recognize, however, that the subject matter of the present disclosure can be practiced without one or more of the specific details, or with other methods, components, devices, steps, and the like. In other instances, well-known structures, methods, devices, implementations, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosure.
Some of the block diagrams shown in the figures are functional entities and do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in the form of software, or in one or more hardware modules or integrated circuits, or in different networks and/or processor devices and/or microcontroller devices.
Fig. 1 is a flowchart illustrating steps of a data verification method provided in an embodiment of the present disclosure, which is used for verifying JSON data received by a client application to avoid application crash caused by different data types in a data processing process.
As shown in fig. 1, in step S10, JSON data is received from at least one remote server, and at least one JSON data is obtained. In this embodiment, the at least one remote server includes A, B, C, and three different remote servers, namely, the remote server a, the remote server B, and the remote server C, respectively send JSON data with different formats to the client application.
As shown in fig. 1, in step S20, each JSON data calls a corresponding standard file from the standard server to be verified, so as to obtain a verification result. The JSON Schema of the standard file in this embodiment is a standard for describing a JSON data format, and the specific specification may be http:// JSON-Schema. The standard file JSON Schema is generated by a standard server according to interface convention documents of JSON data both sides received by a client and one of at least one remote server side in advance, and the standard file can be generated by utilizing a third-party open source library https:// github.
As shown in fig. 1, in step S30, the verification result is determined, and if the verification result is successful, the JSON data is transmitted to the client application; and if the verification result is failure, informing the client that the application verification result is failure.
Fig. 2 shows a schematic diagram of the frame relationships of a remote server a (denoted by 001), a remote server B (denoted by 002), a remote server C (denoted by 0031), a client application 004, and a standard server 005 involved in the method provided in this embodiment, where three remote servers respectively provide JSON data of different data types to the client application, and after the client application 004 receives the JSON data, a JSON check module 0041 in the JSON check module 0041 is configured to compare the JSON data received from the remote servers with data provided by corresponding remote servers in the standard server 005
As shown in the step flowchart shown in fig. 3, in an embodiment of the present disclosure, before verifying that each JSON data calls a corresponding standard file from a standard server in step S20, the method further includes:
step S40: and (5) performing preliminary verification on the JSON data, and if the preliminary verification is successful, continuing to step (S20), namely, calling a corresponding standard file from the standard server for verifying each JSON data.
As shown in fig. 4, the preliminary verification in step S40 includes the following steps:
step S41: and judging whether the object of the JSON data is null or not, so that null pointer abnormity can be avoided.
Step S42: and (4) judging whether the JSON data contains illegal characters or not, if the object of the JSON data is not empty and the JSON data does not contain the illegal characters, the primary verification is successful, and performing the next verification, namely, continuing the verification based on the standard file in the step S20 after the primary verification in the step S40 is successful. In addition to determining whether the JSON data is null or not, it is necessary to determine whether the JSON data contains characters other than UTF8, and since only the characters of UTF8 can be supported in the process of checking the JSON Schema according to the standard file, the characters other than UTF8 are illegal characters. Therefore, illegal JSON data can be filtered out during preliminary verification, and the risk of abnormal collapse in subsequent more complex verification is avoided.
After the preliminary verification is successful, the next verification based on the standard file is carried out, namely, the corresponding JSON Schema standard file is downloaded from the JSON Schema standard server according to the difference of the called remote service terminals (A/B/C). The client application verifies the JSON data (usually in a data packet form) returned by the remote server and the corresponding JSON Schema file, and the verification process is to compare the JSON data with the JSON Schema standard file, for example, a certain field is agreed to be a data type of String in the Schema, but if the data type in the real JSON data is int, the data type does not accord and the verification fails. The checked toolkit can be json-schema-identifier (Android)/kitesjsonvalidator (iOS), and different check toolkits are provided for different systems of Android and iOS. And if the verification of the step fails, informing the client of the JSON data verification failure, and if the verification is successful, transmitting the JSON data to the application for service processing.
As also shown in fig. 3, the method provided by the present disclosure further includes:
step S50: after the standard file is generated, the standard file is cached to the client from the standard server, and the performance can be improved by adopting a local caching mechanism.
Step S60: and when the JSON data format of any remote server side is changed, updating the corresponding standard file in the standard server. Through the step, if the JSON data format of the called remote service is changed, the content of the standard file on the JSON Schema standard server needs to be synchronously updated so as to ensure the consistency of verification.
In summary, the verification method provided in this embodiment builds a set of unified JSON data verification method by using the existing public technology, and performs verification according to comparison between JSON data received from a remote server and a standard file called in a standard server, so as to avoid exception or crash caused by non-specification JSON data in a client application.
Based on the method provided above, fig. 5 further shows a schematic diagram of an apparatus for data verification provided in another embodiment of the present disclosure, where the apparatus 100 includes: the system comprises a receiving module 110, a first checking module 120, a standard file generating module 130 and an executing module 140.
The receiving module 110 is configured to receive JSON data from at least one remote server, so as to obtain at least one JSON data. In this embodiment, the at least one remote server includes A, B, C, and three different remote servers, namely, the remote server a, the remote server B, and the remote server C, respectively send JSON data with different formats to the client application.
The first checking module 120 is configured to call, from the standard server, a corresponding standard file for checking each JSON data, so as to obtain a checking result, where the checking result is a checking success or a checking failure. The JSON Schema of the standard file in this embodiment is a standard for describing a JSON data format, and the specific specification may be http:// JSON-Schema.
The standard file generation module 130 is configured to generate a standard file in advance by the standard server according to the interface agreement document of the JSON data received by the client and the client from one of the at least one remote server. The standard file JSON Schema is generated by a standard server according to interface convention documents of JSON data both sides received by a client and one of at least one remote server side in advance, and the standard file can be generated by utilizing a third-party open source library https:// github.
The execution module 140 is configured to determine a verification result, and if the verification result is successful, transmit the JSON data to the client application; and if the verification result is failure, informing the client that the application verification result is failure.
As shown in fig. 6, in another embodiment of the present disclosure, the apparatus 100 further includes: the second checking module 150 is configured to perform preliminary checking on the JSON data before the first checking module 120 checks the corresponding standard file called by each JSON data from the standard server, and if the preliminary checking is successful, continue to execute the first checking module to check the corresponding standard file called by each JSON data from the standard server.
Specifically, the second verification module 150 includes: a first judgment submodule 151 and a second judgment submodule 152, wherein the first judgment submodule 151 is used for judging whether an object of JSON data is empty; the second judgment sub-module 152 is used to judge whether the JSON data contains illegal characters (e.g., characters other than UTF 8). And when the first judgment submodule judges that the object of the JSON data is not empty and the second judgment submodule judges that the JSON data does not contain illegal characters, the preliminary verification is successful. The null pointer abnormality can be avoided by the judgment of the first judging submodule 151, and the second judging submodule 152 judges that the JSON data contains characters other than UTF8, because only the characters of UTF8 can be supported in the process of checking the JSON Schema according to the standard file, the characters other than UTF8 are illegal characters. Therefore, illegal JSON data can be filtered out during preliminary verification, and the risk of abnormal collapse in subsequent more complex verification is avoided.
As shown in fig. 6, in another embodiment of the present disclosure, the apparatus 100 further includes: the caching module 160 and the updating module 170, the caching module 160 is used for caching the standard file from the standard server to the client after the standard server generates the standard file. By employing a local caching mechanism, performance may be improved.
The updating module 170 is configured to update the corresponding standard file at the standard server when the JSON data format of any remote server changes. If the JSON data format for calling the remote service is changed, the content of a standard file on a JSON Schema standard server needs to be synchronously updated so as to ensure the consistency of verification.
According to the data verification device provided by the disclosure, a set of unified JSON data verification method is established by utilizing the existing public technology, verification is carried out according to the comparison of JSON data received from a far-end server and a standard file called in a standard server, and abnormity or breakdown caused by non-standard JSON data of client application can be avoided.
Based on the above method and apparatus, fig. 7 also shows a system for data verification provided by the embodiment of the present disclosure, where the system 200 includes a processor 210 and a memory 220. The memory 220 is used for storing executable commands of the processor 210, and the processor 210 is used for receiving JSON data from at least one remote server to obtain at least one JSON data; calling a corresponding standard file from a standard server for each JSON data to carry out verification to obtain a verification result, wherein the standard file is generated by the standard server in advance according to the client and an interface agreement document of the JSON data received by the client from one of at least one remote server; judging a verification result, and if the verification result is successful, transmitting JSON data to the client application; and if the verification result is failure, informing the client that the application verification result is failure.
It should be clearly understood that this disclosure describes how to make and use particular examples, but the principles of this disclosure are not limited to any details of these examples. Rather, these principles can be applied to many other embodiments based on the teachings of the present disclosure.
Exemplary embodiments of the present disclosure are specifically illustrated and described above. It is to be understood that the present disclosure is not limited to the precise arrangements, instrumentalities, or instrumentalities described herein; on the contrary, the disclosure is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims.
Claims (9)
1. A method of data verification, comprising:
receiving JSON data from at least one remote server to obtain at least one JSON data, wherein when the number of the remote servers is multiple, the JSON data received from the multiple remote servers are different in format;
for each JSON data, calling a standard file corresponding to the remote server from a standard server to verify according to the remote server corresponding to each JSON data to obtain a verification result, wherein the standard file is generated by the standard server in advance according to a client and an interface agreement document of both JSON data received by the client from one of the at least one remote server;
judging the checking result, and if the checking result is successful, transmitting the JSON data to a client application; if the verification result is failure, informing the client that the verification result is failure;
and when the JSON data format of any remote server side is changed, updating the corresponding standard file in the standard server.
2. The method according to claim 1, wherein before checking that each JSON data calls a corresponding standard file from a standard server, the method further comprises:
and carrying out preliminary verification on the JSON data, and if the preliminary verification is successful, continuing to call a corresponding standard file from a standard server for verifying each JSON data.
3. The method of claim 2, wherein the preliminary verification comprises:
judging whether the object of the JSON data is empty or not; and
judging whether the JSON data contains illegal characters or not;
and when the object of the JSON data is not empty and the JSON data does not contain illegal characters, the preliminary verification is successful.
4. The method of claim 1, further comprising:
after the standard file is generated, caching the standard file from the standard server to the client.
5. An apparatus for data verification, comprising:
the receiving module is used for receiving JSON data from at least one remote server to obtain at least one JSON data, wherein when the number of the remote servers is multiple, the JSON data received from the multiple remote servers are different in format;
the first checking module is used for calling a standard file corresponding to the remote server from a standard server to check each JSON data according to the remote server corresponding to each JSON data to obtain a checking result;
the standard file generation module is used for generating the standard file by the standard server in advance according to a client and an interface agreement document of JSON data received by the client from one of the at least one remote server; and
the execution module is used for judging the checking result, and if the checking result is successful, the JSON data is transmitted to the client application; if the verification result is failure, informing the client that the verification result is failure;
and the updating module is used for updating the corresponding standard file in the standard server when the JSON data format of any remote server side is changed.
6. The apparatus of claim 5, further comprising:
and the second checking module is used for preliminarily checking the JSON data before calling the corresponding standard file from the standard server for checking, and continuously executing the first checking module if the preliminary checking is successful, and calling the corresponding standard file from the standard server for checking the JSON data.
7. The apparatus of claim 6, wherein the second check-up module comprises:
the first judgment submodule is used for judging whether the object of the JSON data is empty or not; and
the second judgment submodule is used for judging whether the JSON data contains illegal characters or not;
and when the first judgment submodule judges that the object of the JSON data is not empty and the second judgment submodule judges that the JSON data does not contain illegal characters, the preliminary verification is successful.
8. The apparatus of claim 5, further comprising:
and the cache module is used for caching the standard file from the standard server to the client after the standard server generates the standard file.
9. A system for data verification, comprising:
a processor; and
a memory for storing the processor-executable commands;
wherein the processor is to:
receiving JSON data from at least one remote server to obtain at least one JSON data, wherein when the number of the remote servers is multiple, the JSON data received from the multiple remote servers are different in format;
for each JSON data, calling a standard file corresponding to the remote server from a standard server to verify according to the remote server corresponding to each JSON data to obtain a verification result, wherein the standard file is generated by the standard server in advance according to a client and an interface agreement document of both JSON data received by the client from one of the at least one remote server;
judging the checking result, and if the checking result is successful, transmitting the JSON data to a client application; if the verification result is failure, informing the client that the verification result is failure;
and when the JSON data format of any remote server side is changed, updating the corresponding standard file in the standard server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610290586.9A CN107347048B (en) | 2016-05-04 | 2016-05-04 | Data verification method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610290586.9A CN107347048B (en) | 2016-05-04 | 2016-05-04 | Data verification method, device and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107347048A CN107347048A (en) | 2017-11-14 |
| CN107347048B true CN107347048B (en) | 2021-04-30 |
Family
ID=60253497
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610290586.9A Active CN107347048B (en) | 2016-05-04 | 2016-05-04 | Data verification method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107347048B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110554929B (en) * | 2018-06-04 | 2023-07-07 | 百度在线网络技术（北京）有限公司 | Data verification method, device, computer equipment and storage medium |
| CN109032886A (en) * | 2018-06-21 | 2018-12-18 | 携程旅游网络技术（上海）有限公司 | Json message comparison method and system |
| CN109165017A (en) * | 2018-07-05 | 2019-01-08 | 平安科技（深圳）有限公司 | Data verification method, device and computer storage medium |
| CN109254792A (en) * | 2018-09-13 | 2019-01-22 | 海南新软软件有限公司 | A kind of dynamic moving promotes the operation method and device of component |
| CN111078512B (en) * | 2019-11-05 | 2023-09-12 | 远景智能国际私人投资有限公司 | Alarm record generation method and device, alarm equipment and storage medium |
| CN111145004B (en) * | 2019-12-06 | 2023-11-14 | 国网浙江省电力有限公司 | Intelligent financial auditing platform based on editable workflow |
| CN111897842A (en) * | 2020-01-02 | 2020-11-06 | 北京京东尚科信息技术有限公司 | Data checking method, device, computer system and medium |
| CN113301160A (en) * | 2021-05-27 | 2021-08-24 | 杭州海康威视数字技术股份有限公司 | Method and device for realizing data message transmission compatibility and electronic equipment |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102479130A (en) * | 2010-11-25 | 2012-05-30 | 上海宇芯科技有限公司 | Method for checking cross-platform and cross-language single-chip system |
| US8260784B2 (en) * | 2009-02-13 | 2012-09-04 | International Business Machines Corporation | Indexing and searching JSON objects |
| US9094435B2 (en) * | 2009-12-23 | 2015-07-28 | Citrix Systems, Inc. | Systems and methods for prevention of JSON attacks |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN100483419C (en) * | 2007-07-27 | 2009-04-29 | 华为技术有限公司 | Data format verification method and device |
| CN101902315B (en) * | 2009-06-01 | 2013-04-17 | 华为技术有限公司 | Retransmission method, device and communication system based on forward error correction |
| US20140067866A1 (en) * | 2012-08-28 | 2014-03-06 | Microsoft Corporation | Javascript object notation schema definition language |
| CN103823872A (en) * | 2014-02-27 | 2014-05-28 | 北京金山网络科技有限公司 | Information pushing method and device |
| CN105426164B (en) * | 2014-09-04 | 2018-12-14 | 北大方正集团有限公司 | A kind of method of calibration and browser of data |
| CN105224511A (en) * | 2015-09-23 | 2016-01-06 | 山东网聪信息科技有限公司 | A kind of method of calibration of intelligent substation SCD file |
| CN105528424B (en) * | 2015-12-07 | 2019-03-05 | 普元信息技术股份有限公司 | The system and method for data persistence is realized under big data environment |
-
2016
- 2016-05-04 CN CN201610290586.9A patent/CN107347048B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8260784B2 (en) * | 2009-02-13 | 2012-09-04 | International Business Machines Corporation | Indexing and searching JSON objects |
| US9094435B2 (en) * | 2009-12-23 | 2015-07-28 | Citrix Systems, Inc. | Systems and methods for prevention of JSON attacks |
| CN102479130A (en) * | 2010-11-25 | 2012-05-30 | 上海宇芯科技有限公司 | Method for checking cross-platform and cross-language single-chip system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107347048A (en) | 2017-11-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107347048B (en) | Data verification method, device and system | |
| CN107133180B (en) | Dynamic page testing method, testing device and storage medium | |
| EP2876865B1 (en) | Communication apparatus, communication system, communication method and recording medium | |
| CN107102908B (en) | Data verification method, data fault tolerance method and device | |
| US9329961B2 (en) | Testing development using real-time traffic | |
| CN107888446B (en) | Protocol robustness testing method and device | |
| CN111367821B (en) | Software testing method and system | |
| CN110297655B (en) | Method, device, equipment and storage medium for generating patch package | |
| CN106571975B (en) | Fault tolerance method and device for communication data | |
| US11734057B2 (en) | Method and apparatus for processing a service of an abnormal server | |
| CN106528078B (en) | method and device for dynamically adjusting payment mode based on react-native | |
| CN109656791B (en) | gPC performance test method and device based on Jmeter | |
| CN115567583A (en) | Equipment communication method and device and electronic equipment | |
| CN111932326B (en) | Data processing method based on block chain network and related equipment | |
| CN111273970B (en) | Calling method, device, system, medium and electronic equipment of intelligent contract | |
| CN114897523A (en) | Payment channel docking method and system of electronic payment platform and electronic equipment | |
| CN114257632A (en) | Disconnection reconnection method and device, electronic equipment and readable storage medium | |
| CN113746851A (en) | Agent system and method for supporting real-time analysis of GRPC request | |
| CN106156235A (en) | A kind of picture method for down loading based on Android platform and system | |
| CN108288135B (en) | System compatibility method and device, computer readable storage medium and electronic equipment | |
| US20210075878A1 (en) | Wireless network device with directional communication functionality | |
| US20230359976A1 (en) | Real-Time Prediction Method, Electronic Device And Non-transitory Computer-Readable Storage Medium | |
| CN113098975B (en) | Cross-platform application publishing method and device | |
| CN114666783A (en) | Upgrading method, device, terminal and storage medium of wireless network module | |
| CN117931612A (en) | Test case generation method and device, computing device cluster and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |