KR100350319B1 - Method of Self-loading Programs in the Communication System - Google Patents

Abstract

The present invention relates to a method of self-loading a program in a communication system, and in particular, to remove unnecessary download tasks by examining a version of a corresponding program when loading a program. It relates to a method for loading a program itself in a communication system.

In the communication system according to an embodiment of the present invention, a method for loading a program itself may include: receiving version information before loading a program and comparing the version information with a version of a file header stored in a download directory; And performing a self loading function or a host loading function according to the version comparison result.

Description

Method of Self-loading Programs in the Communication System

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method for loading a program itself in a communication system, and more particularly, to a method for loading a program itself in a communication system that checks a version of a corresponding program when the program is loaded to remove unnecessary download tasks. .

In general, when there is a request for loading a program in a communication system, two kinds of operations are performed. That is, one is loading without comparing the versions of the file to be loaded, and the other is not loading from the host when the versions are the same by comparing the versions of the file before loading. In this case, the actual version comparison was not performed.

First, when loading is performed without checking the version at the time of loading request, the operation is simple. Whenever there is a request for loading from the outside, the loading is performed unconditionally from the host. In the first case, the loading is performed even if the program is the same version as the previously loaded program. Therefore, the loading operation of the same program is unnecessary, which in turn uses resources inefficiently and reduces the loading time. It causes waste.

Secondly, when version checking is performed at the time of loading request, the following operation is performed.

First, a list of files to be loaded is requested to receive a corresponding list from the host, and a file list is generated by collecting information such as names or versions of files to be loaded from the list.

Accordingly, the file list is used to find a target file to be loaded in the future, and manages a separate list of files to be loaded while performing loading. That is, when loading, it finds the target file of the next loading in the file list to be loaded, adds to the loaded file list with the information of the file, and after loading, it indicates that the loaded file is loaded in the information about the corresponding file in the loaded file list. give.

At this time, the version is checked after adding a file entry to the loaded file list, that is, comparing the file in the loaded file list with the version of the file in the loaded file list. The reason for doing this is mainly to avoid reloading a file that has already been loaded if the connection is restored when the connection is lost while the connection is lost. . Here, the loaded file is not a file loaded in a previous loading task in which all loading tasks are already completed, but a file loaded in a loading task in which the operation is interrupted during loading.

Then, if the same version is checked and the file is already loaded as a result of the inspection, the loading operation is skipped and the target of loading is transferred to the next file. Thus, checking the version is not about when the version of the actual file is upgraded.

In other words, in the second case, if a package is frequently compiled and released due to minor changes in the actual package, the version is changed whenever there is a minor change. There is a limit.

Thus, unless it's a major change, the program to be downloaded is often kept at the same version and no checking of the actual version is performed. In addition, when checking the version, it is not the version check that is suitable when the file to be downloaded is actually upgraded. If two files are to be loaded during the loading operation, only one file is loaded and the host is connected. This is a version check in order to prevent reloading of the first file already downloaded when the connection is restored in case of a broken connection.

In other words, when a file is modified and downloaded again, it can be said to be the same as the method of loading unconditionally, which is the first case. Therefore, when a file having the same version and the same content is loaded, the existing file is removed and downloaded again. Duplicate

As such, in the conventional method, when there is a loading request of a program in a communication system, even if a program of the same version as a previously loaded program is unconditionally loaded, a loading operation for the same program can be performed unnecessarily. This causes the problem of inefficient use of resources required for loading and waste of time required for loading. In addition, even if version checking is performed in a conventional manner, there is a disadvantage in that it does not give sufficient reliability.

In order to solve the above problems or disadvantages, the present invention is to check the version information of the corresponding program when loading the program in the communication system, if the same version (that is, when the compilation time is the same) host during the loading operation Eliminates unnecessary work from downloading from other versions (that is, when compilation time is different) and allows loading from the host to be performed by comparing the exact version, thus reducing loading time and reducing resources It is not only to prevent waste of time and time, but also to reliably load recent programs by accurate version checking.

1 is a block diagram showing the configuration of a system for self-loading a program in a communication system according to an embodiment of the present invention.

2 is a flowchart illustrating a program self loading method in a communication system according to an embodiment of the present invention.

3 is a flowchart illustrating a version comparison process of FIG. 2.

4 is a flowchart illustrating a process of performing a loading function in FIG. 2.

Explanation of symbols on the main parts of the drawings

10: Host

20: Target Processor

21: IPC (Inter Process Communication)

22: IPC Client

23: program loader

In the communication system according to an embodiment of the present invention for achieving the above object, a method of loading a program itself includes: receiving version information before loading the program and comparing the version with a version of a file header stored in a download directory; And performing a self loading function or a host loading function according to the version comparison result.

The version comparison process may include establishing a connection between a host and a target processor and setting the connection to an initialization load state; Requesting a file list to receive a file list table; Regenerating a file list using the name and version of the received file to find a file to load; Checking whether a file is a program file by checking a first loading flag when there is a file to be loaded; Setting the first loading flag to false and requesting version information in case of loading of the program file; And receiving the version information and comparing it with a version of a previous file in a download directory. Alternatively, the version comparison process may include requesting and receiving a corresponding data file in the case of loading the data file by checking the first loading flag; Checking a data loading flag to determine whether loading of the data file is completed; If the loading of the data file is not completed, the step of setting the data loading flag to false and finding the next file to be loaded, characterized in that further comprises. Alternatively, the version comparison process may further include performing an end of loading operation when there is no file to be loaded or when loading of the data file is completed.

And, the process of performing the loading function is characterized in that it comprises a step of using the program file stored in the download directory to set the self-loading state when the comparison version is the same. Alternatively, the performing of the loading function may include requesting a program file to be loaded when the compared version is different and loading a new version of the program. Also, alternatively, the performing of the loading function may include checking a self loading flag to determine whether a self loading state is performed; Checking whether the loading of the corresponding file is completed by checking a data loading flag in the self loading state or after loading a file to be loaded; When the loading of the file is completed, characterized in that further comprising the step of performing the end of the loading operation. Alternatively, the loading function performing process may further include searching for a file to be loaded after setting the data loading flag to false when the file is not in the self loading state or when the loading of the file is not completed. Characterized in that made.

According to the present invention, before loading a program, a request for version information is received from a host, compared with a header of a corresponding file in a directory in which a received and downloaded file is stored. Allows you to download. In addition, the present invention allows a file to be requested and downloaded to the host when there is a data file, which is decompressed onto the current scheme to download two files and a data file to run the execution processor. Allows you to load the data file later. Therefore, it checks whether the first file is loaded or the second file is loaded and sends a message requesting the version information to the host when the first file is loaded and when the second file is loaded. Will immediately send a message requesting the file to the host. Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

In the communication system according to an embodiment of the present invention, as shown in FIG. 1, a program for loading itself may be divided into a host 10 and a target processor 20 of a main body. The inside includes an IPC 21, an IPC client 22, and a program loader 23. Here, FIG. 1 illustrates only a core object for loading the program itself, and objects necessary for other loading but not directly related will be omitted for convenience of description.

The IPC 21 is a block that actually performs a delivery task so that the blocks in the target processor 20 can transmit and receive a message with the host 10. The IPC 21 performs a message transmission at the request of the IPC client 22. Provide service.

The IPC client 22 is an interface object that is in charge of exchanging messages with the host 10 when a program is loaded. The IPC client 22 applies a message transfer request to the host 10 to the IPC 21 and the IPC ( The host 10 receives a message from the host 10 to perform a necessary task or delivers the message to the program loader 23 according to the task.

The program loader 23 is an object that predominantly performs program loading, and requests a file list, version information, files to be actually downloaded, and the like.

Meanwhile, the program loading operation of the target processor 20 downloads the compressed file from the host 10 and stores it in a temporary directory, and decompresses it in another directory to drive the executable file in the corresponding directory. The host 10 does not download the program at once, but because the size of the program to be downloaded is too large, the host 10 splits the program into several sequences and sends the sequences to the target processor 20 one by one. do.

Accordingly, the target processor 20 first receives a header and checks a file size before receiving the sequences, and each time a code (ie, a sequence) is received, the number of sequences of the corresponding block is received. This is accompanied by the overhead of the work to be processed, such as checking and checking the checksum. If the task is executed for the same program of the same version, a lot of resources and time are wasted.

Thus, in order to eliminate the unnecessary work, the target processor 20 of the present invention receives a signal that promises a version of a program to be loaded in advance, that is, a signal including version information, from the host 10 before loading to eliminate unnecessary work. The version of the program to be loaded is compared with the version of the program that is already loaded to determine whether to perform the loading or to use the program that has been previously loaded.

In other words, the target processor 20 supports two types of loading functions, one of which is a host loading, which is a conventional method, and the other of which loads itself using a program stored in the system itself without being downloaded from the host. to be. Here, the self-loading function receives a version of a file to be loaded from the host 10 before performing the loading and compares it with the version of the file loaded in the previous loading operation. Instead of downloading the file, the loading operation proceeds with the previously loaded file, that is, the download operation is omitted. The host loading function receives the version of the file to be loaded from the host 10 before performing the loading and compares the version of the file with the file loaded in the previous loading operation. It downloads from the host 10 and performs loading. In this case, the version refers to the date of creation of the file to be downloaded, not the explicitly named version (Character String) for the file, and refers to a part of the file header.

A method of loading a program itself in a communication system according to an exemplary embodiment of the present invention will be described with reference to the flowchart of FIG. 2.

First, the target processor 20 requests the host 10 for version information before loading the program, receives the version information from the host 10, and checks the corresponding file in the header of the already downloaded file stored in the directory. The version is read and compared with the received version information (step S1).

In this case, the target processor 20 performs the self loading function or the host loading function according to the result of the comparison in the first process S1. That is, if the same program is the result of the comparison, the target processor 20 performs the self loading function. As a result of the comparison, in case of another program, the host loading function is performed (step S2).

First, the version comparison process of the first process S1 will be described in more detail with reference to the flowchart of FIG. 3.

First, the connection between the host 10 and the target processor 20 is established and the state is set to an initial load state, that is, an initial value of flags is set. Here, the flag consists of a self loading flag, a data loading flag, and a first loading flag so that the self loading function and the host loading function can be distinguished and processed, and the processing is true / false of the flags. ) Depends on the value.

In other words, the self loading flag indicates whether the type to be loaded is self loading or host loading. The data loading flag is a flag used to load a data file from the host 10 at the time of self loading. If the value is true, the data loading flag indicates a state before loading the data file and a state after loading if the value is true. The first loading flag is a flag indicating that the first file (for example, a program file) is loaded when loading a file and a data file to decompress two files, that is, a running processor by using the current scheme. If this value is true, it means that the first file is loaded without any file loaded yet. If it is false, it means that the second file (for example, data file) is loaded after the first file is loaded.

At this time, in the initialization load state, the value of the self loading flag is set to false, the value of the data loading flag is set to false and the value of the first loading flag is set to true (step S1-1).

Thereafter, the target processor 20 requests a file list from the host 10 (step S1-2). The host 10 transmits the file list to the target processor 20 in the form of a table according to the file list request of the target processor 20.

Accordingly, the target processor 20 receives a file list in the form of a table from the host 10 (step S1-3), and generates a new file list with the name and version of the received file (step S1-3). S1-4). Then, the file to be loaded is searched for in the corresponding new file list. At this time, it is checked whether there is a file to be loaded (step S1-5).

If there is a file to be loaded in step 1-5 (S1-5), it is checked whether it is a program file or a data file, that is, whether the value of the first loading flag is set to true (step S1-6).

In this case, when loading the first file (for example, a program file) in the first to sixth steps (S1-6), that is, when the value of the first loading flag is set to true, the value of the first loading flag is set. After resetting to false (step S1-7), a message requesting version information is sent to the host 10 (step S1-8). In response to the request of the target processor 20, the host 10 loads version information, that is, information about a production date (compiled and compressed date) of a program to be downloaded, in the response message and the target processor 20. Send it out.

Accordingly, the target processor 20 receives the response message containing the version information from the host 10 (step S1-9) and examines the received response message in the program loader 23, that is, in the download directory. The version information is read from the header of the file to check whether the version of the received response message is the same as the version of the file header in the download directory (step S1-10).

In other words, checking whether the versions are the same in steps 1-10 (S1-10) is to read 4 bytes of the header portion of the previous header of the previously loaded program and receive 4 bytes received from the host 10. ), If the result of comparison with the response message is the same, it means the same version, and the contents of the corresponding 4 bytes are the date of compressing the program.

Alternatively, when the second file (eg, a data file) is loaded in step 1-6 (S1-6), that is, when the value of the first loading flag is set to false, the corresponding data file is requested. A message is sent to the host 10 (step S1-11), and a header, code, and end of a data file are received from the host 10 (step S1-12). In this case, when the file size is large, the host 10 splits the sequence into several sequences and transfers them in order, and the operation of receiving the corresponding code is repeatedly performed until all the sequences are received. Here, the code refers to the sequence.

That is, when the data file exists, the host 10 requests the data file to download the data file. If the data file is downloaded, the data file is loaded later. .

Then, it is checked whether the data file is in a state before loading, that is, whether the value of the data loading flag is set to true (step S1-13), in which case the data loading in the corresponding step 11-13 (S1-13). If the value of the flag is set to true, after resetting the value of the corresponding data loading flag to false, the process returns to step 1-5 (S1-5) to check whether there is a next file to be loaded (step S1). -14).

On the other hand, when there is no file to be loaded in the first step (S1-5) or the state after loading the data file in the first-first step (S1-13), that is, the value of the data loading flag If it is set to false, the end of the loading operation is performed, that is, the file is decompressed and installed with the downloaded file (step S1-15).

Secondly, the process of performing the loading function of the second process S2 will be described in more detail with reference to the flowchart of FIG. 4.

First, as a result of the comparison in the first step S1, it is checked whether the same program is the same version (step S2-1). In this case, when the program is not the same program in the corresponding step 2-1 (S2-1), that is, a program compiled on different dates, the first file and the second file should be loaded because the host is not the self-loading. Sends a message requesting files to be loaded to the host 10 (step S2-2), and receives a header, a code, and an end of the files from the host 10. From the host 10, a reliable program to actually apply the latest version is loaded (step S2-3).

On the other hand, in the case of the same program in step 2-1 (S2-1), that is, programs compiled on the same date, the first file does not need to be loaded because it is self-loading. And the data, ie PLD (Programmable Logic Device) data file, must be downloaded separately from the host 10, so reset the value of the data loading flag to true and indicate that the first list has been loaded. By setting again to true, the state is set to the self-loading execution state (step S2-4). That is, since there is no need to reload from the host 10, the program file of the previously loaded and compressed state on the temporary directory is used.

At this time, the process of storing and decompressing the compressed file in a temporary directory is performed in two cases, namely, the loading from the host 10 and the self-loading, and the PLD data file among the files to be loaded. Only when the data file is to be downloaded from the host (10).

Then, it is checked whether the value of the self loading flag is false (step S2-5).

Therefore, if the value of the self loading flag is true after performing the second to third steps S2-3 or the second to five steps S2-5, whether the value of the data loading flag is set to true. Check (step S2-6).

At this time, when the value of the self loading flag is false in step 2-5 (S2-5) or when the value of the data loading flag is true in step 2-6 (S2-6), loading the corresponding data. After resetting the value of the flag to false (step S2-7), the process returns to the first to fifth steps S1-5 of the first step S1 to reconfirm whether there is a file to be loaded next (step S2-). 8).

On the other hand, if the value of the data loading flag is false in step 2-6 (S2-6), the end of the loading operation is performed, that is, to decompress and install the downloaded file ( Step S2-9).

In the communication system according to the embodiment of the present invention as described above, the program self loading method is applied to the operation maintenance of the intelligent network processor. The biggest difference from the conventional technology is that the request for version information is received by the host before loading and the flag variable is loaded. To determine the next process.

As described above, by investigating the version of a program to be loaded by the present invention first, in the case of a program of the same version, by eliminating the task of downloading from the host during the loading operation, it is possible to prevent waste of resources and time due to unnecessary work. In case of different version, loading from the host is performed by comparing the exact version, so that the latest program can be loaded reliably.

Claims (8)

File header of a program that is already stored in the download directory of the target processor by receiving information about a compile time existing in the file header of the program before the target processor in the system loads a program existing on the host in the communication system Comparing the information with respect to the time of compilation present in the ; And performing the self loading function or the host loading function by the target processor according to the result of comparing the information on the compilation time . The method of claim 1, Comparing information on a compilation time present in the file header may include establishing a connection between a host and a target processor and setting the connection to an initialization load state; Requesting a file list to receive a file list table; Searching for a file to be loaded by regenerating a file list by using the name of the received file and information on a compile time present in a file header ; Checking whether a file is a program file by checking a first loading flag when the file to be loaded is present; Setting the first loading flag to false in the case of loading the program file and requesting information about a compile time present in the file header ; Receiving the information on the compilation time from the host and comparing the information on the compilation time existing in the file header of the previous file in the download directory of the target processor. . The method of claim 2, Comparing the information on the compilation time present in the file header, the method comprising: checking and receiving the first loading flag and requesting and receiving a corresponding data file when the data file is loaded; Checking a data loading flag to determine whether loading of the data file is completed; And if the loading of the data file is not completed, setting the data loading flag to false and finding the next file to be loaded. The method of claim 3, Compiling the information on the compilation time of the file header further comprises the step of performing the end of the loading operation when there is no file to be loaded or the loading of the data file is completed, the program in the communication system, characterized in that Self loading method. The method of claim 1, The performing of the loading function may include setting a self-loading state to use a program file stored in a download directory of a target processor when the information about the compiling time point is the same. How to load the program itself in the system. The method of claim 1, The performing of the loading function may include loading a newly compiled program by requesting a program file to be loaded when information on the compared compilation time points is different from each other. The method according to claim 5 or 6, The performing of the loading function may include: checking whether a loading state is performed by checking a loading flag; Checking whether the loading of the corresponding file is completed by checking a data loading flag in the self loading state or after loading a file to be loaded; When the loading of the file is completed, the method of loading the program itself in the communication system, characterized in that further comprising the step of performing the end of the loading operation. The method of claim 7, wherein The performing of the loading function may further include finding the next file to be loaded after setting the data loading flag to false when the file is not in the self loading state or when the loading of the file is not completed. How to load the program itself in the communication system.