Method and device for downloading configuration data

Abstract

The invention discloses a configuration data downloading method and device. The method comprises the following steps: acquiring a current downloading list file, a historical downloading list file and a bit number assignment list file; comparing the current downloading list file with the historical downloading list file to obtain a comparison result; determining a change list file based on the comparison result; generating configuration data based on the current downloading list file, the change list list file and the bit number assignment list file; and downloading the configuration data into the controller according to the mode of the interface file. Configuration data are downloaded into the controller in an interface file mode and can be directly compatible with configuration software, modification or redesign is not needed, and therefore the flexibility and expandability of the system are improved.

Description

Technical Field

[0001] The present application relates to the field of industrial automation control technology, and in particular to a method and device for downloading configuration data. Background Art

[0002] With the advancement of automation technology, industrial control systems are widely used in fields such as energy, manufacturing, and transportation. Controllers must process signals in real time and provide feedback on operating status and alarms to a host computer (such as configuration software). Configuration software is responsible for configuration, debugging, and monitoring. Operations such as controller firmware updates and incremental downloads rely on the support of configuration software.

[0003] Current technologies mostly rely on a deep coupling between the controller and configuration software to implement controller downloads and updates. Incremental controller downloads and program scheduling are closely coordinated with the configuration software, and all download operations (such as download progress and error checking) require real-time participation from the configuration software. However, supporting different controller types or changing the configuration software often requires extensive modifications or redesign, significantly reducing flexibility and scalability.

[0004] Therefore, how to improve flexibility and scalability has become an urgent problem that needs to be solved in this field. Summary of the Invention

[0005] The present application provides a method and device for downloading configuration data, aiming to improve flexibility and scalability.

[0006] In order to achieve the above objectives, this application provides the following technical solutions:

[0007] A method for downloading configuration data, comprising:

[0008] Get the current download list file, the historical download list file and the bit number assignment list file;

[0009] Comparing the current download list file with the historical download list file to obtain a comparison result;

[0010] Determine a change list file based on the comparison result;

[0011] generating configuration data based on the current download list file, the change list file, and the bit number assignment list file;

[0012] The configuration data is downloaded to the controller in the form of an interface file.

[0013] Optionally, the comparing the current download list file with the historical download list file to obtain a comparison result includes:

[0014] Parsing the current download list file to obtain file information of each file, and constructing a current download cache table based on the file information of each file;

[0015] Parsing the historical download list file to obtain file information of each historical file, and constructing a historical download cache table based on the file information of each historical file;

[0016] For each file in the current download cache table, the file is compared with the historical files in the historical download cache table to obtain a comparison result.

[0017] Optionally, determining a change list file based on the comparison result includes:

[0018] When the comparison result indicates that there is a file name in the current download cache table that is consistent with that in the historical download cache table, comparing the check code of the historical file with the consistent file name with the check code of the file;

[0019] When the verification code of the historical file is inconsistent with the verification code of the file, determining the file type of the file as a modified type;

[0020] Obtaining file information of the file corresponding to the file name from the current download cache table;

[0021] Adding the file type and file information of the file to the original change list file to obtain a change list file;

[0022] When the verification code of the history file is consistent with the verification code of the file, the original change list file is determined as the change list file.

[0023] Optionally, also include:

[0024] Delete the file information of the historical files in the historical download cache table.

[0025] Optionally, determining a change list file based on the comparison result includes:

[0026] When the comparison result indicates that there is a file name in the current download cache table that is inconsistent with that in the historical download cache table, determining the file type of the file with the inconsistent file name as a newly added type;

[0027] Obtain file information of the file corresponding to the file name from the current download list file;

[0028] The file type and file information of the file are added to the original change list file to obtain a change list file.

[0029] Optionally, determining a change list file based on the comparison result includes:

[0030] When the comparison result indicates that there is a file name in the historical download cache table that is inconsistent with the current download cache table, marking the file type of the historical file with the inconsistent file name as a deleted type;

[0031] Obtaining file information of the historical file corresponding to the file name from the historical download cache table;

[0032] The file type of the historical file and the file information of the historical file are added to the original change list file to obtain a change list file.

[0033] A device for downloading configuration data, comprising:

[0034] An acquisition unit, used to acquire the current download list file, the historical download list file and the bit number assignment list file;

[0035] a comparison unit, configured to compare the current download list file with the historical download list file to obtain a comparison result;

[0036] a determining unit, configured to determine a change list file based on the comparison result;

[0037] a generating unit, configured to generate configuration data based on the current download list file, the change list file, and the bit number assignment list file;

[0038] The download unit is used to download the configuration data to the controller in the form of an interface file.

[0039] Optionally, the comparison unit is specifically used to:

[0040] Parsing the current download list file to obtain file information of each file, and constructing a current download cache table based on the file information of each file;

[0041] Parsing the historical download list file to obtain file information of each historical file, and constructing a historical download cache table based on the file information of each historical file;

[0042] For each file in the current download cache table, the file is compared with the historical files in the historical download cache table to obtain a comparison result.

[0043] Optionally, the determining unit is specifically configured to:

[0044] When the comparison result indicates that there is a file name in the current download cache table that is consistent with that in the historical download cache table, comparing the check code of the historical file with the consistent file name with the check code of the file;

[0045] When the verification code of the historical file is inconsistent with the verification code of the file, determining the file type of the file as a modified type;

[0046] Obtaining file information of the file corresponding to the file name from the current download cache table;

[0047] Adding the file type and file information of the file to the original change list file to obtain a change list file;

[0048] When the verification code of the history file is consistent with the verification code of the file, the original change list file is determined as the change list file.

[0049] Optionally, also include:

[0050] The deleting unit is used to delete the file information of the historical files in the historical download cache table.

[0051] The technical solution provided by this application obtains a current download list file, a historical download list file, and a bit number assignment list file; compares the current download list file with the historical download list file to obtain a comparison result; determines a change list file based on the comparison result; generates configuration data based on the current download list file, the change list file, and the bit number assignment list file; and downloads the configuration data to the controller via an interface file. Downloading configuration data to the controller via an interface file allows direct compatibility with configuration software without the need for modification or redesign, thereby improving the flexibility and scalability of the system. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0053] Figure 1 A flowchart of a method for downloading configuration data provided in an embodiment of the present application;

[0054] Figure 2 A flowchart of a file comparison method provided in an embodiment of the present application;

[0055] Figure 3A flowchart of a method for determining a change list file provided in an embodiment of the present application;

[0056] Figure 4 A flowchart of another method for determining a change list file provided in an embodiment of the present application;

[0057] Figure 5 A flowchart of another method for determining a change list file provided in an embodiment of the present application;

[0058] Figure 6 A schematic diagram of a declarative file collection provided in an embodiment of the present application;

[0059] Figure 7 A component diagram of a configuration download module provided in an embodiment of the present application;

[0060] Figure 8 A schematic diagram of the architecture of a configuration data downloading device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0061] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0062] In this application, the terms "comprises," "comprising," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not preclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0063] like Figure 1 FIG. 1 is a flow chart of a method for downloading configuration data provided in an embodiment of the present application, comprising the following steps:

[0064] S101: Obtain a current download list file, a history download list file, and a bit number assignment list file.

[0065] The current download list file contains the list of files to be downloaded, including basic information and verification information for each file. Basic information includes file name, file type, and file size, while verification information includes a verification code generated based on the content of each file.

[0066] Optionally, the historical download list file contains a list of historically downloaded files, including basic information and verification information of each historical file.

[0067] Specifically, the bit number assignment list file includes a bit number identifier and a bit number target value (ie, a specific value that needs to be assigned to the bit number).

[0068] It should be noted that the controller typically retains the same bit number's real-time value by default. The controller identifies bits with the same identifier using compiled bit number identifiers. If the initial value of the bit number is not modified during download, the controller retains the real-time value during operation by default. However, in some special cases, such as when the structure of a sequential function chart programming language changes, the relevant bit number data may need to be restored to its initial value or a specific value. In such cases, a bit number assignment list file is required to specifically assign values ​​to these bits.

[0069] S102: Compare the current download list file with the historical download list file to obtain a comparison result.

[0070] It is understandable that by comparing the current download list file with the historical download list file, the differences between the current download list file and the historical download list file can be clearly identified, and which files have changed can be understood so that subsequent steps can be executed based on the changed files.

[0071] Optionally, in another embodiment of the present application, the specific implementation of step S102 is as follows: Figure 2 As shown, the following steps are included:

[0072] S201: Parse the current download list file to obtain file information of each file, and construct a current download cache table based on the file information of each file.

[0073] The file information of the file at least includes basic information and verification information of the file.

[0074] S202: Parse the historical download list file to obtain file information of each historical file, and construct a historical download cache table based on the file information of each historical file.

[0075] The file information of the historical file at least includes: the file name of the historical file and the check code of the historical file.

[0076] S203: For each file in the current download cache table, the file is compared with the historical files in the historical download cache table to obtain a comparison result.

[0077] It is understandable that, for each file in the current download cache table, the file name is compared with the file name of the historical file in the historical download cache table to obtain a comparison result.

[0078] S103: Determine a change list file based on the comparison result.

[0079] Among them, the change list file contains the difference information of a certain file (that is, the difference information of the file to be downloaded this time relative to the file successfully downloaded last time in the controller, and the granularity of the difference information is in files). The difference information is used to identify whether a file is added, deleted or modified.

[0080] It is understandable that different comparison results correspond to different difference information, and the change list files determined based on the difference information are also different.

[0081] It's important to note that this difference information doesn't refer to internal differences in specific files. Based on the comparison results, the controller quickly processes and downloads the incremental information. Specific internal processing is encapsulated by the controller, and the configuration software is decoupled from the controller, eliminating the need to worry about how the controller handles these difference files. The controller internally loads and analyzes the corresponding files to ensure that the difference files are updated and applied. The configuration software focuses on high-level operations and isn't concerned with the specific details of bit number or code storage and processing.

[0082] In addition, the change list file will be displayed to the user through the configuration interface to let the user know the modified content of this download.

[0083] Optionally, in another embodiment of the present application, the specific implementation of step S103 is as follows: Figure 3 As shown, the following steps are included:

[0084] S301: When the comparison result indicates that there is a file name in the current download cache table that is consistent with that in the historical download cache table, the check code of the historical file with the consistent file name is compared with the check code of the file.

[0085] For example, the current download cache table contains files a and c, and the historical download cache table contains file a. At this time, the comparison result is that the current download cache table contains a file name that is consistent with that in the historical download cache table.

[0086] S302: When the verification code of the historical file is inconsistent with the verification code of the file, the file type is determined to be a modified type.

[0087] It is understandable that when the verification code of the historical file is inconsistent with the verification code of the file, it means that the content of the file in the current download list has changed. Therefore, the file type of the file is determined to be a modified type.

[0088] S303: Obtain file information of the file corresponding to the file name from the current download cache table.

[0089] S304: Add the file type and file information of the file to the original change list file to obtain the change list file.

[0090] It can be understood that the file type and file information of the file are added to the original change list file, that is, the difference information of the file is stored in the original change list file to obtain the change list file, so that the controller can quickly process the download incremental information according to the change list file.

[0091] S305: When the verification code of the historical file is consistent with the verification code of the file, the original change list file is determined as the change list file.

[0092] It is understandable that when the verification code of the historical file is consistent with the verification code of the file, it means that the file content of the historical file at this time has not changed, and there is no need to record it in the original change list. The original change list file is directly determined as the change list file.

[0093] It should be noted that after the change list file is determined, the file information of the historical files in the historical download cache table is deleted. The historical download cache table stores information about files that have already been processed. However, if these files have been updated or are no longer needed, their presence only increases the system storage burden. Deleting no longer needed historical file information can keep the cache table concise and reduce redundant data.

[0094] Optionally, in another embodiment of the present application, the specific implementation of step S103 is as follows: Figure 4 As shown, the following steps are included:

[0095] S401: When the comparison result indicates that there is a file name in the current download cache table that is inconsistent with that in the historical download cache table, the file type of the file with the inconsistent file name is determined to be a newly added type.

[0096] It is understandable that when the comparison result indicates that there is a file name in the current download cache table that is inconsistent with the historical download cache table, it means that the file is a new file, and the file type of the file with the inconsistent file name is determined to be a new type.

[0097] For example, the current download cache table contains files a and c, and the historical download cache table contains file c. The comparison result shows that the current download cache table contains a file with a name inconsistent with that in the historical download cache table: file c. The file type of file c is determined to be a new type.

[0098] S402: Obtain file information of a file corresponding to the file name from the current download list file.

[0099] S403: Add the file type and file information of the file to the original change list file to obtain a change list file.

[0100] It should be noted that the specific implementation of step S403 may refer to step S304 accordingly, and will not be repeated here.

[0101] Optionally, in another embodiment of the present application, the specific implementation of step S103 is as follows: Figure 5 As shown, the following steps are included:

[0102] S501: When the comparison result indicates that there is a file name in the historical download cache table that is inconsistent with the current download cache table, the file type of the historical file with the inconsistent file name is marked as a deleted type.

[0103] It is understandable that when the comparison result shows that the file name in the historical download cache table is inconsistent with the file name in the current download cache table, it means that the historical file is no longer needed, and the file types of these inconsistent historical files should be marked as deleted types.

[0104] For example, the current download cache table contains file a, the historical download cache table contains file a and file c, and the historical download cache table contains a file named c that is inconsistent with the current download cache table. The file type of file c is marked as a deleted type.

[0105] S502: Obtain file information of a historical file corresponding to the file name from a historical download cache table.

[0106] S503: Add the file type of the historical file and the file information of the historical file to the original change list file to obtain the change list file.

[0107] It can be understood that the file type and file information of the historical file are added to the original change list file to obtain the change list file. When the change list file is downloaded to the controller, the controller can delete the historical file according to the file type and file information of the historical file.

[0108] S104: Generate configuration data based on the current download list file, the change list file, and the bit number assignment list file.

[0109] The files in the current download list file include compiled program bit number definition files, program executable code files, system function block library files, controller property configuration files, task list file index files, and other files generated by the downloader, as well as change file lists and bit number assignment lists. The controller uses these files to confirm the integrity and consistency of the current download. This file is download-type-independent and must be generated and included with every download. To reduce the size of the downloaded file, the file content can be dynamically adjusted based on the controller's download type, but the integrity and consistency of the content must be logically guaranteed.

[0110] Specifically, a bit assignment list file lists the bits that require specific assignments and their corresponding memory values ​​after downloading. The controller uses this file to assign values ​​to the specified bits. This file uses a declarative approach, simply identifying the bits that require assignments without involving data storage, copying instructions, or specific processing within the controller.

[0111] It should be noted that the current download list file, the change list file, and the bit number assignment list file are all declarative files, and the generated configuration data is a declarative file set (also including the target download file generated by compilation). The current download list file is used to declare the collection of files downloaded this time and the design for integrity verification of the downloaded content. The change list file is used to declare the files that have been modified compared to the last download, and the design is consistent with the object-level modifications prompted by the configuration interface. The change list file only declares the scope of the modified files and does not involve how the modifications are applied inside the controller. The bit number assignment list file is used to declare that after this download, the real-time values ​​of certain bit numbers should first be synchronized to the specified values. This file only declares the target value and does not involve the method for processing the related copy process of the controller's internal memory.

[0112] For a specific, declarative file collection diagram, see Figure 6 . Figure 6 The program bit number definition file, program executable code file, system function block library file, controller attribute configuration file, task list file index file and other files are files specially generated during the configuration download process to implement the auxiliary download function.

[0113] S105: Download the configuration data to the controller in the form of an interface file.

[0114] The configuration data includes the current download list file and the target value of the bit number after downloading.

[0115] It's understandable that when the configuration software is downloaded, the configuration data is organized according to agreed file names and relative directories. The configuration data is stored in an interface file, a collection of files that serves as the interface between the configuration software and the controller. This file declaratively records the contents of the download, including a list of downloaded files and the target values ​​for the tags after downloading. The configuration software does not specify how the tags and codes are stored or processed within the controller. After downloading to the controller, the controller loads and parses the file according to the agreed-upon conventions, schedules the user program, and ensures that the tags are processed according to the declared values.

[0116] In addition, when downloading, additional files such as a download file list, a changed file list, and a bit number assignment list are generated based on the current configuration compilation result file and the last downloaded configuration compilation result file to ensure a smooth download process. These files can be in readable text formats such as JSON and XML, or binary serialized files.

[0117] For details, see Figure 7 , showing a configuration download module component diagram, Figure 7 The functional modules involved in the configuration software include: "Compilation result loading module", which is responsible for loading and reading the current and previous compilation results; "Changed file and downloaded content identification module", which is responsible for generating a change list file and identifying the file range of the specific downloaded content according to the download type.

[0118] In summary, downloading configuration data to the controller through the interface file can be directly compatible with the configuration software without modification or redesign, thereby improving the flexibility and scalability of the system.

[0119] like Figure 8 , which is a schematic diagram of the architecture of a configuration data downloading device provided in an embodiment of the present application, the downloading device includes: an acquisition unit 100, a comparison unit 200, a determination unit 300, a generation unit 400 and a downloading unit 500.

[0120] The acquisition unit 100 is used to acquire the current download list file, the historical download list file and the bit number assignment list file.

[0121] The comparison unit 200 is used to compare the current download list file with the historical download list file to obtain a comparison result.

[0122] The comparison unit 200 is specifically used to: parse the current download list file to obtain the file information of each file, and build a current download cache table based on the file information of each file; parse the historical download list file to obtain the file information of each historical file, and build a historical download cache table based on the file information of each historical file; for each file in the current download cache table, compare the file with the historical file in the historical download cache table to obtain a comparison result.

[0123] The determining unit 300 is configured to determine a change list file based on the comparison result.

[0124] The determination unit 300 is specifically used for: when the comparison result indicates that there is a file name consistent with the historical download cache table in the current download cache table, comparing the verification code of the historical file with the consistent file name with the verification code of the file; when the verification code of the historical file is inconsistent with the verification code of the file, determining the file type of the file as the modified type; obtaining the file information of the file corresponding to the file name from the current download cache table; adding the file type and the file information of the file to the original change list file to obtain the change list file; when the verification code of the historical file is consistent with the verification code of the file, determining the original change list file as the change list file.

[0125] The determination unit 300 is specifically used to: when the comparison result indicates that there is a file name in the current download cache table that is inconsistent with the historical download cache table, determine the file type of the file with the inconsistent file name as a new type; obtain the file information of the file corresponding to the file name from the current download list file; add the file type and file information of the file to the original change list file to obtain the change list file.

[0126] The determination unit 300 is specifically used to: when the comparison result indicates that there is a file name in the historical download cache table that is inconsistent with the current download cache table, identify the file type of the historical file with the inconsistent file name as a deleted type; obtain the file information of the historical file corresponding to the file name from the historical download cache table; add the file type and file information of the historical file to the original change list file to obtain the change list file.

[0127] The generating unit 400 is configured to generate configuration data based on the current download list file, the change list file and the bit number assignment list file.

[0128] The download unit 500 is used to download the configuration data to the controller in the form of an interface file.

[0129] In summary, downloading configuration data to the controller through the interface file can be directly compatible with the configuration software without modification or redesign, thereby improving the flexibility and scalability of the system.

[0130] Combine Figure 8 The downloading device further includes: a deleting unit for deleting the file information of the historical files in the historical download cache table.

[0131] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for system or system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. Ordinary technicians in this field can understand and implement it without expending creative work.

[0132] Professionals may further appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of the two. In order to clearly illustrate the interchangeability of hardware and software, the above description has generally described the components and steps of each example according to their functions. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians may use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present invention.

[0133] The above description of the disclosed embodiments is intended to enable one skilled in the art to implement or use the present application. Various modifications to these embodiments will be readily apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application is not limited to the embodiments shown herein, but is intended to conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for downloading configuration data, characterized in that: include: Get the current download list file, the historical download list file and the bit number assignment list file; Comparing the current download list file with the historical download list file to obtain a comparison result; Determine a change list file based on the comparison result; generating configuration data based on the current download list file, the change list file, and the bit number assignment list file; The configuration data is downloaded to the controller in the form of an interface file.

2. The method according to claim 1, characterized in that The comparing the current download list file with the historical download list file to obtain a comparison result includes: Parsing the current download list file to obtain file information of each file, and constructing a current download cache table based on the file information of each file; Parsing the historical download list file to obtain file information of each historical file, and constructing a historical download cache table based on the file information of each historical file; For each file in the current download cache table, the file is compared with the historical files in the historical download cache table to obtain a comparison result.

3. The method according to claim 1, characterized in that Determining a change list file based on the comparison result includes: When the comparison result indicates that there is a file name in the current download cache table that is consistent with that in the historical download cache table, comparing the check code of the historical file with the consistent file name with the check code of the file; When the verification code of the historical file is inconsistent with the verification code of the file, determining the file type of the file as a modified type; Obtaining file information of the file corresponding to the file name from the current download cache table; Adding the file type and file information of the file to the original change list file to obtain a change list file; When the verification code of the history file is consistent with the verification code of the file, the original change list file is determined as the change list file.

4. The method according to claim 3, characterized in that Also includes: Delete the file information of the historical files in the historical download cache table.

5. The method according to claim 1, characterized in that Determining a change list file based on the comparison result includes: When the comparison result indicates that there is a file name in the current download cache table that is inconsistent with that in the historical download cache table, determining the file type of the file with the inconsistent file name as a newly added type; Obtain file information of the file corresponding to the file name from the current download list file; The file type and file information of the file are added to the original change list file to obtain a change list file.

6. The method according to claim 1, characterized in that Determining a change list file based on the comparison result includes: When the comparison result indicates that there is a file name in the historical download cache table that is inconsistent with the current download cache table, marking the file type of the historical file with the inconsistent file name as a deleted type; Obtaining file information of the historical file corresponding to the file name from the historical download cache table; The file type of the historical file and the file information of the historical file are added to the original change list file to obtain a change list file.

7. A device for downloading configuration data, characterized in that: include: An acquisition unit, used to acquire the current download list file, the historical download list file and the bit number assignment list file; a comparison unit, configured to compare the current download list file with the historical download list file to obtain a comparison result; a determining unit, configured to determine a change list file based on the comparison result; a generating unit, configured to generate configuration data based on the current download list file, the change list file, and the bit number assignment list file; The download unit is used to download the configuration data to the controller in the form of an interface file.

8. The device according to claim 7, characterized in that The comparison unit is specifically used for: Parsing the current download list file to obtain file information of each file, and constructing a current download cache table based on the file information of each file; Parsing the historical download list file to obtain file information of each historical file, and constructing a historical download cache table based on the file information of each historical file; For each file in the current download cache table, the file is compared with the historical files in the historical download cache table to obtain a comparison result.

9. The device according to claim 7, characterized in that The determining unit is specifically configured to: When the comparison result indicates that there is a file name in the current download cache table that is consistent with that in the historical download cache table, comparing the check code of the historical file with the consistent file name with the check code of the file; When the verification code of the historical file is inconsistent with the verification code of the file, determining the file type of the file as a modified type; Obtaining file information of the file corresponding to the file name from the current download cache table; Adding the file type and file information of the file to the original change list file to obtain a change list file; When the verification code of the history file is consistent with the verification code of the file, the original change list file is determined as the change list file.

10. The device according to claim 9, characterized in that Also includes: The deleting unit is used to delete the file information of the historical files in the historical download cache table.

Images