WO2006066446A1

WO2006066446A1 - A method and device for compatible loading of equipments software in distributed control system

Info

Publication number: WO2006066446A1
Application number: PCT/CN2004/001482
Authority: WO
Inventors: Cheng Xiong
Original assignee: Zte Corporation
Priority date: 2004-12-21
Filing date: 2004-12-21
Publication date: 2006-06-29
Also published as: CN100419680C; CN101040258A

Abstract

The present invention disclose a method for compatible loading of equipments software in distributed control system, wherein it merge the different subfile which support various hardwares into one file, and write the information of the subfile in the file head, and identify the query method of each subfile and select the said subfile base on hardware requirements. The method of present invention almost completely avoid the problem of hardware difference, which is compatible to very different hardware equipments, and acquire sufficient free degree in the design of system software and system hardware, and achieve the effect of simplifying complicate system, and save a great deal of manpower and material resources of development, and economize the equipments investment for the customer, and prolong the service life of the old equipments, and improve the flexibility of system control.

Description

Method and device for compatible loading of equipment software in distributed control system

The invention relates to a software version control method and device suitable for a distributed control system, so that the same software version can be compatible with different hardware platforms, in particular, a software version distributed control related to the communication field, so that each has the same or different functions A hardware platform can be completed using only one and the same software version. Background technique

At present, distributed control systems are widely used in all aspects of social life. Industrial automation, monitoring, communication, etc. are widely used. With the development of computer control and embedded systems, software control has been used in distributed control systems. Become the mainstream.

In a distributed control system, a central device often has to control many peripheral devices, while peripheral devices with the same or different functions may have different hardware implementations, and thus require different software versions for control. In the current technology, different software versions are generally used to control different hardware devices. If the hardware changes, it is often impossible to implement multiple hardware compatibility through simple software modification, which requires a new software to be added accordingly. The version is controlled. In this way, as more and more types of devices are in the system, more and more software versions need to be controlled, and the control relationship of the system becomes more and more complicated. The method proposes a method for controlling the compatibility of different hardware devices by using the same software version, which reduces the control complexity of the central device software, improves the versatility and compatibility of the device, and has different hardware implementations for solving the same function. The device compatibility issue has unique advantages. Invention disclosure

The technical problem to be solved by the present invention is to provide a method and device for compatible loading of device software in a distributed control system, and to overcome the existing distributed control system, different software versions are required for peripheral sub-modules with different logical functions and different physical implementations. The disadvantage of performing control is to solve the problem that the software versions of different hardware implementations existing in the prior art are difficult to be compatible.

In order to achieve the above object, the present invention provides a method for compatible loading of device software in a distributed control system, which is characterized in that different sub-files supporting multiple hardwares are combined into one file, and The sub-file information is written at the beginning of the piece, the query method of each sub-file is identified, and the sub-file is selected according to the requirements of the hardware.

The above method is characterized in that the method further includes the following steps: Step 1: Read the number of file information from the file header; Step 2, check the file information one by one, and extract the version type and version number of the required subfile; Step 3 According to the file information, the sub-file block in which the sub-file is located is indexed; Step 4, the sub-file is used as the running file.

The above method is characterized in that: the file header includes a file identifier, a file length, a number of sub-file information, and a file header check; the file identifier is a magic number, which is used to represent a file category, to quickly determine the file. Format; file length is equal to the length of the entire software version file; the number of subfile information is used to indicate the number of subfiles contained in the current file; the file information check is used to verify that the data of the entire file header and all file information is correct. .

The above method is characterized in that: the sub-file information includes: a version type, a version number, a sub-file start address, a sub-file block length, and a sub-file block check; the version type is a discriminating information, and represents a sub-file corresponding Supported hardware type, by judging whether the version type matches the hardware type, to obtain the sub-file block required by the current hardware; the version number is used for version management and discriminating whether the sub-file matches; the sub-file start address is used to give the sub-file The offset address of the block in the entire file; the subfile block length is the length of the subfile block represented by the subfile information; the subfile block check is the check of the subfile block represented by the subfile information.

The above method is characterized in that, in the step 3, the method further comprises: reading out the entire sub-file block by extracting a starting offset address of the sub-file block from the current sub-file information.

The above method is characterized in that in the step four, the subfile is used by generating a separate version file of the subfile block.

The above method is characterized in that the sub-file is used in the step four by extracting the sub-file block directly from the file.

The above method is characterized in that, in the step 1, the verification extraction process of the version file header is further included:

Step a, discriminate the file mark, if the requirements are met, perform step b, otherwise perform step f;

Step b, reading the number of sub-file information;

Step c, calculating the length of the file information;

Step d, calculating file information verification; Step e, determining whether the verification is correct, if yes, executing step g, otherwise performing step f;

Step f, performing exception processing;

Step g, the process ends.

The foregoing method is characterized in that: the generating a separate version file includes the following steps: Step A: obtaining a hardware type of the lower level device;

Step B: Obtain a sub-file block suitable for the subordinate device;

In step C, the sub-file block is delivered as a separate software version.

The technical effect of the present invention is that: according to the method of the present invention, compared with the prior art, great progress is made in software compatibility, and in the past, when the same software is compatible with multiple hardware devices, due to hardware devices The limitation of the software compatibility is very limited. Once the hardware difference is too large, it may not be compatible. This method almost completely avoids the hardware difference problem and can be compatible with the extremely different hardware devices. The software and hardware design has achieved a great degree of freedom, which has the effect of simplifying complex systems, saving a lot of development manpower and material resources, saving equipment investment for customers, extending the service life of old equipment, and improving the flexibility of system control. Sex. BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is the verification extraction process of the version file header;

Figure 2 is a sub-file information indexing process;

Figure 3 is a sub-file block extraction process;

FIG. 4 is a flowchart of software loading of a lower-level device by a superior control device;

Figure 5 is a flow diagram of a hardware device selectively using a subfile block;

Figure 6 is a flow chart of the steps of the method of the present invention. The best way to implement the invention

The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings:

The software version of the present invention is compatible with different hardware methods as follows:

The core of the method implementation is that a software version supports multiple hardwares. In fact, multiple files are merged into one file, and file information is written at the beginning of the file to identify the query method for software sub-files supporting various hardware. . The format of the entire software version file is as follows

File header file letter* subfile information subfile subfile

Figure 6 is a flow chart of the steps of the method of the present invention, comprising the following steps:

Step 601 reads the number of file information from the file header.

File header

The file identifier, the file length, the number of subfile information, and the file header check are included in a file header. among them:

The file identifier is a specific magic number (Magic numbers, which refers to a string of numbers at the beginning of the binary file), especially the category of the file, used to quickly determine the file format.

The file length is equal to the length of the entire software version file.

The number of subfile information indicates the number of subfiles contained in the current file.

The file information check is used to verify the entire header and whether the data in the range from file information 1 to subfile information N is correct.

From the header, you can index the number of subfiles and verify that the header is correct.

Step 602 checks the file information one by one, and extracts the required version type and version number.

Subfile information

After confirming that the file header is correct, all sub-file information can be scanned. The sub-file information includes the following information:

Version type

version number

Subfile start address

Subfile block length

Subfile block check

The version type is a main discriminating information, which represents the type of hardware supported by the subfile. By judging whether the version type matches the hardware type, the subfile block required by the current hardware can be obtained.

The version number is mainly used for version management, and it can be determined whether the software is integrated with other software. The subfile start address gives the offset address of the subfile block in the entire file.

The subfile block length refers to the length of the subfile block represented by one subfile information.

Subfile block check refers to the check of a subfile block represented by a subfile information.

In this way, by scanning the file sub-information, the sub-file information corresponding to the current hardware can be found, and the file block can be found by the sub-file information.

Step 603 indexes the subfile block according to the file information.

After the current sub-file information is obtained, the starting offset address of the sub-file block in the software version can be extracted, the entire sub-file block is read, and the sub-file block check is performed.

Step 604 uses the sub-file block to run the software for the board.

After the sub-file block is obtained, the sub-file block can be additionally generated as a separate version file, or only extracted from the file when the sub-file block needs to be used.

Figure 1 shows the verification extraction process of the version file header, including:

Step 101: Identify the file identifier, if yes, go to step 102, otherwise go to step 106; Step 102: Read the number of sub-file information;

Step 103: Calculate the length of the file information;

Step 104: Calculate the file information check; 'Step 105: Determine whether the check is correct, if yes, go to step 107, otherwise go to step 106; Step 106: Perform exception handling;

Step 107: Go to the next process.

The version file header must be verified to verify that the data is error-free before it can be valid. The check in the file header is the verification of the entire file header and all sub-file information. After the file header is verified, the number of subfile information is extracted as the range of the index subfile information.

Figure 2 is a sub-file information indexing process;

Step 201: The current sub-file information index is set to zero;

Step 202: Determine whether the file version type matches the hardware, if yes, go to step 206, otherwise go to step 203;

Step 203: The current sub-file information index is incremented by one;

Step 204: Determine whether the current sub-file information index is the maximum, if yes, go to step 205, no. Return to step 202;

Step 205: Perform exception processing. Step 206: Extract current sub-file information and save it;

Step 207: Go to the next process.

The flow of Figure 2 is the continuation of the flow of Figure 1. The sub-file information indexing process needs to use the number of sub-file information read in the process of Figure 1, as the maximum value of the sub-file information index. The process iterates through all the subfile information until it finds the required subfile information.

Figure 3 is a sub-file block extraction process, including - step 301: obtaining file information;

Step 302: Read a sub-file block start address;

Step 303: Read the sub-file block length;

Step 304: Calculate the subfile block and verify;

Step 305: Determine whether the calculated checksum is equal to the stored in the subfile information, if yes, go to step 307, otherwise go to step 306;

Step 306: exception handling;

Step 307: Read out the entire subfile block;

Step 308: End.

The flow of Figure 3 is next to the flow of Figure 2, and the current sub-file information obtained in the process of Figure 2 is the entry parameter of the process of Figure 3. The process obtains the offset and length of the subfile block from the current subfile information, and calculates the checksum of the file block. The extracted subfile block is the available target data.

This specification provides two common implementations.

Embodiment 1, the selective software loading of the superior control device to the lower device:

As shown in FIG. 4, the process of software loading the lower-level device by the upper-level control device includes: Step 401: Obtain a hardware type of the lower-level device;

Step 402: Obtain a sub-file block suitable for the subordinate device;

Step 403: The sub-file block is delivered as a separate software version.

When the upper-level control device performs software loading on the lower-level device, the upper-level control device may not load all the software versions to the lower-level device, but only need to reconfigure the sub-file blocks needed for the lower-level device to form a new software version, and then directly load the The lower-level device has the advantage of saving storage resources of the lower-level device.

In the second embodiment, the hardware device selectively uses the subfile block:

Figure 5 shows the flow of selective use of subfile blocks by hardware devices, including: Step 501: Extract a subfile block from the version file.

Step 502: Use the subfile block.

The hardware device downloads the entire software version to the storage device of the device, and then determines the extracted sub-file block according to the current hardware type, and uses the sub-file block.

The difference between the two implementations is actually to extract the sub-file blocks on different devices. The first implementation is to extract the sub-file blocks at the superior control device, and the second implementation is to extract the sub-file blocks at the device.

In order to achieve the above object, the present invention further provides a distributed control system, including a device software compatible loading module, wherein the device software is compatible with a loading module, and is used to merge different sub-files supporting multiple hardware into In a file, and write sub-file information at the beginning of the file, identify the query method of each sub-file and select the sub-file according to the requirements of the hardware.

The distributed control system software compatibility scheme described in this paper is a very powerful software compatibility scheme, which plays an important role in simplifying the system structure and improving system compatibility in complex systems.

The above are only specific embodiments of the invention and should not be construed as limiting the scope of the invention. The invention may be embodied in a variety of other embodiments without departing from the spirit and scope of the invention. Industrial applicability

The invention solves the problem of hardware difference, can be compatible with the hardware device with great difference, obtains a great degree of freedom in the design of the system software and hardware, plays the effect of simplifying the complex system, saves a lot of development manpower and material resources, and replaces Customers save on equipment investment, extend the life of older equipment, and increase the flexibility of system control. The invention can be widely applied in various aspects of social life, industrial automation, monitoring, communication and the like.

Claims

Claim

A method for compatible loading of device software in a distributed control system, characterized in that different sub-files supporting multiple hardwares are combined into one file, and sub-file information is written at the beginning of the file, and the sub-files are identified. Query the method and select the subfile according to the requirements of the hardware.

2. The method according to claim 1, further comprising the steps of: Step 1: reading the number of file information from the file header;

Step 2: Check the file information one by one, extract the version type and version number of the required subfile; Step 3, index the subfile block where the subfile is located according to the file information;

Step 4, use this subfile as the run file.

The method according to claim 2, wherein the file header includes a file identifier, a file length, a number of sub-file information, and a file header check;

The file identifier is a magic number used to represent the category of the file to quickly determine the file format; the file length is equal to the length of the entire software version file;

The number of subfile information is used to indicate the number of subfiles contained in the current file;

The file information check is used to verify that the data of the entire file header and all file information is correct.

The method according to claim 3, wherein the sub-file information includes: a version type, a version number, a sub-file start address, a sub-file block length, and a sub-file block check;

The version type is a discriminating information, which represents the supported hardware type of the subfile, and determines whether the version type matches the hardware type to obtain the subfile block required by the current hardware;

The version number is used for version management and determines whether the subfile matches;

The subfile start address is used to give the offset address of the subfile block in the entire file;

The subfile block length is the length of the subfile block represented by the subfile information;

The subfile block check is a check of a subfile block represented by a subfile information.

The method according to claim 4, wherein the step 3 further comprises: reading out the entire sub-file block by extracting a starting offset address of the sub-file block from the current sub-file information.

6. The method according to claim 5, wherein in the step four, the subfile is used by generating a separate version file of the subfile block.

7. The method according to claim 5, wherein in the step four, the subfile is used by extracting the subfile block directly from the file.

The method according to claim 2, 3, 4, 5, 6 or 7, wherein the step 1 further comprises a verification extraction process of the version file header - step a, discriminating the file flag, conforming If necessary, perform step b, otherwise perform step f;

Step b, reading the number of sub-file information;

Step c, calculating the length of the file information;

Step d, calculating file information verification;

Step e, determine whether the verification is correct, if yes, execute step g, otherwise perform step f;

Step f, performing exception processing;

Step g, the process ends.

9. The method according to claim 6, wherein the generating the separate version file comprises the following steps:

Step A, obtaining the hardware type of the lower device;

Step B: Obtain a sub-file block suitable for the subordinate device;

In step C, the sub-file block is delivered as a separate software version.

10. A distributed control system, comprising a device software compatible loading module, wherein the device software compatible loading module is configured to merge different subfiles supporting multiple hardware into one file, and write at the beginning of the file. The subfile information identifies the query method of each subfile and selects the subfile according to the requirements of the hardware.