A transaction publishing, transaction updating method, device, equipment and storage medium

Abstract

The present invention discloses a transaction publishing and transaction updating method, device, equipment and storage medium. The method comprises: obtaining a transaction file, wherein the transaction file comprises: transaction file information and a transaction dependent file list; determining a first target hash value of the transaction file based on a message digest algorithm; if the transaction file is not included in a server database, storing the transaction file information and the first target hash value of the transaction file in the server database. Through the technical solution of the present invention, the redundancy of transaction publishing and transaction updating can be reduced, the consumption of network bandwidth, storage space and transaction time can be reduced, the efficiency of transaction publishing and updating can be improved, and the user experience can be enhanced.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of data transaction technology, and in particular to a transaction publishing and transaction updating method, device, equipment and storage medium. Background Art

[0002] Due to the rise of mobile Internet, transaction release and update iterations are becoming faster and faster. Especially for banking transactions with a rich variety of business types, how to quickly and stably release and update transactions has put forward higher requirements on the efficiency and accuracy of transaction release and update.

[0003] For the release and update of transactions based on the VUE platform, the usual practice is to release and update transactions in full. A large amount of redundant data needs to be recorded when releasing, and a large amount of redundant data needs to be obtained when updating. This practice not only consumes a lot of network bandwidth, storage space and transaction time, but also has a large amount of file redundancy, making it impossible to quickly obtain the latest version of the transaction, which is not conducive to discovering program changes, and it is impossible to locate and analyze problems. Summary of the invention

[0004] Embodiments of the present invention provide a transaction publishing and transaction updating method, apparatus, device and storage medium to reduce the redundancy of transaction publishing and transaction updating, reduce the consumption of network bandwidth, storage space and transaction time, improve transaction publishing and updating efficiency, and enhance user experience.

[0005] In a first aspect, an embodiment of the present invention provides a transaction publishing method, comprising:

[0006] Obtaining a transaction file, wherein the transaction file includes: transaction file information and a transaction dependent file list;

[0007] Determining a first target hash value of the transaction file based on a message digest algorithm;

[0008] If the transaction file is not included in the server database, the transaction file information and the first target hash value of the transaction file are stored in the server database.

[0009] Further, determining that the transaction file is not included in the server database includes:

[0010] Parsing identification information in the transaction file information, the identification information including: a file name or a file identification number;

[0011] If the transaction file is not found in the server database based on the identification information, it is determined that the transaction file is not included in the server database.

[0012] Furthermore, it also includes:

[0013] If the transaction file is included in the server database, determining whether the first target hash value is the same as the hash value of the server transaction file; the server transaction file is a transaction file that has been included in the server database;

[0014] If not, the server-side transaction file is updated based on the transaction file and the first target hash value.

[0015] In a second aspect, an embodiment of the present invention provides a transaction update method, including:

[0016] Obtaining a transaction file, wherein the transaction file includes: transaction file information and a transaction dependent file list;

[0017] If the transaction dependency file in the transaction dependency file list is not included in the client transaction file, then downloading the transaction dependency file, the client transaction file being the transaction file corresponding to the transaction file information included in the client database;

[0018] The client transaction file in the client database is updated according to the transaction dependency file.

[0019] Further, determining that the transaction dependent files in the transaction dependent file list are not included in the client transaction file includes:

[0020] Calculating a second target hash value of the transaction dependency file based on a message digest algorithm;

[0021] If the second target hash value is different from the hash value of the transaction dependency file in the client database, the transaction dependency file is not included in the client database.

[0022] Further, downloading the transaction dependency file includes:

[0023] Adding the second target hash value to the download file list;

[0024] The transaction dependent file is downloaded from the server based on the download file list.

[0025] In a third aspect, an embodiment of the present invention further provides a transaction publishing device, the device comprising:

[0026] An acquisition module, used to acquire a transaction file, wherein the transaction file includes: transaction file information and a transaction dependent file list;

[0027] A determination module, configured to determine a first target hash value of the transaction file based on a message digest algorithm;

[0028] A storage module is used to store the transaction file information and the first target hash value of the transaction file in the server-side database if the transaction file is not included in the server-side database.

[0029] In a fourth aspect, an embodiment of the present invention further provides a transaction update device, the device comprising:

[0030] An acquisition module, used to acquire a transaction file, wherein the transaction file includes: transaction file information and a transaction dependent file list;

[0031] a download module, configured to download the transaction-dependent file if the transaction-dependent file in the transaction-dependent file list is not included in the client transaction file, wherein the client transaction file is a transaction file corresponding to the transaction file information included in the client database;

[0032] An updating module is used to update the client transaction file in the client database according to the transaction dependency file.

[0033] In the fifth aspect, an embodiment of the present invention further provides a terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the program, the transaction update method as described in any one of the embodiments of the present invention is implemented or the transaction update method as described in any one of the embodiments of the present invention is implemented.

[0034] In a sixth aspect, an embodiment of the present invention further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a transaction update method as described in any one of the embodiments of the present invention or implements a transaction update method as described in any one of the embodiments of the present invention.

[0035] The embodiment of the present invention obtains a transaction file, wherein the transaction file includes: transaction file information and a list of transaction dependent files; determines a first target hash value of the transaction file based on a message digest algorithm; if the transaction file is not included in a server-side database, stores the transaction file information and the first target hash value of the transaction file in the server-side database, thereby solving the problem of recording the full transaction file when publishing and updating transactions, and solving the problem of large network bandwidth, storage, and time consumption. It can reduce the redundancy of transaction publishing and transaction updating, reduce the consumption of network bandwidth, storage space, and transaction time, improve transaction publishing and updating efficiency, and enhance user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.

[0037] Figure 1 is a flow chart of a transaction publishing method in Embodiment 1 of the present invention;

[0038] Figure 2A is a flow chart of a transaction update method in Embodiment 2 of the present invention;

[0039] Figure 2B It is a timing diagram of a transaction update method in Embodiment 2 of the present invention;

[0040] Figure 3 It is a structural diagram of a transaction publishing device in Embodiment 3 of the present invention;

[0041] Figure 4 It is a structural diagram of a transaction updating device in Embodiment 4 of the present invention;

[0042] Figure 5 It is a structural diagram of a terminal device in Embodiment 5 of the present invention. DETAILED DESCRIPTION

[0043] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0044] It should be noted that similar reference numerals and letters represent similar items in the following drawings, so once an item is defined in one drawing, it does not need to be further defined and explained in the subsequent drawings. At the same time, in the description of the present invention, the terms "first", "second", etc. are only used to distinguish the description and cannot be understood as indicating or implying relative importance.

[0045] Embodiment 1

[0046] Figure 1 This is a flowchart of a transaction publishing method provided in the first embodiment of the present invention. This embodiment is applicable to the case of publishing transactions to a server. The method can be executed by a transaction publishing device in the embodiment of the present invention. The device can be implemented in software and / or hardware. The transaction publishing device can be integrated in the server. Figure 1 As shown, the method specifically comprises the following steps:

[0047] S110, obtaining a transaction file, the transaction file including: transaction file information and a transaction dependent file list.

[0048] Among them, the transaction file refers to the file consisting of transaction-related information, including: transaction file information and transaction dependency file list, and may also include transaction data; transaction file information may include the name of the transaction file, index sequence number, storage path and other information. When opening a transaction, it is usually necessary to rely on one or more configuration files, namely transaction dependency files. The transaction dependency file list is a list of transaction dependency files required to record the transaction file.

[0049] Exemplarily, the way to obtain the transaction file may be that the server receives the transaction file information and the transaction dependent file list uploaded by the user through the user interface. The transaction file may be a file in json format.

[0050] S120, determining a first target hash value of the transaction file based on a message digest algorithm.

[0051] Among them, the message digest algorithm is also called the hash algorithm or hash algorithm. Its characteristics are that the encryption process does not require a key, and the encrypted data cannot be decrypted. Only when the same plaintext data is input and the same message digest algorithm is used to obtain the same ciphertext, which is used to ensure the integrity and consistency of information transmission. Commonly used message digest algorithms include: MD5 (Message Digest Algorithm 5).

[0052] Exemplarily, the first target hash value of the transaction file determined by the message digest algorithm is a unique 128-bit binary hash value, which can also be converted into a hexadecimal system to obtain a 32-bit string.

[0053] S130: If the transaction file is not included in the server database, the transaction file information and the second target hash value of the transaction file are stored in the server database.

[0054] Among them, a database is set up on the server side for storing transaction files. The process of storing transaction files in the server-side database is called the transaction publishing process. The transaction files are published to the server-side database and can be obtained by the client that establishes communication with the server.

[0055] Specifically, it is determined whether the transaction file is included in the server database. If the transaction file is not included in the server database, the transaction file information and the first target hash value of the transaction file are stored in the server database to implement the transaction publishing process.

[0056] In an embodiment of the present invention, a transaction file is obtained, and the transaction file includes: transaction file information and a list of transaction dependent files; a first target hash value of the transaction file is determined based on a message digest algorithm; if the transaction file is not included in a server-side database, the transaction file information and the first target hash value of the transaction file are stored in the server-side database, thereby reducing the redundancy of transaction publishing, reducing the consumption of network bandwidth, storage space and transaction time, improving transaction publishing efficiency, and enhancing user experience.

[0057] Optionally, also include:

[0058] If the transaction file is included in the server database, determining whether the first target hash value is the same as the hash value of the server transaction file; the server transaction file is a transaction file included in the server database;

[0059] If not, the server transaction file is updated based on the transaction file and the first target hash value.

[0060] The server-side transaction file refers to a transaction file already included in the server-side database, and the hash value of the server-side transaction file is a hash value calculated on the transaction file stored in the server based on the same information digest algorithm as that used to determine the first target hash value.

[0061] By comparing the first target hash value of the transaction file with the hash value of the server-side transaction file contained in the server-side database, it is determined whether the first target hash value is the same as the hash value of the server-side transaction file. If they are different, it means that although a transaction file with the same name or index sequence number is stored in the server-side database, the transaction data in the transaction file has changed, causing the hash value of the transaction file to change accordingly. Therefore, it is necessary to update the server-side transaction file based on the transaction file and the first target hash value. The update process can be considered as replacing the server-side transaction file with the transaction file, and replacing the hash value of the server-side transaction file based on the first target hash value. If they are the same, it means that a transaction file with exactly the same transaction data has been stored in the server-side database, and there is no need to publish it repeatedly, thereby realizing incremental publishing of transactions. Compared with full-volume publishing of transactions, it can reduce the redundancy of transaction publishing, reduce the consumption of network bandwidth, storage space and transaction time, improve transaction publishing efficiency, and improve user experience.

[0062] Optionally, determining that the transaction file is not included in the server database includes:

[0063] Parsing identification information in the transaction file information, the identification information includes: file name or file identification number;

[0064] If the transaction file is not found in the server database based on the identification information, it is determined that the transaction file is not included in the server database.

[0065] The transaction file information includes identification information, and the identification information includes: a file name or a file identification number.

[0066] Specifically, the transaction file information is parsed to extract the identification information, and each transaction file stored in the server database is queried based on the identification information, and whether the transaction file is included in the server database is determined based on the query result of the identification information. If the transaction file is not found in the server database based on the identification information, it is determined that the transaction file is not included in the server database. On the contrary, if the transaction file is found in the server database based on the identification information, it is determined that the transaction file is included in the server database.

[0067] Embodiment 2

[0068] Figure 2A This is a flow chart of a transaction update method provided in the second embodiment of the present invention. This embodiment is applicable to the case of updating transactions on a client. This method can be executed by a transaction update device in the embodiment of the present invention. The device can be implemented in software and / or hardware. The transaction update device can be integrated in the client. Figure 2A As shown, the method specifically comprises the following steps:

[0069] S210, obtaining a transaction file, the transaction file including: transaction file information and a transaction dependent file list.

[0070] Among them, the transaction file refers to a file consisting of transaction-related information, and the transaction file includes: transaction file information and a list of transaction-dependent files. The transaction file information may include information such as file name, file identification number, and storage path. When opening a transaction file, it is usually necessary to rely on multiple configuration files, namely transaction-dependent files. The list of transaction-dependent files is a list of transaction-dependent files required to record the transaction file.

[0071] Specifically, the transaction file can be obtained by sending an acquisition instruction to the server after the server publishes the transaction, so as to obtain the transaction file published by the server.

[0072] S220, if the transaction dependency file in the transaction dependency file list is not included in the client transaction file, then download the transaction dependency file, the client transaction file is the transaction file corresponding to the transaction file information included in the client database.

[0073] When a client opens a transaction, it usually needs to rely on one or more configuration files, namely transaction dependency files. A database is set on the client to store transaction dependency files.

[0074] Specifically, the transaction file corresponding to the transaction file information contained in the client database, i.e., the client transaction file, is determined according to the transaction file information. It is determined whether the transaction dependency file in the transaction dependency file list of the client transaction file is contained in the client database. If the transaction dependency file is not contained in the client database, the transaction dependency file is downloaded according to the name, storage path, and other information of the transaction dependency file recorded in the transaction dependency file list. The transaction dependency file to be downloaded may be pre-stored in the server.

[0075] S230, updating the client transaction file in the client database according to the transaction dependency file.

[0076] Specifically, the client transaction file in the client database is incrementally updated according to the downloaded transaction dependency file. Incrementally updating the transaction dependency file can reduce the redundancy of transaction updates.

[0077] The technical solution of this embodiment is to obtain a transaction file, which includes: transaction file information and a list of transaction dependency files; if the transaction dependency file in the list of transaction dependency files is not included in the client transaction file, then download the transaction dependency file, and the client transaction file is the transaction file corresponding to the transaction file information contained in the client database; update the client transaction file in the client database according to the transaction dependency file, which can reduce the redundancy of transaction updates, reduce the consumption of network bandwidth, storage space and transaction time, improve transaction update efficiency, and enhance user experience.

[0078] Optionally, determining that the transaction dependency files in the transaction dependency file list are not included in the client database includes:

[0079] Calculating a second target hash value of the transaction dependency file based on a message digest algorithm;

[0080] If the second target hash value is different from the hash value of the transaction dependency file in the client database, the transaction dependency file is not included in the client database.

[0081] Among them, the message digest algorithm is also called the hash algorithm or hash algorithm. Its characteristics are that the encryption process does not require a key, and the encrypted data cannot be decrypted. Only when the same plaintext data is input and the same message digest algorithm is used to obtain the same ciphertext, which is used to ensure the integrity and consistency of information transmission. Commonly used message digest algorithms include: MD5 (Message Digest Algorithm 5).

[0082] Exemplarily, the second target hash value of the transaction file determined by the message digest algorithm is a unique 128-bit binary hash value, which can also be converted into a hexadecimal system to obtain a 32-bit character string.

[0083] Specifically, the second target hash value is compared with the hash value of the transaction dependency file in the client database. If the two are different, it indicates that the transaction dependency file is not included in the client database. Otherwise, it indicates that the transaction dependency file is included in the client database.

[0084] Optionally, download transaction dependency files including:

[0085] Add the second target hash value to the download file list;

[0086] The transaction dependent files are downloaded from the server based on the download file list.

[0087] The download file list is used to record the second target hash value of the file to be downloaded.

[0088] Specifically, if the transaction dependency file is not included in the client database, the second target hash value of the transaction dependency file is added to the download file list, the server is queried according to the second target hash value of the transaction dependency file recorded in the download file list, and the transaction dependency file is downloaded.

[0089] For example, Figure 2B As shown in the figure, during the transaction update process, the interaction process between the client and the server is as follows: the client sends a transaction file acquisition instruction to the server to obtain the transaction file sent by the server, parses the transaction dependency file list in the transaction file to determine the transaction dependency file, and sends a second target hash value acquisition instruction to the server to obtain the second target hash value of the transaction dependency file. The second target hash value is compared with the hash value of the transaction dependency file in the client. If they are different, the second target hash value is added to the download file list; the download file list is sent to the server to download the transaction dependency file from the server for updating the client's transaction file.

[0090] Embodiment 3

[0091] Figure 3 This is a schematic diagram of the structure of a transaction publishing device provided in the third embodiment of the present invention. This embodiment is applicable to the case of publishing transactions to a server. The device can be implemented in software and / or hardware. The device can be integrated in any device that provides a transaction publishing function, such as Figure 3 As shown, the transaction publishing device specifically includes: an acquisition module 310, a determination module 320 and a storage module 330.

[0092] The acquisition module 310 is used to acquire a transaction file, wherein the transaction file includes: transaction file information and a transaction dependent file list;

[0093] A determination module 320, configured to determine a first target hash value of the transaction file based on a message digest algorithm;

[0094] The storage module 330 is configured to store the transaction file information and the first target hash value of the transaction file in the server-side database if the transaction file is not included in the server-side database.

[0095] Optionally, the storage module 330 is specifically used for:

[0096] Parsing identification information in the transaction file information, the identification information including: a file name or a file identification number;

[0097] If the transaction file is not found in the server database based on the identification information, it is determined that the transaction file is not included in the server database.

[0098] Optionally, also include:

[0099] a judgment module, configured to judge whether the first target hash value is the same as the hash value of the server-side transaction file if the transaction file is included in the server-side database; the server-side transaction file is a transaction file already included in the server-side database;

[0100] An updating module is used for, if not, updating the server-side transaction file based on the transaction file and the first target hash value.

[0101] The above-mentioned product can execute the transaction publishing method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0102] Embodiment 4

[0103] Figure 4 This is a schematic diagram of the structure of a transaction update device provided in the fourth embodiment of the present invention. This embodiment is applicable to the case of updating transactions of a client. The device can be implemented in software and / or hardware. The device can be integrated in any device that provides a transaction update function, such as Figure 3 As shown, the transaction updating device specifically includes: an acquisition module 410 , a download module 420 and an update module 430 .

[0104] The acquisition module 410 is used to acquire a transaction file, wherein the transaction file includes: transaction file information and a transaction dependent file list;

[0105] A download module 420, configured to download the transaction-dependent file if the transaction-dependent file in the transaction-dependent file list is not included in the client transaction file, wherein the client transaction file is a transaction file corresponding to the transaction file information included in the client database;

[0106] The updating module 430 is used to update the client transaction file in the client database according to the transaction dependency file.

[0107] Optionally, the download module 420 is specifically used for:

[0108] Calculating a second target hash value of the transaction dependency file based on a message digest algorithm;

[0109] If the second target hash value is different from the hash value of the transaction dependency file in the client database, the transaction dependency file is not included in the client database.

[0110] Optionally, the download module 420 is further used to:

[0111] Adding the second target hash value to the download file list;

[0112] The transaction dependent file is downloaded from the server based on the download file list.

[0113] The above-mentioned product can execute the transaction update method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0114] Embodiment 5

[0115] Figure 5 A structural block diagram of a terminal device provided in Embodiment 5 of the present invention, such as Figure 5 As shown, the terminal device includes a processor 510, a memory 520, an input device 530 and an output device 540; the number of processors 510 in the terminal device can be one or more. Figure 5 A processor 510 is taken as an example; the processor 510, the memory 520, the input device 530 and the output device 540 in the terminal device can be connected via a bus or other means. Figure 5 The example of connecting through bus is taken in the following.

[0116] The memory 520, as a computer-readable storage medium, can be used to store software programs, computer executable programs and modules, such as program instructions / modules corresponding to the transaction publishing method or transaction updating method in the embodiments of the present invention (for example, the acquisition module 310, the determination module 320 and the storage module 330 in the transaction publishing device; or the acquisition module 410, the download module 420 and the update module 430 in the transaction updating device). The processor 510 executes various functional applications and data processing of the terminal device by running the software programs, instructions and modules stored in the memory 520, that is, realizes the above-mentioned transaction publishing method or transaction updating method.

[0117] The memory 520 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system and at least one application required for a function; the data storage area may store data created according to the use of the terminal, etc. In addition, the memory 520 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 520 may further include a memory remotely arranged relative to the processor 510, and these remote memories may be connected to the terminal device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0118] The input device 530 may be used to receive input digital or character information and generate key signal input related to user settings and function control of the terminal device. The output device 540 may include a display device such as a display screen.

[0119] Embodiment 6

[0120] Embodiment 6 of the present invention provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements a transaction publishing method as provided in all the embodiments of the present invention: obtaining a transaction file, the transaction file including: transaction file information and a list of transaction dependent files; determining a first target hash value of the transaction file based on a message digest algorithm; if the transaction file is not included in a server-side database, storing the transaction file information and the first target hash value of the transaction file in the server-side database. Or a transaction update method: obtaining a transaction file, the transaction file including: transaction file information and a list of transaction dependent files; if the transaction dependent files in the list of transaction dependent files are not included in a client transaction file, downloading the transaction dependent files, the client transaction file being a transaction file corresponding to the transaction file information contained in the client database; updating the client transaction file in the client database according to the transaction dependent files.

[0121] Any combination of one or more computer-readable media can be used. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or devices, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above. In this document, computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0122] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0123] The program code embodied on the computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0124] Computer program code for performing the operation of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0125] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A transaction update method, characterized in that: The method comprises: Obtaining a transaction file through a client, wherein the transaction file includes: transaction file information and a transaction dependency file list; the transaction dependency file list is a list of transaction dependency files required for recording the transaction file; the transaction dependency file is a configuration file required to be relied upon when opening the transaction file; If the transaction dependency file in the transaction dependency file list is not included in the client transaction file, then downloading the transaction dependency file, the client transaction file being the transaction file corresponding to the transaction file information included in the client database; updating the client transaction file in the client database according to the transaction dependency file; Determining that the transaction dependent files in the transaction dependent file list are not included in the client transaction file includes: Calculating a second target hash value of the transaction dependency file based on a message digest algorithm; If the second target hash value is different from the hash value of the transaction dependency file in the client database, the transaction dependency file is not included in the client database.

2. The method according to claim 1, characterized in that Downloading the transaction dependency files includes: Adding the second target hash value to the download file list; The transaction dependent file is downloaded from the server based on the download file list.

3. The method according to any one of claims 1 to 2, characterized in that: Before obtaining the transaction file through the client, it also includes: Obtaining a transaction file through the server, wherein the transaction file includes: transaction file information and a transaction dependency file list; the transaction dependency file list is a list of transaction dependency files required for recording the transaction file; the transaction dependency file is a configuration file that needs to be relied upon when opening the transaction file; Determining a first target hash value of the transaction file based on a message digest algorithm; If the transaction file is not included in the server database, the transaction file information and the first target hash value of the transaction file are stored in the server database for acquisition by the client that establishes communication with the server.

4. The method according to claim 3, characterized in that: Determining that the transaction file is not included in the server database includes: Parsing identification information in the transaction file information, the identification information including: a file name or a file identification number; If the transaction file is not found in the server database based on the identification information, it is determined that the transaction file is not included in the server database.

5. The method according to claim 3, characterized in that: Also includes: If the transaction file is included in the server database, determining whether the first target hash value is the same as the hash value of the server transaction file; the server transaction file is a transaction file that has been included in the server database; If not, the server-side transaction file is updated based on the transaction file and the first target hash value.

6. A transaction update device, characterized in that: include: An acquisition module is used to acquire a transaction file through a client, wherein the transaction file includes: transaction file information and a transaction dependency file list; the transaction dependency file list is a list of transaction dependency files required for recording the transaction file; the transaction dependency file is a configuration file that needs to be relied upon when opening the transaction file; a download module, configured to download the transaction-dependent file if the transaction-dependent file in the transaction-dependent file list is not included in the client transaction file, wherein the client transaction file is a transaction file corresponding to the transaction file information included in the client database; An updating module, used for updating the client transaction file in the client database according to the transaction dependency file; Download modules, specifically for: Calculating a second target hash value of the transaction dependency file based on a message digest algorithm; If the second target hash value is different from the hash value of the transaction dependency file in the client database, the transaction dependency file is not included in the client database.

7. A terminal device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the transaction update method as described in any one of claims 1-5 is implemented.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the transaction update method as described in any one of claims 1 to 5 is implemented.

Images