CN115828278A

CN115828278A - File reliability interaction method and device based on file list

Info

Publication number: CN115828278A
Application number: CN202211395318.5A
Authority: CN
Inventors: 王铖
Original assignee: Bank of China Ltd
Current assignee: Bank of China Ltd
Priority date: 2022-11-09
Filing date: 2022-11-09
Publication date: 2023-03-21

Abstract

The file reliability interaction method and device based on the file list comprise that a first end system is used for generating a data file; generating a first file list according to the data file; sending the data file and the first file list to a second end system; receiving the information of the missed push data file; calling the missed push data file according to the missed push data file information; and sending the missed data file to the second end system. The second end system is used for receiving the data file and the first file list; generating a second file list according to the received data files; judging whether the first file list and the second file list are consistent, if not, determining missing data file information according to the first file list and the second file list; sending the information of the missed push data file to a first end system; in response to the received data file. When the file is sent, the file list is also sent, so that the reliability and the integrity of file sending can be ensured.

Description

File list-based file reliable interaction method and device

Technical Field

The present disclosure relates to the field of data interaction, and in particular, to a method and an apparatus for file reliable interaction based on a file list.

Background

With the development of science and technology, more and more enterprises switch the interaction channel with the bank from the traditional online bank to the bank-enterprise direct connection, which is a new access mode of online direct connection between the online bank system and the enterprise financial system, in order to reduce financial cost and improve efficiency, and group enterprises realize connection between the internal fund system and the commercial bank system through a data interface. The interaction mode of the bank-enterprise direct connection comprises online interaction, active push, centralized file interaction and the like, wherein the centralized file interaction mode is a file docking mode, namely, the interaction of instructions and data among systems is realized in a file interaction mode.

Disclosure of Invention

The method is used for solving the problem that file loss is not easy to notice in a file interaction mode in a set under the existing scenes such as bank-enterprise direct connection and the like, and further operation is missed.

In order to solve the above technical problem, an aspect of the present disclosure provides a file reliability interaction method based on a file manifest, applied to a first end system, including:

generating a data file;

generating a first file list according to the data files, wherein attribute information of the data files is recorded in the first file list;

sending the data file and the first file list to a second end system;

receiving the missing push data file information sent by the second end system;

calling the missed push data file according to the missed push data file information;

and sending the missed push data file to the second end system.

As a further embodiment herein, the file reliability interaction method based on the file manifest further comprises: acquiring system time information and encrypting the system time information;

and when the data file and the first file list are sent to a second end system, encrypted time information is also sent to the second end system.

As a further embodiment herein, the file reliability interaction method based on the file manifest further includes:

counting the times of receiving the attribute information of the missed push data file in a preset time period;

and if the frequency is greater than a preset value, sending abnormal alarm information.

As a further embodiment herein, the attribute information includes: file identification, file size, and file type.

A second aspect of the present disclosure provides a file reliability interaction method based on a file manifest, applied to a second end system, including:

receiving a data file and a first file list sent by a first end system;

generating a second file list according to the received data files, wherein the second file list records the attribute information of the received data files;

judging whether the first file list and the second file list are consistent or not, if not, determining missing data file information according to the first file list and the second file list;

sending the missing push data file information to the first end system;

in response to the received data file.

As a further embodiment herein, the receiving the data file and the first file list sent by the first end system further comprises: receiving a data file, a first file list and encrypted time information sent by a first end system;

before determining whether the first file list and the second file list are consistent, the method further includes:

decrypting the encrypted time information;

and judging whether the difference between the time information obtained by decryption and the current time information meets a preset condition, and if so, judging whether the first file list and the second file list are consistent.

As a further embodiment herein, determining whether the first file list and the second file list are consistent comprises:

respectively calculating hash values of the first file list and the second file list;

and judging whether the hash values of the first file list and the second file list are the same or not, and if so, determining that the first file list is inconsistent with the second file list.

A third aspect of the present document provides a file-manifest-based file reliability interaction apparatus, comprising:

a data file generating unit for generating a data file;

a sending list generating unit, configured to generate a first file list according to the data file, where attribute information of the data file is recorded in the first file list;

the file/list sending unit is used for sending the data file and the first file list to a second end system;

the missed push request receiving unit is used for receiving missed push data file information sent by the second end system;

the missed push file calling unit is used for calling missed push data files according to the missed push data file information;

and the file complementary pushing unit is used for sending the missed pushed data file to the second end system.

A fourth aspect of the present document provides a file reliability interaction apparatus based on a file manifest, comprising:

the file/list missing push request receiving unit is used for receiving a data file and a first file list sent by a first end system;

the receiving list generating unit is used for generating a second file list according to the received data files, and the second file list records the attribute information of the received data files;

the missed pushing file identification unit is used for judging whether the first file list and the second file list are consistent, and if not, determining the missed pushing data file information according to the first file list and the second file list;

the missed push file request unit is used for sending the missed push data file information to the first end system;

and the file processing unit is used for responding to the received data file.

A fifth aspect of the present disclosure provides a computer apparatus comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any of the preceding embodiments when executing the computer program.

A sixth aspect of the present document provides a computer storage medium having stored thereon a computer program which, when executed by a processor of a computer device, executes instructions of a method according to any of the preceding embodiments.

A seventh aspect of the present invention provides a computer program product comprising a computer program which, when executed by a processor, implements the method of any of the preceding embodiments.

According to the file reliability interaction method and device based on the file list, the first file list including the attribute information of the data files is sent while the first end system is arranged to send the data files, the second end system can generate the second file list recording the attribute information of the received data files when receiving the data files and the first file list, whether the first file list is consistent with the second file list is judged, when the first file list is inconsistent with the second file list, the missed-push data file information is determined according to the first file list and the second file list and is sent to the first end system, the first end system calls the missed-push files according to the missed-push data file information and sends the missed-push files to the second end system of a child, the reliability and the integrity of file sending can be guaranteed, and the accuracy of data processing is further guaranteed.

In order to make the aforementioned and other objects, features and advantages of the present invention comprehensible, preferred embodiments accompanied with figures are described in detail below.

Drawings

In order to more clearly illustrate the embodiments or technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.

FIG. 1 shows an interaction diagram of a file manifest-based file reliability interaction system of embodiments herein;

FIG. 2 shows a first flowchart of a file manifest-based file reliability interaction method applied to a first end system according to embodiments herein;

FIG. 3 shows a second flowchart of a file manifest based file reliability interaction method as applied to a first end system of embodiments herein;

FIG. 4 shows a third flowchart of a file manifest-based file reliability interaction method applied to a first-end system according to an embodiment of the present disclosure;

FIG. 5 shows a first flowchart of a file manifest-based file reliability interaction method applied to a second end system of embodiments herein;

FIG. 6 shows a second flowchart of a file manifest-based file reliability interaction method applied to a second end system of embodiments herein;

FIG. 7 shows a first configuration diagram of a file manifest based file reliability interaction apparatus of embodiments herein;

FIG. 8 is a second block diagram of a file-manifest-based file reliability interaction apparatus according to an embodiment of the present disclosure;

FIG. 9 shows a block diagram of a computer device according to an embodiment of the present disclosure.

Description of the figures the symbols:

110. a first end system;

120. a second end system;

701. a data file generation unit;

702. a transmission list generation unit;

703. a file/list transmission unit;

704. a missed push request receiving unit;

705. a missed push file calling unit;

706. a file supplementing and pushing unit;

801. a file/list missing push request receiving unit;

802. a reception list generation unit;

803. a missed push file identification unit;

804. a missed push file request unit;

805. a document processing unit;

902. a computer device;

904. a processor;

906. a memory;

908. a drive mechanism;

910. an input/output module;

912. an input device;

914. an output device;

916. a presentation device;

918. a graphical user interface;

920. a network interface;

922. a communication link;

924. a communication bus.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments herein without making any creative effort, shall fall within the scope of protection.

It should be noted that the terms "first," "second," and the like in the description and claims herein and in the above-described drawings are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments herein described are capable of operation in sequences other than those illustrated or described herein. Moreover, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, apparatus, article, or device that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or device.

The present specification provides method steps as described in the examples or flowcharts, but may include more or fewer steps based on routine or non-inventive labor. The order of steps recited in the embodiments is merely one manner of performing the steps in a multitude of orders and does not represent the only order of execution. When an actual system or apparatus product executes, it can execute sequentially or in parallel according to the method shown in the embodiment or the figures.

It should be noted that the file reliable interaction method and apparatus based on the file list may be used in the bank-enterprise direct connection field, and may also be applied in other scenarios of transmitting files, and the specific application scenario is not limited herein.

In an embodiment of the present disclosure, a file-manifest-based file reliability interaction system is provided, as shown in fig. 1, including a first end system 110 and a second end system 120. The first end system 110 refers to an end system that transmits data files, such as a corporate financial system. The second end system 120 refers to an end system that processes data files, such as a bank processing system. The first end system 110 is configured to generate a data file; generating a first file list according to the data files, wherein attribute information of the data files is recorded in the first file list; the data file and the first file list are sent to the second end system 120. In detail, the data file may be generated according to a user instruction, where the data file includes multiple files, each file has recorded therein necessary data to be processed by the second end system, and the data file format is, for example, an ftp file, an xml file, or the like. The attribute information of the data file includes a file identifier, a file size, and a file type. The record information in the first file list is shown in table 1 below:

TABLE 1

File identification	File size	File type
			Document 1	100M
Document 2	50M
			……

The second end system 120 is configured to receive the data file and the first file list transmitted by the first end system 110; generating a second file list according to the received data files, wherein the second file list records the attribute information of the received data files; judging whether the first file list and the second file list are consistent, if not, determining missing data file information according to the first file list and the second file list; sending the missing push data file information to a first end system; in response to the received data file.

In a specific implementation, the second end system 120 may generate the second file list according to an algorithm agreed in advance with the first end system 110, and when the data file sent by the first end system 110 to the second end system 120 has no transmission error, the information included in the first file list and the information included in the second file list are the same, based on which, the second end system 120 can determine whether the file miss-pushing occurs by determining whether the first file list and the second file list are consistent, specifically, if the first file list and the second file list are not consistent, it indicates that the file miss-pushing occurs, and the file information existing in the first file list but not existing in the second file list is used as the data file miss-pushing information. And responding the data file, namely processing the data file to complete the corresponding service action. Specifically, the data file includes, for example, a transaction payment instruction, a credit adjustment instruction, and the like, and the corresponding service action is used to complete deduction and credit adjustment.

The first end system 110 is further configured to receive the missing data file information sent by the second end system 120; calling the missed push data file according to the missed push data file information; the missed data file is sent to the second end system 120.

In this embodiment, a first file list including attribute information of a data file is sent while a first end system is sending the data file, when a second end system receives the data file and the first file list, a second file list in which the attribute information of the received data file is recorded is generated, whether the first file list is consistent with the second file list is judged, when the first file list is inconsistent with the second file list, missing push data file information is determined according to the first file list and the second file list and is sent to the first end system, the first end system calls the missing push file according to the missing push data file information and sends the missing push file to a second end system of a child, reliability and integrity of file sending can be guaranteed, and accuracy of data processing is further guaranteed.

In an embodiment of this document, there is further provided a file reliability interaction method based on a file manifest, applied to a first end system, as shown in fig. 2, including:

step 201, generating a data file;

step 202, generating a first file list according to the data files, wherein attribute information of the data files is recorded in the first file list;

step 203, sending the data file and the first file list to the second end system;

step 204, receiving the missing push data file information sent by the second end system;

step 205, calling the missed push data file according to the missed push data file information;

and step 206, sending the missed pushed data file to the second end system.

In this embodiment, the first file list is also sent while the data file is sent, so that the second end system generates the second file list according to the received data file, and identification of the missed file is realized by comparing the second file list with the first file list, so that reliability and integrity of file sending can be ensured, and accuracy of data processing is further ensured.

In an embodiment herein, as shown in fig. 3, the file reliability interaction method based on the file manifest applied to the first end system includes:

step 301, generating a data file;

step 302, generating a first file list according to the data file, wherein the attribute information of the data file is recorded in the first file list;

step 303, acquiring system time information, and encrypting the system time information;

step 304, sending the data file, the first file list and the encrypted system time information to a second end system;

step 305, receiving the missing push data file information sent by the second end system;

step 306, calling the missed push data file according to the missed push data file information;

and 307, sending the missed data file to the second end system.

In this embodiment, the first file list and the encrypted system time information are also sent while the data file is sent, so that the second end system verifies the encrypted system time information, thereby ensuring the timeliness of the data file and avoiding a malicious attacker from attacking the second end system after acquiring the data file. And after the encrypted system time information passes verification, generating a second file list according to the received data file, and comparing the second file list with the first file list to realize identification of the missed push file, so that the reliability and integrity of file sending can be ensured, and the accuracy of data processing is further ensured.

In an embodiment herein, as shown in fig. 4, the file-manifest-based file reliability interaction method applied to the first end system further includes, in addition to the above steps:

step 401, counting the times of receiving attribute information of a missed push data file in a preset time period;

and step 402, if the times are larger than a preset value, sending abnormal alarm information.

In specific implementation, the predetermined value may be set according to actual requirements, and if the remaining resources of the first end system can respond to the calling of the missed push data file, the predetermined value may be set to be larger, and if the remaining resources of the first end system do not sufficiently respond to the calling of the missed push data file (for example, the time required for calling is longer than the normal time), the predetermined value may be set to be smaller.

The abnormal alarm information may be sent by broadcasting, short message, mail, etc., and this document does not limit this.

According to the method and the device, the abnormity of the file link between the first end system and the second end system can be identified in time, the abnormity removing efficiency can be improved by sending an abnormity alarm, and the user experience is improved.

In an embodiment of this document, there is further provided a file reliability interaction method based on a file manifest applied to a second end system, as shown in fig. 5, including:

step 501, receiving a data file and a first file list sent by a first end system;

step 502, generating a second file list according to the received data file, wherein the second file list records the attribute information of the received data file;

step 503, judging whether the first file list and the second file list are consistent, if not, determining the information of the missed data file according to the first file list and the second file list;

step 504, sending the missing push data file information to the first end system;

step 505, responding to the received data file.

The embodiment is used in combination with the embodiment shown in fig. 2, so that the reliability and integrity of file transmission can be ensured, and the accuracy of data processing can be further ensured.

In an embodiment of the present invention, when the step 501 is implemented, it is further determined whether the first file list corresponding to the data file is received, and if not, the data file is rejected from being processed.

In an embodiment of the present invention, when the step 501 is implemented, if the first file list is not received, the data file may still be processed, the first end system sends a summary file list (a file list within a predetermined time period (for example, daily)) to the second end system according to a predetermined time (for example, morning every day), the second end system determines whether the data file is processed according to the locally recorded summary file list (generated from the data file received within the predetermined time period) and the received summary file list, and if not, the missed-pushing data file information is generated to the first end system, so as to complete the re-pushing of the data file. And if the second end system does not receive the date and junction file list at the appointed time, sending a reminding message to the first end system so that the first end system can resend the date and junction file list.

This embodiment can guarantee the accuracy through the mode of secondary check.

In an embodiment herein, there is further provided a file-manifest-based file reliability interaction method applied to the second end system, as shown in fig. 6, including:

step 601, receiving a data file, a first file list and encrypted time information sent by a first end system;

step 602, decrypting the encrypted time information;

step 603, judging whether the difference between the time information obtained by decryption and the current time information meets a preset condition, if so, executing step 604, and if not, returning to the first end system in the risk prompt message;

step 604, determining whether the first file list and the second file list are consistent, if not, executing step 605, and if so, executing step 607;

step 605, determining missing data file information according to the first file list and the second file list;

step 606, sending the missing push data file information to the first end system;

step 607, responding to the received data file.

The embodiment is used in cooperation with the embodiment shown in fig. 3, and can identify the repeatedly sent data files, so as to avoid repeated response and malicious attack of the data files.

In one embodiment, the step 503 and the step 604 of determining whether the first file list and the second file list are consistent includes:

In this embodiment, the efficiency of consistency determination can be improved by calculating the hash value of the file list and comparing the hash values of the first file list and the second file list.

Based on the same inventive concept, a file-list-based file reliability interaction device applied to a first end system and a second end system is also provided, as described in the following embodiments. Because the principle of solving the problems of the file list-based file reliability interaction device applied to the first end system and the second end system is similar to the file list-based file reliability interaction method applied to the first end system and the second end system, the implementation of the file list-based file reliability interaction device applied to the first end system and the second end system can refer to the file list-based file reliability interaction method applied to the first end system and the second end system, and repeated parts are not repeated.

Specifically, as shown in fig. 7, the file-manifest-based file reliability interaction apparatus applied to the first end system includes:

a data file generating unit 701 for generating a data file;

a sending list generating unit 702, configured to generate a first file list according to the data file, where attribute information of the data file is recorded in the first file list;

a file/list sending unit 703, configured to send the data file and the first file list to a second end system;

a missed push request receiving unit 704, configured to receive missed push data file information sent by the second end system;

a missed push file retrieving unit 705, configured to retrieve a missed push data file according to the missed push data file information;

and a file complementary pushing unit 706, configured to send the missed pushed data file to the second end system.

As shown in fig. 8, the file-manifest-based file reliability interaction apparatus applied to the second end system includes:

a file/list skip request receiving unit 801, configured to receive a data file and a first file list sent by a first end system;

a receiving list generating unit 802, configured to generate a second file list according to the received data file, where attribute information of the received data file is recorded in the second file list;

a missed push file identification unit 803, configured to determine whether the first file list and the second file list are consistent, and if not, determine missed push data file information according to the first file list and the second file list;

a missed push file request unit 804, configured to send the missed push data file information to the first end system;

a file processing unit 805 for responding to the received data file.

The devices shown in fig. 7 and 8 can be used together to ensure the reliability and integrity of file transmission, and thus the accuracy of data processing.

In an embodiment herein, there is also provided a computer device, as shown in fig. 9, the computer device 902 may include one or more processors 904, such as one or more Central Processing Units (CPUs), each of which may implement one or more hardware threads. The computer device 902 may also include any memory 906 for storing any kind of information, such as code, settings, data, etc. For example, and without limitation, memory 906 may include any one or more of the following in combination: any type of RAM, any type of ROM, flash memory devices, hard disks, optical disks, etc. More generally, any memory may use any technology to store information. Further, any memory may provide volatile or non-volatile retention of information. Further, any memory may represent fixed or removable components of computer device 902. In one case, when the processor 904 executes the associated instructions, which are stored in any memory or combination of memories, the computer device 902 can perform any of the operations of the associated instructions. In particular, the instructions of any of the preceding method embodiments are implemented when the processor 904 executes a computer program. The computer device 902 also includes one or more drive mechanisms 908, such as a hard disk drive mechanism, an optical disk drive mechanism, etc., for interacting with any memory.

Computer device 902 may also include an input/output module 910 (I/O) for receiving various inputs (via input device 912) and for providing various outputs (via output device 914). One particular output mechanism may include a presentation device 916 and an associated Graphical User Interface (GUI) 918. In other embodiments, input/output module 910 (I/O), input device 912, and output device 914 may also be excluded, acting as only one computer device in a network. Computer device 902 may also include one or more network interfaces 920 for exchanging data with other devices via one or more communication links 922. One or more communication buses 924 couple the above-described components together.

Communication link 922 may be implemented in any manner, such as over a local area network, a wide area network (e.g., the Internet), a point-to-point connection, etc., or any combination thereof. The communication link 922 may include any combination of hardwired links, wireless links, routers, gateway functions, name servers, etc., governed by any protocol or combination of protocols.

Corresponding to the methods in fig. 2-6, the embodiments herein also provide a computer-readable storage medium having stored thereon a computer program, which, when executed by a processor, performs the steps of the above-described method.

Embodiments herein also provide computer readable instructions, wherein a program therein causes a processor to perform the methods as shown in fig. 2-6 when the instructions are executed by the processor.

It should be understood that, in various embodiments herein, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments herein.

It should also be understood that, in the embodiments herein, the term "and/or" is only one kind of association relation describing an associated object, meaning that three kinds of relations may exist. For example, a and/or B, may represent: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be embodied in electronic hardware, computer software, or combinations of both, and that the components and steps of the examples have been described in a functional general in the foregoing description for the purpose of illustrating clearly the interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

It can be clearly understood by those skilled in the art that, for convenience and simplicity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided herein, it should be understood that the disclosed system, apparatus, and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may also be an electric, mechanical or other form of connection.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purposes of the embodiments herein.

In addition, functional units in the embodiments herein may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the present invention may be implemented in a form of a software product, which is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the methods described in the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The principles and embodiments of this document are explained herein using specific examples, which are presented only to aid in understanding the methods and their core concepts; meanwhile, for a person skilled in the art, according to the idea of the present disclosure, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present disclosure should not be construed as a limitation to the present disclosure.

Claims

1. A file reliability interaction method based on a file list is applied to a first-end system and comprises the following steps:

generating a data file;

generating a first file list according to the data files, wherein the attribute information of the data files is recorded in the first file list;

sending the data file and the first file list to a second end system;

receiving the missing push data file information sent by the second end system;

and sending the missed data file to the second end system.

2. The method of claim 1, further comprising: acquiring system time information and encrypting the system time information;

3. The method of claim 1, further comprising:

4. The method of claim 1, wherein the attribute information comprises: file identification, file size, and file type.

5. A file reliability interaction method based on a file list is applied to a second end system and comprises the following steps:

receiving a data file and a first file list sent by a first end system;

judging whether the first file list and the second file list are consistent, if not, determining missing data file information according to the first file list and the second file list;

sending the missing push data file information to the first end system;

in response to the received data file.

6. The method of claim 5, wherein receiving the data file and the first file list sent by the first end system further comprises: receiving a data file, a first file list and encrypted time information sent by a first end system;

decrypting the encrypted time information;

7. The method of claim 5, wherein determining whether the first file list and the second file list are consistent comprises:

8. A file-manifest-based file reliability interaction apparatus, comprising:

a data file generating unit for generating a data file;

9. A file-manifest-based file reliability interaction apparatus, comprising:

the file/list missing push request receiving unit is used for receiving the data file and the first file list sent by the first end system;

and the file processing unit is used for responding to the received data file.

10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method of any one of claims 1 to 7 when executing the computer program.

11. A computer storage medium on which a computer program is stored, characterized in that the computer program, when being executed by a processor of a computer device, executes instructions of a method according to any one of claims 1 to 7.

12. A computer program product, characterized in that the computer program product comprises a computer program which, when being executed by a processor, carries out the method of any one of claims 1 to 7.