A data processing method, device, apparatus, and storage medium

Abstract

The present disclosure provides a data processing method, device and equipment and storage medium, which can determine the target on-chain time of target data in response to a time query request for the target data on the blockchain, and obtain the first timing timestamp of the first transit data uploaded by the transit database to the time service end after the first transit data is received from the client, the first receiving time of each return data received by the client from the transit database, the first timing timestamp of the first transit data uploaded by the transit database to the time service end after the first upload data uploaded by the client is received, the last timing data received by the transit database from the time service end before the target return data is sent, and the second timing timestamp indicated by the last timing data, and determine the trusted time domain of the target data based on the first timing timestamp and the second timing timestamp. In this way, according to the process of data interaction, the trusted time domain which can be used to represent the evidence time of the data is obtained by gradually tracing back based on the time sequence.

Description

Technical Field

[0001] This disclosure relates to the field of information technology, and more specifically, to a data processing method, apparatus, device, and storage medium. Background Technology

[0002] With the advent of the big data era, the requirements for data storage and management have also increased. Blockchain-based databases, such as the Trusted Ledger Database (LedgerDB), are widely used in big data scenarios for data storage and management. These databases can receive user-uploaded data, perform certain transformations and processing, and then write the data into the blockchain in a managed manner. These databases record trusted timestamps (Timestamp Authority, TSA), achieving strong external auditability, and also introduce a trusted time service with two-way PEG (Two-Way Peer Estimation), thus possessing trusted time properties.

[0003] In the process of data storage management through blockchain-style databases, for each piece of data uploaded by users, only a rough time period is given to characterize the time range to which the data was stored. This time period may have low correlation with the data itself and is not very reliable in characterizing the data storage time. Summary of the Invention

[0004] This disclosure provides at least one data processing method, apparatus, device, and storage medium.

[0005] This disclosure provides a data processing method, the method comprising:

[0006] In response to a time query request for target data, the target on-chain time of the target data is determined, wherein the target data is any one of multiple business data that are uploaded to the blockchain through a client.

[0007] Based on the time order of each business data being uploaded to the blockchain, the first time stamp assigned by the time synchronization terminal to the first relay data is obtained after the relay database receives the first uploaded data uploaded by the client and uploads the first relay data to the time synchronization terminal for the first time. The first uploaded data is the data that the client sends to the relay database for the first time after the target data is uploaded to the blockchain.

[0008] Based on the first receiving time of each return data received from the relay database and the target on-chain time, a second timing timestamp indicating the last timing data received by the relay database from the timing terminal before sending the target return data is obtained. The target return data is the last data received by the client from the relay database before the target on-chain time.

[0009] Based on the first and second time synchronization timestamps, the reliable time domain of the target data is determined.

[0010] In one optional implementation, the step of obtaining the first time synchronization timestamp assigned to the first relay data by the time synchronization terminal after the relay database first uploads the first relay data to the time synchronization terminal after receiving the first upload data uploaded by the client, based on the time order of each business data being uploaded to the blockchain, includes:

[0011] For multiple business data that have already been uploaded to the blockchain, the order in which each business data is uploaded to the blockchain is determined based on the upload time of each business data.

[0012] Based on the time order of each business data being uploaded to the blockchain, the first uploaded data that the client first sends to the transit database after uploading the target data to the blockchain is determined from the multiple business data;

[0013] For the multiple relay data stored in the relay database, based on the first sending time of each relay data sent to the time synchronization terminal by the relay database, the first relay data that was first uploaded to the time synchronization terminal after receiving the first uploaded data is determined from the multiple relay data, and the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data is determined. The multiple relay data includes the relay data obtained by the relay database after processing the first uploaded data.

[0014] In one optional implementation, the step of determining the first relay data that was first uploaded to the time synchronization terminal after receiving the first uploaded data from the plurality of relay data based on the first transmission time of each relay data sent to the time synchronization terminal from the relay database, and determining the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data, includes:

[0015] The second receiving time when the relay database receives the first uploaded data, and the first sending time when the relay database sends each stored relay data to the time synchronization terminal are obtained;

[0016] Based on the acquired first transmission time and second reception time, a first target transmission time is determined in at least one first transmission time after the second reception time, wherein the time difference between the first target transmission time and the second reception time is minimized;

[0017] The first relay data that was uploaded to the timing terminal at the first target transmission time is determined from the plurality of relay data;

[0018] Obtain the first time stamp assigned by the time synchronization terminal to the first relay data.

[0019] In one optional implementation, the step of obtaining a second timing timestamp, indicated by the last timing data received by the relay database from the timing terminal before sending the target backhaul data, based on the first reception time of each backhaul data received from the relay database and the target on-chain time, includes:

[0020] The first reception time of each returned data received from the relay database is obtained. The returned data is data obtained by the relay database through the relay data and the time synchronization timestamp corresponding to the relay data. The time synchronization timestamp is time data obtained from the time synchronization data corresponding to the relay data received from the time synchronization end.

[0021] Based on each first receiving time and the target on-chain time, determine the target backhaul data that the client last received from the relay database before the target on-chain time;

[0022] The third receiving time corresponding to each time synchronization data returned by the time synchronization terminal is obtained from the relay database, and the second target sending time when the relay database sends the target return data. The time synchronization data is the data obtained by the time synchronization terminal based on the received relay data and the time synchronization timestamp assigned to the relay data.

[0023] Based on the acquired third receiving times and the second target sending time, the last timing data received before the relay database sends the target return data is determined, along with the second timing timestamp included in the last timing data.

[0024] In one optional implementation, determining the last timing data received before the relay database sends the target return data, and the second timing timestamp included in the last timing data, based on the acquired third receiving timestamps and the second target sending timestamp, includes:

[0025] Based on the acquired third reception times and the second target transmission time, a third target reception time is determined in at least one third reception time before the second target transmission time, wherein the time difference between the third target reception time and the second target transmission time is minimized;

[0026] The timing data received by the relay database at the third target receiving time and sent by the timing terminal shall be regarded as the last timing data received.

[0027] Determine the second time stamp included in the last time synchronization data.

[0028] In an optional implementation, after determining the reliable time domain of the target data based on the first and second time synchronization timestamps, the method further includes:

[0029] Based on the trusted time domain, the time query results corresponding to the time query request are displayed to the user;

[0030] The time query results include one or more of the following: earlier reliable time point, later reliable time point, and reliable time period.

[0031] In one optional implementation, the method further includes:

[0032] Receive business data uploaded by users;

[0033] The business data is processed on the blockchain to obtain multiple business data on the blockchain.

[0034] The business data to be uploaded to the blockchain is uploaded to the relay database. The relay database can convert the received business data into corresponding relay data and write it into the relay database, and forward the relay data to the time synchronization terminal. The time synchronization terminal can assign a time synchronization timestamp to the received relay data and send the time synchronization data obtained by the relay data and the corresponding time synchronization timestamp back to the relay database. After receiving the time synchronization data sent back by the time synchronization terminal, the relay database can obtain the return data according to the received time synchronization data and the corresponding relay data and write it into the relay database, and return the obtained return data to the client.

[0035] Receive the data returned by the relay database.

[0036] In an optional implementation, after receiving the return data from the relay database, the method further includes:

[0037] Based on the received feedback data, the service data corresponding to the feedback data is updated.

[0038] This disclosure also provides a data processing apparatus, the apparatus comprising:

[0039] The time determination module is used to respond to a time query request for target data and determine the target on-chain time of the target data, wherein the target data is any one of multiple business data that are uploaded to the blockchain through the client.

[0040] The first data acquisition module is used to acquire, based on the time order of each business data being uploaded to the blockchain, the first time stamp assigned by the time synchronization terminal to the first relay data after the relay database receives the first uploaded data uploaded by the client and first uploads the first relay data to the time synchronization terminal. The first uploaded data is the data that the client first sends to the relay database after the target data is uploaded to the blockchain.

[0041] The second data acquisition module is used to acquire, based on the first receiving time of each return data received from the relay database and the target on-chain time, the second timing timestamp indicated by the last timing data received by the relay database from the timing terminal before sending the target return data, wherein the target return data is the last data received by the client from the relay database before the target on-chain time;

[0042] The time domain determination module is used to determine the reliable time domain of the target data based on the first time synchronization timestamp and the second time synchronization timestamp.

[0043] In one optional implementation, the first data acquisition module is specifically used for:

[0044] For multiple business data that have already been uploaded to the blockchain, the order in which each business data is uploaded to the blockchain is determined based on the upload time of each business data.

[0045] Based on the time order of each business data being uploaded to the blockchain, the first uploaded data that the client first sends to the transit database after uploading the target data to the blockchain is determined from the multiple business data;

[0046] For the multiple relay data stored in the relay database, based on the first sending time of each relay data sent to the time synchronization terminal by the relay database, the first relay data that was first uploaded to the time synchronization terminal after receiving the first uploaded data is determined from the multiple relay data, and the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data is determined. The multiple relay data includes the relay data obtained by the relay database after processing the first uploaded data.

[0047] In an optional implementation, when the first data acquisition module determines, from the plurality of relay data, the first relay data that was first uploaded to the time synchronization terminal after receiving the first uploaded data, at the first sending time when each relay data is sent to the time synchronization terminal based on the relay database, and determines the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data, it is specifically used for:

[0048] The second receiving time when the relay database receives the first uploaded data, and the first sending time when the relay database sends each stored relay data to the time synchronization terminal are obtained;

[0049] Based on the acquired first transmission time and second reception time, a first target transmission time is determined in at least one first transmission time after the second reception time, wherein the time difference between the first target transmission time and the second reception time is minimized;

[0050] The first relay data that was uploaded to the timing terminal at the first target transmission time is determined from the plurality of relay data;

[0051] Obtain the first time stamp assigned by the time synchronization terminal to the first relay data.

[0052] In one optional implementation, the second data acquisition module is specifically used for:

[0053] The first reception time of each returned data received from the relay database is obtained. The returned data is data obtained by the relay database through the relay data and the time synchronization timestamp corresponding to the relay data. The time synchronization timestamp is time data obtained from the time synchronization data corresponding to the relay data received from the time synchronization end.

[0054] Based on each first receiving time and the target on-chain time, determine the target backhaul data that the client last received from the relay database before the target on-chain time;

[0055] The third receiving time corresponding to each time synchronization data returned by the time synchronization terminal is obtained from the relay database, and the second target sending time when the relay database sends the target return data. The time synchronization data is the data obtained by the time synchronization terminal based on the received relay data and the time synchronization timestamp assigned to the relay data.

[0056] Based on the acquired third receiving times and the second target sending time, the last timing data received before the relay database sends the target return data is determined, along with the second timing timestamp included in the last timing data.

[0057] In one optional implementation, when the second data acquisition module determines, based on the acquired third receiving times and the second target sending time, the last timing data received before the relay database sends the target return data, and the second timing timestamp included in the last timing data, it is specifically configured to:

[0058] Based on the acquired third reception times and the second target transmission time, a third target reception time is determined in at least one third reception time before the second target transmission time, wherein the time difference between the third target reception time and the second target transmission time is minimized;

[0059] The timing data received by the relay database at the third target receiving time and sent by the timing terminal shall be regarded as the last timing data received.

[0060] Determine the second time stamp included in the last time synchronization data.

[0061] In an optional embodiment, the device further includes a result display module, the result display module being used for:

[0062] Based on the trusted time domain, the time query results corresponding to the time query request are displayed to the user;

[0063] The time query results include one or more of the following: earlier reliable time point, later reliable time point, and reliable time period.

[0064] In one optional embodiment, the apparatus further includes a data processing module, the data processing module being used for:

[0065] Receive business data uploaded by users;

[0066] The business data is processed on the blockchain to obtain multiple business data on the blockchain.

[0067] The business data to be uploaded to the blockchain is uploaded to the relay database. The relay database can convert the received business data into corresponding relay data and write it into the relay database, and forward the relay data to the time synchronization terminal. The time synchronization terminal can assign a time synchronization timestamp to the received relay data and send the time synchronization data obtained by the relay data and the corresponding time synchronization timestamp back to the relay database. After receiving the time synchronization data sent back by the time synchronization terminal, the relay database can obtain the return data according to the received time synchronization data and the corresponding relay data and write it into the relay database, and return the obtained return data to the client.

[0068] Receive the data returned by the relay database.

[0069] In an optional implementation, the data processing module is further configured to:

[0070] Based on the received feedback data, the service data corresponding to the feedback data is updated.

[0071] This disclosure also provides an electronic device, including a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus, and when the machine-readable instructions are executed by the processor, the steps of the above-described data processing method are performed.

[0072] This disclosure also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the above-described data processing method.

[0073] For a description of the effects of the aforementioned data processing apparatus, electronic equipment, and computer-readable storage medium, please refer to the description of the aforementioned data processing method; it will not be repeated here.

[0074] In the embodiments provided in this disclosure, in response to a time query request for target data uploaded to the blockchain, the target on-chain time of the target data can be determined. Based on the on-chain time order of various business data, the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data after the relay database first uploads the first relay data to the time synchronization terminal after receiving the first upload data uploaded by the client can be obtained. Based on the first reception time of the client receiving each return data from the relay database and the target on-chain time, the second time synchronization timestamp indicated by the last time synchronization data received by the relay database from the time synchronization terminal before sending the target return data can be obtained. Thus, the trusted time domain of the target data can be determined based on the first time synchronization timestamp and the second time synchronization timestamp.

[0075] In this way, upon receiving a time query request for target data, the system can trace back step by step according to the data interaction process, based on the target data's on-chain time, the on-chain time order of various business data, and the reception time of each returned data received from the transit database. This allows the system to obtain the time stamps assigned by the time synchronization terminal before and after the target data, thereby determining the reliable time domain of the target data. Based on the actual data interaction process, this step-by-step search method ensures that each step in determining the reliable time domain is traceable, thus obtaining a reliable time domain that can be used to characterize the data's storage time.

[0076] Furthermore, it helps to improve the correlation between the determined time stamp and the target data, effectively enhancing the rigor and reliability of the trusted time domain.

[0077] To make the above-mentioned objects, features and advantages of this disclosure more apparent and understandable, preferred embodiments are described below in detail with reference to the accompanying drawings.

[0078] It should be understood that the above general description and the following detailed description are merely exemplary and explanatory, and are not intended to limit the technical solutions of this disclosure. Attached Figure Description

[0079] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the accompanying drawings used in the embodiments will be briefly described below. These drawings are incorporated in and constitute a part of this specification. They illustrate embodiments conforming to this disclosure and, together with the specification, serve to explain the technical solutions of this disclosure. It should be understood that the following drawings only show some embodiments of this disclosure and should not be considered as limiting the scope. Those skilled in the art can obtain other related drawings based on these drawings without creative effort.

[0080] Figure 1 A schematic diagram of a data system provided by an embodiment of this disclosure is shown;

[0081] Figure 2 This illustration shows a data interaction process provided by an embodiment of the present disclosure;

[0082] Figure 3 A flowchart of a data processing method provided by an embodiment of this disclosure is shown;

[0083] Figure 4 A schematic diagram of a data processing procedure provided by an embodiment of this disclosure is shown;

[0084] Figure 5 A flowchart of another data processing method provided by an embodiment of this disclosure is shown;

[0085] Figure 6 One of the schematic diagrams of a data processing apparatus provided in an embodiment of the present disclosure is shown;

[0086] Figure 7 One of the schematic diagrams of a data processing apparatus provided in an embodiment of the present disclosure is shown;

[0087] Figure 8 A schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure is shown. Detailed Implementation

[0088] To make the objectives, technical solutions, and advantages of the embodiments of this disclosure clearer, the technical solutions of the embodiments of this disclosure will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this disclosure, and not all of them. The components of the embodiments of this disclosure described and shown in the accompanying drawings can generally be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of this disclosure provided in the accompanying drawings is not intended to limit the scope of the claimed disclosure, but merely represents selected embodiments of this disclosure. All other embodiments obtained by those skilled in the art based on the embodiments of this disclosure without inventive effort are within the scope of protection of this disclosure.

[0089] It should be noted that similar labels and letters in the following figures indicate similar items. Therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0090] In this document, the term "and / or" merely describes a relationship, indicating that three relationships can exist. For example, A and / or B can represent three cases: A alone, A and B simultaneously, and B alone. Furthermore, the term "at least one" in this document means any combination of at least two of any one or more elements. For example, including at least one of A, B, and C can mean including any one or more elements selected from the set consisting of A, B, and C.

[0091] Research has found that in the process of data storage management through blockchain-based databases, for each piece of data uploaded by a user, in order to determine the time range to which the data belongs, most methods first identify the data that the user uploaded data was converted and written into the database, and then delineate the corresponding trusted time domain based on the most recent received time stamp before and the most recent received time stamp after the data. However, this method is relatively coarse, and the time span of the determined trusted time domain may be large, with weak correlation to the data itself.

[0092] Considering the shortcomings of traditionally determined reliable time domains, such as their coarseness and low correlation with user-uploaded data, this disclosure provides a data processing method. Upon receiving a time query request for target data, the method can trace back step by step according to the data interaction process and the time sequence to obtain the time stamps assigned by the time synchronization terminal before and after the target data. This allows the reliable time domain of the target data to be determined. Based on the actual data interaction process, this step-by-step search method ensures that each step in the reliable time domain determination process is traceable, thereby obtaining a reliable time domain that can be used to characterize the data's storage time.

[0093] The shortcomings of the above solutions are the result of the inventor's practical experience and careful research. Therefore, the discovery process of the above problems and the solutions proposed in this disclosure below should be considered as the inventor's contribution to this disclosure.

[0094] To facilitate understanding of this embodiment, a data processing method disclosed in this disclosure will first be described in detail. The executing entity of the data processing method provided in this disclosure can be an electronic device with a certain computing power. In this embodiment, the electronic device can be a server. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud storage, big data, and artificial intelligence platforms.

[0095] In other embodiments, the electronic device can be a terminal device or other processing device. The terminal device can be a user equipment (UE), user terminal, terminal, computing device, etc., and other processing devices can be devices including a processor and memory, which are not limited here. In some possible implementations, the data processing method can be implemented by the processor calling computer-readable instructions stored in memory.

[0096] The following describes a data processing method provided by an embodiment of this disclosure.

[0097] Please see Figure 1 , Figure 1 This is a schematic diagram of a data system provided in an embodiment of this disclosure. To assist in data storage and management, a data system can be built to process the data. For example... Figure 1 As shown, the data system includes a client, a relay database, and a time synchronization terminal. The relay database can communicate with the client and the time synchronization terminal, respectively.

[0098] Here, the client can be a trusted database created by the user. Optionally, it can be created locally on the user's terminal device or based on cloud storage space. Data in the client is stored in a blockchain manner. Users can upload data to the client via desktop computers, laptops, tablets, or other terminals. The client can convert the received data into business data and process it on the blockchain. The client can send the processed business data to the relay database and can also receive data returned from the relay database.

[0099] Here, the relay database can be a trusted database that relays data between the client and the timing terminal, and the data in the relay database is stored in a blockchain manner. For example, the relay database can be a trusted ledger database (LedgerDB), etc. It should be noted that the relay database has the ability to interact with the timing terminal. Specifically, the relay database can transform the received business data according to a data structure matching the relay database, such as decoding and specific encoding to obtain transformed relay data, and then write the transformed relay data. Furthermore, the relay database can also send the relay data to the timing terminal for timing synchronization at a certain sending period, and receive the timing data returned by the timing terminal. The relay database can transform the received timing data according to a data structure matching the relay database, and write the transformed return data. Moreover, the relay database can send the return data back to the client at a certain return period.

[0100] Here, the time synchronization terminal can be an authoritative time synchronization server. The time synchronization terminal can convert the relay data received from the relay database according to the data structure that matches the time synchronization terminal, such as decoding and specific encoding to obtain the converted data, assign a time synchronization timestamp to the converted data, and return the time-stamped data to the relay database.

[0101] In some implementations, the client can receive business data uploaded by the user, process the business data for blockchain uploading, obtain multiple business data on the blockchain, and upload the business data that has been uploaded to the transit database.

[0102] Optionally, when the client uploads the business data to the relay database, it can send a summary of the business data to the relay database. Specifically, the summary of the business data may include the data name of the business data, the data number of the business data in the client, the address of the business data in the client's blockchain, etc.

[0103] The business data refers to the data generated by users during their own business processes, and the content of the business data is related to the users.

[0104] For example, the user is an e-commerce platform, and the business data may be order records completed by the e-commerce platform.

[0105] The relay database can convert received business data into corresponding relay data and write it into the relay database, and forward the relay data to the time synchronization terminal.

[0106] Optionally, when the relay database forwards the relay data to the time synchronization terminal, it may send a summary of the relay data to the time synchronization terminal. Specifically, the summary of the relay data may include the data name of the relay data, the data number of the relay data in the relay database, and the address of the relay data in the blockchain of the relay database.

[0107] The timing terminal can assign a timing timestamp to the received relay data and send the timing data obtained by the relay data and the corresponding timing timestamp back to the relay database.

[0108] After receiving the timing data returned by the timing terminal, the relay database can obtain the return data based on the received timing data and the corresponding relay data, write it into the relay database, and return the obtained return data to the client. The client can receive the return data returned by the relay database.

[0109] In other implementations, after receiving the return data from the relay database, the client can also update the business data corresponding to the received return data based on the received return data.

[0110] Based on the above, it can be known that the returned data is obtained from the timing data and the corresponding relay data. The timing data includes a timing timestamp. Therefore, the returned data includes a timing timestamp. Thus, the client can determine the business data corresponding to the timing timestamp from multiple business data in the client based on the timing timestamp included in the received returned data, and then mark the timing timestamp corresponding to the business data.

[0111] You can refer to this at the same time. Figure 2 , Figure 2 This is a schematic diagram of a data interaction process provided in an embodiment of this disclosure. Figure 2 As shown, the client can upload business data for blockchain on-chain processing to the relay database. The relay database can convert the received business data into corresponding relay data, write the relay data into the relay database, and then forward the relay data to the time synchronization terminal. The time synchronization terminal can assign a time synchronization timestamp to the received relay data and send the time synchronization data obtained through the relay data and the corresponding time synchronization timestamp back to the relay database. After receiving the time synchronization data sent back by the time synchronization terminal, the relay database can obtain the return data based on the received time synchronization data and the relay data corresponding to the time synchronization data, write the return data into the relay database, and then return the obtained return data to the client. The client can receive the return data returned by the relay database and update the business data corresponding to the return data.

[0112] Please see Figure 3 , Figure 3 A flowchart illustrating a processing method provided in an embodiment of this disclosure. Figure 3 As shown in the embodiments of this disclosure, the data processing method includes:

[0113] S301: In response to a time query request for target data, determine the target on-chain time of the target data, wherein the target data is any one of multiple business data uploaded to the blockchain through the client.

[0114] In this step, the client can process multiple business data uploaded by the user on the blockchain. When a time query request is received from the user, the time query request includes the data information and request information of the target data that the user needs to query. Based on the data information and the request information, the target data can be filtered out from multiple business data and the blockchain upload time of the target data can be obtained.

[0115] The data information can be information that indicates the target data. For example, the data information may include the data number of the target data and the address of the target data in the blockchain. The target data can be found from multiple business data on the chain based on the data information.

[0116] The request information may represent the type of time that the user needs to query. For example, the request information may include a prior trusted time point, a subsequent trusted time point, a trusted time period, etc., so as to subsequently display the time query results that match the request information to the user.

[0117] For example, you can also refer to Figure 4 , Figure 4 This is a schematic diagram of a data processing procedure provided for a disclosed embodiment. For example... Figure 4 As shown, the client writes data B0-B10, a total of 11 data entries, and the relay database writes data A0-A16, a total of 17 data entries. Here, the numerical sequence numbers in the client and relay databases indicate the time order in which the data was written, with data entries with smaller numerical sequence numbers being written before those with larger numerical sequence numbers.

[0118] It should be noted that the amount of data written to the client and the amount of data written to the relay database shown in the figure are only examples, and the amount of data written in actual applications is not limited to these.

[0119] In this example, based on the time query request, the target data to be queried is found to be data B6 from the data B0-B10 uploaded to the blockchain in the client, and the target time of data B6 being uploaded to the blockchain is determined to be T5.

[0120] S302: Based on the time order of each business data being uploaded to the blockchain, obtain the first time synchronization timestamp assigned to the first relay data by the time synchronization terminal after the relay database first uploads the first relay data to the time synchronization terminal after receiving the first upload data uploaded by the client. The first upload data is the data that the client first sends to the relay database after uploading the target data to the blockchain.

[0121] In this step, the time order of each business data being uploaded to the blockchain can be determined first. Based on the time order, the data that the client first sends to the relay database after uploading the target data to the blockchain is determined, and this data is determined as the first uploaded data. Then, the first relay data that the relay database first uploads to the time synchronization terminal after receiving the first uploaded data uploaded by the client is determined, thereby obtaining the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data.

[0122] The relay database stores multiple relay data, and the first relay data is the relay data that the relay database sends to the time synchronization terminal for the first time from the multiple relay data stored after receiving the first uploaded data.

[0123] Accordingly, in one possible implementation, the first time synchronization timestamp can be obtained through the following steps:

[0124] For multiple business data that have already been uploaded to the blockchain, the order in which each business data is uploaded to the blockchain is determined based on the upload time of each business data.

[0125] Based on the time order of each business data being uploaded to the blockchain, the first uploaded data that the client first sends to the transit database after uploading the target data to the blockchain is determined from the multiple business data;

[0126] For the multiple relay data stored in the relay database, based on the first sending time of each relay data sent to the time synchronization terminal by the relay database, the first relay data that was first uploaded to the time synchronization terminal after receiving the first uploaded data is determined from the multiple relay data, and the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data is determined. The multiple relay data includes the relay data obtained by the relay database after processing the first uploaded data.

[0127] Specifically, after determining the first uploaded data, the first sending time when the relay database sends each relay data to the time synchronization terminal and the second receiving time when the relay database receives the first uploaded data can be determined. By comparing the first sending time and the second receiving time, the first relay data that the relay database first uploads to the time synchronization terminal after receiving the first uploaded data can be determined, and the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data can be determined.

[0128] Therefore, in some implementations, the second receiving time when the relay database receives the first uploaded data and the first sending time when the relay database sends each stored relay data to the time synchronization terminal can be obtained. Then, based on the obtained first sending time and second receiving time, a first target sending time in at least one first sending time after the second receiving time can be determined. Here, the time difference between the first target sending time and the second receiving time is the smallest. Then, the target relay data uploaded to the time synchronization terminal at the first target sending time can be determined from the plurality of relay data. Then, the first time synchronization timestamp assigned by the time synchronization terminal to the target relay data can be obtained.

[0129] For example, you can also refer to Figure 4Based on the on-chain order of data 0-10 in the client, it can be determined that the first uploaded data sent by the client to the relay database after data B6 is on the blockchain is data B9. Here, the client sends data B9 at time T6, which is after T5. Then, for data A0-A16 stored in the relay database, it can be determined that the relay data that received B9 is data A11. The second receiving time of B9 received by the relay database can be determined to be T7, which is after T6. Then, the first target sending time after T7 with the smallest time difference from T7 can be found to be T8. Thus, the first relay data uploaded by the relay database to the time synchronization terminal at time T8 is data A12. Therefore, the first time synchronization timestamp assigned by the time synchronization terminal to data A12 can be obtained as T9.

[0130] S303: Based on the first receiving time of each return data received from the relay database and the target on-chain time, obtain the second timing timestamp indicated by the last timing data received by the relay database from the timing terminal before sending the target return data, wherein the target return data is the last data received by the client from the relay database before the target on-chain time.

[0131] In this step, the first receiving time of each return data received by the client from the relay database can be obtained. Then, combined with the target on-chain time, the last target return data received by the client from the relay database before the target on-chain time can be determined. Then, the second time synchronization timestamp indicated by the last time synchronization data received by the relay database from the time synchronization terminal before the relay database sends the target return data to the client can be determined.

[0132] Accordingly, in one possible implementation, the second time synchronization timestamp can be obtained through the following steps:

[0133] The first reception time of each returned data received from the relay database is obtained. The returned data is data obtained by the relay database through the relay data and the time synchronization timestamp corresponding to the relay data. The time synchronization timestamp is time data obtained from the time synchronization data corresponding to the relay data received from the time synchronization end.

[0134] Based on each first receiving time and the target on-chain time, determine the target backhaul data that the client last received from the relay database before the target on-chain time;

[0135] The third receiving time corresponding to each time synchronization data returned by the time synchronization terminal is obtained from the relay database, and the second target sending time when the relay database sends the target return data. The time synchronization data is the data obtained by the time synchronization terminal based on the received relay data and the time synchronization timestamp assigned to the relay data.

[0136] Based on the acquired third receiving times and the second target sending time, the last timing data received before the relay database sends the target return data is determined, along with the second timing timestamp included in the last timing data.

[0137] Specifically, after obtaining the third receiving time corresponding to each time synchronization data returned by the time synchronization terminal when the relay database receives it, and the second target sending time when the relay database sends the target return data, the last time synchronization data received before the relay database sends the target return data to the client can be determined by comparing the third receiving time and the second target sending time. Thus, the second time synchronization timestamp included in the last time synchronization data can be determined.

[0138] Therefore, in some implementations, a third target reception time can be determined based on the acquired third reception time and the second target transmission time, in at least one third reception time before the second target transmission time, where the time difference between the third target reception time and the second target transmission time is the smallest. Then, the timing data received by the relay database at the third target reception time and sent by the timing terminal is taken as the last timing data received, and the timing timestamp included in the last timing data is determined as the second timing timestamp.

[0139] For example, you can also refer to Figure 4 Based on the first reception time of each return data received by the client from the relay database, it can be determined that the first reception time of the last target return data received by the client from the relay database before the target on-chain time T5 is T4. Here, T4 is before T5. At the same time, it can be determined that the service data that received the target return data is data B4. Thus, the target return data sent to the client can be determined in the relay database as data A5. The second target sending time when the relay database sends data A5 is T3. Here, T3 is before T4. Then, the third target reception time with the smallest time difference between T3 and T2 can be found. Thus, the timing data received by the relay database at T2 and sent by the timing terminal is determined as the last timing data received. Then, the second timing timestamp included in the last timing data is determined as T1.

[0140] S304: Determine the reliable time domain of the target data based on the first time synchronization timestamp and the second time synchronization timestamp.

[0141] In this step, after obtaining the first time synchronization timestamp and the second time synchronization timestamp, the time domain determined by using the first time synchronization timestamp as the right time endpoint and the second time synchronization timestamp as the left time endpoint can be determined as the reliable time domain of the target data.

[0142] Here, for the target data, the storage time of the target data will not be later than the first time synchronization timestamp, and the storage time of the target data will not be earlier than the second time synchronization timestamp.

[0143] For example, following the above example, if the first time stamp is T9 and the second time stamp is T1, the time domain formed by T1 as the left time endpoint and T9 as the right time endpoint can be determined as the reliable time domain of data B6.

[0144] The data processing method provided in this embodiment, upon receiving a time query request for target data, can, based on the target on-chain time of the target data, the on-chain time order of various business data, and the reception time of each return data received from the transit database, trace back step by step according to the data interaction process and the time sequence, thereby obtaining the time stamps assigned by the time synchronization terminal before and after the target data. This allows for the determination of the credible time domain of the target data. For the target data, based on the actual data interaction process, this step-by-step search method ensures that each step in the determination of the credible time domain is traceable, thus obtaining a credible time domain that can be used to characterize the data's storage time.

[0145] Furthermore, it helps to improve the correlation between the determined time stamp and the target data, effectively enhancing the rigor and reliability of the trusted time domain.

[0146] Please see Figure 5 , Figure 5 A flowchart of another data processing method provided in this disclosure embodiment, such as Figure 5 As shown in the embodiments of this disclosure, the data processing method includes:

[0147] S501: In response to a time query request for target data, determine the target on-chain time of the target data, wherein the target data is any one of multiple business data uploaded to the blockchain through the client.

[0148] S502: Based on the time order of each business data being uploaded to the blockchain, obtain the first time synchronization timestamp assigned to the first relay data by the time synchronization terminal after the relay database receives the first upload data uploaded by the client and uploads the first relay data to the time synchronization terminal for the first time. The first upload data is the data that the client sends to the relay database for the first time after the target data is uploaded to the blockchain.

[0149] S503: Based on the first receiving time of each return data received from the relay database and the target on-chain time, obtain the second timing timestamp indicated by the last timing data received by the relay database from the timing terminal before sending the target return data, wherein the target return data is the last data received by the client from the relay database before the target on-chain time.

[0150] S504: Determine the reliable time domain of the target data based on the first time synchronization timestamp and the second time synchronization timestamp.

[0151] The descriptions of steps S501 to S504 can refer to the descriptions of steps S301 to S304, and can achieve the same technical effect and solve the same technical problem, so they will not be repeated here.

[0152] S505: Based on the trusted time domain, display the time query results corresponding to the time query request to the user; the time query results include one or more of the following: earlier trusted time point, later trusted time point, trusted time period.

[0153] In this step, after determining the reliable time domain of the target data, the user can be shown the time query results corresponding to the request information indicated by the time query request.

[0154] Optionally, the request information indicated by the time query request may be a prior credible time point of the target data, a subsequent credible time point of the target data, or a credible time period of the target data.

[0155] Accordingly, in some embodiments, when the request information indicated by the time query request is a prior trusted time point of the target data to be queried, the second time synchronization timestamp can be displayed as the prior trusted time point.

[0156] In other embodiments, when the request information indicated by the time query request is a later trusted time point for the target data, the first time stamp can be displayed as the later trusted time point.

[0157] In other embodiments, when the request information indicated by the time query request is a trusted time period for querying target data, the trusted time domain can be displayed as the trusted time period.

[0158] Those skilled in the art will understand that, in the above-described method of the specific implementation, the order in which each step is written does not imply a strict execution order and does not constitute any limitation on the implementation process. The specific execution order of each step should be determined by its function and possible internal logic.

[0159] The data processing method provided in this embodiment, upon receiving a time query request for target data, can, based on the target on-chain time of the target data, the on-chain time order of various business data, and the reception time of each returned data received from the transit database, trace back step by step according to the data interaction process, thereby obtaining the time stamps assigned by the time synchronization terminal before and after the target data. This allows for the determination of the reliable time domain of the target data. For the target data, based on the actual data interaction process, this step-by-step search method ensures that each step in the reliable time domain determination process is traceable, thus obtaining a reliable time domain that can be used to characterize the data storage time.

[0160] Furthermore, it helps to improve the correlation between the determined time stamp and the target data, effectively enhancing the rigor and reliability of the trusted time domain.

[0161] Based on the same inventive concept, this disclosure also provides a data processing device corresponding to the data processing method. Since the principle of the device in this disclosure for solving the problem is similar to the data processing method described above in this disclosure, the implementation of the device can refer to the implementation of the method, and repeated details will not be repeated.

[0162] Please see Figure 6 and Figure 7 , Figure 6 This is one of the schematic diagrams of a data processing apparatus provided in an embodiment of the present disclosure. Figure 7 This is a second schematic diagram of a data processing apparatus provided in an embodiment of this disclosure. The data processing apparatus provided in this embodiment is applied to the aforementioned client. The data processing apparatus may be the same device under a different name as the client, or it may be part of the client. Modules in the data processing apparatus and corresponding functional components in the client can be coupled together to achieve the same function. For example... Figure 6 As shown in the figure, the data processing apparatus 600 provided in this embodiment includes:

[0163] The time determination module 610 is used to respond to a time query request for target data and determine the target on-chain time of the target data, wherein the target data is any one of multiple business data that are uploaded to the blockchain through the client.

[0164] The first data acquisition module 620 is used to acquire, based on the time order of each business data being uploaded to the blockchain, the first time stamp assigned by the time synchronization terminal to the first relay data after the relay database receives the first uploaded data uploaded by the client and first uploads the first relay data to the time synchronization terminal. The first uploaded data is the data that the client first sends to the relay database after the target data is uploaded to the blockchain.

[0165] The second data acquisition module 630 is used to acquire, based on the first receiving time of each return data received from the relay database and the target on-chain time, the second timing timestamp indicated by the last timing data received by the relay database from the timing terminal before sending the target return data, wherein the target return data is the last data received by the client from the relay database before the target on-chain time;

[0166] The time domain determination module 640 is used to determine the reliable time domain of the target data based on the first time synchronization timestamp and the second time synchronization timestamp.

[0167] In one optional implementation, the first data acquisition module 620 is specifically used for:

[0168] For multiple business data that have already been uploaded to the blockchain, the order in which each business data is uploaded to the blockchain is determined based on the upload time of each business data.

[0169] Based on the time order of each business data being uploaded to the blockchain, the first uploaded data that the client first sends to the transit database after uploading the target data to the blockchain is determined from the multiple business data;

[0170] For the multiple relay data stored in the relay database, based on the first sending time of each relay data sent to the time synchronization terminal by the relay database, the first relay data that was first uploaded to the time synchronization terminal after receiving the first uploaded data is determined from the multiple relay data, and the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data is determined. The multiple relay data includes the relay data obtained by the relay database after processing the first uploaded data.

[0171] In an optional implementation, when the first data acquisition module 620 is used to determine, from the plurality of relay data, the first relay data that was first uploaded to the time synchronization terminal after receiving the first uploaded data, at the first sending time when each relay data is sent to the time synchronization terminal based on the relay database, and to determine the first time synchronization timestamp assigned by the time synchronization terminal to the first relay data, specifically:

[0172] The second receiving time when the relay database receives the first uploaded data, and the first sending time when the relay database sends each stored relay data to the time synchronization terminal are obtained;

[0173] Based on the acquired first transmission time and second reception time, a first target transmission time is determined in at least one first transmission time after the second reception time, wherein the time difference between the first target transmission time and the second reception time is minimized;

[0174] The first relay data that was uploaded to the timing terminal at the first target transmission time is determined from the plurality of relay data;

[0175] Obtain the first time stamp assigned by the time synchronization terminal to the first relay data.

[0176] In one optional implementation, the second data acquisition module 630 is specifically used for:

[0177] The first reception time of each returned data received from the relay database is obtained. The returned data is data obtained by the relay database through the relay data and the time synchronization timestamp corresponding to the relay data. The time synchronization timestamp is time data obtained from the time synchronization data corresponding to the relay data received from the time synchronization end.

[0178] Based on each first receiving time and the target on-chain time, determine the target backhaul data that the client last received from the relay database before the target on-chain time;

[0179] The third receiving time corresponding to each time synchronization data returned by the time synchronization terminal is obtained from the relay database, and the second target sending time when the relay database sends the target return data. The time synchronization data is the data obtained by the time synchronization terminal based on the received relay data and the time synchronization timestamp assigned to the relay data.

[0180] Based on the acquired third receiving times and the second target sending time, the last timing data received before the relay database sends the target return data is determined, along with the second timing timestamp included in the last timing data.

[0181] In an optional implementation, when the second data acquisition module 630 determines, based on the acquired third receiving time and the second target sending time, the last timing data received before the relay database sends the target return data, and the second timing timestamp included in the last timing data, it is specifically configured to:

[0182] Based on the acquired third reception times and the second target transmission time, a third target reception time is determined in at least one third reception time before the second target transmission time, wherein the time difference between the third target reception time and the second target transmission time is minimized;

[0183] The timing data received by the relay database at the third target receiving time and sent by the timing terminal shall be regarded as the last timing data received.

[0184] Determine the second time stamp included in the last time synchronization data.

[0185] In one alternative implementation, such as Figure 7 As shown, the device further includes a result display module 650, which is used for:

[0186] Based on the trusted time domain, the time query results corresponding to the time query request are displayed to the user;

[0187] The time query results include one or more of the following: earlier reliable time point, later reliable time point, and reliable time period.

[0188] In one alternative implementation, such as Figure 7 As shown, the device further includes a data processing module 660, which is used for:

[0189] Receive business data uploaded by users;

[0190] The business data is processed on the blockchain to obtain multiple business data on the blockchain.

[0191] The business data to be uploaded to the blockchain is uploaded to the relay database. The relay database can convert the received business data into corresponding relay data and write it into the relay database, and forward the relay data to the time synchronization terminal. The time synchronization terminal can assign a time synchronization timestamp to the received relay data and send the time synchronization data obtained by the relay data and the corresponding time synchronization timestamp back to the relay database. After receiving the time synchronization data sent back by the time synchronization terminal, the relay database can obtain the return data according to the received time synchronization data and the corresponding relay data and write it into the relay database, and return the obtained return data to the client.

[0192] Receive the data returned by the relay database.

[0193] In an optional implementation, the data processing module 660 is further configured to:

[0194] Based on the received feedback data, the service data corresponding to the feedback data is updated.

[0195] In some embodiments, the functions or modules of the apparatus provided in this disclosure can be used to perform the methods described in the above method embodiments. The specific implementation can be referred to the description of the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0196] The data processing apparatus provided in this embodiment, upon receiving a time query request for target data, can, based on the target on-chain time of the target data, the on-chain time order of various business data, and the reception time of each returned data received from the transit database, trace back step by step according to the data interaction process and the time sequence, thereby obtaining the time stamps assigned by the time synchronization terminal before and after the target data. This allows the determination of the credible time domain of the target data. For the target data, based on the actual data interaction process, this step-by-step search method ensures that each step in the determination of the credible time domain is traceable, thus obtaining a credible time domain that can be used to characterize the data storage time.

[0197] Furthermore, it helps to improve the correlation between the determined time stamp and the target data, effectively enhancing the rigor and reliability of the trusted time domain.

[0198] Corresponding to the data processing method described above, this disclosure also provides an electronic device 800, such as... Figure 8 The diagram shown is a structural schematic of an electronic device 800 provided in an embodiment of this disclosure, including:

[0199] The system includes a processor 810, a memory 820, and a bus 830. The memory 820 stores execution instructions and includes a main memory 821 and an external memory 822. The main memory 821, also known as internal memory, is used to temporarily store the computational data in the processor 810 and the data exchanged with external memory 822 such as a hard disk. The processor 810 exchanges data with the external memory 822 through the main memory 821. When the computer device 800 is running, the processor 810 and the memory 820 communicate through the bus 830, enabling the processor 810 to execute the steps of the data processing method described above.

[0200] This disclosure also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, performs the steps of the data processing method described in the above method embodiments. The storage medium may be a volatile or non-volatile computer-readable storage medium.

[0201] This disclosure also provides a computer program product, which includes computer instructions. When the computer instructions are executed by a processor, they can perform the steps of the data processing method described in the above method embodiments. For details, please refer to the above method embodiments, which will not be repeated here.

[0202] The aforementioned computer program product can be implemented through hardware, software, or a combination thereof. In one optional embodiment, the computer program product is specifically embodied in a computer storage medium; in another optional embodiment, the computer program product is specifically embodied in a software product, such as a software development kit (SDK), etc.

[0203] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the devices and apparatuses described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. In the several embodiments provided in this disclosure, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. The apparatus embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. Furthermore, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Another point is that the displayed or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces; the indirect coupling or communication connection of devices or units may be electrical, mechanical, or other forms.

[0204] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0205] In addition, the functional units in the various embodiments of this disclosure can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0206] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a processor-executable, non-volatile, computer-readable storage medium. Based on this understanding, the technical solution of this disclosure, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this disclosure. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0207] Finally, it should be noted that the above-described embodiments are merely specific implementations of this disclosure, used to illustrate the technical solutions of this disclosure, and not to limit it. The protection scope of this disclosure is not limited thereto. Although this disclosure has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that any person skilled in the art can still modify or easily conceive of changes to the technical solutions described in the foregoing embodiments, or make equivalent substitutions for some of the technical features, within the scope of the technology disclosed in this disclosure. Such modifications, changes, or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this disclosure, and should all be covered within the protection scope of this disclosure. Therefore, the protection scope of this disclosure should be determined by the protection scope of the claims.

Claims

1. A data processing method, characterized by, The method comprises: determining a target on-chain time of target data in response to a time query request for the target data, the target data being any one of a plurality of business data on-chained by a client to a blockchain; based on a time sequence of on-chaining of each business data, obtaining a first timing timestamp of the first relay data uploaded by the relay database to the time service end after the first upload data uploaded by the client is received for the first time, the first timing timestamp being timing of the first relay data by the time service end; based on a first reception time of each return data received from the relay database and the target on-chain time, obtaining a second timing timestamp indicated by the last timing data received from the time service end before the target return data is sent, the target return data being the last data received by the client from the relay database before the target on-chain time; based on the first timing timestamp and the second timing timestamp, determining a trusted time domain of the target data.

2. The method of claim 1, wherein, The method comprises: for a plurality of business data that have been on-chained, determining a time sequence of on-chaining of each business data in the plurality of business data based on the on-chaining time of each business data; based on the time sequence of on-chaining of each business data, determining the first upload data sent by the client to the relay database for the first time after the target data is on-chained to the blockchain from the plurality of business data; for a plurality of relay data stored in the relay database, based on a first sending time of each relay data sent by the relay database to the time service end, determining the first relay data uploaded to the time service end for the first time after the first upload data is received from the plurality of relay data, and determining a first timing timestamp of the first relay data timed by the time service end, the plurality of relay data including relay data obtained by the relay database after processing the first upload data.

3. The method of claim 2, wherein, The method comprises: obtaining a second reception time of the first upload data received by the relay database, and a corresponding first sending time of each relay data stored by the relay database when sent to the time service end; determining a first target sending time in the at least one first sending time after the second receiving time based on the obtained respective first sending times and the second receiving time, the first target sending time having a minimum time difference with the second receiving time; determining first relay data sent to the time service end at the first target sending time from the plurality of relay data; obtaining a first time service timestamp of the time service end for the first relay data.

4. The method of claim 1, wherein, The method further comprises the following steps of: obtaining the first receiving time of the respective backhaul data received from the relay database, the backhaul data being data obtained by the relay database from the relay data and a time service timestamp corresponding to the relay data, the time service timestamp being time data obtained from time service data corresponding to the relay data received from the time service end; determining target backhaul data last received by the client from the relay database before the target uplink time based on the respective first receiving times and the target uplink time; obtaining a third receiving time of the relay database corresponding to each time service data returned by the time service end, and a second target sending time of the relay database sending the target backhaul data, the time service data being data obtained by the time service end from received relay data and a time service timestamp for the relay data; determining the last time service data received before the relay database sends the target backhaul data based on the obtained respective third receiving times and the second target sending time, and a second time service timestamp included in the last time service data.

5. The method of claim 4, wherein, The method further comprises the following steps of: determining a third target receiving time in the at least one third receiving time before the second target sending time based on the obtained respective third receiving times and the second target sending time, the third target receiving time having a minimum time difference with the second target sending time; determining the last time service data received by the relay database at the third target receiving time as the last received time service data sent by the time service end; determining the second time service timestamp included in the last time service data.

6. The method of claim 1, wherein, After determining the trusted time domain of the target data based on the first time service timestamp and the second time service timestamp, the method further comprises the following steps of: displaying a time query result corresponding to the time query request for a user based on the trusted time domain; the time query result comprising one or more of the following: an earlier trusted time point, a later trusted time point, and a trusted time period.

7. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receive business data uploaded by users; The business data is processed on the blockchain to obtain multiple business data on the blockchain. The business data to be uploaded to the blockchain is uploaded to the relay database. The relay database can convert the received business data into corresponding relay data and write it into the relay database, and forward the relay data to the time synchronization terminal. The time synchronization terminal can assign a time synchronization timestamp to the received relay data and send the time synchronization data obtained by the relay data and the corresponding time synchronization timestamp back to the relay database. After receiving the time synchronization data sent back by the time synchronization terminal, the relay database can obtain the return data according to the received time synchronization data and the corresponding relay data and write it into the relay database, and return the obtained return data to the client. Receive the data returned by the relay database.

8. The method of claim 7, wherein, After receiving the return data from the relay database, the method further includes: Based on the received feedback data, the service data corresponding to the feedback data is updated.

9. A data processing apparatus, characterized by, The data processing device includes: The time determination module is used to respond to a time query request for target data and determine the target on-chain time of the target data, wherein the target data is any one of multiple business data that are uploaded to the blockchain through the client. The first data acquisition module is used to acquire, based on the time order of each business data being uploaded to the blockchain, the first time stamp assigned by the time synchronization terminal to the first relay data after the relay database receives the first uploaded data uploaded by the client and first uploads the first relay data to the time synchronization terminal. The first uploaded data is the data that the client first sends to the relay database after the target data is uploaded to the blockchain. The second data acquisition module is used to acquire, based on the first receiving time of each return data received from the relay database and the target on-chain time, the second timing timestamp indicated by the last timing data received by the relay database from the timing terminal before sending the target return data, wherein the target return data is the last data received by the client from the relay database before the target on-chain time; The time domain determination module is used to determine the reliable time domain of the target data based on the first time synchronization timestamp and the second time synchronization timestamp.

10. An electronic device, comprising: include: The device includes a processor, a memory, and a bus. The memory stores machine-readable instructions executable by the processor. When the electronic device is running, the processor communicates with the memory via the bus. When the machine-readable instructions are executed by the processor, they perform the steps of the data processing method as described in any one of claims 1 to 8.

11. A computer readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, performs the steps of the data processing method as described in any one of claims 1 to 8.

Images