JPH11102337A - Data distribution route managing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To automate maintenance by placing a reference relation analyzing device in operation according to the access from a client device and updating registration information on data only at need without allowing the client device to perform a registering and updating process at all. SOLUTION: The device 100 is provided with an identifier storage device 110 and an identifier replacing device 107 and the reference relation analyzing device 103 is placed in operation according to the access from the client device to update registration information on the data only at need without allowing the client device to perform the registering and updating process at all. Here, a user stores a data identifier to be referred to and an identifier assigned to data on a server discriminatingly. The movement of the entity of data is automatically decided and the stored identifiers are updated. When the entity of the data is moved, the identifier is rewritten at the time of 1st access to the server, so old data is not accessed thereafter.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] The present invention relates to a system for distributing data via a network. In particular, the present invention relates to a method for shortening a distribution route of redundant data.
In particular, the present invention relates to an apparatus for automatically managing a server that distributes data.

[0002]

2. Description of the Related Art In recent years, the maintenance of network infrastructure and the spread of personal computers have been promoted not only by public institutions and private companies but also by the use of computer networks on an individual basis. In the developing world, computer networks existed as independent, small and medium sized networks. However, with the improvement of the Internet environment, the scale of the network is expanding worldwide. And the current Internet is World-Wide
The spread of the Web (hereinafter, WWW) has been greatly promoted.

[0003] The WWW uses the Internet to realize an access environment that is transparent to the network, and makes it possible to use remote images, voices, texts, and the like. Data is described in Hypertext Markup Language (HTML), and communication is performed by a procedure called Hypertext Transfer Protocol (HTTP). A user can access data specified on a server by using a URL (Uniform Resource Locators) through a WWW terminal or a client.

[0004] The WWW system provides a single space for collecting data on a plurality of servers, and assigns a unique identifier (URL) to all data. It is not necessary for both server administrators and client users to be aware of access routes, data can be distributed and managed by multiple servers without being aware of users, and services can be easily provided to an unspecified number of users. In particular, there is the characteristic of WWW.

[0005] These technical details are described in The Internet Eng.
ineering Steering Group (IESG), Internet Engineerin
g Request for Comm formulated by the Task Force (IETF)
ent (RFC). RFC1866 for HTML,
2070 etc., HTTP is detailed in RFC2068, 2069 etc. Originally, HTML itself is a Stand specified by ISO8879.
Based on ard Generalized Markup Language (SGML). The technique for realizing data transmission and reception between the server and the client is hereinafter referred to as Conventional Technique 1.

In some cases, a host called a proxy or the like is arranged at a relay point between the server and the client. By providing a relay host, various data conversion functions such as access management from a client, caching of frequently accessed data, kanji code conversion, and image processing, and addition / synthesis of data by the relay host can be realized. Such a data relay technique is referred to as Conventional Technique 2.

[0007]

The prior art 1 makes it possible to provide various services to an unspecified number of users through a network. However, in order to update the contents of services to be provided and to increase the number of users, it is necessary for the administrator on the service providing side to continuously add servers, rearrange data on the servers, and the like. On the other hand, if the number of users is unspecified, it is not possible to notify all users of data relocation.

Therefore, in general, an index of the service is prepared, the user always accesses the data through the index, and the server administrator updates the data and updates the index. I went by work. Prior Art 1 cannot provide means for automating this type of maintenance work.

In the current HTML specification, it is possible to describe an instruction in HTML so that the client automatically refers to another data. By utilizing this, a reference instruction to new data can be embedded in old data, and new data can be accessed without the user being aware of it. Also in the HTTP specification, an instruction to automatically switch the referenced data on the server side can be used. However, as the number of users is unspecified,
The timing for deleting old data cannot be determined. Further, the deletion operation needs to be performed manually by the administrator. Prior Art 1 cannot provide means for automating this type of maintenance work.

[0010] Further, there is a specialized site for providing index pages on the WWW. The service provider registers the URL in a well-known index page providing site, and creates an index in accordance with the URL. When the data on the service providing side is updated, there is a problem that the old URL registered in the index page providing site cannot be updated automatically. The prior art 1 alone cannot provide a means for solving the problem.

Prior art 2 is a URL requested by a client.
It provides a means to perform various processing on the data itself, but does not provide a function to track URL update information. Therefore, it is not possible to cope with the reconfiguration of the server-side data according to the related art 2. Furthermore, it is assumed that the filtering process for the data sent from the server at the time of relaying does not depend on the URL, and it is not possible to perform an appropriate process for data in which the URL frequently moves.

[0012]

According to a first preferred embodiment of the present invention, there are provided means for registering one or more data identifiers, means for storing the registered identifiers, and data identifiers from a client device. Means for receiving
Means for receiving data having an arbitrary identifier from the server, means for transmitting data received from the server to the client device, analysis of data received from the server device, and data referred to by the data. Means for extracting an identifier; means for comparing the detected data identifier with the registered data identifier; means for replacing the registered data identifier with the detected data identifier; and Means for transmitting a signal indicating the fact to the server device.

In the first embodiment, a data identifier referred to by a user and an identifier assigned to data on a server are stored separately. In addition, using the reference command in the data, it is automatically determined that the data entity has moved, and the stored identifier is updated. When the entity of the data moves, the identifier is rewritten at the time of the first access to the server, so that access to the old data does not occur from the next time. Also, there is no need for the client to be aware of the movement. Further, when the server detects that the registered identifier has been replaced, the old data can be automatically deleted.

[0014] In a preferred second embodiment of the present invention, means for registering one or more data identifiers, means for storing the registered identifiers, means for receiving data identifiers from a client device, Means for receiving data having an arbitrary identifier from the server, means for transmitting data received from the server to the client device, and analysis of data received from the server device;
Means for extracting a data identifier referred to by the data, means for comparing the detected data identifier with the registered data identifier, and replacing the registered data identifier with the detected data identifier Means, means for transmitting a signal indicating that the data identifier has been replaced to the server device, means for inputting additional data, means for inputting an identifier of data to be added, and Means for combining with the data received from the server.

Thus, even when the identifier of the data on the server is changed, it is possible to perform a new data combining process on the data transmission path.

In a third preferred embodiment of the present invention, means for registering one or more data identifiers, means for storing the registered identifiers, means for receiving data identifiers from a client device, Means for receiving data having an arbitrary identifier from the server, means for transmitting data received from the server to the client device, and analysis of data received from the server device,
Means for extracting a data identifier referred to by the data, means for comparing the detected data identifier with the registered data identifier, and replacing the registered data identifier with the detected data identifier Means, means for transmitting a signal indicating that the data identifier has been replaced to the server device, means for inputting additional data, means for inputting an additional position, and analysis of the logical structure of the data received from the server device Means for synthesizing the input data with data received from the server using the analyzed logical structure, the input data identifier, and the definition of the logical structure.

Thus, it is possible to perform the data synthesizing process depending on the position information while responding to the change in the position information of the data.

In the third embodiment, the means for inputting an additional position includes means for receiving the additional position as a set of an identifier of the data and the additional position in the data based on the context definition, and means for storing the data format. And means for converting position information based on the input context information into position information in a data format.

Thus, the user who determines the data combining position determines the combining position based on the semantic structure of the data. When converting the combining position, the system determines from the data format described in advance. select. For this reason, even when the content of the data on the server side to be combined is revised, the data can be determined at an appropriate position.
Also, to determine the composition position from the data format,
When there is no combining position, inappropriate combining processing can be avoided.

[0020]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 shows a data distribution path management device 100.
2 shows the configuration and data flow. 101 is a data identifier input device, 102 is a data identifier receiving device, 103
Is a reference relation analysis device, 104 is an identifier comparison device, 105
Is an identifier updating device, 106 is a conversion result output device, 107
Is an identifier replacing device, 108 is a data receiving device, 109 is a data transmitting device, 110 is an identifier storage device, 111 is received data, 112 is transmitted data, 113 is a registered identifier,
Reference numeral 114 denotes a data identifier, and 115 denotes a conversion result.

FIG. 2 is a configuration diagram of the entire system including a server device, a client device, and a data distribution route management device. In the device 200, 202 is a server device, 203 is a data distribution route management device, and 204 and 20.
5 is a client device, 206 is a network connecting each device, and device 203 is the same as device 100.

The device 201 represents a mode in which the data distribution route management device is included in the server device. 207 is a server device, 208 is a data distribution route management device, 210
211 is a client device. The devices 200, 2
01, the operation of the data distribution route management device is the same.

FIG. 3 shows data 300 stored in the server device.
Is shown. Reference numeral 301 denotes data before the identifier change, and ht
An identifier (URL) tp: //www.old.co.jp/da is given. In the URL, "http" indicates the protocol name, "www.old.co.jp" indicates the host name of the server, and "da" indicates the name given to the data. The data 301 includes a data definition storage unit, a display content storage unit, and an identifier storage unit for referring to a new identifier when a new identifier is given to the data.

Data 302 is data after the identifier is updated. Http://www.new.co.jp in the identifier storage section 302
/ da indicates that the data originally located at http://www.old.co.jp/da has moved to http://www.new.co.jp/da. Data http://www.new.co.jp/da and http: //www.ol
d.co.jp/da may be on a different server device.

Reference numeral 303 denotes a state where the data 301 and 302 are displayed on the client device. The data definition section represents a data format such as designation of items and designation of character types, and data in the display content storage section is output to the client device according to these definitions.

FIG. 4 shows data 400 representing an identifier registered in the apparatus 100. Reference numeral 401 denotes a registration status when the data 301 is stored in the server device. 401
Is composed of an external data identifier storage unit and an internal data identifier storage unit. The external data identifier is a URL for the client device to access, while the internal data identifier is a URL for the device 100 to access the server device.

When the data of the server device is changed to 302, the registration state is changed to data 402 in response to access from the client device.

In each of the devices 200 and 201, the operation of the data distribution route management device is the same, so that the operation of each device will be described according to the device 200 for convenience of explanation. First, it is assumed that the server device 202 has data 301. UR to get from client device 204
L, when sending http://www.bar.co.jp/da, the device 203
Receive. The data identifier receiving device 102 passes the received identifier to the identifier comparing device 104 and checks whether or not the identifier has been registered. The identifier replacement device 107 performs an actual conversion operation. If the received data identifier 114 is not registered in the data 401, no conversion operation is performed. In this example, http: // ww
Identifier corresponding to w.bar.co.jp/da http://www.old.co.jp
get / da. The data receiving device 108 is a server device 202
Order data from http://www.old.co.jp/da. The reference relationship analyzer 103 retrieves the identifier storage unit of the obtained data and checks whether the location information of the registered identifier has been changed. Since the data 301 does not indicate that there has been a change, the data device 1
When the server device 202 has data 302 that transmits data 301 to the client device 204, the reference relationship analysis device determines that the entity of the data is in the data of the identifier http://www.new.co.jp/da. 103 detects. At this time, the identifier updating device 105 rewrites the data 401, and the data corresponding to the identifier http://www.bar.co.jp/da is a URL,
Data 40 indicating that it is http://www.new.co.jp/da
2 is stored in the identifier storage device 110. Next, the data receiving device 108 obtains data having the identifier http://www.new.co.jp/da, and the reference relationship analyzing device 103 analyzes the location information again. http://www.new.co.jp/da
If points to other data, the above operation is repeated once again. However, when the number of times of analysis reaches the upper limit set by the user, the analysis is interrupted and the data obtained at that time is transmitted by the data transmitting device 109. At the same time, the conversion result output device outputs that the registration of the identifier has been updated.

As described above, by providing the identifier storage device 110 and the identifier replacing device 107 and operating the reference relation analyzing device 109 in response to access from the client device, the registration updating process is not performed at all on the client device. This embodiment is characterized in that the registration information of data can be updated only when necessary.

Compared with the conventional method in which the client device tracks the movement of data, the client device always accesses between the server device and the client device. In the present embodiment, the client device keeps accessing until the necessary data is obtained. Since data is not transmitted to the network, the load on the network can be reduced.

The feature of the present embodiment is that the registration information is automatically updated, as compared with a method in which static registration information is provided in the server device and the movement of data is tracked.

FIG. 14 shows an example. A system 1400 is a conventional system that does not include a data distribution path management device. Reference numeral 1402 denotes a client device that operates a WWW browser. Reference numeral 1403 denotes a server device that serves as a WWW server, and supplies data to the client device 1402. Initially, data is stored in the server device 1403, and the client device 1402 specifies http://www.old.co.jp/da as a URL when obtaining the data 1404.

Next, the substance of the data 1404 is moved to the new server 1405 and changed to the data 1406.
It is assumed that the URL for receiving 06 is http://www.new.co.jp/da. In a known example, the data 1404 is left in the server 1403, and <META HTTP-EQUIV = "REFRESH" CONTE
NT = "3; URL = HTTP: // http: //www.new.co.jp/da"> and the like and reference 1417 can be described. In such a case, when the client device 1402 accesses the data 1404, the WWW browser in the client device automatically accesses the data 1406.

However, although the data 1404 is unnecessary, it flows along the path 1415 and the client device 1
Sent to 402. Of course, when there are a plurality of client devices, the same phenomenon occurs for all the client devices. Even if the data 1406 is automatically accessed, if the data 1404 is deleted,
A user of a client device that does not know that the URL has moved loses the means of knowing the data 1406.

On the other hand, a system 1401 is a system including a data distribution route management device. Reference numeral 1408 denotes a data distribution path management device, 1407 denotes a client device for operating a WWW browser, 1409 denotes a server device serving as a WWW server, and stores data 1410 in the client device 140.
7 However, the client device 1407 transmits the data 1410 through the data distribution route management device 1408.
Have gained. Http: //www.old.c from the client device
o.jp/da is not visible and is accessed using the URL http://www.bar.co.jp/da. URL association is performed by the data distribution route management device 1408.

Next, as in the system 1400, the data 14
Assume that ten entities have moved to http://www.new.co.jp/da. When a client accesses http // www.bar.co.jp / da, the data distribution route is the same as before the data is transferred.
Attempt to access 409. When the data 1410 arrives at the data distribution route management device 1408, the data is sent to http: //www.new.c
A reference 1418 to o.jp/da is detected. The data distribution path management device 1408 does not transmit the data 1410 to the client device 1407, but accesses data having the URL http://www.new.co.jp/da to obtain the data 1412. When data 1412 is obtained, http://www.bar.co.
The correspondence 1413 between jp / da and http://www.old.co.jp/da is updated, and finally the data 1412 is stored in the client device 1
407.

Thereafter, the data distribution route management device 1408
If http://www.bar.co.jp/da is accessed through http: //www.new.c
o.jp/da will be accessed directly.

As compared with the system 1400, the data 1
Even if 410 is updated, unnecessary data flowing along the path 1418 is not transmitted to the client device 1407, and the URL in 1408 is automatically updated, so that the client device loses a means of knowing the data 1412. There is no. If the server 1409 is notified that the correspondence in 1408 has been updated, the data 1410 can be safely deleted at this point without affecting the client.

Hereinafter, the flow of processing of this embodiment when the data 302 is in the server will be described with reference to the drawings.

In step 501, a data identifier is received from the client, and it is determined whether the identifier received in step 502 is registered. If not registered, the process proceeds to step 509 to receive the data from the server device and transfer it to the client device as it is in step 511.

If the identifier has been registered, the process 5
03, the data identifier is converted, the data is requested to the server according to the conversion result, and the data is received by the process 504. In the process 505, it is analyzed whether or not the entity of the received data has moved. The process 505 is performed by determining whether a value exists in the identifier storage unit in the data. If the data entity has not moved, process 509
Move to At this time, the data obtained in 504 is transmitted to the server in processing 513.

Processing 51 when the data entity has moved
The process proceeds to step 2 to check whether or not the number of times of movement has reached the preset upper limit. If the upper limit has not been reached, the registration information of the data identifier is updated in step 507, and the process returns to step 503. If the upper limit has been reached, process 508
Then, it is output that the registration information of the server has been updated. Using the output of the process 508, the server device can automatically delete the data before the movement.

Next, a second embodiment of the present invention will be described.
FIG. 6 shows the configuration of the data distribution route management device 600 and the flow of data. A device 601 is an additional data input device, 602 is a movement information determination device, 603 is an identifier input device, 604 is a data storage device, 605 is a synthesis device, and 6
06 is additional data, 607 is a data position, 608 is output, 609 is data received from the server,
Apparatus 602 is similar to apparatus 100.

FIG. 7 shows input / output data of the apparatus 600. An input 701 is provided from the devices 601 and 603 and becomes data to be combined with data from the server. Input 70
1 includes a data identifier to be combined, combined data, and a combined position, which are stored in the data storage device 604. Data 702 is a state in which data output by the distribution route management device 600 is displayed on the client. Data 703 indicates an output of the synthesizing device 605. In the output 703, "supplementary information" is added to the last line of the data in addition to the output 702 of the distribution route management device 600.

The operation of the apparatus 600 when data 701 and 702 are input will be described below. The combined data in the data 701 is input from the additional data input device 601, the data identifier and the combined position in the data 701 are input from the identifier input device 603, and the data storage device 60
4 is saved. Data 7 from movement information determination device 602
02, the synthesizing device 605 changes the data storage device 604.
Is compared with the data 701 stored in the first data storage unit, and if both data have the same data identifier, the data is combined.

By using the movement information determination device 602, even if the data entity is moving, the data entity can be obtained, and even if the data entity cannot be obtained, the data tracking can be completed by looking at the output of the device 602. You know if you were. Therefore, when the tracking of the movement is completed, the combining process can be performed without being affected by the movement of the data entity, and when the tracking is not completed, the combining process can be prevented from being performed. There is a feature of this embodiment in the point.

Referring to FIG. 8, the details of the processing of this embodiment will be described.

In the process 801, data movement is tracked by analyzing data received from the server device by using the movement information determination device 602, and data is obtained from the server device. In the process 802, the output of the movement information determination device 602 is referred to, and it is determined whether the tracking process of the data movement has been completed or has been completed halfway. If all the tracking processes have been completed, the process proceeds to step 803; otherwise, the process proceeds to step 807. In step 803, data is read from the data storage device 604. In step 804, it is determined from the data identifier whether or not the data from the movement information determination device 602 is to be combined. If the data is to be combined, the data combining position is determined in step 805. Here, it is either the beginning or end of the data. Process 806
Then, the data is actually synthesized, and the data is transmitted to the client device by processing 807.

Next, a third embodiment of the present invention will be described. FIG. 9 shows the configuration and data flow of the present embodiment. 901 is an additional data input device, 902 is a data storage device, 903 is a movement information determination device, 904 is a data addition position input device, 905 is an identifier input device, 906 is a position information input device, 907 is a position information conversion device, and 910 is Context definition storage device, 911 is a data format storage device, 912 is additional data, 933 is a data position,
Reference numeral 914 denotes data from the server, 915 denotes output, and the movement information determination device 903 is similar to the device 100.

Data 1000 in FIG. 10 represents data transmitted from the server to the movement information determination device 903. The data 1000 is data having the identifier http://www.old.co.jp/da. 1001 is an identifier storage unit, 1002 is a definition storage unit, and an item name unit that stores the name of the definition;
The data is composed of an entry point section for storing a candidate position of the synthesis position. A display content storage unit 1003 holds the content of each definition.

Data 1000 in FIG. 1100 represents a data structure stored in each storage device. Reference numeral 1101 is stored in the context definition storage device 910, and holds the relationship between the semantic structure of data and the combination position. 1102 is stored in the data format storage device, and holds the relationship between the structure of the data format and the combination position. 1103 represents synthesized data stored in the data storage device. The “synthesis target data identifier” stores the data to be processed, the “synthesis position type” stores the type of synthesis, the “synthesis position” stores the position to be synthesized, and the “synthesis data” stores the data to be synthesized.

The items actually displayed on the client device are item names, item 1, item 2,..., And the contents of each item, and the item contents represent the outline thereof in a semantic manner. ing. Data 1101 and data 1102 indicate that item 1 describes related laws and regulations, and indicate that items 2 and 3 include the content of the corresponding substance name. Further, since the items 2 and 3 have the same comprehensive meaning even if the details are different, the entry point indicating the data synthesis position is the same P2.

Here, P1, P representing the entry point
The actual position at the time of synthesis of 2,.
1, the item name is determined from the data format. Relationship between item contents and entry points,
That is, the apparatus 900 determines the relationship between the context definition and the actual position at the time of synthesis using the data 1101 and data 1102. Therefore, the data on the server device does not need to be involved in the semantic information at all, and only the entry point candidates need to be prepared.

The data 1200 in FIG.
08. Reference numeral 1201 denotes an output when data from the server is not a target of the combining process; 1202, a result of the combining process when "item name" is designated as the combining position type; 1203, "item content" as the combining position type;
Represents the result of the combining process when the is specified.

The outline of this embodiment will be described below with reference to FIG.

First, data to be synthesized is input using the data addition position input device 904 and the additional data input device 901. The contents of the data are given to the additional data input device 901, and the identifier of the data to be combined and the combining position are given to the devices 905 and 906 as corresponding designations. The identifier input device 905 causes the combining target data identifier to be selected from the registered identifiers by using the identifier of the movement information determination device. Here, the selection is limited to the external data identifier. The position information input device 906 causes the composite position type to be selected from two items, “item content” and “item name”. At this time, the context definition storage device 910,
With reference to the data format storage device 911, a value corresponding to each of the item content and the item name is input. Based on the data stored in the devices 910 and 911, the position information conversion device 907 stores the data from the data addition position input device 904 in the device 902.

When data is sent from the server, the data is first tracked by the movement information determination device 903. Upon receiving the output of the device 903, the synthesizing device 903 refers to the data of the device 902, synthesizes the data, and outputs the result.

As described above, by providing the semantic structure of the data and the data addition position device 907 and the movement information determination device 903, an appropriate data synthesizing process is performed even when the data is updated and the data position information is changed. This embodiment is characterized in that it is possible to specify the combination processing based on the semantic information of the data.

Hereinafter, the processing of this embodiment will be described in detail with reference to FIG. In processing 1301, the movement information determination device 90
3, the data movement is tracked by analyzing the data 914 received from the server device, and as a result, the data is obtained from the server. In the processing 1302, the output of the movement information determination device 903 is referred to, and it is determined whether or not the tracking processing of the data movement has been completed or has been completed halfway. Process 1 if all tracking processes have been completed
Proceed to 303, otherwise proceed to process 1311.
A process 1303 reads the data stored in the data storage device 902. A process 1304 determines whether or not the data from the movement information determination device 903 is to be combined and processed.
Judge by the data identifier. If the target is a combination target, the process proceeds to step 1305; otherwise, the process proceeds to step 1311. In processing 1305, the combining position is extracted from the data 91. A process 1306 compares the data read in the process 1303 with the combining position extracted in the process 1305, and determines whether the combining based on the data format is possible. If possible, proceed to processing 1308; otherwise, processing 1
Proceed to 307. A process 1307 determines whether or not composition based on the context definition is possible. If possible, the process proceeds to a process 1308; otherwise, the process proceeds to a process 1309. In step 1308, the combining position is determined using the data read in step 1303. A process 1310 performs a data combining process. If the entry point does not exist, the process 1309 outputs that fact, and does not combine the data. A process 1311 outputs the result of the combining process to the client device.

[0060]

As described above, according to the present invention, the identifier storage device and the identifier replacement device are provided, and the reference relation analysis device is operated according to the access from the client device.
The registration information of the data can be updated only when necessary without performing any registration update processing on the client device.

When compared with the conventional method in which the client device tracks the movement of data, access has always occurred between the server device and the client device.
In this embodiment, since data is not transmitted to the client until necessary data is obtained, the load on the network can be reduced. Compared to a method in which static registration information is provided in the server device to track the movement of data, the registration information can be automatically updated.

Further, by using the apparatus 100, it is possible to realize processing for automatically responding to the update of the position information while handling the position information of the data.

[Brief description of the drawings]

FIG. 1 is an overall configuration of a data distribution route management device. And the first
FIG.

FIG. 2 is a system configuration diagram including a data distribution route management device.

FIG. 3 is a view showing data on a server according to the first embodiment;

FIG. 4 is a view showing input data in the first embodiment.

FIG. 5 is a processing flowchart according to the first embodiment;

FIG. 6 is a configuration diagram of a second embodiment.

FIG. 7 is a view showing input / output data according to the second embodiment;

FIG. 8 is a processing flowchart of the second embodiment.

FIG. 9 is a configuration diagram of a third embodiment.

FIG. 10 is a view showing data on a server according to the third embodiment.

FIG. 11 is a diagram showing input data according to the third embodiment;

FIG. 12 is output data of the third embodiment.

FIG. 13 is a processing flowchart of the third embodiment.

FIG. 14 is a comparison diagram of a conventional example and the present embodiment.

 ──────────────────────────────────────────────────続 き Continuing on the front page (72) Inventor Akira Maeda 1099 Ozenji Temple, Aso-ku, Kawasaki City, Kanagawa Prefecture Inside System Development Laboratory, Hitachi, Ltd. (72) Toshihiko Nakano 5-2-1 Omika-cho, Hitachi City, Ibaraki Prefecture No. 7 Omika-machi, Hitachi, Ibaraki Prefecture, Japan 5-72 Omika-machi, Hitachi-shi, Ibaraki Prefecture (72) Inside the Omika-machi, Hitachi, Ibaraki Prefecture No.2-1, Hitachi Process Computer Engineering Co., Ltd. (72) Inventor Shinya Yoshikawa 5-2-1, Omika-cho, Hitachi City, Ibaraki Pref.

Claims (8)

[Claims] 1. A server for providing data having uniquely determined position information, at least one client for receiving data from the server, and a connection between the server and the client. In a data distribution system comprising a network, a means for registering one or more data identifiers, a means for storing the registered identifiers, a means for receiving data identifiers from a client device, and an arbitrary identifier Means for receiving data from the server, means for transmitting data received from the server to the client device, means for analyzing data received from the server device, and extracting a data identifier referred to by the data Means for comparing the detected data identifier with the registered data identifier, Means for replacing the registered data identifier with the detected data identifier; means for storing the result of the replacement; means for converting the identifier received from the client device based on the stored replacement result; Means for outputting a signal indicating that the identifier has been replaced. 2. The data distribution route management device according to claim 1, wherein said means for registering said data identifier uses an identifier received from said server device. 3. The data distribution path management device according to claim 1, wherein the means for registering the data identifier uses an identifier received from the client device. 4. The data distribution route management device according to claim 1, wherein the means for storing the registered identifiers comprises: means for inputting the number of identifiers to be stored; A data distribution path management device for storing the latest data identifier according to time information registered in the data distribution path. 5. The data distribution path management device according to claim 1, wherein the means for storing the registered identifier is the same as the identifier received from the client device among the stored identifiers. Means for recording the number of receptions for the identifier;
A data distribution path management device, wherein an identifier is deleted from the one with the smaller recorded number. 6. The data distribution path management device according to claim 1, wherein the means for outputting a signal indicating that the data identifier has been replaced transmits the replaced identifier to the client device. A data distribution route management device characterized by the above-mentioned. 7. The data distribution path management device according to claim 1, wherein said means for outputting a signal indicating that the data identifier has been replaced is a server device holding data having an identifier to be replaced. A data distribution route management device, which transmits a signal to the data distribution route management device. 8. The data distribution route management device according to claim 1, wherein the means for storing the registered data identifier comprises: a data identifier referred to by the client device; and a data identifier managed by the server device. A data distribution path management device characterized by storing identifiers in pairs.