JP4360089B2 - Data transfer method, apparatus and recording medium - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
In a hierarchically configured network environment, the management system collects various information of the managed system and manages the information in the management system (the managed system is regarded as a client that calls the management system request) , A server that responds to requests).
[0002]
[Prior art]
In the system shown in FIG. 1, the managed system is a system that returns static (unique) results in response to a request for information acquisition from the management system. The information acquisition request is sent to the managed system (106) via the relay management system (102 to 105) via the relay method.
[0003]
Similarly, a response result to the information acquisition request is also returned to the management system via each relay management system in the relay system. In this case, the information acquisition request and the response result are not exchanged along different paths.
[0004]
As shown in FIG. 2, the relay management system (202 to 205) is composed of a management function and a managed function, and issues an information acquisition request in the same manner as the management system, and makes the same information acquisition request as the management system. is there. As an example of a system having such properties, there is a system that acquires asset information and the like on a managed system from a management system in a multi-layer configuration as shown in FIG.
[0005]
[Problems to be solved by the invention]
In the above conventional method, when the management system and each relay management system make the same information acquisition request to the managed system, the same information acquisition request and response result flow multiple times on the route, which is redundant. Yes (the part where the information acquisition request and the response result arrow in FIG. 1 overlap), and in some cases, a problem occurs such as loading the network.
[0006]
[Means for Solving the Problems]
In the present invention, the following means are performed in order to solve the above problems. When making an information acquisition request from the management system to the managed system, it is determined whether or not the same information acquisition request is made in the relay management system on each route.
[0007]
When making the same information acquisition request, the relay management system recognizes the same information acquisition request. When an information acquisition request is passed to the managed system and a response result is returned, it is acquired when the response result is required in each relay management system, and finally the response result is passed to the management system.
[0008]
As a result, it is possible to prevent the same data from flowing in the path. Each relay management system has a response result for a specific information acquisition request in advance, so that if there is an information acquisition request from a higher-level management system or relay management system, the relay management system displays the response result. By returning it, it becomes possible to reduce the data transfer amount of the route from the relay management system to the managed system.
[0009]
DETAILED DESCRIPTION OF THE INVENTION
Examples of the present invention will be described below. The embodiment will be described by taking as an example a system for managing the asset information of the managed system in a multi-level network environment as shown in FIG. 3 (although it is omitted in FIG. 3, such as offices, branches, sales offices, etc.) There are multiple relay management systems and managed systems in each base and department within each base).
[0010]
It is assumed that the relay management system in each hierarchy is subordinate to the higher-level management system and does not require information on other management systems in the same hierarchy. The flow of processing will be briefly described.
[0011]
First, as shown in FIG. 4, items of information necessary for the management system and the relay management system of each hierarchy are defined. Next, as shown in FIG. 5, an information acquisition request is issued from the management system, and an information acquisition request is made to the managed system by repeatedly merging items of information required by the relay management system of each layer and downloading an item file.
[0012]
Next, as shown in FIG. 6, the asset information result file input in the managed system is uploaded to the upper management system. Each relay management system updates information on items defined in its own system, and repeatedly uploads other items to the higher-level management system and returns a response result.
[0013]
Although the asset information management system is described as an example, the present invention can also be applied to a system that handles other information for an information acquisition request.
[0014]
Example 1
FIG. 8 shows a block diagram of a program on the relay management system. A merge processing unit (hereinafter referred to as merge processing) (805) and a lower layer system that receives an item file composed of a group of items downloaded from the management program main body (802) and the upper layer management system, and performs item merge processing Receives a result file consisting of items and asset information from a lower-level management system or managed system and updates the asset information (hereinafter referred to as update processing) (804) and is managed by its own system An editing processing unit (hereinafter abbreviated as editing processing) (803), a user terminal (801) for displaying and operating information, and a DB (806) for storing items and asset information. Then, as shown in FIG. 7, a DB structure for adding attributes to each item is adopted.
[0015]
This attribute includes a self-system management item indicating that management is performed at its own hierarchical position of “0”, a high-level system management item indicating management by a high-level system of “1”, and a high-level system of “2”. Set one of the three statuses of the common items that are common to your system. Basically, the relay management systems of all layers can be realized with the same configuration, but the highest management system is a program that does not require merge processing.
[0016]
In addition, each process can be processed in parallel, and there is a timing at which DB updates overlap in that case, but it is assumed that exclusive control has been applied to that part in advance (in the flow) (Omitted).
[0017]
First, editing processing will be described. In the editing process, the contents of the DB of the own system are displayed and edited. As for the display of asset information stored in the DB, only items other than the higher system management items are displayed.
[0018]
In addition to the display of the user terminal, it can be output to a file or a printer in a free format. Editing can add / delete / change attributes. An example of the editing screen is shown in FIG. 9, and flowcharts of the editing operation are shown in FIGS. The item list and its attributes are displayed on the display of the user terminal (S301), and an operation input is waited for (S302).
[0019]
When an editing operation is performed and an end is instructed (S303), an item is extracted from the DB of the own system to the lower layer relay management system / managed system directly connected to the system and the item file is downloaded. (S304), editing is terminated.
[0020]
If nothing is edited, the item file is not downloaded. When the addition of the item is instructed (S305), the item is added to the DB of the own system, the attribute of the item is set to the own system management item (“0”) (S306), and the operation is waited for input (S302). When deletion of an item is instructed (S307), if the attribute of the item is the own system management item ("0"), the item is deleted as it is from the DB (if asset information is set for the item, asset information (S309), if it is a higher system management item (“1”), an error message is output (S311), and if it is a common item (“2”), the attribute is set as a higher system management item (“1”). (S310).
[0021]
After performing each process, it waits for an input of an operation (S302). When an item attribute change is instructed (S312), the attribute of the item is changed from the higher-level system management item ("1") to the common item ("2"). When the change is reversed, the attribute of the item is changed as it is (S314), otherwise an error message is output (S315), and an operation input is waited (S302).
[0022]
In the case of other instructions, an error message is output (S316), and an operation input is awaited (S302). It should be noted that an operation that causes an error can be disabled in advance by determining the button to be operated from the condition and deactivating it.
[0023]
Next, the merging process will be described with reference to the state transition diagrams from FIG. 12 to FIG. 14 and the flowchart of FIG. Further, the description is made in the lower management system in the state transition diagram. In the initial state, it is in a waiting state for data download from the host management system (S001). The state of the DB item of each management system at this time is as shown in FIG.
[0024]
However, for convenience of explanation, it is assumed that items from the upper management system have already been created in the items of the lower management system (item A to item C and item F).
[0025]
First, when an item file is downloaded from the higher-level management system, all the higher-level system management items ("1") attribute items are deleted (S002). Next, the attribute value of all the common items (“2”) is changed to the own system management item (“0”) (S003). The state of the DB item at this time is shown in FIG.
[0026]
Next, the downloaded item file (1304) is opened and the item is read (S004). When all items have been read from the item file (S005), an item file is created by extracting item data existing in the DB of the own system, and is directly connected to the lower layer relay management system or managed system. On the other hand, the item file is downloaded (S008), and download waits again (S008 to S001).
[0027]
The item of the item file (1304) is read, and it is checked whether or not the same item exists in the DB of the own system (S006). If the same item exists, the DB is updated with the attribute of the item as the common item (“2”), and the next item is read (S009 to S004). If it does not exist, the read item is added to the DB, the attribute is set to the upper system management item (“1”), and the next item is read (S007 to S004).
[0028]
FIG. 14 shows an example in which the DB is updated according to the merge process flowchart. In FIG. 14, the items A, B, and C are downloaded from the upper management system, and the result of merging with the items C, D, and E held by the lower management system is shown after the change, and the lower layer system , Item C to item B are downloaded.
[0029]
Next, the update process will be described with reference to the state transition diagrams of FIGS. 14 and 16 and the flowchart of FIG. In the initial state, the result file is waiting to be uploaded from the lower layer system (S101). The state of the DB item at this time is the state after the change in FIG.
[0030]
First, the uploaded result file 1 (1606) is opened, and items and asset information are read (S102). The read item is searched from the DB of the own system, and if the attribute of the found item is the higher system management item (“1”) (S104), the result of uploading the item of the result file 1 and the asset information to the higher management system The file 2 (1605) is written (S105), and the next item and asset information are read (S102). If the attribute of the found item is other than the higher system management item (“1”) (S104), the asset information of the item in the own system DB is updated (S107).
[0031]
Further, if the attribute of the item is the common item (“2”) (S108), the item of the result file 1 (1606) and the asset information are written to the result file 2 (1605) for uploading to the upper management system (S108). To S105), the next item is read (S102). When all items and information have been read, the created result file 2 (1605) is uploaded to the upper management system (S106), and again waits for uploading of the result file 1 (1606) from the lower layer system (S101). .
[0032]
The state of the DB at this time is as shown in FIG. In FIG. 16, in the result file 1 (1606) from the lower layer, asset information on item C, item D, and item E is reflected in the DB, and item A, item B, and item C are uploaded to the upper system. It shows that.
[0033]
Since item C is a common item, DB update and uploading to a higher system are performed, and duplication of item C is prevented. As described above, the method described above makes it possible to efficiently transmit data without double data transfer for the same item in the management system and the managed system.
[0034]
Example 2
Since the implementation method and the merge process in the first embodiment are substantially the same except that the merge process is different, only the merge process will be mainly described with reference to the state transition diagrams of FIGS. 18 and 19 and the flowchart of FIG. Only the changes will be described for the processing. As shown in FIG. 18, an operation flag is added to the item to be downloaded. In this operation status, either “A” indicating addition or “D” indicating deletion is set (1805).
[0035]
In the upper management system, information edited in the item editing process is stored (addition of a process for saving the operation history after each operation process in the flowcharts of FIGS. 10 and 11), and when the editing is completed. An operation flag is added to each item of the item file (1805) to be downloaded (only the item operated in S304 in FIG. 10 is extracted, and processing for creating an item file is added).
[0036]
As shown in FIG. 18, when an item is added, “A” is added to the item D and the item X to be added, and “D” is added to the item A to be deleted. First, in an item file download waiting state (S201), when an item file is downloaded from the higher-level management system, an operation flag and an item are read (S202). When the operation flag is deleted (“D”) and the item attribute is the upper system management item (“1”), the item is deleted from the DB and the next item is read (S204-S205-S208-A).
[0037]
When the operation flag is deleted (“D”) and the item attribute is the common item (“2”), the item attribute is changed to the own system management item (“0”), and the next item is read (S204-S205). -S206-S209-A). If the operation flag is added (“A”) and the item does not exist, the item is added to the DB, the attribute of the item is set to the upper system management item (“1”), and the next item is read (S204- S210-S212-A).
[0038]
When the operation flag is added (“A”) and the attribute of the item existing in the local system is the local system management item (“0”), the item attribute is set to the common item (“2”), and the next item (S204-S210-S211-S213-A). As described above, in the case of other status combinations, the next item is read without doing anything (A).
[0039]
When all items have been read, the item file downloaded from the upper management system is downloaded as it is to all connected relay management systems and managed systems in the lower layer (S207), and the item file is downloaded again. Waiting (S207 to C).
[0040]
Through this series of processing, the table status is as shown in FIG. In FIG. 19, the item A, the added item D, and the item X that have been deleted in the upper management system are downloaded, merged with the items held in the lower management system, and the item D is newly added as an upper system item. Indicates that the attribute is changed to the common item.
[0041]
According to this method, there is an effect that the data transfer for the same item is not duplicated, and the size of the item file to be downloaded can be a constant size corresponding to the difference for the change.
[0042]
Example 3
In the previous examples, the same item was managed by using attribute information in each management system. However, each management system has only items managed only by its own system and does not have attribute information. A method for holding the system will be described (the program configuration is the same as in the first embodiment).
[0043]
First, the merge process will be described with reference to the flowchart of FIG. 24 and the state transition diagrams of FIGS. Further, the description is made in the lower management system in the state transition diagram. In the initial state, it is in a waiting state for downloading from the upper management system (S401).
[0044]
The state of the DB item of each management system at this time is as shown in FIG.
[0045]
As the system name, “SYSTEM” is set in the upper management system, and “SITE” is set in the lower management system. As for management items, the upper management system holds items A, B, and C, and the lower management system holds items C, D, and E.
[0046]
The item file to be downloaded is composed of an item and the name of a management system that manages the item as shown in FIG. If the item file 1 (2305) is downloaded from the upper management system in the download waiting state (S401), the item and the management system name are read (S402).
[0047]
If the read item overlaps with the item managed by the local system (S404), the local system name is added to the item and the management system name as a management system, and the item file 2 (2307) to be downloaded to the lower layer system (S408). If it does not exist, the item and management system name are written in the item file 2 (2307) to be downloaded to the lower layer system without changing them (S405).
[0048]
When all the items have been read (S403), items that are not duplicated in the items managed by the own system are extracted, the own system name is added as the management system name, and the item file 2 (2307) to be downloaded to the lower layer system ) (S406), the created item file 2 (2307) is downloaded to the lower layer system (S407), and the download of the item file 1 (2305) from the upper management system is awaited (S401).
[0049]
FIG. 23 shows item file download. Since item C is duplicated in the upper management system and the lower management system, both system names “SYSTEM” and “SITE” are set as management system names. The managed system holds the item file in the form of the item file to be downloaded (holds which item is returned to which management system).
[0050]
After entering asset information on the managed system, create a result file with the item + asset information + management system name and upload it to the management system. Next, the update process will be described with reference to the flowchart of FIG. 26 and the state transition diagram of FIG.
[0051]
In the initial state, the result file 1 (2505) from the lower layer system is waiting to be uploaded (S501). When the result file 1 (2505) is uploaded from the lower layer system, the result file 1 (2505) is opened, and the item, asset information, and management system name information for one entry are read (S502).
[0052]
When the management system name of the entry includes the local system name (S504), the asset information of the local system DB is updated (S507), and the local system name is deleted from the management system name (S508). If another system name remains in the management system name (S509), the entry from which the local system name has been removed is written in a result file 2 (2507) that is uploaded as a result file to the higher management system (S505).
[0053]
If the read system does not include the own system from the beginning, the entry is not updated and written to the result file 2 (2507) to be uploaded to the upper management system (S505). When all entries have been read (S503), the created result file 2 (2507) is uploaded to the upper management system (S506), and the result file 1 (2505) from the lower layer system is again waited for uploading (S501). .
[0054]
FIG. 25 shows the flow of the result file. Asset items A, B, C, D, and E are uploaded as a result from the lower layer system, and the DB is updated for items C, D, and E. Items A, B, and C are uploaded to the upper management system.
[0055]
Since item C is a common item, DB update and uploading to a higher system are performed, and duplication of item C is prevented. Note that the editing process only edits the items of its own system, and a special process is not performed.
[0056]
As described above, by the management method different from the first and second embodiments, the management system and the managed system can prevent double data transfer for the same item and efficiently transmit data. .
[0057]
Example 4
In addition to the method of the first embodiment, default items and asset information can be defined in advance in each relay management system. This method will be described with reference to FIGS.
[0058]
FIG. 27 shows an initial state, in which the “office code”, “department code”, “name”, and “extension” items are created in the head office management system, and the “office code” is relayed to the department in the office relay management system. In the management system, “department code” is defined as the default. Processing to add or delete default item definitions can be processed as part of the editing process.
[0059]
FIG. 28 shows the flow of downloading the item file to each system. The item file (2805) is downloaded from the management system at the head office, and the relay management system at the office compares the item name in the item file with the default item name. To store. Then, the item file (2808) of “department code”, “name”, and “extension” with the “office code” removed is downloaded to the relay management system of the department. In the department relay management system, the “department code” is processed in the same manner, the item file (2811) of “name” and “extension” is downloaded to the managed system, and asset information is set for the item.
[0060]
Note that items and asset information registered in the default DB are deleted when a new item file is downloaded from the higher-level management system.
[0061]
FIG. 29 shows the flow of uploading the result file. Asset information is input in the managed system, and the result file is uploaded to the relay management system of the department.
[0062]
The departmental relay management system adds the items in the default DB and asset information to the result file and uploads them to the office relay management system. The same processing is performed in the relay management system at the office, and a result file in which asset information of all items is stored is uploaded to the management system at the head office. The actual mounting method can be achieved by adding a part of processing to the flow of the first embodiment.
[0063]
First, in the merge process, a process for deleting all the contents of the default DB when an item file is downloaded is added (a process is added after S003 in FIG. 15), and whether there is a default item in the downloaded item. The asset information is registered in the default DB for the same item as the default item, and processing that is not downloaded to the lower layer system is added (processing is added after S005 in FIG. 15).
[0064]
Next, when information is uploaded in the update process, a process for adding and uploading items and default values to the result file to the higher-level management system is added (the process is performed at the time of EOF in S103 in FIG. 17). to add). By this method, data transfer can be suppressed by the number of items defined by default.
[0065]
Example 5
In the method of the fourth embodiment, it is determined whether there is a default item among the items downloaded in the relay management system, and after registering asset information for the same item as the default item in the default DB, the lower layer management system Or, if there are no more items to download to the managed system (when all items are set as default items in the relay management system), the items and asset information are extracted from the default DB, and a result file is created. Upload to the management system.
[0066]
About an actual mounting method, it is possible by adding a part process to the flow of Example 1 in which the function of Example 4 was mounted. In merge processing, it is determined whether there is an item file to be downloaded to the lower-layer management system or the managed system. If it exists, the file is downloaded as it is. Create a result file for the system and add a process to upload to the higher-level management system. (A process is added after S008 in FIG. 15).
[0067]
By this method, it is possible to suppress data transfer from the relay management system to the managed system that has completed the input of asset information using the items defined by default.
[0068]
【The invention's effect】
According to the present invention, it is possible to efficiently transfer the amount of data on a one-route network in a hierarchical network environment, and as a result, there is an effect of efficiently transferring data transfer of the entire network.
[Brief description of the drawings]
FIG. 1 is a configuration diagram of a system to which the present invention is applicable and a diagram showing a flow of data transfer.
FIG. 2 is a diagram showing a configuration diagram of a system to which the present invention is applicable.
FIG. 3 is a diagram illustrating an example of a system configuration when asset information is managed in a multi-tier system.
FIG. 4 is a diagram illustrating a state in which each management system has items.
FIG. 5 is a diagram illustrating a method of merging items in each management system.
FIG. 6 is a diagram illustrating a method for updating asset information in each management system.
FIG. 7 is a diagram illustrating a structure of a DB having attributes.
FIG. 8 is a diagram illustrating a configuration of a program of the management system.
FIG. 9 is a diagram illustrating an example of an item editing screen in the management system.
FIG. 10 is a flowchart of item editing.
FIG. 11 shows a continuation of FIG.
FIG. 12 is a diagram showing an initial state.
FIG. 13 is a diagram illustrating a state in which items are initialized.
FIG. 14 is a diagram illustrating a state in which items are merged.
FIG. 15 is a flowchart of merge processing.
FIG. 16 is a diagram illustrating a state in which asset information is updated.
FIG. 17 is a flowchart of update processing.
FIG. 18 is a diagram illustrating a state in which items are initialized.
FIG. 19 is a diagram illustrating a state in which items are merged.
FIG. 20 is a flowchart of merge processing.
FIG. 21 shows a continuation of FIG.
FIG. 22 is a diagram illustrating a state in which items are initialized.
FIG. 23 is a diagram illustrating a state in which items are merged.
FIG. 24 is a flowchart of merge processing.
FIG. 25 is a diagram illustrating a state in which asset information is updated.
FIG. 26 is a flowchart of update processing.
FIG. 27 is a diagram illustrating a state in which items are initialized.
FIG. 28 is a diagram illustrating a state in which items are merged.
FIG. 29 is a diagram illustrating a state in which asset information is updated.
[Explanation of symbols]
101 ... Management system
102 to 105 ... relay management system
106 ... managed system
801 ... Display device,
802 ... Management system program body,
803 ... edit processing unit,
804 ... Update processing unit,
805 ... merge processing unit,
806. Database.

Claims (4)

A data transfer method for transferring data from a lower system to a higher system via a relay system,
The item of data transferred from the lower system has an attribute, and whether the attribute is a management item of the upper system, a common item of the upper system and the relay system, or management of the relay system Information about whether it is an item,
The relay system receives data having items from the lower system,
If the received item attribute is a management item of the higher system, the data is transferred to the higher system, and if the item attribute is a common item, the data is stored in a storage device in the relay system. Transferring the data to the host system, and storing the data in a storage device in the relay system without transferring the data to the host system if the attribute of the item is not a management item and a common item of the host system A featured data transfer method . 2. The data transfer method according to claim 1, wherein an item corresponding to the relay system is set in advance, and an item set in advance in the relay system is added to an item received from the lower system. The data transfer method is characterized in that the transfer of the preset items is suppressed by transferring to the data . A data transfer system for transferring data from a lower system to a higher system via a relay system,
The item of data transferred from the lower system has an attribute, and whether the attribute is a management item of the upper system, a common item of the upper system and the relay system, or management of the relay system Information about whether it is an item,
The relay system is
Means for receiving data having items from said subsystem;
If the received item attribute is a management item of the higher system, the data is stored in the storage device in the relay system if the data is transferred to the higher system and the item attribute is a common item. And means for transferring the data to the host system;
A data transfer system comprising: means for storing the data in a storage device in the relay system without transferring to the higher system if the attribute of the item is not a management item and a common item of the higher system . The data transfer system according to claim 3, wherein an item corresponding to the relay system is set in a storage unit in advance, and an item set in advance in the relay system is added to an item received from the lower system, A data transfer system characterized in that transfer of the preset item is suppressed by having means for transferring to the host system .

Images