JP4033134B2 - Data access system and data access method - Google Patents

Description

The present invention relates to a data access system and a data access method , and more particularly to a data access system and a data access method for requesting data from a server.

  In recent years, the Internet, which is a huge computer network connecting the whole world, has been rapidly spreading. The Internet, which is a network between networks, can be accessed from a host computer (hereinafter simply referred to as a “host”) in a closed network such as a LAN (Local Area Network), and can be used to send e-mails or access external databases. Can be used. As described above, there are various services on the Internet. Among them, the WWW (World Wide Web) that can receive multimedia screens containing various moving images and sounds from all over the world is popular.

  In order to browse data on the WWW, client software called a browser such as Netscape Navigator (registered trademark of Netscape Communications) is used. The user writes a URL (Uniform Resource Locator) that specifies the WWW that he / she wants to view, or a link (highlighted character or image in an HTML (Hyper Text Markup Language) document). If you select with, you can see other data related to the document you are currently viewing.)

  By the way, there is a large amount of data on the WWW, but the data required by the user is a part of it. And since the data that was required in the past is very likely to be required in the future, the client software can store the history of the data viewed by following the link, or save the favorite page as a bookmark. It often has a function to do. The user can access necessary data with reference to the history and bookmarks stored in the client software.

  However, the history information is stored here in the environment where the client software is operating. A function for acquiring history information is incorporated in the client software in advance. Therefore, in order for the user to use history information from another environment or add a function for acquiring a new type of history, the client software has to be changed.

Therefore, several methods for simplifying access to a favorite page without changing the client software have been considered.
For example, there is a method of storing information about a user's favorite page in client software using JavaScript (registered trademark of Sun Microsystems). In this method, by selecting a specific page from information stored in advance by the user, the corresponding page can be displayed by JavaScript.

  As another method, there is a method of acquiring a user's page browsing history using JavaScript. In this method, JavaScript is moved in one of the client software windows, another window of the client software being operated is monitored by the JavaScript, and the history of tracing the link is sent to the server and stored. In this case, since the user's history information is stored on the server, the history information can be viewed from different client software.

  By the way, when using the Internet from the inside of a LAN or the like, generally, a method of connecting a host on which client software operates to a server having a data relay function called a proxy server is employed. Unauthorized intrusion and the like can be prevented by making the host inside the LAN and the Internet not directly connected but allowing them to access each other only through a proxy server.

  For example, a gateway device that eliminates unwanted access from the outside by replacing a hypertext link relayed between client software and a server is considered (for example, see Patent Document 1).

  Some proxy servers have a function of storing data once acquired in a cache in the server, and supplying data from the same when the same data is accessed again from inside the LAN. By saving log information during data relay and checking the data in the cache each time a data request is received, the load on the network can be minimized.

FIG. 40 is a diagram for explaining the operating environment of a conventional proxy server.
The proxy server 610 relays data between the network 620 and the LAN 600. Here, a server 621 having supply data 621a and a server 622 having supply data 622a are connected to the network 620. In addition, hosts 601 and 602 are connected to the LAN 600, and client software 601a and 602a for browsing data supplied from a server operate on each host. The proxy server 610 has a storage unit 611. When log information or data is acquired, the proxy server 610 stores the log information or data in the storage unit 611.

Here, how the proxy server operates when the client software 601a requests the contents of the supply data 621a held by the server 621 will be described.
FIG. 41 is a diagram for explaining the operation of a conventional proxy server. Parts that are not necessary for the description are omitted.

Assume that the client software 601a requests “data A”, a part of the supply data 621a of the server 621.
Upon receiving the data request from the client software 601a, the proxy server 610 acquires log information related to the data request and stores it in the storage unit 611. Then, the server 621 is accessed, and “data A” that is a part of the supply data 621a is requested. The obtained “data A” is stored in the storage unit 611 and supplied to the client software 601a. Thereafter, when “data A” is requested from any client software, the proxy server 610 issues a request for “data A” stored in the storage unit 611 without requesting the server 621 for data. Supply to client software.

As a result, the proxy server acts as a cache, and traffic on the network can be reduced and access can be speeded up.
In addition, when the WWW is shared by the proxy broadcast method, it is possible to share the data before participation to the midway participants by maintaining the access log to the WWW server in the proxy server. A technique is also considered (for example, refer nonpatent literature 1).

  However, in the method of storing favorite page information in the client software, the user must input information about the favorite page to the client software one by one. And in order to see the information stored in this way, you must call either a specific page or a specific function of the client, and simultaneously display the calling page while navigating the page. I can't. Furthermore, since information about a favorite page is stored on the client software, even if the same user is used, this function cannot be used when other client software is used.

  Similarly, even in the method of causing JavaScript to monitor other windows, there remains a problem that a dedicated page must be viewed in order to see the history. Moreover, in this method, a special page for starting the history must be viewed each time the access is made.

  In addition, since this method stores history information on a server, it is difficult not only to see the history information of a specific user, but also there is a security problem that it is possible to see history information of others.

Furthermore, the method using a proxy server as a cache has the following two problems.
The first problem is that stored log information is not normally provided to client software. For this reason, when the user makes a data request, the log information is not referred to. If log information is to be acquired, the proxy server storage means must be accessed in some way regardless of the client software.

  The second problem is that since only the latest data is held in the cache, it is not guaranteed that it remains in the cache when an attempt is made to reference a document before update. In other words, when accessing the same file, the cache assumes that the document has not been updated thereafter, and uses the result accessed in the past. Therefore, if it is found that the original file has been updated, the cache must also be updated, and previous access results are discarded. Even if it remains, there is no way to identify and access the old file, and it is impossible to refer to the file.

For the second problem in the proxy server, it is conceivable to apply workspace technology. A workspace is a system that supports and performs a plurality of tasks in parallel by storing and managing a work environment when a user performs work using a computer and switching between them. In such a workspace technology, a work environment existing in the past can be reproduced by storing and managing a work environment and / or a history of work performed by the user (for example, patents). Reference 2).
JP-A-8-446432 JP-A-7-295930 Mizuno et al., “Multimedia groupware system integrating DTC, VOD, and WWW” Information Processing Society of Japan, Information Processing Society of Japan, June 1996, Vol. 96, No. 60 (96-GW-18), p.49-54

  However, the system disclosed in Patent Document 2 has the following problems. That is, the old file before the change is saved with a file name such as “0331BK” even if the original file name is “specification”. For this reason, it is very difficult for the user to understand which file and which file has been operated in spite of continuous work.

  Moreover, there is a problem that the conventional work space technology cannot be applied when handling external documents or data obtained through the Internet or the like represented by the WWW. That is, even if the data on the server connected via the Internet is updated, the fact cannot be known on the client side referring to the data. Moreover, in the WWW, the data is specified by linking the data with the URL. Therefore, if the URL is changed to an alias when the past data is stored, it no longer works as a link. Therefore, the past state cannot be saved and cannot be reproduced.

The present invention has been made in view of these points, the data that can be contents of the data acquired from the server in the past be already modified, to refer to the contents of the data at the time acquired in the past again and to provide access systems, and data access methods.

  In the present invention, in order to solve the above-described problem, in an information terminal device that accesses data on a server connected via a network, a save command for a work state in which an icon associated with the data on the server is displayed. If there is, a storage means for storing the workspace indicating the work state in association with time information indicating the work state, a period specifying means for specifying a period for searching for past workspaces, and the specified period And a history display unit for displaying the searched workspace as an icon representing the workspace on a time axis. Is provided.

  In addition to relaying data to and from the server, the relayed data, the name of the data, and the time information are retained and managed as history information, and in response to a data request including the data name and history information, In an information terminal device that accesses data on a server connected via a network via a data relay device that sends back data included in the corresponding history information, an icon associated with the data on the server is displayed. If there is an instruction to save the working state, the saving means for saving the workspace indicating the working state in association with the time information indicating the working state, and the period specifying means for specifying the period for searching the past workspace Search means for searching for the saved workspace within the specified period; and A history display means for displaying the workspace as an icon on the axis, a reproduction means for reproducing the workspace corresponding to the icon representing the workspace instructed by the user, and an icon for the reproduced workspace By selecting, a request means for transmitting a data acquisition request including the name of data associated with the selected icon and time information associated with the workspace to the data relay device; Accordingly, there is provided an information terminal device comprising data receiving means for receiving data sent from the data relay apparatus and data display means for displaying the received data.

  Further, in an access control method for accessing data on a server connected via a network by an information terminal device, the information terminal device displays a working state in which an icon associated with the data on the server is displayed. When there is a save command, the workspace indicating the work status is saved in association with the time information indicating the work status, the specification of the period for searching the past workspace is received, and the save within the specified period is received. There is provided an access control method characterized in that a searched workspace is searched and the searched workspace is displayed as an icon representing the workspace on a time axis.

  In addition to relaying data to and from the server, the relayed data, the name of the data, and the time information are retained and managed as history information, and in response to a data request including the data name and history information, In an access control method for accessing data on a server connected via a network by an information terminal device via a data relay device that sends back data included in the corresponding history information, the information terminal device uses the server If there is a save command for the work status that displays the icon associated with the above data, save the workspace indicating the work status in association with the time information indicating the work status, and search for past workspaces. Receiving a specification of a period to be searched, searching for the saved workspace within the specified period, and searching for the searched workspace. Displaying the workspace as an icon representing the workspace on the time axis, reproducing the workspace corresponding to the icon representing the workspace instructed by the user, and selecting the icon on the reproduced workspace Transmits a data acquisition request including the name of the data associated with the selected icon and the time information associated with the workspace to the data relay device, and the data relay device according to the data acquisition request An access control method is provided, which receives data sent from the server and displays the received data.

  In the present invention, the history of the workspace is displayed on the time axis. This makes it possible to list how many workspaces are saved at a specified time and the positions on the time series, thereby improving work efficiency.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the following description, a data relay apparatus that can use history information from any client software will be described first, and then a data relay apparatus and server for reusing the contents of data at the time of access in the past. The information terminal device will be described.

  FIG. 1 is a diagram illustrating functions of the data relay apparatus. The data relay device 2 relays data between the information terminal device 1 and the server 4 connected to the network 3. The server 4 holds the data 4a and supplies the data 4a upon request.

  The data relay device 2 includes history information holding means 2a that holds history information relating to past data requests of the information terminal device, and data acquisition means 2b that acquires data in response to a data request input from the information terminal device. The data output unit 2 c outputs the acquired data and history information to the information terminal device 1.

  Here, the history information holding means 2a holds history information related to past data requests of the information terminal device 1, and when a new data request is input from the information terminal device 1, the history information holding means 2a displays the information related to the new data request as history information. Add as

  The data acquisition unit 2 b analyzes the input data request and requests the server 4 for the data 4 a via the network 3. If the data 4a is supplied from the server 4, the data 4a is input to the data output means 2c.

  When the data 4a is input from the data acquisition unit 2b, the data output unit 2c acquires the history information from the history information holding unit 2a. Then, the data 4 a and the acquired history information are output to the information terminal device 1.

Next, a first example of the network system used in the present invention will be described.
FIG. 2 is a block diagram illustrating a first example of a network system. The correspondence between FIG. 1 and FIG. 2 will be described after the description of FIG.

  The data relay device 20 of this system relays data between the information terminal devices (hosts) 11, 12,... Connected to the LAN 10 and the servers 31, 32,. I do.

  Here, the client software 11a is operating on the host 11 of the LAN 10 and the client software 12a is operating on the host 12, and requests data to the data relay apparatus 20 via the LAN 10. The server 31 of the network 30 holds data 31a, and the server 32 holds data 32a. The data relay device 20 acquires these data via the network 30.

  The data relay device 20 includes a history information holding unit 21 that holds history information related to past data requests, a data acquisition unit 22 that acquires data in response to a data request input from a host via a LAN, A data creation unit 23 that creates history-added data by adding history information to the received data, and a data output unit 24 that outputs the created data with history to the host via the LAN 10.

  The data request output from the client software 11a, 12a includes a URL that specifies the requested data. Here, the URL of the data includes necessary information such as a host name and an IP address in the network 30 of the server holding the data.

  The history information holding unit 21 holds, as history information, a URL of data included in a data request input in the past from the client software 11a, 12a on the hosts 11, 12 connected to the LAN 10.

  Further, when a new data request is input via the LAN 10, the history information holding unit 21 inputs the history information held so far to the request processing unit 22a. Then, the URL of the data included in the new data request is added as history information. The history information held by the history information holding unit 21 is supplied to the data creation unit 23 when requested.

  The data acquisition unit 22 includes a request processing unit 22a that processes an input data request based on history information, and a data holding unit 22b that holds data supplied via the network 30 in the past. .

  Here, when a data request is newly input, the request processing unit 22a checks with the history information input from the history information holding unit 21 to check whether the same data has been relayed in the past. If the same data has been relayed in the past, since the data should be held in the data holding unit 22b, an instruction is issued to output the corresponding data to the data holding unit 22b. If the same data has not been relayed in the past, the network 30 is requested for data based on the URL. Since the data supplied in response to this request is first stored in the data holding unit 22b, the data holding unit 22b is instructed to output the data after waiting for the supplied data.

  The data holding unit 22b holds data previously supplied via the network 30. If data is supplied through the network 30, the data is also stored. Then, the data is output to the data creation unit 23 in accordance with the instruction from the request processing unit 22a.

  When data is input from the data holding unit 22 b of the data acquisition unit 22, the data creation unit 23 requests history information from the history information holding unit 21. The history input data is added to the data input from the data holding unit 22b, and a link to the data indicated by the history information is added to create data with history. The created data is input to the data output unit 24.

The data output unit 24 outputs the data with history input from the data creation unit 23 to the client software of the host that has input the data request via the LAN 10.
The information terminal device 1 shown in FIG. 1 corresponds to the hosts 11 and 12 shown in FIG. Similarly, the data relay device 2 corresponds to the data relay device 20, the network 3 corresponds to the network 30, the server 4 corresponds to the servers 31 and 32, and the data 4a corresponds to the data 31a and 32a, respectively.

The history information holding unit 2a corresponds to the history information holding unit 21, the data acquisition unit 2b corresponds to the data acquisition unit 22, and the data output unit 2c corresponds to the data output unit 24.
Next, what kind of procedure is performed when such data relay device 20 outputs data in response to a data request from client software will be described.

FIG. 3 is a flowchart showing a data relay procedure of the data relay apparatus. Hereinafter, description will be made along the steps in the figure.
[S1] When a data request is input, first, information related to the data request is added and stored as new history information in the history information holding unit 21. At this time, history information up to that time is input to the request processing unit 22a.

  [S2] The request processing unit 22a of the data acquisition unit 22 examines the history information input from the history information holding unit 21 in step S1. That is, it is determined whether or not the URL of data included in the input data request is included in the history information.

  [S3] If the URL of the data included in the input data request is included in the history information as a result of the determination in step S2, it means that the same data has been relayed in the past, and the process proceeds to step S8. If the same data has not been relayed in the past, the process proceeds to step S4.

  [S4] The request processing unit 22a requests the corresponding data based on the URL of the data included in the input data request. This request is for requesting a designated server to supply data to the data relay device 20 via the network 30.

  [S5] It is determined whether or not the corresponding data exists. If the corresponding data exists, the process proceeds to step S7, and if the corresponding data does not exist, that is, the designated server does not exist or the data having the designated data name does not exist in the designated server, the process proceeds to step S6.

  [S6] If the corresponding data does not exist, the input data request requests non-existing data. An error message is output and the processing of this flowchart is terminated.

  [S7] When the corresponding data exists, the data holding unit 22b of the data acquisition unit 22 is supplied with the corresponding data via the network 30. The data holding unit 22b holds the supplied data.

[S8] The data holding unit 22b outputs data corresponding to the input data request to the data creation unit 23.
[S9] The data creation unit 23 requests history information from the history information holding unit 21 when the corresponding data is input from the data holding unit 22b. The history information supplied from the history information holding unit 21 and the link to the data indicated by the history information are added to the corresponding data to create data with history. The created data with history is supplied to the data output unit 24.

  [S10] The data output unit 24 outputs the data with history supplied from the data creation unit 23 to the client software of the host that has input the data request to the data relay device 20 via the LAN 10.

Here, an example of a client software screen when browsing data with the host 11 shown in FIG. 2 is shown.
FIG. 4 is a diagram illustrating an example of a client software screen for browsing data with history.

  The client software screen 40 displayed by the operation of the client software 11a includes a data window 41 for displaying requested data. When the data relay device 20 is not used, the requested data is displayed as it is in the data window 41. In this case, the data window 41 is provided with a history information column 42 and a data column 43. The client software screen 40 shown here shows a display example when “data A” is called by specifying a URL.

  In the history information column 42 of the data window 41, a link 42a to “data A” is arranged as history information. Further, “Data A” displayed in the data column 43 has a link 43 a to “Data B” in the content.

  Here, when the link 43a to “data B” in the data column 43 is selected by a pointing device or the like, a data request for requesting “data B” is issued from this client software.

A display example when “data B” is called in this way is shown below.
FIG. 5 is a diagram showing a screen in which “data B” is called from the client software screen shown in FIG. Since the screen shown in FIG. 4 and the screen shown in FIG. 5 are basically the same, the same portions are denoted by the same reference numerals and description thereof is omitted.

  In the history information column 42 of the data window 41, a link 42b to “data B” is added as history information. “Data B” displayed in the data column 43 has a link 43b to “data C” in the content.

  Here, when the link 43b to “data C” in the data column 43 is selected by a pointing device or the like, a data request for requesting “data C” is issued from the client software.

A display example when “data C” is called in this way is shown below.
FIG. 6 is a diagram showing a screen in which “data C” is called from the client software screen shown in FIG. Since the screen shown in FIG. 5 and the screen shown in FIG. 6 are basically the same, the same portions are denoted by the same reference numerals and description thereof is omitted.

  In the history information column 42 of the data window 41, a link 42c to “data C” is added as history information. Further, the contents of “data C” are displayed in the data column 43.

  Next, an example of the client software screen when the host 11 browses data after performing the operations of FIGS. The client software that operates here may be the same as or different from the client software of the host 11.

  FIG. 7 is a diagram illustrating another example of a client software screen for browsing data with history. The client software screen 50 displayed by the operation of the client software 12a includes a data window 51 for displaying requested data. When the data relay device 20 is not used, the requested data is displayed as it is in the data window 51. In this case, the data window 51 is provided with a history information column 52 and a data column 53. The client software screen 50 shown here shows a display example when “data D” is called by specifying a URL.

  In the history information column 52 of the data window 51, as the history information, a link 52a to "data A", a link 52b to "data B", a link 52c to "data C", and "data D" A link 52d is arranged. Further, the contents of “data D” are displayed in the data column 53. Even if there is no past history information of the host 12 itself, the history information of the host 11 connected to the data relay device 20 via the same LAN 10 is arranged in the history information column 52 and can be used as a link for calling data.

  As described above, by storing history information in the data relay device, data with history can be obtained even from different client software. In addition, by retaining history information and data relayed in the past and adding a link to the data indicated by the history information, the client software can re-access the data accessed in the past easily, quickly and safely. It became possible to do. This re-access need not be from the same client software.

  Further, when using this data relay device, history information is added to the data and is output to the client software together with the data, so there is no need to change the contents of the client software.

  In the above description, the history information holding unit 21 adds and stores information about the data information every time a data request is input. However, if the history information has a counter and the same information exists, You may make it replace with addition by increasing the count of applicable historical information.

  In the above description, the data relay unit 20 is provided with the data creation unit 23 and the history data is output to the client software. However, the request data and the history information may be output separately to the host.

  Furthermore, in the above description, only the URL of the data is used as history information, and only the link to the data is arranged in the history information column. However, the user name and host name that issued the data request, the date and time when the data request was made, etc. May also be stored in the history information holding unit 21 as history information and described in the history information column. At that time, it is also possible to add only history information from the same user to the request data and not to notify other users' history information.

Next, a second example of the network system used in the present invention will be described.
FIG. 8 is a block diagram illustrating a second example of the network system.
The data relay device 70 of this system relays data between information terminal devices (hosts) 61, 62,... Connected to the LAN 60 and servers 81, 82,. I do.

  Here, the client software 61 a operates on the host 61 of the LAN 60 and the client software 62 a operates on the host 62, and requests data to the data relay device 70 via the LAN 60. The server 81 of the network 80 holds data 81a, and the server 82 holds data 82a. The data relay device 70 acquires these data via the network 80.

  The data relay device 70 includes a history information holding unit 71 that holds history information relating to past data requests, a data acquisition unit 72 that acquires data in response to a data request input from the host via the LAN, A condition management unit 75 for determining whether or not to add history information to the obtained data; a data creation unit 73 for creating history-added data by adding history information to the obtained data; And a data output unit 74 for outputting to the host.

The data request output from the client software 61a, 62a includes the URL of the requested data.
The history information holding unit 71 holds, as history information, the URL of the data included in the data request input in the past from the client software 61a, 62a on the hosts 61, 62 connected to the LAN 60.

  Further, when a new data request is input via the LAN 60, the history information holding unit 71 adds the URL of the data included in the data request as history information. The history information held by the history information holding unit 71 is supplied to the condition management unit 75 if requested.

The data acquisition unit 72 requests data from the network 80 in response to the input data request. Then, the acquired data is input to the condition management unit 75.
The condition management unit 75 holds history unnecessary conditions. When data is input from the data acquisition unit 72, it is determined whether the data matches the history unnecessary condition. If they match, only that data is input to the data creation unit 73. If they do not match, the history information is requested from the history information holding unit 71, and the data and the history information are input to the data creation unit 73 as a set.

  When only data is input from the condition management unit 75, the data creation unit 73 outputs the data to the data output unit 74 without adding anything to the data. When data and history information are input as a set from the condition management unit 75, history information and a link to the data indicated by the history information are added to the data to create data with history. The created data with history is input to the data output unit 74.

The data output unit 74 outputs the data input from the data creation unit 73 or the data with history to the client software of the host that has input the data request via the LAN 60.
Next, a description will be given of the procedure in which processing is performed when such data relay device 70 outputs data in response to a data request from client software.

FIG. 9 is a flowchart showing a data relay procedure of the data relay apparatus. Hereinafter, description will be made along the steps in the figure.
[S21] When a data request is input, the history information holding unit 71 adds and stores information related to the data request as new history information.

  [S22] The data acquisition unit 72 requests the corresponding data based on the URL of the data included in the input data request. This request is for requesting a designated server to supply data to the data relay device 70 via the network 80.

  [S23] It is determined whether the corresponding data exists. If the corresponding data exists, the process proceeds to step S25, and if the corresponding data does not exist, that is, if the designated server does not exist or the data having the designated data name does not exist in the designated server, the process proceeds to step S24.

  [S24] If the corresponding data does not exist, the input data request requests non-existing data. An error message is output and the processing of this flowchart is terminated.

[S25] When the corresponding data exists, the data acquisition unit 72 is supplied with the corresponding data via the network 80. The corresponding data is input to the condition management unit 75.
[S26] When the corresponding data is input, the condition management unit 75 collates the stored history unnecessary condition with the corresponding data. If the history unnecessary condition matches the corresponding data in this collation, the process proceeds to step S29. If they do not match, the process proceeds to step S27.

  [S27] Since the history unnecessary condition does not match the corresponding data, data with history is created. The condition management unit 75 requests history information from the history information holding unit 71 and inputs the supplied history information and the corresponding data to the data creation unit 73 as a set.

[S28] The data creation unit 73 creates history-added data from the set of input data and history information. The created data with history is input to the data output unit 74.
[S29] Since the history unnecessary condition matches the corresponding data, data with history is not created. The condition management unit 75 inputs the corresponding data as it is to the data creation unit 73. Then, the data creation unit 73 inputs the input data as it is to the data output unit 74.

  [S30] The data output unit 74 outputs the input data with history or the corresponding data to the client software of the host that has input the data request to the data relay device 70 via the LAN 60.

Here, the operation of the data relay apparatus of the present system will be described with an example of the history unnecessary condition.
FIG. 10 is a diagram illustrating an example of the history unnecessary condition.

  The history unnecessary condition 75a is held in the condition management unit 75 shown in FIG. 8. If any one of the conditions described in the history unnecessary condition 75a matches, it is considered that the history unnecessary condition is met. .

  Looking at the history unnecessary condition 75a, the data type is image data as a condition for not adding the history to the data relayed to “user A”, the data content includes the character string “history”, and the URL is “http "http://www.xxx.co.jp".

  In addition, as a condition for not adding a history to data relayed to “user B”, the data type is HTML, the URL is “http://www.yyy.co.jp/index.html”, and What is “http://www.zzz.com” is listed.

  Therefore, the condition management unit 75 collates the data acquired in response to the data request with the history unnecessary condition 75a one by one and cancels the addition of history information if any one of the above conditions is met.

  In the above description, the history unnecessary conditions are three types, that is, the data type, data content, and URL. However, other history unnecessary conditions may be set. It is also possible to decide to add a history without specifying the user.

  Furthermore, in the above description, the determination as to whether or not the history is unnecessary is performed after the acquisition of the corresponding data. However, if the history unnecessary condition is a URL or a user name, the determination is performed before the acquisition of the corresponding data. You may go.

  This completes the description of the data relay apparatus that can use history information from any client software. Hereinafter, a data relay device, a server, and an information terminal device for reusing data contents when accessed in the past will be described.

  FIG. 11 is a block diagram illustrating a third example of the network system. This is because the client software connected to the network acquires the data through the data relay means when the data is acquired from the server connected to the network by specifying the name of the data. The past data is acquired by specifying the data name.

  The host 110 is connected to the data relay device 120 via the network 101. The data relay device 120 is connected to a server 131 that holds data 132 via the network 102.

  In the host 110, client software 111 that refers to data via the network 101 is executed. The user of the host 110 can output a data acquisition request by inputting a data name or the like to the client software 111. The data acquisition request output from the client software 111 to the data relay device 120 includes a data relay request for referring to the data of the server 131 and a history information acquisition request for referring again to the data referred to in the past. . If the data acquisition request is a data relay request, the data acquisition request includes the name of the data to be referenced (including the server name, storage location, and file name). When the data acquisition request is a history information acquisition request, time information at the time of reference in the past is included in addition to the name of the data to be referred to. Further, the client software 111 has a function of receiving data sent from the data relay device 120 and displaying the content of the data on the screen of the display device.

The data relay device 120 includes the following elements.
The request analysis unit 121 determines whether the data acquisition request from the host 110 is a data relay request or a history information acquisition request. If the data acquisition request is a data relay request, the data name is extracted from the data acquisition request. If the data acquisition request is a history information acquisition request, the data name and time information are extracted from the data acquisition request.

  The data request unit 122 receives the data name extracted by the request analysis unit 121 when the data acquisition request is a data relay request. When the name of the data is input, the name of the data is input to the name analysis unit 123. Then, the data corresponding to the name of the data extracted by the request analysis unit 121 is requested from the server corresponding to the identifier returned from the name analysis unit 123, and the data from the server 131 is received.

The name analysis unit 123 analyzes the name of the data input from the data request unit 122 and returns an identifier of the server that should request the data corresponding to the name.
When the data acquisition request is a data relay request, the history management unit 124 uses the data received by the data request unit 122 as the time information indicating the data name, the data content, and the time when the data relay process was performed. Corresponding information is stored in the history holding means 125 as history information. Then, the history management unit 124 sets the data received by the data request unit 122 as output data. If the data acquisition request is a history information acquisition request, the history management unit 124 matches the data name and time information indicated by the data acquisition request from the data stored in the history storage unit 125. History information to be output is output data.

The history holding unit 125 stores the name of the data relayed by the data relay device 120, the data contents, and the time when the data relay processing was performed in association with each other and stored as history information.
The output unit 126 outputs the contents of the output data specified by the history management unit 124 to the client software 111.

The server 131 adds other information to the data contents, and holds and manages them in a table format.
FIG. 12 is a diagram illustrating an example of a data table held by the server. In the data table 131a, “data name”, “data content”, and “last update date” are stored and managed in association with each other.

  In the system configured as described above, when the user of the host 110 refers to the data 132 of the server 131, the client software 111 is used to transmit a data acquisition request specifying the name of the data to be referenced. Here, it is assumed that data corresponding to the name “NAME1” is requested.

  In the data relay device 120, the request analysis unit 121 receives a request from the client software 111. The request analysis unit 121 analyzes the request and recognizes that it is a data relay request. In this example, since the time information is not included in the data acquisition request, it can be determined that the request is a data relay request. Then, the request analyzing unit 121 extracts the name “NAME1” and inputs the name “NAME1” to the data requesting unit 122.

  When the name “NAME1” is input from the request analysis unit 121, the data request unit 122 inputs the name “NAME1” to the name analysis unit 123. The name analyzing unit 123 analyzes the name “NAME1” input from the data requesting unit 122 and returns an identifier of a server that should request data corresponding to the name “NAME1”. The data request unit 122 transmits the name “NAME1” to the server corresponding to the identifier returned from the name analysis unit 123 in order to request data corresponding to the name “NAME1”.

  When the server 131 receives the name “NAME1” from the data requesting unit 122, the server 131 holds the data “DATA1” and the data “DATA1” last updated when the data corresponding to the name “NAME1” is held. Returns the date “LAST1”. If the server does not hold data corresponding to the name “NAME1”, it returns “not found”.

  The data request unit 122 inputs the data “DATA1” and the last update date “LAST1” returned from the server to the history management unit 124 together with the name “NAME1”. When the name “NAME1”, the data “DATA1”, and the last update date “LAST1” are input from the data request unit 122, the history management unit 124 receives the name “NAME1”, the data “DATA1”, the last update date “LAST1”, and the time. The time “T11” (the time when the history information storage process was performed) is held and managed in the history holding means 125. If the content input from the data request unit 122 is “not found”, nothing is stored in the history holding unit 125.

  FIG. 13 shows an example of a table held by the history holding means. In this way, in the table 125a, “name of data”, “content of data”, “date of last update”, and “time” are stored and managed in association with each other.

  The history management unit 124 inputs the data “DATA1” input from the data request unit 122 to the output unit 126 as output data. The output unit 126 transmits the data “DATA1” input from the history management unit 124 to the client software 111. The client software 111 receives the transmitted data “DATA1” and displays the contents on the screen of the display device. Thereby, the user who operated the client software 111 can refer to the target data.

  In the above description, the history management unit 124 is described to always store the history information of the data from the server 131 in the history holding unit 125, but it is not necessarily stored in the history holding unit 125 in all cases. do not have to. For example, when the name “NAME1”, the data “DATA1”, and the last update date “LAST1” are input from the data requesting unit 122, the name held by the history holding unit 125 is searched, and the history holding unit 125 searches the data requesting unit 122. When the same name as the name “NAME1” input from the data “DATA1” is stored, the data “DATA1” associated with the name “NAME1” is compared with the data “DATA1” input from the data requesting unit 122. Only when they are different from each other, the name “NAME1”, the data “DATA1”, the last update date “LAST1”, and the time “T11” may be held in the history holding unit 125.

  In addition, the history management unit 124 searches for the name held by the history holding unit 125 when the name “NAME1”, the data “DATA1”, and the last update date “LAST1” are input from the data request unit 122, and the history holding unit When 125 holds the same name as the name “NAME1” input from the data request unit 122, the last update date associated with the name “NAME1” and the last update date “LAST1” input from the data request unit 122. ”And only when the last update date“ LAST1 ”input from the data requesting unit 122 is new, the name“ NAME1 ”, the data“ DATA1 ”, the last update date“ LAST1 ”, and the time“ T11 ”are stored in the history holding unit 125. May be held.

  In addition, as the time to be stored in the history holding unit 125, the time at which data is written to the history holding unit 125 is stored. However, if the time information is generated during the data relay process, another time is used. You can also For example, the following processing may be performed. First, the time “T01” when the request analysis unit 121 receives a request from the client software 111 is input to the data request unit 122 together with the name “NAME1”. The data request unit 122 inputs the time “T01” input from the request analysis unit 121 together with the name “NAME1”, the data “DATA1”, and the last update date “LAST1” to the history management unit 124. Then, the history management unit 124 associates the name “NAME1”, the data “DATA1”, the last update date “LAST1”, and the time “T01” input from the data requesting unit 122, and holds and manages them in the history holding unit 125. To do. As a result, the time “T01” when the request analysis unit 121 receives a request from the client software 111 is used as time information for specifying data of history information.

  Further, the output means 126 inputs the time “T02” when the output means 126 transmits the data “DATA1” to the client software 111, and the history management means 124 is associated with the name “NAME1”. Along with other information, the time “T02” at which the data “DATA1” was transmitted may be stored in association with the name “NAME1”.

  Further, when the data requesting unit 122 inputs the time “T03” when the data requesting unit 122 transmits the name “NAME1” to the server 131, the history requesting unit 124 is associated with the name “NAME1”. In addition to other information, the time “T03” at which the name “NAME1” is transmitted may be stored and managed in association with the name “NAME1”.

  Further, by inputting the time “T04” when the data request unit 122 receives the data “DATA1” from the server 131 to the history management unit 124, the history management unit 124, together with other information associated with the name “NAME1”, The time “T04” at which the data “DATA1” is received may be stored and managed in association with the name “NAME1”.

  The user name can also be included in the data acquisition request output by the client software 111. In this case, the request analysis unit 121 extracts the user name from the data acquisition request, and inputs the user name together with the name “NAME1” to the data request unit 122. The data request unit 122 inputs the user name input from the request analysis unit 121 together with the name “NAME1”, the data “DATA1”, and the last update date “LAST1” to the history management unit 124. The history management unit 124 associates the name “NAME1”, the data “DATA1”, the last update date “LAST1”, the user name, and the time at that time, which are input from the data requesting unit 122, and holds and manages them in the history holding unit 125. .

  Further, the host name can be included in the data acquisition request output by the client software 111. In this case, the request analysis unit 121 inputs the host name sent in response to the data acquisition request to the data request unit 122 together with the name “NAME1”. The data requesting means 122 inputs the host name inputted from the request analyzing means 121 together with the name “NAME1”, the data “DATA1”, and the last update date “LAST1” to the history managing means 124, and the history managing means 124 The name “NAME1”, the data “DATA1”, the last update date “LAST1”, the host name, and the time at that time input from the means 122 are associated and held in the history holding means 125.

  Similarly, various context information other than the user name and host name can be included in the data acquisition request. For example, a job name, department name, or group name may be included as context information.

  In addition, the data acquisition request output from the client software 111 can include a designation not to take a history. When this designation is made, the request analysis unit 121 notifies the history management unit 124 to that effect. The history management unit 124 that has received the notification does not hold and manage the name “NAME1” and information associated with the name even if the data and the related information are received from the data requesting unit 122. By designating that no history is taken, useless data is not saved, and the storage area of the data relay device 120 can be used effectively.

The above is the description regarding the processing until the data relay device 120 relays data and stores information regarding the content and time of the data.
Next, processing when the client software 111 re-browses data that has been browsed in the past by specifying the past time and the name of the data will be described.

  The client software 111 transmits a data acquisition request including the name “NAME1” and the time “T11” to the data relay apparatus 120 in order to acquire data at a certain time “T11” corresponding to the name “NAME1”. . Here, the time “T11” is specified by the user inputting to the client software 111, but the time “T11” may not be strictly correct. That is, it is sufficient if the user himself / herself stores the time when the data “DATA1” of the name “NAME1” is referred to in the past and designates the time.

  In the data relay device 120, the request analysis unit 121 receives a request from the client software 111. The request analysis unit 121 analyzes the data acquisition request and extracts the name “NAME1” and the time “T11”. Since the time “T11” is included in the data acquisition request, it can be recognized that this request is a history information acquisition request. Therefore, the request analysis unit 121 inputs the name “NAME1” and the time “T11” to the history management unit 124.

  When the name “NAME1” and the time “T11” are input from the request analysis unit 121, the history management unit 124 determines whether the history holding unit 125 stores data corresponding to the name “NAME1” and time “T11” pair. Check out. If it is held, the data “DATA1” is input to the output means 126. If not held, “not found” is input to the output means 126. Note that a certain amount of error is allowed in determining whether or not the times “T11” match.

  The output unit 126 transmits the data received from the history management unit 124 to the client software 111. The client software 111 displays the received data on the screen. Thereby, even if the content of the data of the name “NAME1” held by the server 131 is changed, the user can refer to the same content as that referenced at the past time “T11”.

  When the name “NAME1” and the time “T11” are input from the request analysis unit 121, the history management unit 124 does not hold the data corresponding to the name “NAME1” and the time “T11”. May be such that only the names match, and the data that the history holding unit 125 holds in association with the name “NAME1” is the closest to the input time “T11”. Thereby, even if the time is specified based on the ambiguous memory of the user, the target data can be referred to.

  Further, when the name “NAME1” and the time “T11” are input from the request analysis unit 121, the history management unit 124 does not hold the data corresponding to the name “NAME1” and the time “T11”. And the time that the history holding means 125 holds in association with the name “NAME1” is closest to the input time “T11” and the history holding means 125 holds in association with the name “NAME1”. Data that is older than the time “T11” when is input may be input to the output means 126. If there is no old data, “not found” may be returned.

  Further, when the name “NAME1” and the time “T11” are input from the request analysis unit 121, the history management unit 124 does not hold the data corresponding to the name “NAME1” and the time “T11”. And the time that the history holding means 125 holds in association with the name “NAME1” is closest to the input time “T11” and the history holding means 125 holds in association with the name “NAME1”. Data that is newer than the time “T11” when the “” is input may be input to the output means 126. If there is no new data, “not found” may be returned.

  Further, when the name “NAME1” and the time “T11” are input from the request analysis unit 121, the history management unit 124 does not hold the data corresponding to the name “NAME1” and the time “T11”. May instruct the data requesting unit 122 to acquire data of the name “NAME1” from the server 131. When the name “NAME1” is input from the history management unit 124, the data request unit 122 performs the same processing as when the name “NAME1” is input from the request analysis unit 121.

  Moreover, although this system demonstrated the example which distributed the client software 111, the data relay apparatus 120, and the server 131 on the network, any combination may exist on the same computer.

  When each element of the data relay device 120 is included in the server 131, the data acquisition request sent from the host is either the latest data acquisition request or the history information acquisition request. The data request unit 122 is replaced with a data search unit. The data retrieval means retrieves data corresponding to the data name extracted by the request analysis means from the data holding means (holding data to be provided to other devices) when the data acquisition request is the latest data acquisition request. To do.

  When the client software 111 includes each element of the data relay device 120, the request analysis unit 121 analyzes a data acquisition request input by the user using an input device (such as a keyboard). Further, the output unit 126 is replaced with a display unit. The display means displays the contents of the output data specified by the history management means on the screen of the display device.

  Further, the data relay device 120 manages the requested data name, data content, last update date and time in association with each other, instead of managing the requested data name, data content, and last update date. And identifiers that can identify these three sets may be stored in association with each other. In this case, the client software 111 acquires an identifier from the data relay device 120, and transmits the name and identifier to the data relay device 120, thereby acquiring past viewed data.

  The client software 111 may hold and manage time information. In this case, the client software includes time holding means, access time management means, and time information display means. The time holding means holds time information. When outputting the data acquisition request, the time management means stores the name of the requested data and the time information of the time when the request is output in association with the time holding means, and when the access time acquisition request is input, The time information held in the time holding means is output. The time information display means displays the time information output from the access time management means on the screen of the display device. This eliminates the need to rely on the user's memory for the time at which data was acquired in the past.

  Next, a fourth example of the network system will be described. In the fourth example of the network system, the client software acquires past environment information (related information other than data in the history information) from the data relay device, and the information browsed by the user in the past using the environment information. Is requested again from the data relay device. As the environment information, “user name”, “URL”, “work name”, and “time” are used. As the “time”, the time when the client software requests data to the data relay apparatus is used.

  FIG. 14 is a block diagram illustrating a fourth example of the network system. This figure shows an example in which client software 141a, 142a, which is a WWW browser, browses an HTML document stored in a WWW server existing on the Internet via the data relay device 150.

  In the figure, a plurality of hosts 141 and 142 are connected to the data relay apparatus 150 via a network 143. The data relay device 150 is connected to a plurality of WWW servers 161 and 163 via the Internet 165. The WWW servers 161 and 163 hold HTML documents 162 and 164, respectively.

  In each of the hosts 141 and 142, client software 141a and 142a which are WWW browsers are executed. The client software 141a, 142a requests data to the data relay device 150 and accepts the requested data. The received data is displayed on the screen by the client software 141a, 142a. Further, the client software 141a, 142a sends environment information to the data relay device 150 when data is requested, inquires the environment information to the data relay device 150, and designates the environment information to the data relay device 150. Request data for

  The data relay apparatus 150 includes a request analysis unit 151, a data request unit 152, a name analysis unit 153, a history management unit 154, a history holding unit 155, and an output unit 156. These components basically have the same functions as the elements of the same name in the data relay apparatus 120 shown in FIG. However, in order to receive environment information from the client software 141a and 142a and to respond to an inquiry about the environment information, it further has the following functions.

  Upon receiving the data acquisition request from the client software 141a, 142a, the request analysis unit 151 extracts environment information such as time information (time when the client outputs the request) included in the request and sends it to the history management unit 154. If the data acquisition request is a data relay request, the history management unit 154 stores environment information from the request analysis unit 151 in the history holding unit 155 together with information such as the contents of data sent from the data request unit 152. If the data acquisition request is a history information acquisition request, data matching the environment information sent from the request analysis unit 151 is extracted from the history holding unit 155 and sent to the output unit 156. The output unit 156 sends the environment information to the client software 141a and 142a.

When the URL is sent, the WWW servers 161 and 163 determine whether or not to retain data corresponding to the URL, and if so, transmit the data to the request source.
In the system configured as described above, a user who uses the client software 141a of the host 141 refers to a document having a file name “index.html” held by the WWW server 161 having an address “www.test.com”. The case where it does is demonstrated.

  First, the user logs in to the client software 141a. In the client software 141a, user names of available users are registered in advance, and only login using the registered user names is permitted. In this example, it is assumed that the user has logged in with the user name “hashimoto”. If the login is successful, the browsing screen is displayed as one window in the screen of the display device. The user browses a desired HTML document by inputting predetermined items on the browsing screen. The job name and URL are input.

  FIG. 15 is a diagram showing a browsing screen. On the upper left side of the browsing screen 200, there is a user name display unit 201 that displays the user name of the logged-in user. In this example, “hashimoto” is displayed. On the right side of the user name display unit 201 is a text box 202 for inputting a work name. In this text box 202, the user inputs a category of work currently being performed. Below the user name display unit 201 is a text box 203 for URL input. In this text box 203, the URL of the document to be referred to is input. To the right of the URL input text box 203, an “Open” button 204 and a “history display” button 205 are provided. If the “Open” button 204 is pressed, a data acquisition request including the time when the button 204 is pressed is output from the client software 141 a to the data relay device 150. The “history display” button 205 is a button for requesting history information to the data relay device 150. When this button 205 is pressed, a history display screen is displayed.

  The user enters “patent” in the work name input text box 202 of the browsing screen 200 and “http://www.test.com/index.html” in the URL input text box 203. .

If the input work name and URL are correct, the user presses the “Open” button 204. The date and time at this time is “97/03/08 12:35”. Then, the client software 141a sends the URL “http://www.test.com/index.html”, the user name “hashimoto”, the work name “patent”, and the time “97/03” to the data relay device 150. / 08 12:35 "is sent. The data to be sent is represented by the following structure, for example.
(GET
(USER hashimoto)
(URL http: //www.test.com/index.html)
(WORK patent)
(TIME 97/03/08 12:35)
)
Also,
"Http://proxy.xxx.co.jp/cgi-bin/GET?USER=hashimoto&URL=http://www.test.com/index.html&WORK=patent&TIME=97/03/08_12:35"
As described above, the request may be transmitted to the data relay apparatus 150 in a format in which all information is included in the URL. If this format is used, an existing browser can be used as client software.

  Further, HTTP (Hypertext Transfer Protocol) may be extended to transmit data corresponding to USER, WORK, or TIME to the data relay device 150.

The request analysis unit 151 of the data relay device 150 receives from the client software 141a.
(GET
(USER hashimoto)
(URL http: //www.test.com/index.html)
(WORK patent)
(TIME 97/03/08 12:35)
)
Is received, the data is analyzed,
(1) GET request, that is, data relay request,
(2) The user who made the request is “hashimoto”.
(3) The requested URL is “http://www.test.com/index.html”;
(4) The job name at the time of request is “patent”,
(5) The time when the request is issued is “97/03/08 12:35”,
I understand.

The request analysis unit 151 inputs the request sent from the client software 141 a to the data request unit 152.
The data request unit 152 sends the URL “http://www.test.com/index.html” to the name analysis unit 153. The name analysis means 153 analyzes the sent URL and returns a server name “www.test.com”. The data requesting unit 152 requests data of the URL “http://www.test.com/index.html” from the WWW server 161 whose server name is “www.test.com”.

  The WWW server 161 determines whether or not to hold data corresponding to the URL “http://www.test.com/index.html”, and if so, the corresponding data “HTML document 1” is stored. Return to the data requesting means 152.

  The data requesting unit 152 includes a URL “http://www.test.com/index.html”, corresponding data “HTML document 1”, time “97/03/08 12:35”, and job name “patent”. Is input to the history management means 154.

The history management unit 154 associates the information input from the data request unit 152, stores it in the history holding unit 155, and inputs the data “HTML document 1” to the output unit 156.
When the data “HTML document 1” is input from the history management unit, the output unit 156 transmits the data to the client software 141a.

The client software 141 a displays the content of the data “HTML document 1” returned from the data relay device 150 in the window 206 of the browsing screen.
FIG. 16 is a diagram showing a browsing screen that displays the contents of “HTML document 1”. The difference from FIG. 15 is that “patent” is displayed in the text box 202 for inputting the work name, “http://www.test.com/index.html” is displayed in the text box 203 for inputting the URL, The content of the data “HTML document 1” is displayed in the window 206.

  Similarly, at the time “97/03/11 11:03”, the user with the user name “hashimoto” has the work name “patent” and the content of the URL “http://www.fujiyama.co.jp/index.html”. Is requested. Then, the URL “http://www.fujiyama.co.jp/index.html”, the data “HTML document 2” corresponding to the URL, and the time “97/03/11 11:03” ”, The user name“ hashimoto ”, and the work name“ patent ”are stored in association with each other.

  In addition, at the time “97/03/14 13:15”, the user with the user name “yamada” requested the content of the URL “http://www.test.com/index.html” with the work name “R & D”. And Then, the history holding means 155 has a URL “http://www.test.com/index.html”, data “HTML document 1” corresponding to the URL, time “97/03/14 13:15”, The user name “yamada” and the work name “R & D” are stored in association with each other.

Then, consider a case where the content of “HTML document 1” is changed to “HTML document 3” in WWW server 161 on “97/03/17”.
Assume that the user with the user name “hashimoto” requests the content of the URL “http://www.test.com/index.html” with the work name “patent” at the time “97/03/25 10:54”. . Then, the history holding means 155 has a URL “http://www.test.com/index.html”, data “HTML document 3” corresponding to the URL, time “97/03/25 10:54”, The user name “hashimoto” and the work name “patent” are stored in association with each other.

Further, since the content of the data has been changed, the content of the data “HTML document 3” is displayed on the browsing screen of the client software 141a.
FIG. 17 is a diagram showing a browsing screen that displays the contents of “HTML document 3”. The URL input in the URL input text box 203 on the browsing screen 200 is the same as in FIG. 16, but the time when the data acquisition request is output (the time when the button 204 is pressed) is different. In the example of FIG. 16, the time is “97/03/08 12:35”, and in the example of FIG. 17, the time is “97/03/25 10:54”. Since data is changed by the WWW server 161 during this period, the contents displayed in the window 206 are different.

  FIG. 18 is a diagram showing history information stored in the history holding means. In the history information 155a, “user name”, “URL”, “work name”, “time”, and “data” are stored in association with the data relayed by the data relay device 150.

Next, a case where data browsed in the past is displayed will be described.
First, the user presses a “history display” button 205 to search for data browsed in the past. When this button 205 is pressed, the client software 141a sends the data relay device 150
(SEARCH
(USER hashimoto)
(WORK patent)
)
Send a request. This request is for requesting the URL and time corresponding to the user name “hashimoto” and the work name “patent”.

  In this example, the history information is searched using the user name and the work name. However, the client software may request the entire history. Further, the time range may be limited to search within the range.

Upon receiving the request, the request analysis unit 151 analyzes it,
(1) SEARCH request, that is, a history information search request;
(2) The search user name is “hashimoto”,
(3) The job name to be searched is “patent”.
To extract.

  The request analysis unit 151 transfers this information to the history management unit 154. When the request is transferred from the request analysis unit 151, the history management unit 154 searches the information held by the history holding unit 155 for information with the user name “hashimoto” and the work name “patent”. To do.

The history management unit 154 inputs the searched information to the output unit 156, and the output unit 156 transfers the information to the client software 141a. At this time, for example, the following information is returned to the client software 141a.
((http://www.test.com/index.html,97/03/08/ 12:35))
(http://www.fujiyama.co.jp/index.html,97/03/11 17:03)
(http://www.test.com/index.html,97/03/25 10:54)
)
The client software 141a processes the information received from the data relay device 150 and displays it on the history display screen.

  FIG. 19 is a diagram showing a history display screen after receiving the detected information. This screen 210 has a URL display unit 211. Below that is a window 212 that displays the contents of the data. Below that, there are a user name display section 213 and a work name display section 214. Furthermore, there is a window 215 that displays data included in the history information in time series. At the position indicating each data, a white icon 215a. 215b and 215c are provided. Under each icon 215a, 215b, 215c, the time when the data was viewed is displayed.

  Here, it is assumed that the user selects the icon 215a at the time “97/03/08 12:35” in the window 215. Then, the selected icon 215a turns gray. Further, the URL “http://www.test.com/index.html” corresponding to “97/03/08 12:35” is displayed on the URL display unit 211, and “97/03/08 12:35” is displayed. The user name “hashimoto” corresponding to “” is displayed on the user name display unit 213, and the work name “patent” corresponding to “97/03/08 12:35” is displayed on the job name display unit 214.

Further, a data acquisition request corresponding to “97/03/08 12:35” is sent from the client software 141 a to the data relay device 150. For example, the following request is sent.
(GET-LOG
(USER hashimoto)
(URL http://www.test.com/index.html)
(WORK patent)
(TIME 97/03/08 12:35)
)
Upon receiving this data acquisition request, the request analysis unit 151 analyzes the request and recognizes that it is a history information acquisition request from “GET-LOG”. Then, information included in this request is sent to the history management unit 154. The history management unit 154 extracts the data “HTML document 1” that matches the content of the data acquisition request from the history holding unit 155 and sends it to the output unit 156. The output unit 156 transfers the data “HTML document 1” to the client software 141a.

The client software 141a displays the data returned from the data relay device 150 on the window 212.
FIG. 20 is a diagram showing a history display screen for displaying “HTML document 1”. The difference from FIG. 19 is that “http://www.test.com/index.html” is displayed in the URL display section 211, the contents of “HTML document 1” are displayed in the window 212, and the user name display section. “Hashimoto” is displayed in 213, “patent” is displayed in the work name display unit 214, and the icon 215 a is gray.

By this screen, the user can refer to the data of the content before the change.
When the user selects the icon 215c of the time “97/03/25 10:54” in the window 215, the selected icon 215c turns gray, and the URL display unit 211, the user name display unit 213, and the job name The display content of the display unit 214 also changes to the content corresponding to the time “97/03/25 10:54”. Then, a data acquisition request corresponding to “97/03/25 10:54” is sent from the client software 141 a to the data relay device 150. For example, the following request is sent.
(GET-LOG
(USER hashimoto)
(URL http://www.test.com/index.html)
(WORK patent)
(TIME 97/03/25 10:34)
)
The data relay apparatus 150 returns data “HTML document 3” that matches the request of the client software 141a to the client. The client software 141 a displays the sent data “HTML document 3” on the window 212.

  FIG. 21 is a diagram showing a history display screen for displaying “HTML document 3”. The difference from FIG. 20 is that the content of “HTML document 3” is displayed in the window 212, and the icon 215c is gray instead of the icon 215a.

  As described above, history information can be acquired on the client software side, and past data can be browsed based on the information. Thus, by acquiring history information from the data relay device 150, even if the user has not accurately remembered the time when the target data was browsed in the past, the data can be easily browsed. In addition, since history information is narrowed down by user name or work name, a large amount of unnecessary history is not displayed in the window 215 of the history display screen.

  In the above description, the history information is acquired by specifying the user name and the work name. However, all the history information may be acquired from the data relay apparatus 150 without being limited to these. In addition, it is possible to acquire all the histories that match the user name without specifying the work name. Furthermore, when other context information such as a host name is held as history information, the history information according to the purpose can be acquired by specifying the context information.

Next, a data relay apparatus for changing data held by a server from client software will be described as a fifth example.
In the fifth example of the network system, a client connected to the network designates a data name and outputs data to a server connected to the network. At that time, the data is output through the data relay means. Further, the client software acquires the data output in the past by designating the past time and the name of the data and making a request to the data relay apparatus.

  FIG. 22 is a block diagram illustrating a fifth example of the network system. In this figure, the host 310 is connected to the data relay device 320 via the network 301. The data relay device 320 is connected to a server 331 that holds data 332 via the network 302.

The host 310 has client software 311 that outputs data to the server 331.
The data relay device 320 includes request analysis means 321, data output means 322, name analysis means 323, history management means 324, history holding means 325, and output means 326. Each component other than the data output means 322 basically has the same function as the element of the same name shown in FIG. The data output unit 322 outputs a data output request output from the client software 311 to the server 311.

  In the system having such a configuration, the user first uses the client software 311 to transmit a data output request including the name and data to the data relay device 320 in order to output data corresponding to the name. This data output request, for example, transmits a user name, data name, data content, etc., following the command “PUT”.

  In the data relay device 320, the request analysis unit 321 receives a request from the client software 311. When the request analysis unit 321 analyzes the request and recognizes that it is a data output request, it extracts the name and data. When the name and data are obtained as the analysis result of the request sent by the client software 311, the request analysis unit 321 inputs the name and data to the data output unit 322 and also to the history management unit 324. Enter name and data.

  When a name and data are input from the request analysis unit 321, the history management unit 324 holds and manages the name, data, and time at that time in the history holding unit 325. The history management unit 324 searches for a name held by the history holding unit 325 when the name and data are input from the request analysis unit 321, and the history holding unit 325 is the same as the name input from the request analysis unit 321. When the name is held, the data associated with the name is compared with the data input from the request analysis unit 321, and the name, data, and time are held in the history holding unit 325 only when they are different. You may make it do.

  When the name and data are input from the request analysis unit 321, the data output unit 322 inputs the name to the name analysis unit 323. The name analysis unit 323 analyzes the name input from the data output unit 322, and passes the identifier of the server that should output the data corresponding to the name. The data output unit 322 transmits the name and data to the server 331 corresponding to the identifier returned from the name analysis unit 323.

  When the server 331 receives the name and data from the data output means 322, the server 331 holds and manages the name and data. As a result, the data output by the client software 311 is held and managed in the server 331, and time information is added to the data and held by the history holding unit 325.

Next, a case where the client software 311 requests data corresponding to a name output at a certain time will be described.
The client software 311 transmits a data request including the name and time to the data relay device 320 in order to acquire data corresponding to the name output at a certain time.

In the data relay device 320, the request analysis unit 321 receives a request from the client software 311.
The request analysis unit 321 analyzes the request and extracts the name and time. When the result obtained as the analysis result of the request sent by the client software 311 is the name and time, the request analysis unit 321 inputs the name and time to the history management unit 324.

  When the name and time are input from the request analysis unit 321, the history management unit 324 checks whether the history storage unit 325 stores data corresponding to the name / time pair. If it is held, the data is input to the output means 326. If not held, “not found” is input to the output means 326. The output unit 326 transmits data to the client software 311.

In this way, the client software 311 can acquire data output at a certain time.
Also, a system as shown in FIG. 22 can be applied to the WWW. That is, client software that is a WWW browser can store an HTML document on a WWW server existing on the Internet via the data relay apparatus according to the present invention, and browse the document later.

  Further, a system for storing history information when referring to server data from client software (the system shown in FIG. 11), and a system for storing history information when data output by client software is stored in the server (FIG. 22). It is also possible to construct a system having both of the functions shown in FIG. In that case, the data relay device includes both the data requesting means 122 (shown in FIG. 11) and the data output means 322 (shown in FIG. 22). In addition to the items shown in FIG. 18, the history information held by the history holding means indicates whether the processing when the data is stored is the reference of data in the server or the storage of data in the server. Provide a flag to distinguish. By providing the flag, when the client software acquires the history information from the data relay device, it is possible to narrow down the history information depending on whether the data has been referred to in the past or stored in the past.

Next, a system in which workspace technology is applied to the third example of the network system shown in FIG. 11 will be described as an embodiment of the present invention.
The embodiment of the present invention described below is an information terminal device having a workspace for storing and reproducing a past state, and selecting an icon on the workspace to display information related to the icon. In an information terminal device having a workspace to be displayed, when an icon on a past workspace is selected, past information browsed on the workspace is displayed again.

  FIG. 23 is a block diagram showing a configuration of the embodiment of the present invention. In this figure, a host 410 is connected to a data relay device 420 and a work space control device 430 via a network 401. The data relay device 420 is connected to a server 441 that holds data 442 via the network 402.

The host 410 has client software 411 that refers to data 442 held by the server 441 using a work space.
The data relay device 420 includes request analysis means 421, data request means 422, name analysis means 423, history management means 424, history holding means 425, and output means 426. Each component basically has the same function as the element of the same name shown in FIG.

  The workspace control device 430 includes a workspace management unit 431, a user management unit 432, a snap management unit 433, a link information management unit 434, and an icon management unit 435. Each component has the following functions.

  The workspace management unit 431 receives a request from the client software 411, holds the workspace information, and makes an inquiry to other user management unit 432, snap management unit 433, link information management unit 434, and icon management unit 435. In response to the request from the client software 411.

  FIG. 24 is a diagram showing an example of a management table held by the work space management means. In the figure, “WS_ID” in the management table 431a is an identifier for identifying a work space. “WS_title” represents a title assigned to the workspace.

  The user management unit 432 holds a user identifier (ID), a user name, a password, and a user home workspace in association with each other. A home workspace represents a workspace that the user is currently using.

  FIG. 25 is a diagram illustrating an example of a management table held by the user management unit. In the figure, “user_ID” in the management table 432a represents a user identifier, “user_name” represents a user name, “passwd” represents a password, and “home_WS_ID” represents a user home workspace identifier.

The snap management means 433 manages the state of the past work space as a snap.
FIG. 26 shows an example of a management table held by the snap management means. In the figure, “snap_ID” in the management table 433a is an identifier for identifying the state of the saved past workspace, “create_date” is the date and time when the snap was created, “WS_ID” is an identifier for identifying the workspace, and “link_ID” Represents an identifier for identifying link information included in the snap, and “operation” represents a user operation that triggered the creation of the snap.

The link information management means 434 holds the title assigned to the information by the user, the URL indicating the name of the information, and the memo attached to the information by the user in association with each other.
FIG. 27 is a diagram illustrating an example of a management table held by the link information management unit. In the figure, “link_ID” in the management table 434a is an identifier for identifying link information, “link_TITLE” is a title given to the information by the user, “URL” is a URL indicating the name of the information, and “MEMO” is information by the user. Represents a memo attached to.

  The icon management unit 435 associates and holds the identifier of the snap associated with the icon, the identifier of the link information, and the x and y coordinates at which the icon is displayed on the workspace.

  FIG. 28 is a diagram showing an example of a management table held by the icon management means. In the figure, “SANAP_ID” of the management table 435a represents an identifier for identifying a snap, “link_ID” represents an identifier for identifying link information, and “x” and “y” represent an x coordinate and a y coordinate, respectively.

In the system configured as described above, the user performs the following operations.
First, a procedure for displaying a workspace on the client software 411 will be described. The user first logs into the system on the client software 411. FIG. 29 is a diagram showing a login screen 510. The login screen 510 displays a text box 511 for entering a user name and a text box 512 for entering a password. The user inputs the user name and password in the text boxes 511 and 512 of the login screen 510. Here, it is assumed that “hashimoto” is input as the user name and “hogehoge” is input as the password.

The client software 411 transmits the input user name and password to the work space management means 431.
The workspace management unit 431 receives and analyzes a request from the client software 411. Since this request is a log-in request, the user management unit 432 is inquired about the transmitted user name and password.

The user management unit 432 refers to the stored management table 432a (shown in FIG. 25) and checks whether the correspondence between the user name and the password is correct. Here, the correspondence between the username and password is correct,
(home_ws_id = 2)
Is returned to the work space management means 431.

If the correspondence between the user name and the password is not correct, a message to that effect is returned to the work space management means 431.
The workspace management unit 431 has information that the correspondence between the user name and the password is correct,
(home_ws_id = 2)
Is returned to the client software 411.

  If the correspondence between the user name and the password is not correct, the client software 411 displays that fact and displays the login screen 510 (shown in FIG. 29) again to prompt the user to enter the user name and password. If the correspondence between the user name and the password is correct, the workspace management unit 431 is requested for a list of workspaces.

The workspace management means 431 searches the held management table 431a (shown in FIG. 24) and returns a list of workspaces to the client software. Here, since three workspaces of “patent”, “accounting”, and “development” are managed, the workspace management means 431
((ws_id = 1, ws_title = patent)
(ws_id = 2, ws_title = Accounting)
(ws_id = 3, ws_title = development)
)
Is returned to the client software 411. 1 to 3 represent identifiers for identifying the respective workspaces.

The client software 411 displays the received workspace information on the screen.
FIG. 30 is a diagram showing a screen of workspace information. The workspace information screen 520 includes a user name display unit 521, which displays “hashimoto” in this example. Below that is a workspace display window 522. In window 522, a list of workspace names is displayed. In this example, a “patent” workspace name 522a, an “accounting” workspace name 522b, and a “development” workspace name 522c are displayed. To the right of the user name display section 521 are search period input fields 523 and 524 for “from” and “to”. The search period input field 523 for “from” is an input field for the start date / time of the search target period, and the search period input field 524 for “to” is an input field for the end date / time of the search target period. To the right of the search period input fields 523 and 524 is a “history display” button 525. When this button 525 is pressed, history display is performed. The history is displayed in a history display window 526.

After displaying the workspace information screen 520, the client software 411 asks the workspace management unit 431 to inquire about the home workspace of the user “hashimoto”.
(home_ws_id = 2)
Send.

The workspace management unit 431 inquires of the snap management unit 433 about the snap identifier corresponding to the workspace identifier “2”.
The snap management unit 433 searches the held management table 433a (shown in FIG. 26),
(snap_id = 2, create_date = "96/07/10 15:22", ws_id = 2, link_id = 4, operation = "print")
return it.

The workspace management unit 431 inquires of the icon management unit 435 about the link identifier corresponding to the snap identifier “2”.
The icon management means 435 searches the held management table 435a (shown in FIG. 28), and
(
(link_id = 2, x = 45, y = 89)
(link_id = 3, x = 42, y = 105)
)
return it.

The workspace management unit 431 inquires of the link information management unit 434 about the information having the link identifiers “2” and “3”.
The link information management means 434 searches the held management table 434a (shown in FIG. 27), and
(
(link_id = 2, link_title = "accounting procedure", url = http: //www.keiri/tejyunnsho.htm, memo = "urgent")
(link_id = 3, link_title = "97 department budget proposal", url = http: //www.keiri/xxdepbudget-97.htm, memo = "reference material")
)
return it.

The workspace management means 431 provides the client software 411 with
(
(snap_id = 2, create_date = "96/07/10 15:22", ws_id = 2, link_id = 4, operation = "print")
((link_id = 2, x = 45, y = 89) (link_id = 3, x = 42, y = 105))
((link_id = 2, link_title = "accounting procedure", url = http: //www.keiri/tejyunnsho.htm, memo = "urgent")
(link_id = 3, link_title = "97 department budget proposal", url = http: //www.keiri/xxdepbudget-97.htm, memo = "reference material"))
)
Is returned.

The client software 411 displays the workspace in the window 526 based on the sent information.
FIG. 31 is a diagram showing a screen of the home work space. In this example, since the home workspace identifier is “2”, the corresponding “accounting” workspace name 522b on the window 522 is displayed in bold. In the window 526, an icon 526a indicating "accounting procedure" and an icon 526b indicating "1997 department budget plan" are displayed.

  Here, an example in which the user's home workspace is displayed first has been described, but when one of the workspaces is selected in the window 522, the workspace may be displayed in the window 526.

Next, an example will be described in which the state of the workspace is saved as a snap when browsing information associated with an icon on the workspace.
First, assume that the user is working on a “patent” workspace. FIG. 32 is a diagram showing a display screen of the “patent” workspace. In this figure, the workspace name 522a of “patent” is displayed with a bold line. In the window 526, an icon 526c indicating "Publication Gazette" is displayed. The identifier of the “patent” workspace is “1”. And the client software 411
(
(user_id = 2)
(snap_id = 1, create_date = "96/06/05 13:10", ws_id = 1, link_id = 1, operation = "view")
((link_id = 1, x = 50, y = 100)),
((link_id = 1, link_title = "Public Publication", url = http: //www.pat.ccc/pat? id = h08368297, memo = "Important"))
)
Is held.

  Here, it is assumed that the user double-clicks the “publication publication” icon 526c to display information associated with the icon. The time at this time is “96/07/25 10:09”. Then, the client software 411 transmits the URL “http: //www.pat.ccc/pat? Id = h08368297” and the time “96/07/25 10:09” to the data relay device 420, and the URL Request data corresponding to.

For example, the client software 411 provides the data relay device 420 with
(GET
(user hashimoto)
(url http: //www.pat.ccc/pat? id = h08368297)
(work "patent")
(time 96/07/25 10:09)
)
Send the information.

  The data relay device 420 downloads data corresponding to the URL “http: //www.pat.ccc/pat? Id = H08368297”, the URL, the downloaded data, and the time “96/07/25 10 : 09 ”is stored in the history storage unit 425 in association with each other. An example of information held by the history holding unit 425 at this time is shown below.

  FIG. 33 is a diagram illustrating an example of a management table held by the history holding unit. In this example, in the management table 425a held by the history holding unit 425, a history of browsing the “HTML document 4” and the “HTML document 5” by the user with the user name “hashimoto” is held. Note that “HTML document 4” and “HTML document 5” have the same URL.

  The data relay apparatus 420 returns the downloaded data to the client software 411. The client software 411 displays the data returned from the data relay device 420 on the screen.

  FIG. 34 is a diagram showing a client screen browsing the “HTML document 5”. The data returned from the data relay device 420 when the “publication publication” icon 526 c in the workspace information screen 520 is clicked is displayed on the document browsing screen 530. This screen 530 includes a URL display unit 531 that displays the URL of the data being browsed, and a window 532 that displays the contents of the document.

  When the information browsing operation is set as an opportunity to save the workspace state, the client software 411 stores the workspace state at this time in the workspace management unit 431.

The client software 411 gives the work space management means 431
(
(CREATE_DATE = "96/07/25 10:09", WS_ID = 1, LINK_ID = 1, OPERATION = "view")
((LINK_ID = 1, X = 50, Y = 100)),
((LINK_ID = 1, LINK_TITLE = "Public Publication", URL = http: //www.pat.ccc/pat? Id = H08368297, MEMO = "Important"))
)
And send a request to save the workspace.

  The work space management unit 431 transfers the information sent from the client software 411 to the snap management unit 433. The snap management unit 433 generates a new snap identifier (here, “4”) and stores it in the management table 433a (shown in FIG. 26). The management table 433a illustrated in FIG. 26 is in a state after storing the information of the snap identifier “4”.

The workspace management means 431 provides the client software 411 with
(
(SNAP_ID = 4, CREATE_DATE = "96/07/25 10:09", WS_ID = 1, LINK_ID = 1, OPERATION = "view")
((LINK_ID = 1, X = 50, Y = 100))
((LINK_ID = 1, LINK_TITLE = "Public Publication", URL = http: //www.pat.ccc/pat? Id = H08368297, MEMO = "Important"))
)
Is returned.

With this procedure, the state of the workspace when browsing the information associated with the icon on the workspace is stored in the snap management means 433.
Next, an example of searching for past workspace states will be described.

Assume that the user is working in the workspace shown in FIG. Assume that this screen 520 is in a state after browsing information associated with the icon 526c “Publication Publication” on “96/07/25 10:09”. The identifier of this workspace is “1”, and the snap identifier is “4”. The client software 411
(
(USER_ID = 2)
(SNAP_ID = 4, CREATE_DATE = "96/07/25 10:09", WS_ID = 1, LINK_ID = 1, OPERATION = "view")
((LINK_ID = 1, X = 50, Y = 100))
((LINK_ID = 1, LINK_TITLE = "Public Publication", URL = http: //www.pat.ccc/pat? Id = H08368297, MEMO = "Important"))
)
Is held.

  Here, in order to search for a past workspace, the user inputs a search period in the “from:” and “to:” fields 523 and 524 and clicks a “history display” button 525. When the “history display” button 525 is clicked, the client software 411 indicates to the workspace management unit 431 the past workspace state within the specified period corresponding to the workspace identifier “1”. Request a list of

The workspace management unit 431 inquires of the snap management unit 433 about the snap corresponding to the work space identifier “1” within the specified period. The snap management means 433 refers to the held management table 433a (shown in FIG. 26),
(
(SNAP_ID = 1, CREATE_DATE = "96/06/05 13:10", WS_ID = 1, LINK_ID = 1, OPERATION = "view")
(SNAP_ID = 4, CREATE_DATE = "96/07/25 10:09", WS_ID = 1, LINK_ID = 1, OPERATION = "view")
)
Is returned to the work space management means 431. The workspace management unit 431 transfers the information returned from the snap management unit 433 to the client software 411.

The client software 411 performs history display based on the information returned from the work space management means 431.
FIG. 35 is a diagram illustrating an example of a history display screen. The history display screen 540 includes a time display unit 541 that displays the time associated with the specified history information. Below that, a window 542 for reproducing the state of the past workspace is provided. Further below that, a window 543 for displaying history information in time series is provided. This window 543 displays the time when the workspace snap was created on the time axis. Here, icons 543a and 543b indicating that a snap has been created are displayed at the times “96/06/05 13:10” and “96/07/25 10:09”. The user can display the state of the workspace at that time in the window 542 by selecting one of the two icons 543a and 543b.

Now, assume that the user clicks on the icon 543a corresponding to “96/06/05 13:10”.
The client software 411 searches the workspace management means 431 for the snap created at “96/06/05 13:10”.
(SNAP_ID = 1, CREATE_DATE = "96/06/05 13:10", WS_ID = 1, LINK_ID = 1, OPERATION = "view")
And send a snap request.

The workspace management unit 431 requests the icon management unit 435 for icon information corresponding to the snap identifier “1”.
Icon management means 435
((LINK_ID = 1, X = 50, Y = 100))
Is returned to the work space management means 431.

The work space management unit 431 requests the link information management unit 434 for link information corresponding to the link identifier “1”.
The link information management means 434
((LINK_ID = 1, LINK_TITLE = "Public Publication", URL = http: //www.pat.ccc/pat? Id = H08368297, MEMO = "Important"))
Is returned to the work space management means 431.

The workspace management means 431
(
(SNAP_ID = 1, CREATE_DATE = "96/06/05 13:10", WS_ID = 1, LINK_ID = 1, OPERATION = "view")
((LINK_ID = 1, X = 50, Y = 100))
((LINK_ID = 1, LINK_TITLE = "Public Publication", URL = http: //www.pat.ccc/pat? Id = H08368297, MEMO = "Important"))
)
Is returned to the client software 411.

Based on this information, the client software 411 reproduces the past workspace state in the window 542 of FIG.
FIG. 36 is a diagram showing a screen in which a past (96/06/05 13:10) workspace is reproduced. In this history display screen 540, an icon 543a corresponding to “96/06/05 13:10” is displayed in gray to indicate that the icon corresponding to “96/06/05 13:10” has been selected. ing. The time display unit 541 displays the time corresponding to the selected icon 543a. In the window 542, the work space at the time of “96/06/05 13:10” is displayed, and in this example, an icon “542a” of “Publication Publication” is displayed.

Similarly, clicking the icon corresponding to “96/07/25 10:09” displays the workspace at that time.
FIG. 37 is a diagram showing a screen in which a past (96/07/25 10:09) workspace is reproduced. In the history display screen 540, an icon 543b corresponding to “96/07/25 10:09” is displayed in gray, and a time corresponding to the selected icon 543b is displayed in the time display unit 541. In the window 542, the workspace at the time of “96/07/25 10:09” is displayed, and in this example, an icon “542b” of “publication publication” is displayed.

Next, an example of re-browsing information browsed in the past by searching past workspace states and browsing icons on the past workspaces will be described.
In FIG. 37, the “publication publication” icon 542a is displayed in gray. This indicates that the snap was saved because this icon was viewed. When multiple icons exist on the workspace, only one icon is displayed in gray. Therefore, the user double-clicks this icon 542a to re-view this information.

When the gray icon 542a is double-clicked, the client software 411 requests the data relay apparatus 420 to request the name of information associated with the icon, the time when the snap was created, and the data corresponding to the name. Send. For example, the following information is transmitted.
(GET-LOG
(USER hashimoto)
(URL http: //www.pat.ccc/pat? Id = H08368297)
(WORK patent)
(TIME 96/06/05 13:10)
)
The data relay device 420 searches the history held by the history holding unit 425 in the same manner as in the fourth example of the network system, and returns data “HTML document 4” to the client software 411. Here, it is assumed that the history holding unit 425 holds the information shown in FIG.

The client software 411 displays the data “HTML document 4” returned from the data relay device 420.
FIG. 38 is a diagram showing a screen for re-browsing “HTML document 4”. When the icon 542a is double-clicked, the browsing display screen 550 is newly displayed. The browsing display screen 550 is provided with a URL display unit 551 and a window 552 for displaying the contents of the document. The window 552 displays the content of “HTML document 4”.

Similarly, in the past workspace shown in FIG. 37, when the “publication publication” icon 542b is double-clicked, the client software 411 transfers the data to the data relay device 420.
(GET-LOG
(USER hashimoto)
(URL http: //www.pat.ccc/pat? Id = H08368297)
(WORK patent)
(TIME 96/07/25 10:09)
)
The data request and the data request are transmitted, and the data “HTML document 5” is returned from the data relay apparatus 420 to the client software 411.

  The client software 411 displays the data “HTML document 5” returned from the data relay device 420. FIG. 39 is a diagram showing a screen for re-browsing “HTML document 5”. The browsing display screen 560 is provided with a URL display unit 561 and a window 562 for displaying the contents of the document. The window 562 displays the contents of “HTML document 5”.

  FIG. 38 and FIG. 39 differ in the portion of the examination request. The contents displayed in FIG. 38 and FIG. 39 are different between the time “96/06/05 13:10” and the time “96/07/25 10:09”, the server “www.pat.ccc”. This is because the data corresponding to the URL “http: //www.pat.ccc/pat? Id = H08368297” has been updated.

  In this way, it becomes possible to reproduce past workspaces and re-view information browsed in the past. In addition, when a past workspace is reproduced, it is displayed with the same name as when it was referred to in the past, so the relationship between the document before and after the change does not become unclear.

It is a figure which shows the function of a data relay apparatus. It is a block diagram which shows the 1st example of a network system. It is a flowchart which shows the procedure of the data relay of a data relay apparatus. It is a figure which shows an example of the client software screen which browses data with a history. FIG. 5 is a diagram showing a screen in which “data B” is called from the client software screen shown in FIG. 4. It is a figure which shows the screen which called "data C" from the client software screen shown in FIG. It is a figure which shows another example of the client software screen which browses data with a history. It is a block diagram which shows the 2nd example of a network system. It is a flowchart which shows the procedure of the data relay of a data relay apparatus. It is a figure which shows an example of a log | history unnecessary condition. It is a block diagram which shows the 3rd example of a network system. It is a figure which shows the example of the data table which a server hold | maintains. It is a figure showing the example of the table which a log | history holding means hold | maintains. It is a block diagram which shows the 4th example of a network system. It is a figure which shows the screen for browsing. It is a figure which shows the screen for browsing which displays the content of "HTML document 1". It is a figure which shows the screen for browsing which displays the content of "HTML document 3". It is a figure which shows the log | history information stored in the log | history holding means. It is a figure which shows the screen for log | history display after receiving the detected information. It is a figure which shows the screen for log | history display which displays "HTML document 1". It is a figure which shows the screen for log | history display which displays "HTML document 3". It is a block diagram which shows the 5th example of a network system. It is a block diagram which shows the structure of embodiment of this invention. It is a figure which shows the example of the management table which a workspace management means hold | maintains. It is a figure which shows the example of the management table which a user management means hold | maintains. It is a figure which shows the example of the management table which a snap management means hold | maintains. It is a figure which shows the example of the management table which a link information management means hold | maintains. It is a figure which shows the example of the management table which an icon management means hold | maintains. It is a figure which shows a login screen. It is a figure which shows the screen of workspace information. It is a figure which shows the screen of a home workspace. It is a figure which shows the display screen of the workspace of a "patent". It is a figure which shows the example of the management table which a log | history holding means hold | maintains. It is a figure which shows the client screen which is browsing "HTML document 5". It is a figure which shows the example of a log | history display screen. It is a figure which shows the screen which reproduced the past (96/06/05 13:10) workspace. It is a figure which shows the screen which reproduced the past (96/07/25 10:09) workspace. It is a figure which shows the screen which re-browses "HTML document 4". It is a figure which shows the screen which re-browses "HTML document 5". It is a figure explaining the operating environment of the conventional proxy server. It is a figure explaining operation | movement of the conventional proxy server.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Information terminal device 2 Data relay apparatus 2a History information holding means 2b Data acquisition means 2c Data output means 3 Network 4 Server 4a Data

Claims (4)

Data is relayed to and from the server, and the relayed data, data name, and time information are retained and managed as history information. Applicable according to the data acquisition request that includes the data name and time information In a data access system that accesses data on the server connected via a network via a data relay device that sends back data included in the history information.
  When receiving a workspace saving request including the workspace indicating the work state and the time information from the information terminal device, a storage unit that stores the workspace in association with the time information;
  In response to a search request specifying a search target workspace and a period from the information terminal device, the search target workspace stored within the specified period is searched from the storage unit, and a search result is stored as the information. Search means for transmitting to the terminal device;
  A workspace control device comprising:
  Each time data is acquired via the data relay device in response to an operation input for selecting an icon on the working workspace, the working workspace and data acquisition time are obtained from the workspace control device. Save request means for sending a save request for the workspace including time information indicating
  Upon receiving a specification of a period for searching the past workspace related to the selected workspace, the workspace control device issues a search request including the specified period and using the selected workspace as the search target workspace. Search request means to send to
  History display means for displaying an icon representing the workspace searched by the workspace control device on the time axis;
  Reproduction means for reproducing the workspace corresponding to the icon representing the workspace designated by the user;
  Accept selection of icon on reproduced workspace and request acquisition of history information including name of data associated with selected icon and time information associated with workspace Request means for transmitting the data acquisition request to the data relay device;
  Data receiving means for receiving data sent from the data relay device in response to the data acquisition request;
  Data display means for displaying the received data;
  The information terminal device comprising:
  A data access system comprising: In a data access system for accessing data on a server connected via a network,
  History holding means for holding history information of relayed data;
  Upon receiving a data acquisition request from the information terminal device, the request analysis means for analyzing whether the data relay request or the history information acquisition request, and extracting the data name and time information from the data acquisition request;
  If the data acquisition request is a data relay request, the server requests data corresponding to the data name extracted by the request analysis unit, and receives data sent from the server in response to the request Request means;
  When the data acquisition request is a data relay request, the history holding means is used as the history information by associating the data received by the data request means with the name and time information of the data extracted by the request analysis means. And when the data acquisition request is an acquisition request for the history information, it matches the name and time information of the data extracted by the request analysis means. The history information is retrieved from the history holding means, and the history management means uses the data included in the detected history information as output data;
  Output means for outputting the data that the history management means uses as output data to the information terminal device that is the output source of the data acquisition request;
  A data relay device comprising:
  When receiving a workspace saving request including the workspace indicating the work state and the time information from the information terminal device, a storage unit that stores the workspace in association with the time information;
  In response to a search request specifying a search target workspace and a period from the information terminal device, the search target workspace stored within the specified period is searched from the storage unit, and a search result is stored as the information. Search means for transmitting to the terminal device;
  A workspace control device comprising:
  The data on the server corresponding to the icon is acquired via the data relay device in response to an operation input for selecting an icon on the working workspace, and each time data is acquired from the server, the work Save request means for sending a save request for a workspace including the working workspace and time information indicating the data acquisition time to the space control device;
  Upon receiving a specification of a period for searching the past workspace related to the selected workspace, the workspace control device issues a search request including the specified period and using the selected workspace as the search target workspace. Search request means to send to
  History display means for displaying an icon representing the workspace searched by the workspace control device on the time axis;
  Reproduction means for reproducing the workspace corresponding to the icon representing the workspace designated by the user;
  Accept selection of icon on reproduced workspace and request acquisition of history information including name of data associated with selected icon and time information associated with workspace Request means for transmitting the data acquisition request to the data relay device;
  Data receiving means for receiving data sent from the data relay device in response to the data acquisition request;
  Data display means for displaying the received data;
  The information terminal device comprising:
  A data access system comprising: Data is relayed to and from the server, and the relayed data, data name, and time information are retained and managed as history information. Applicable according to the data acquisition request that includes the data name and time information In a data access method for accessing data on the server connected via a network via a data relay device that sends back data included in the history information.
  Each time the storage request means of the information terminal device acquires data via the data relay device in response to an operation input for selecting an icon on the work space being worked on, the work request is made to the work space control device. Send a workspace save request containing the current workspace and time information indicating the data acquisition time,
  When the storage unit of the workspace control device receives a workspace save request including the workspace indicating the work state and time information from the information terminal device, the workspace is stored in association with the time information,
  When the search request means of the information terminal device receives a specification of a period for searching the past workspace related to the selected workspace, the selected workspace includes the specified period and the selected workspace is a search target workspace. The search request is sent to the workspace control device,
  In response to the search request specifying the search target workspace and the period from the information terminal device, the search unit of the workspace control device selects the search target workspace stored within the specified period. Search from the storage means, send the search results to the information terminal device,
  The history display means of the information terminal device displays an icon representing the work space searched by the work space control device on the time axis,
  The reproduction means of the information terminal device reproduces the workspace corresponding to the icon representing the workspace designated by the user,
  The request means of the information terminal device accepts the selection of the icon on the reproduced workspace, and includes the name of the data associated with the selected icon and the time information associated with the workspace , Sending the data acquisition request to request acquisition of the history information to the data relay device,
  The data reception means of the information terminal device receives data sent from the data relay device in response to the data acquisition request,
  The data display means of the information terminal device displays the received data;
  A data access method. In a data access method for accessing data on a server connected via a network,
  In response to an operation input for selecting an icon on the working workspace, the storage request unit of the information terminal device transmits a data acquisition request, which is a data relay request on the server corresponding to the icon, to the data relay device And
  When the request analysis means of the data relay device receives the data acquisition request from the information terminal device, it analyzes whether it is a data relay request or a history information acquisition request, and the data name and time information from the data acquisition request Extract
  If the data acquisition request is a data relay request, the data requesting means of the data relay device requests the data corresponding to the name of the data extracted by the request analysis means to the server, and in response to the request, the data Receives data sent from the server,
  When the data acquisition request is a data relay request, the history management unit of the data relay device associates the data received by the data request unit with the name and time information of the data extracted by the request analysis unit. In addition to storing the history information in the history holding means, the data received by the data request means as output data,
  The output means of the data relay device outputs data as output data to the information terminal device that is the output source of the data acquisition request,
  The data receiving means of the information terminal device receives data sent from the data relay device,
  The data display means of the information terminal device displays the received data,
  The storage request means of the information terminal device transmits a workspace storage request including the workspace during the work and time information indicating the data acquisition time to the workspace control device,
  When the storage unit of the workspace control device receives the storage request for the workspace from the information terminal device, the workspace is stored in association with the time information,
  When the search request means of the information terminal device receives a specification of a period for searching for the past workspace related to the selected workspace, the selected workspace includes the specified period, and the selected workspace is set as a search target workspace. The search request is sent to the workspace control device,
  In response to the search request specifying the search target workspace and the period from the information terminal device, the search unit of the workspace control device selects the search target workspace stored within the specified period. Search from the storage means, send the search results to the information terminal device,
  The history display means of the information terminal device displays an icon representing the work space searched by the work space control device on the time axis,
  The reproduction means of the information terminal device reproduces the workspace corresponding to the icon representing the workspace designated by the user,
  The request means of the information terminal device accepts the selection of the icon on the reproduced workspace, and includes the name of the data associated with the selected icon and the time information associated with the workspace , Sending the data acquisition request to request acquisition of the history information to the data relay device,
  When the request analysis means of the data relay device receives a data acquisition request from the information terminal device, it analyzes whether it is a data relay request or the history information acquisition request, and from the data acquisition request the data name and time information And extract
  When the data acquisition request is the history information acquisition request, the history management unit of the data relay device holds the history information that matches the data name and time information extracted by the request analysis unit. Search from the means, the data included in the detected history information as output data,
  The output means of the data relay device outputs data as output data to the information terminal device that is the output source of the data acquisition request,
  The data receiving means of the information terminal device receives data sent from the data relay device,
  The data display means of the information terminal device displays the received data;
  A data access method.

Images