JPH10222435A - Data managing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce the load of communication traffic, respective servers and network by decreasing the number of times to reload data concerning communication between servers connected on the network. SOLUTION: A possession date 24 of data 23 to be accessed on a local server 20 is compared with a final update date/time 14 of data 13 at a DB server 10 and only, when the data 13 are updated after the data 13 are possessed at the local server 20, the data 13 are to be received so that the double reception of the same data can be prevented and unwanted data reception can be prevented. Further, when receiving the updated data 13, only an update log 12 is received and the data 23 of local server 20 are updated so that the amount of data to be received can be remarkably decreased and the load of network can be reduced.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a network computer, and more particularly, to a data management method on a network in which data is loaded from a host server that collectively manages data and each local server uses the data.

[0002]

2. Description of the Related Art Conventionally, there is an environment in which a plurality of servers independently manage data in a network environment and do not cooperate in data management. However, if this is done, data management will be fragmented and disorderly. In order to manage this data, the server that updates the data is reduced to one server, this server is used as a host server, and the other servers are local servers that copy data from this host server and use it locally.
Users of data connected to this local server,
The client acquires data from the local server and uses it.

When a client requests use of data from a local server, data on the host server may have been updated, and whether data on the local server is the latest data is determined. When the latest data is needed, the following method has been adopted. When accessing data from a client, the local server unconditionally acquires data from a host server on the network that has the data.

[0004] The host server sets an expiration date for the data in advance, and when the expiration date of the data has passed, the local server requests the host server to reload the data. When accessing data from the local server, the host server determines whether or not there is an update. If there is an update, the data is reloaded to the local server.

[0005]

However, the above method has the following problems. In such a case, each local server and client need to reload the data every time the data is used, so that the response is deteriorated due to an increase in traffic.

In this case, if the data update time is not known in advance, it is not effective. Then, if there is an update, the entire data is always reloaded, so that a load is imposed on the network when targeting large-sized data. Therefore, an object of the present invention is to prevent the response from deteriorating and reduce the load on the network.

[0007]

According to a first aspect of the present invention, there is provided an apparatus for updating basic data to be updated, an update log recording a part of the basic data including an updated portion of the basic data, and an external log. Communication means for transmitting and receiving data to and from the device, wherein the communication means, when receiving the basic data transmission request, transmits the update log instead of the basic data.

According to the first aspect of the present invention, since the update log is transmitted instead of the basic data, the amount of transmitted data can be reduced. According to a second aspect of the present invention, in the data management device according to the first aspect, the communication unit includes:
An update log created after the transmission date and time when the update log was transmitted last time is transmitted.

According to the second aspect of the present invention, since only the update log created after the transmission date and time is transmitted, the already transmitted update log is not transmitted twice. According to a third aspect of the present invention, in the data management device according to the first aspect, the data management apparatus has an update log expiration date indicating a period during which the update log is stored, and a transmission date and time when the update log was transmitted last time is updated. Before the log expiration date, the communication means transmits the basic data.

According to the third aspect of the present invention, when the transmission date and time is before the update log expiration date, the basic data is transmitted, so that the update log before the update log expiration date is not used, and the old log is not used. There is no need to keep the update log. According to a fourth aspect of the present invention, there is provided a display unit for displaying an outline of basic data, and a communication unit for transmitting and receiving data to and from an external device, wherein the communication unit transmits a request for receiving the contents of the basic data. Then, the content of the basic data is received.

According to the fourth aspect of the present invention, since the outline of the displayed basic data can be confirmed and the contents of the basic data can be received, unnecessary data reception can be prevented. According to a fifth aspect of the present invention, in the data management device according to the fourth aspect, when the content of the basic data is in the data management device, the content of the basic data in the device is displayed on the display means. It is characterized by the following.

According to the fifth aspect of the present invention, when the contents of the basic data are in the management device, data transmission / reception is not performed, so that the load on the network can be reduced. According to a sixth aspect of the present invention, in the data management device according to the fourth aspect,
When the contents of the basic data are in the data management device, the communication means receives the update log when transmitting a request to receive the contents of the basic data.

According to the sixth aspect of the present invention, since the update log is transmitted instead of the basic data, the amount of data to be transmitted can be reduced without transmitting unnecessary data. According to a seventh aspect of the present invention, in the data management device according to the fifth or sixth aspect, a reference value serving as a reference for reliability of the basic data is provided, and when the basic data satisfies the reference value, the communication is performed. Means for transmitting the reception request.

According to the seventh aspect of the present invention, the transmission and reception of data is not performed for data outside the reliability reference value, so that the load on the network can be reduced. The invention according to claim 8 is the data management device according to claim 5 or 6, wherein the basic data has an expiration date, and when the basic data is out of the expiration date, the communication means transmits the reception request to the basic data. It is characterized by transmitting.

According to the eighth aspect of the present invention, data is not transmitted / received for data within the expiration date, so that the load on the network can be reduced.

[0016]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of the present invention will be described below with reference to the accompanying drawings. As shown in FIG. 1, a DB server 10 and a local server 20 are provided on a network according to the present invention, and both can communicate with each other via the network. The DB server 10 is a server D that is a master database on the network.
B11 and an update log 12 of the server DB11.

Here, the update log 12 is a server DB
11 shows a record of the update of the server DB11.
Indicates the date and time of the update, the location of the updated data, and the value of the updated data. Also, the update log 12
In principle, in addition to the update date, it is sufficient to store updated bit-unit information. However, in practice, the physical unit in which the update was performed (for example, a sector or the like on a floppy disk) ).

The server DB 11 has data 13, last update date and time 14, and expiration date 15 of the data 13. The last update date and time is the date and time when the data 13 was last updated.
And the logs before the expiration date 16 can be discarded.

The local server 20 is a local server DB2 which is a database having the same contents as the server DB11.
1 and a user application program 22 for a user of the local server DB 21 to access the local server DB 21. The local server DB 21 may copy the server DB 11 of the DB server 10, but since the local server 20 and the DB server 10 are connected via a network, it is only necessary to load from the DB server 10 via the network. . Further, the local server DB 21 has data 23, key information 24, and an expiration date 25 of the data 23. The key information 24 is the date and time when the data 23 was last obtained or the date and time when the server DB 11 was last referenced.

The user application program 22 is provided with the latest data for each program. The latestness of the data is set based on the reliability of the data and whether or not to obtain the latest data value. The higher the latestness, the more the latest data value is required. Here, the degree of currency is specified for each program, but there is a method of setting the currency for each of the data 13 and data 23 on the DB server 10 or the local server 20.

Next, processing performed in response to a data access request from the user application program 22 will be described for each case. First, from the user application program 22 to the local server DB
When an access request is made to data 23 of data 21, data 2
The case where the expiration date 25 of the third is within the expiration date will be described.

In this case, if the request for the latest data 23 by the user application program 22 is low, the data 23 in the local server 20 is transferred to the user application program 22. The case where the demand for the latestness of the data 23 is high will be described below.
From the data access request issued from the user application program 22, the local server 20 sends the key information 24 of the data 23 together with the data access request to the DB server 10 (here, the DB server 10 of the data 23).
Data acquisition date and time. ). The DB server 10 compares the last update date and time 14 of the data 13 with the acquisition date and time 24 of the data on the local server 20.

When the acquisition date / time 24 is equal to or greater than the last update date / time 14, that is, when the data 13 is acquired on the local server 20 after the data 13 on the DB server 10 is last updated, the DB server 10 Local server 2
0, the data 23 is valid, and the local server 20 passes the data 23 on the local server 20 to the user application program 22.

When the acquisition date and time 24 is smaller than the last update date and time 14, that is, when the data 13 on the DB server 10 is updated after the acquisition of the data 13 on the local server 20, the log of the DB server 10 Expiration date 16
And the data acquisition date and time 24 are compared. If the data acquisition date / time 24 is within the log expiration date 16, the DB server 1
0 transfers the update log 12 to the local server 20, and the local server 20 updates the data 23, and passes the updated data 23 to the user application program 22.

When the data acquisition date / time 24 is older than the log expiration date 16, the DB server 10
3 are all downloaded to the local server 20. The local server 20 updates the data 23 with the downloaded data 13 and passes the downloaded data 13 to the user application program 22.

Next, when the user application program 22 requests access to the data 23 of the local server DB 21 and the expiration date of the data 23 is out of the validity period 25, the request for the latestness of the data 23 is made. The same processing as in the case where is high is performed. In addition, even when the expiration date is not set, the same processing as that described above when the request for the latestness of the data 23 is high is performed.

FIGS. 2 to 8 show an embodiment for specifically showing a data management method according to the present invention. In the present embodiment, as shown in FIG.
Local server 40 of each of A, B, and C stores connecting server DB 31 of B server 30 via a network
Is a data management method in which a user refers to and updates the local server DB 41 in each local server 40.

As shown in FIG. 3, the DB server 30 has a server DB 31 and an update log 32. The server DB 31 has data 33, last update date and time 34, and expiration date 35. The update log 32 has a log expiration date 36. As shown in FIG. 4, the local server 40 has a local server DB 41 and a user application program 42. The local server DB 41 has data 43, data acquisition date and time 44, and expiration date 45. Here, data acquisition date and time 4
4 is the data 33 or the update log 3 from the DB server 30.
Let 2 be the date and time of acquisition.

First, the local server 40 downloads the data 33 from the server DB 31 of the DB server 30 to obtain data 43. Next, as shown in FIG. 5, it is assumed that the number of products: the data 33 of the DB server 30 has been updated. Here, for simplicity of explanation, it is assumed that the data is only date. The update log 32 is created each time data is updated, as shown in FIG. The update log 32 is 1
The logs before that date are deleted on the 7th of the month, and a new log is started to be created on the 7th of the month, and the expiration date 36 of the log is reset on the 7th of the month.

Hereinafter, the case where the user application program 42 accesses the data 43 of the local server DB 41 until the latest data is reached will be described with reference to FIGS. 7 and 8. First, on January 2, the user application program 42 inquires the local server DB 41 about the quantities of the products A, B, and C without the data 43 of the products A, B, and C on the local server DB 41. If
Since there is no data 43 for the products A, B, and C, the local server 40 accesses the DB server 30 to access the server DB3.
1 to 10 of product A and 2 of product B in the data 33
0, the quantity 30 of the product C is received, and the local server DB4
1, the data 43 of the products A, B, and C are written, and the data 33 is transferred to the user application program 42. Further, the local server 40 stores the data acquisition date 44
January 2 is stored.

Next, on January 3, the product A,
When there is an inquiry about the quantities of B and C, the local server 40 transmits the data acquisition date 44: January 2 to the DB server 30 together with the data access request. The DB server 30 compares the last update date 34: January 1 of the data with the last update date 34: January 1 and obtains the data 44: January 2
Since the date is before the date, it can be seen that the data 33 has not been updated after being acquired by the local server 40. Therefore,
Inform the local server 40 that the data 43 is valid. The local server 40 sends the user application program 42 data 43 on the local server 40:
The product A quantity 10, the product B quantity 20, and the product C quantity 30 are passed.

Next, on January 4, the product A, without requesting the latest from the user application program 42,
When the quantity is inquired to B and C, the data 33 of the DB server 30 is actually 11
However, since the latest value is not requested, the data 43 in the local server 40, the product A quantity 10,
The product B quantity 20 and the product C quantity 30 are passed to the user application program 42. Therefore, the response to the user application program 42 is quick and the network and the DB server 30 are not loaded.

Next, on January 5, the product A,
When there is an inquiry about the quantities of B and C, the local server 40 transmits the data acquisition date 44: January 2 to the DB server 30 together with the data access request. The DB server 30 compares the last update date 34: January 4 of the data with the last update date 34: January 4 and obtains the data 44: 1.
Since the date is after the month 2, the data 33 is transferred to the local server 4
It can be seen that the value has been updated to 0 after the acquisition. Therefore, the next processing, the expiration date 36 of the update log 32: January 1
Make a comparison with the day. Log expiration date 36: January 1 is acquisition date 44: before January 2, so acquisition date 44: update log 32 from January 2 onwards to January 5 of the day, here January 4 Is transmitted to the local server 40. The local server 40 updates the data 43 with the received update log 32, and outputs a product A quantity 11 and a product B quantity 2
0, the product C quantity is 30, and the acquisition date 44 is January 5
The date is updated and the updated data 43 is passed to the user application program 42.

Next, on January 7, the product A,
When the number of B and C is inquired, the local server 40 transmits the data acquisition date 44: January 5 to the DB server 30 together with the data access request. The DB server 30 compares the last update date 34: January 7 with the last update date 34: January 7 of the data and obtains the data 44: 1
Since the date is after March 5, the data 33 is stored in the local server 4
It can be seen that the value has been updated to 0 after the acquisition. Therefore, the following processing, the expiration date 36 of the update log 32: January 7
Make a comparison with the day. The log expiration date 36: January 7 is later than the acquisition date 44: January 5. Therefore, the update in the update log 32 is not enough, so the data 33 of the DB server 30: the number of goods A 11, the number of goods B 22, and the number of goods C 29 are transmitted to the local server 40. The local server 40 overwrites the data 43 with the received data 33, updates the acquisition date 44 on January 7, and passes the received data 33 to the user application program 42.

As described above, in response to the access request to the DB server 30, only the data 43 that has been caught in the time deadline needs to be updated again.
Is reduced, and the communication traffic and the load on the DB server 30, the local server 40, and the client are reduced. Furthermore, since the entire data 33 need not be reloaded for updating, the load on the network and the like is further reduced.

As another embodiment, there is a method of accessing a home page on the Internet. As shown in FIG. 9, there is a screen on which photos of Mt. Fuji are posted every day. If you only want to see today's Mt. Fuji, you can click on the item with today's Mt. Fuji and the title. As a result, only photos of today's Mount Fuji are downloaded and displayed. If you have no choice but to display them all, you will have to download all the photos for 6 days, the amount of data sent and received will be enormous, the network will be overwhelmed, and before it is displayed It takes a long time. In addition, since an outline of the data is displayed, it is possible to confirm which item is necessary data before downloading, and it is not necessary to download extra data.

Also, as shown in FIG. 10, the present invention can be applied to the price movement of stock prices and the like. Can be.

[0038]

According to the first aspect of the present invention, a transmission request for basic data can be received and an update log can be transmitted instead of the basic data. Data in the device can be updated, and the load on the network can be reduced.

According to the second aspect of the invention, only the update log created after the previous transmission date and time is transmitted, so that the updated update log is not transmitted twice.
It is possible to update to the latest data while reducing the load on the network. According to the third aspect of the present invention, when the update log has an update log expiration date and the transmission date and time is before the update log expiration date, the basic data is transmitted. There is no need to save logs and the data area can be used effectively.

According to the fourth aspect of the present invention, since a data reception request can be transmitted from the one on which the outline of the basic data is displayed, unnecessary data can be prevented from being received, and the load on the network can be reduced. it can. According to the fifth aspect of the present invention, when data is stored in the device, transmission / reception to / from the outside is not performed, so that unnecessary data transmission / reception can be prevented, and the load on the network can be reduced.

According to the sixth aspect of the present invention, when data is stored in the device, the update log can be received instead of the basic data. Can be updated, and the load on the network can be reduced. According to the seventh aspect of the present invention, a reference value of data reliability is provided, and a reception request is transmitted only for data that satisfies the reference value. Therefore, data transmission / reception is not performed for data outside the reference value. Therefore, the load on the network can be reduced.

According to the invention of claim 8, when the data has an expiration date and the data is within the expiration date, no data transmission / reception is performed, so that unnecessary data transmission / reception is prevented and the load on the network is reduced. Can be reduced.

[Brief description of the drawings]

FIG. 1 is a diagram showing a relationship between a DB server and a local server according to the present invention.

FIG. 2 is a diagram showing one embodiment of a DB server and a local server on a network according to the present invention.

FIG. 3 is a diagram illustrating a server DB and data of a DB server according to an embodiment;

FIG. 4 shows a local server D of a local server according to one embodiment.
It is a figure which shows B and data.

FIG. 5 is a diagram showing a transition of a change in the quantity of goods in one embodiment.

FIG. 6 is a diagram showing an update log created according to a change in the quantity of goods in one embodiment.

FIG. 7 is a diagram showing a processing progress when data of a local server DB is accessed from a user application program in one embodiment.

FIG. 8 is a diagram showing a processing progress when accessing data in a local server DB from a user application program in one embodiment.

FIG. 9 is a diagram showing an embodiment in which the present invention is applied to the Internet.

FIG. 10 is a diagram showing an embodiment in which the present invention is applied to the Internet.

[Explanation of symbols]

 10 DB Server 11 Server DB 12 Update Log 13 Data 14 Last Update Date 15 Expiration Date 16 Log Expiration Date 20 Local Server 21 Local Server DB 22 User Application Program 23 Data 24 Key Information 25 Expiration Date 30 DB Server 31 Server DB 32 Update Log 33 Data 34 Last update date and time 35 Expiration date 36 Log expiration date 40 Local server 41 Local server DB 42 User application program 43 Data 44 Data acquisition date and time 45 Expiration date

Claims (8)

[Claims] 1. An apparatus comprising: basic data for which data is updated; an update log recording a part of the basic data including an updated part of the basic data; and communication means for transmitting and receiving data to and from an external device. A data management device for transmitting the update log in place of the basic data when the communication unit receives the basic data transmission request. 2. The data management device according to claim 1, wherein said communication means transmits an update log created after a transmission date and time when said update log was previously transmitted. 3. The data management device according to claim 1, further comprising an update log expiration date indicating a period during which the update log is stored, wherein the transmission date and time at which the update log was transmitted last time is greater than the update log expiration date. The data management apparatus according to claim 1, wherein the communication unit transmits the basic data. And a communication means for transmitting / receiving data to / from an external device, wherein the communication means transmits a request for receiving the contents of the basic data. A data management device for receiving data contents. 5. The data management device according to claim 4, wherein when the content of the basic data is in the data management device, the content of the basic data in the device is displayed on the display means. Data management device. 6. The data management device according to claim 4, wherein when the content of the basic data is in the data management device, the communication unit transmits a request to receive the content of the basic data, A data management device for receiving the data. 7. The data management device according to claim 5, wherein a reference value serving as a reference of reliability of the basic data is provided, and when the basic data satisfies the reference value, the communication unit performs the reception. A data management device for transmitting a request. 8. The data management device according to claim 5, wherein said basic data has an expiration date, and said communication means transmits said reception request when said basic data is outside said expiration date. Characteristic data management device.