A method of data updating and related apparatus

Abstract

Embodiments of the present application disclose a data updating method, which can use multiple bills to update target asset data in parallel, thereby improving the efficiency of updating data. The method comprises the following steps: in the case that a terminal uses a first bill to update target asset data, the terminal acquires a second bill, the second bill being used to update the target asset data; the terminal judges whether the first bill and the second bill are bills of the same type; if the terminal judges that the first bill and the second bill are bills of the same type, the terminal uses the first bill and the second bill to update the target asset data in parallel. Through the above method, the bills of the same type sent by multiple users can be used to update the target asset data in parallel, the target asset data can be updated by multiple users, and the efficiency of updating is improved.

Description

Technical Field

[0001] This application relates to the field of computers, and more particularly to a method for updating data and related equipment. Background Technology

[0002] In enterprise management systems, documents are used to record asset data, such as financial information, physical information, information on ancillary equipment, and information on usage and allocation of assets.

[0003] During production and management, users may handle assets in various ways. This necessitates updating the target document recording asset information based on asset changes. For example, after a user applies for asset requisition, the target document needs to be updated to show that the asset has already been requisitioned, preventing other users from repeatedly applying for the same asset. The specific update process is as follows: First, the user submits an application document. The target document is updated based on the user's application document, generating a document change record to record the updated asset data. This record provides other users with the latest asset information. During the target document update process, the target document is locked to prevent other application documents from updating the asset card, thus preventing conflicts between update operations.

[0004] However, a target document can only be updated based on one application document at a time. When multiple users need to make changes to multiple assets under the same target document, the target document can only be updated based on one application document from one user at a time. Other users' update requests can only wait, resulting in low update efficiency and wasting users' time. Summary of the Invention

[0005] This application provides a data updating method to improve the efficiency of the update process.

[0006] This application provides a method for updating data, including:

[0007] When the terminal updates the target asset data using the first document, the terminal obtains a second document, which is used to update the target asset data.

[0008] The terminal determines whether the first document and the second document are of the same type.

[0009] If so, the terminal uses the first document and the second document in parallel to update the target asset data.

[0010] In one possible implementation, before the terminal updates the target asset data using the first document and the second document in parallel, the method further includes: the terminal acquiring the first asset data corresponding to the first document and the second asset data corresponding to the second document;

[0011] The terminal determines whether the first asset data and the second asset data are the same, and the first asset data and the second asset data are part of the asset data within the target asset data;

[0012] If they are different, the terminal triggers the step of updating the target asset data in parallel using the first document and the second document.

[0013] In one possible implementation, after the terminal updates the target asset data using the first document and the second document in parallel, the method further includes: the terminal storing the updated first asset data and the updated second asset data into a storage stack, wherein the storage stack stores the first asset data and the second asset data, and the storage stack is a stack data structure.

[0014] In one possible implementation, the terminal obtains a revocation request, which is used to instruct the terminal to revoke the use of the first document to update the first asset data, or to instruct the terminal to revoke the use of the second document to update the second asset data. The revocation request includes a first ID or a second ID, where the first ID is the sequence number of the first asset data stored in the storage address, and the second ID is the sequence number of the second asset data stored in the storage address.

[0015] When the revocation request includes a first ID, the terminal obtains the first asset data based on the first ID;

[0016] The terminal generates third asset data based on the first asset data, and the third asset data is the same as the data in the first asset data.

[0017] When the revocation request includes a second ID, the terminal obtains the second asset data based on the second ID;

[0018] The terminal generates fourth asset data based on the second asset data, and the fourth asset data is the same as the second asset data.

[0019] In one possible implementation, the first document and the second document include a type identifier, which is used to distinguish the user type using the first document and the second document;

[0020] The terminal determines whether the first document and the second document are of the same type by including:

[0021] The terminal determines whether the first document and the second document are documents of the same type based on the type identifier of the first document and the type identifier of the second document.

[0022] This application also provides a terminal, including:

[0023] The acquisition unit is used to acquire a second document when the target asset data is updated using the first document, wherein the second document is used to update the target asset data;

[0024] The judgment unit is used to determine whether the first document and the second document are documents of the same type.

[0025] The processing unit is configured to update the target asset data in parallel using the first document and the second document when the first document and the second document are documents of the same type.

[0026] In one possible implementation, the acquisition unit is further configured to acquire the first asset data corresponding to the first document and the second asset data corresponding to the second document;

[0027] The judgment unit is also used to determine whether the first asset data and the second asset data are the same, wherein the first asset data and the second asset data are part of the asset data within the target asset data;

[0028] The processing unit is further configured to trigger the step of updating the target asset data using the first document and the second document in parallel when the first asset data and the second asset data are different.

[0029] In one possible implementation, the acquisition unit is further configured to acquire a revocation request, the revocation request being used to instruct the terminal to revoke the use of the first document to update the first asset data, or to instruct the terminal to revoke the use of the second document to update the second asset data. The revocation request includes a first ID or a second ID, the first ID being the sequence number of the first asset data stored in the storage address, and the second ID being the sequence number of the second asset data stored in the storage address.

[0030] The judgment unit is further configured to obtain the first asset data based on the first ID when the revocation request includes the first ID;

[0031] The processing unit is further configured to generate third asset data based on the first asset data, wherein the third asset data is identical to the data in the first asset data.

[0032] The determination unit is further configured to obtain the second asset data based on the second ID when the revocation request includes the second ID;

[0033] The processing unit is further configured to generate fourth asset data based on the second asset data, the fourth asset data being identical to the second asset data.

[0034] This application also provides a computer device, including: a processor and a memory.

[0035] The memory is used to store program code; the processor is used to execute the data update method described above according to the instructions in the program code.

[0036] In another aspect, this application provides a computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the data update method described in any of the preceding aspects.

[0037] According to another aspect of this application, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the data update method described in any of the preceding aspects.

[0038] In this implementation, when the terminal uses the first document to update the target asset data, it obtains the second document. The terminal determines whether the second document and the first document being used are of the same type. If they are of the same type, the terminal allows the second document to be used to update the target asset data, thereby enabling the target asset data to be updated based on multiple documents and improving update efficiency. Attached Figure Description

[0039] Figure 1 A flowchart illustrating a data update method provided in an embodiment of this application;

[0040] Figure 2 This is another schematic flowchart illustrating a data update method provided in an embodiment of this application;

[0041] Figure 3 This is a schematic diagram illustrating the target asset data update and storage process in the embodiments of this application;

[0042] Figure 4 This is a schematic diagram of the structure of a terminal provided in an embodiment of this application;

[0043] Figure 5This is a schematic diagram of the structure of a computer device in an embodiment of this application. Detailed Implementation

[0044] The terms "first," "second," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms are interchangeable where appropriate; this is merely a way of distinguishing objects with the same attributes in the embodiments of this application. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, so that a process, method, system, product, or apparatus that comprises a series of elements is not necessarily limited to those elements, but may include other elements not explicitly listed or inherent to those processes, methods, products, or apparatuses.

[0045] The embodiments of this application will now be described with reference to the accompanying drawings. Those skilled in the art will recognize that, with technological advancements and the emergence of new scenarios, the technical solutions provided in the embodiments of this application are equally applicable to similar technical problems.

[0046] This application proposes a data updating method that can be applied to a terminal, which can be a computer, smartphone, server, or portable wearable device.

[0047] Asset cards are documents used to record asset information. Target asset data is presented to users through asset cards, providing them with asset information.

[0048] Please see Figure 1 , Figure 1 A flowchart illustrating a data update method provided in this application embodiment, which includes the following steps:

[0049] 101. When the terminal updates the target asset data using the first document, the terminal obtains the second document.

[0050] The target asset data consists of asset data of an asset, and one target asset data set can include asset data of multiple assets. In this application, for example, if there is an asset: a computer, then the target asset data can include the computer's serial number, its warehouse location, and its usage and allocation information. The first and second documents are documents submitted by the user, mainly recording the asset data that needs to be updated and how to update it. When the terminal uses the first document to update the target asset data, the terminal can also obtain the second document sent by the user or other users. In this application embodiment, the types of the first and second documents are not limited; for example, the first and second documents can be a requisition form or a disposal form. "First document" and "second document" are just general terms for documents and do not specifically refer to any particular document. In practical applications, other names can be used instead, and no specific limitation is made here. In this application embodiment, only "first document" and "second document" are used as examples for illustration.

[0051] Understandably, in practical applications, other documents submitted by users can also be received. This application uses the first and second documents as examples for illustration.

[0052] 102. The terminal determines whether the first document and the second document are of the same type.

[0053] When a terminal receives a second document after updating target asset data using a first document, the terminal determines whether the first and second documents are of the same type. In one embodiment, the document contains a type identifier, which is used to distinguish the type of user using the document. For example, if the document contains a personal identifier, it indicates that the document was submitted by a regular employee. When the document contains a fixed identifier, it indicates that the document was submitted by an administrator. The terminal distinguishes whether the documents belong to the same type by identifying the identifiers contained in the documents.

[0054] For example, when a user submits a first order containing a personal identifier, if the terminal is using the first order to update the target asset data and receives a second order, the terminal will first determine whether the identifier in the second order is a personal identifier. If the second order does not contain a personal identifier, it will not use the second order to update the target asset data. This prevents errors from occurring during the update process due to different processing procedures being invoked when using the second order to update the target asset data.

[0055] 103. The terminal uses the first and second documents in parallel to update the target asset data.

[0056] When the terminal determines that the first and second documents are of the same type, it also needs to determine whether the first and second documents are updating the same asset data under the target document. For easier understanding, please refer to [link / reference needed]. Figure 2 , Figure 2Another flowchart illustrating a data update method provided in this application embodiment specifically includes the following steps:

[0057] 1031. The terminal obtains the first asset data corresponding to the first document and the second asset data corresponding to the second document.

[0058] The target asset data consists of multiple asset data sets. The first document contains information about the asset that needs updating, and the second document also contains information about the asset that needs updating. Based on the asset information recorded in the first and second documents, the corresponding asset data within the target asset data set can be located and updated. When the first document corresponds to the first asset data within the target asset data set, and the second document corresponds to the second asset data within the target asset data set, the terminal retrieves the first asset data from the target asset data set based on the first document, and the second asset data from the target asset data set based on the second document.

[0059] The terms "first asset data" and "second asset data" are merely general terms for a portion of the asset data within the target asset data set, and do not specifically refer to any particular asset data set. In practical applications, other names can be used instead, and no specific limitation is made here. In this application embodiment, only "first asset data" and "second asset data" are used as examples for illustration.

[0060] 1032. The terminal determines whether the data of the first asset and the data of the second asset are the same.

[0061] Both the first and second asset data are partial asset data from the same target asset data. When the first and second asset data are identical, using both documents in parallel to update the same asset data will cause an update error. For example, the first document contains information about deleting the first computer, and the second document contains information about requisitioning the first computer. Both documents need to update the data for the first computer. The terminal needs to delete the asset data according to the first document, but needs to requisition the first computer according to the second document. The two updates are contradictory, leading to an update error. Therefore, after obtaining the first asset data corresponding to the first document and the second asset data corresponding to the second document, it is necessary to determine whether the first and second asset data are identical. Based on the determination result, it is then necessary to decide whether to use both documents in parallel to update the target asset data, preventing two documents from updating the same asset data within the target asset data, thereby preventing update errors.

[0062] 1033. The steps for the terminal to trigger the parallel use of the first and second documents to update the target asset data.

[0063] When the terminal determines that the first asset data and the second asset data are different, the terminal allows the first document and the second document to be used in parallel to update the target asset data. At this time, the first asset data updated with the first document and the second asset data updated with the second document, and the target asset data updated with different documents, do not interfere with each other, thus preventing update errors.

[0064] 1034. The terminal triggers a step that disallows the concurrent use of the first and second documents to update the target asset data.

[0065] When the terminal determines that the first asset data and the second asset data are the same, the terminal triggers the step of not allowing the concurrent use of the first document and the second document to update the target asset data, thereby preventing the concurrent use of the first document and the second document to update the same asset data under the target asset data and thus preventing update errors.

[0066] When the terminal determines that the first document and the second document do not come from the same type of user and are not updating the same asset data, the terminal allows the first document and the second document to be used in parallel to update the target asset data, thereby improving update efficiency.

[0067] When the terminal determines that the first document and the second document are not of the same type, the terminal does not allow the second document to be used to update the target asset data, in order to prevent errors from occurring during the process of updating the same asset data under the target asset data based on different documents.

[0068] It is understood that in other embodiments, multiple documents of the same type can be used in parallel to update the target asset data. In this embodiment, only the "first document" and the "second document" are used as examples for illustration.

[0069] In this embodiment, when the terminal uses the first document to update the target asset data, it obtains the second document. When it is determined that the second document and the first document are of the same type, the first document and the second document are allowed to be used in parallel to update the target asset data. This enables the terminal to use multiple documents to update the same target asset data, thereby improving the efficiency of the update.

[0070] Please see Figure 3 , Figure 3 The above method further includes: the terminal stores the updated first asset data and the updated second asset data into a storage stack, the storage stack containing the first asset data and the second asset data, and the storage stack being a stack data structure.

[0071] Rollback refers to the act of restoring a program or data to a previous state when a program or data processing error occurs. This is particularly important when multiple documents update target asset data concurrently, constantly generating new asset data. Rollback reverts to the asset data before the update by undoing the latest asset data. This is especially problematic when documents contain personal identifiers. Since there are many individual users and frequent updates, the target asset data is updated frequently, constantly generating new asset data. Users requesting rollback cannot request the deletion of asset data updated by other users, leading to rollback errors. For example, the first asset data is updated using a first order sent by a first user, and the second asset data is updated using a second order sent by a second user. After obtaining the updated first asset data, the first user discovers an error and needs to restore the first asset data to its previous state. If a rollback is used, both the updated first and second asset data need to be deleted. However, since the updated second asset data is updated based on the second user's second order, the terminal cannot undo the second user's update request, thus preventing the deletion of the updated second asset data and causing a rollback error. The stack data structure stores and retrieves data according to a first-in, last-out (LIFO) rule. For example, the first asset data, second asset data, updated first asset data, and updated second asset data are stored sequentially in the stack. The updated first asset data is the first to be added to the stack. Due to the LIFO rule, the updated first asset data cannot be directly manipulated, making it impossible to restore the data to its previous state using a rollback method based on the user's request, thus preventing rollback errors.

[0072] An asset card is a document that records asset information. It visually displays the target asset data to the user. A single asset card can contain information on multiple assets; therefore, the target asset data can include data on multiple assets. Please refer to the previous section for further details. Figure 3 If a user submits a first document containing a personal identifier, a second document containing a personal identifier, a third document containing a personal identifier, and a document containing a fixed identifier, and the terminal is currently updating an asset card using a document containing a personal identifier, updating the target asset data using a document containing a fixed identifier is prohibited to prevent update errors. The target asset data can only be updated using a document containing a fixed identifier after the update based on the document containing a personal identifier has been completed. Figure 3The target asset data within the asset card includes first asset data, second asset data, third asset data, and fourth asset data. When the first asset data is updated based on the first document, update 4 is generated and stored in the storage stack; update 4 represents the updated first asset data. When the second asset data is updated based on the second document, update 1 is generated and stored in the storage stack; update 1 represents the updated second asset data. When the fourth asset data is updated based on the third document, update 5 is generated and stored in the storage stack; update 5 represents the updated fourth asset data.

[0073] When the first asset data, the second asset data, the updated first asset data, and the updated second asset data are stored in the storage stack, the IDs are obtained according to the order in which they are stored in the storage stack. The first asset data obtains the first ID, and the second asset data obtains the second ID.

[0074] In this embodiment of the application, the terminal obtains a revocation request, which is used to instruct the terminal to revoke the use of the first document to update the first asset data, so that the updated first asset data is restored to the first asset data before the update, or to instruct the terminal to revoke the use of the second document to update the second asset data, so that the updated second asset data is restored to the second asset data before the update.

[0075] The revocation request includes either a first ID or a second ID. The first ID is the sequence number of the first asset data stored in the storage address, which facilitates the terminal to obtain the first asset data corresponding to the first ID in the storage stack. The second ID is the sequence number of the second asset data stored in the storage address, which facilitates the terminal to obtain the second asset data corresponding to the second ID in the storage stack.

[0076] When the revocation request includes the first ID, since the first ID is the ID corresponding to the first asset data, the terminal obtains the first asset data based on the first ID. The terminal copies the first asset data to generate the third asset data. The third asset data is the same as the first asset data, generating new asset data. This new asset data is obtained by copying the asset data before it was updated, preventing the restoration of the asset data before it was updated through rollback.

[0077] When the revocation request includes the second ID, since the second ID is the ID corresponding to the first asset data, the terminal obtains the second asset data based on the second ID. The terminal copies the second asset data to generate the fourth asset data. The fourth asset data is the same as the second asset data, generating new asset data. This new asset data is obtained by copying the asset data before it was updated, avoiding the need to restore the asset data before it was updated through rollback, thereby avoiding errors in the recovery process.

[0078] Please refer to it again. Figure 3For example, when the terminal receives a revocation request, it needs to revoke the update of the third document and return to the unupdated fourth asset data. The revocation request includes the ID of the unupdated fourth asset data. Based on the ID, the unupdated fourth asset data is found, and the unupdated fourth asset data is copied to generate update 6. Update 6 is the same as the unupdated fourth asset data.

[0079] In this application, each time the terminal updates the asset data of an asset using a document, a new target asset data is generated after the update is completed. This updated target asset data includes both the unupdated asset data and the updated asset data. For example, after the terminal updates the first asset data using the first document, the new target asset data consists of the updated first asset data and other unupdated asset data. Each update of asset data generates a new target asset data to provide users with the latest asset information.

[0080] The data transmission method in the embodiments of this application has been described above. The terminal in the embodiments of this application is described below. Please refer to [link / reference]. Figure 4 , Figure 4 This application provides a schematic diagram of the structure of a terminal, one embodiment of which includes:

[0081] The acquisition unit 401 is used to acquire a second document when the target asset data is updated using the first document. The second document is used to update the target asset data.

[0082] The judgment unit 402 is used to determine whether the first document and the second document are documents of the same type;

[0083] The processing unit 403 is used to update the target asset data in parallel using the first document and the second document when it is determined that the first document and the second document are documents of the same type.

[0084] One embodiment of the terminal includes:

[0085] The acquisition unit 401 is also used to acquire the first asset data corresponding to the first document and the second asset data corresponding to the second document.

[0086] The judgment unit 402 is also used to determine whether the first asset data and the second asset data are the same, wherein the first asset data and the second asset data are part of the asset data within the target asset data;

[0087] The processing unit 403 is also configured to, when the first asset data is different from the second asset data, trigger the step of updating the target asset data in parallel using the first document and the second document.

[0088] One embodiment of the terminal includes:

[0089] Storage unit 404 is used to store the updated first asset data and the updated second asset data into the storage stack. The storage stack stores the first asset data and the second asset data, and the storage stack is a stack data structure.

[0090] One embodiment of the terminal includes:

[0091] The acquisition unit 401 is also used for the terminal to acquire a cancellation request. The cancellation request is used to instruct the terminal to cancel the use of the first document to update the first asset data, or to instruct the terminal to cancel the use of the second document to update the second asset data. The cancellation request includes a first ID or a second ID. The first ID is the sequence number of the first asset data stored in the storage address, and the second ID is the sequence number of the second asset data stored in the storage address.

[0092] Processing unit 403 is also configured to, when the revocation request includes the first ID, obtain the first asset data based on the first ID;

[0093] Third asset data is generated based on the first asset data, and the third asset data is identical to the first asset data.

[0094] When the revocation request includes a second ID, the terminal obtains the second asset data based on the second ID;

[0095] The fourth asset data is generated based on the second asset data, and the fourth asset data is the same as the second asset data.

[0096] In this embodiment, the bank receipt recognition device can perform the aforementioned... Figures 1 to 3 The operation of any of the embodiments shown is not described in detail here.

[0097] This application also provides a computer device for performing... Figures 1 to 3 The operation of any of the embodiments shown in the corresponding examples. Please refer to... Figure 5 , Figure 5This is a schematic diagram of a computer device 500 according to an embodiment of this application. As shown, the computer device 500 can vary significantly due to different configurations or performance, and may include one or more central processing units (CPUs) 522 (e.g., one or more processors) and memory 532, and one or more storage media 530 (e.g., one or more mass storage devices) for storing application programs 542 or data 544. The memory 532 and storage media 530 can be temporary or persistent storage. The program stored in the storage media 530 may include one or more modules (not shown in the figure), each module may include a series of instruction operations on the computer device. Furthermore, the CPU 522 may be configured to communicate with the storage media 530 and execute the series of instruction operations in the storage media 530 on the computer device 500.

[0098] Computer device 500 may also include one or more power supplies 526, one or more wired or wireless network interfaces 550, one or more input / output interfaces 558, and / or one or more operating systems 541, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, etc.

[0099] The steps performed in the above embodiments can be based on this Figure 5 The structure of the computer device shown.

[0100] This application also provides a computer-readable storage medium storing a computer program that, when run on a computer, causes the computer to perform the methods described in the foregoing embodiments.

[0101] This application also provides a computer program product including a program, which, when run on a computer, causes the computer to execute the methods described in the foregoing embodiments. Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0102] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between apparatuses or units through some interfaces, and may be electrical, mechanical, or other forms.

[0103] 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.

[0104] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit 403, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0105] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part 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, an interactive video management device, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. 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.

[0106] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications 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 application.

Claims

1. A method for updating data, characterized in that, The method includes: When the terminal updates the target asset data using the first document, the terminal obtains a second document, which is used to update the target asset data. The terminal determines whether the first document and the second document are of the same type. The first document and the second document include type identifiers, which are used to distinguish the user types using the first document and the second document; the type identifiers include personal identifiers and fixed identifiers. The terminal determines whether the first document and the second document are of the same type by including: The terminal determines whether the first document and the second document are documents of the same type based on the type identifier of the first document and the type identifier of the second document; If so, the terminal uses the first document and the second document in parallel to update the target asset data; Before the terminal updates the target asset data using the first document and the second document in parallel, the method further includes: The terminal acquires the first asset data corresponding to the first document and the second asset data corresponding to the second document; The terminal determines whether the first asset data and the second asset data are the same, and the first asset data and the second asset data are part of the asset data within the target asset data; If they are different, the terminal triggers the step of updating the target asset data in parallel using the first document and the second document.

2. The method according to claim 1, characterized in that, After the terminal updates the target asset data using the first document and the second document in parallel, the method further includes: The terminal stores the updated first asset data and the updated second asset data into a storage stack. The storage stack contains the first asset data and the second asset data, and the storage stack is a stack data structure.

3. The method according to claim 1, characterized in that, The method further includes: The terminal obtains a revocation request, which is used to instruct the terminal to revoke the use of the first document to update the first asset data, or to instruct the terminal to revoke the use of the second document to update the second asset data. The revocation request includes a first ID or a second ID, where the first ID is the sequence number of the first asset data stored in the storage address, and the second ID is the sequence number of the second asset data stored in the storage address. When the revocation request includes a first ID, the terminal obtains the first asset data based on the first ID; The terminal generates third asset data based on the first asset data, and the third asset data is the same as the data in the first asset data. When the revocation request includes a second ID, the terminal obtains the second asset data based on the second ID; The terminal generates fourth asset data based on the second asset data, and the fourth asset data is the same as the second asset data.

4. A terminal, characterized in that, The terminal includes: The acquisition unit is used to acquire a second document when the target asset data is updated using the first document, wherein the second document is used to update the target asset data; The judgment unit is used to determine whether the first document and the second document are documents of the same type. The first document and the second document include type identifiers, which are used to distinguish the user types using the first document and the second document; the type identifiers include personal identifiers and fixed identifiers; the judgment unit is specifically used to: determine whether the first document and the second document are documents of the same type based on the type identifiers of the first document and the second document; A processing unit is configured to update the target asset data in parallel using the first document and the second document when the first document and the second document are of the same type. The acquisition unit is further configured to acquire the first asset data corresponding to the first document and the second asset data corresponding to the second document; The judgment unit is also used to determine whether the first asset data and the second asset data are the same, wherein the first asset data and the second asset data are part of the asset data within the target asset data; The processing unit is further configured to, when the first asset data is different from the second asset data, trigger the step of updating the target asset data by using the first document and the second document in parallel; and when the terminal determines that the first asset data is the same as the second asset data, trigger the step of disallowing the updating of the target asset data by using the first document and the second document in parallel.

5. The terminal according to claim 4, characterized in that, The acquisition unit is further configured to acquire a revocation request, which is used to instruct the terminal to revoke the use of the first document to update the first asset data, or to instruct the terminal to revoke the use of the second document to update the second asset data. The revocation request includes a first ID or a second ID, where the first ID is the sequence number of the first asset data stored in the storage address, and the second ID is the sequence number of the second asset data stored in the storage address. The judgment unit is further configured to obtain the first asset data based on the first ID when the revocation request includes the first ID; The processing unit is further configured to generate third asset data based on the first asset data, wherein the third asset data is identical to the data in the first asset data. The judgment unit is further configured to obtain the second asset data based on the second ID when the revocation request includes the second ID; The processing unit is further configured to generate fourth asset data based on the second asset data, the fourth asset data being identical to the second asset data.

6. A computer device, characterized in that, The computer device includes a processor and memory: The memory is used to store program code; the processor is used to execute the data update method according to any one of claims 1 to 3 according to the instructions in the program code.

7. A computer-readable storage medium storing instructions that, when executed on a computer, cause the computer to perform the data update method according to any one of claims 1 to 3.

Images