JP2020087264A - Time stamp storage proxy system, proxy system management program, and proxy system use program - Google Patents

Abstract

To easily and properly perform depositing and payment of time stamp tokens of a storage object file relative to a time stamp storage organization.SOLUTION: A time stamp storage proxy system 1 includes: a user terminal 7 which requests depositing or payment of a TST file 73 consisting of a TST 72 added to a storage object file 70; a TST storage server 5 which carries out the depositing or payment of the TST file 73 in accordance with the request for depositing or payment; and a storage proxy device 6 which is communicably connected to the user terminal 7 and the TST storage server 5 through a network 8. When receiving the TST file 73 and a proxy request for depositing, from the user terminal 7, the storage proxy device 6 performs by proxy depositing of the TST file 73 relative to the TST storage server 5, and further, when receiving payment identification information of the TST file 73 and a proxy request for payment, from the user terminal 7, the storage proxy device performs by proxy payment of the TST file 73 from the TST storage server 5 on the basis of the payment identification information.SELECTED DRAWING: Figure 2

Description

The present invention relates to a time stamp storage proxy system, a proxy system management program, and a proxy system utilization program for proxying storage processes such as depositing and withdrawing time stamp token files.

For example, for files to be managed for electronic data such as documents, images, videos, and sounds, a time stamp (time stamp token) is issued by a time stamp authority (time certification authority), and the file to be managed is verified using the time stamp token. Time authentication technology has become popular. Further, a time stamp storage service in which time stamp tokens are stored in a time stamp storage organization (INPIT) has also become popular.

For example, Patent Document 1 below describes a technique of storing a hash value generated from an electronic file to be managed in a storage server operated by a public institution.

JP, 2016-218554, A

By the way, the user needs to identify the electronic file corresponding to the time stamp token that needs to be deposited in order to deposit the time stamp token in the time stamp storage organization. Therefore, the user identifies and manages the electronic files that are subject to the time stamp management among the electronic files that he/she owns, but the electronic file to which the time stamp token is issued and the time stamp token is not issued. It is necessary to identify and manage electronic files. However, it is difficult and burdensome for the user to perform the identification and management as described above for a large number of electronic files. As described above, it is difficult to deposit the time stamp token of the electronic file in the time stamp storage institution easily and appropriately.

Further, the user's terminal device stores the electronic file that is the subject of time stamp management, while the time stamp token is issued from the time certification authority independently of the electronic file. If the electronic file and the time stamp token are stored independently, it becomes difficult to manage them while associating them with each other.

Further, it is necessary to obtain the one-time password issued from the time stamp storage service every time storage processing such as depositing and withdrawing time stamp tokens is performed in the time stamp storage service. Therefore, it may not be possible to smoothly deposit and withdraw the time stamp token, which makes the use of the time stamp storage service troublesome and troublesome.

The present invention has been made in view of the problems as described above, for example, and an object of the present invention is to easily and appropriately deposit and withdraw a time stamp token added to a managed file to a time stamp storage organization. The purpose is to provide a time stamp storage agent system, an agent system management program, and an agent system utilization program for performing.

In order to solve the above problems, the first time stamp storage agent system of the present invention requests deposit or withdrawal of a time stamp token file including a time stamp token added to a management target file that is a time stamp management target. And a time stamp token storage server that performs the deposit or withdrawal of the time stamp token file in response to the deposit or withdrawal request from the user terminal. And a storage agent device communicatively connected to the user terminal and the time stamp token storage server via a predetermined network, the storage agent device including the time stamp token file from the user terminal. When the proxy request for deposit is received together with, the deposit of the time stamp token file is delegated to the time stamp token storage server, and the payout identification information of the time stamp token file is sent from the user terminal. When the payout proxy request is received, the payout from the time stamp token storage server of the time stamp token file based on the payout identification information is proxyed.

In order to solve the above problems, the first program of the present invention uses a request to deposit or withdraw a time stamp token file including a time stamp token added to a management target file that is a time stamp management target. System in a proxy system for storing time stamps, which includes a user terminal and a time stamp token storage server that performs the deposit or the withdrawal of the time stamp token file in response to the deposit or withdrawal request from the user terminal. A management program, wherein a storage agent device communicatively connected to the user terminal and the time stamp token storage server via a predetermined network is used for depositing the time stamp token file together with the user terminal. When a proxy request is received, a step of proxying the deposit of the time stamp token file to the time stamp token storage server; and the storage proxy device, payout identification information of the time stamp token file from the user terminal. And, upon receipt of the withdrawal request, performing the withdrawal from the time stamp token storage server of the time stamp token storage server of the time stamp token file on the basis of the withdrawal identification information, causing the computer of the storage agent device to execute. Is characterized by.

According to the first time stamp storage agent system and the first program of the present invention, the user obtains the one-time password and the time stamp token every time the storage processing such as depositing and withdrawing the time stamp token file is performed. There is no need to log in to the storage server. Therefore, the user can smoothly deposit and withdraw the time stamp token file, and can use the time stamp storage service without feeling trouble and hassle, thus promoting the use of the time stamp storage service. can do. In this way, it is possible to easily and properly deposit and withdraw the time stamp token added to the managed file to the time stamp token storage server of the time stamp storage organization while maintaining the security of the time stamp storage organization. You can

A second time-stamp storage agency system of the present invention is the above-mentioned first time-stamp storage agency system of the present invention, wherein the user terminal corresponds to the management target file for the deposit of the time-stamp token file. Is designated, it is possible to select a direct deposit request to the time stamp token storage server and an indirect deposit request to the time stamp token storage server via the storage agent device. It is characterized by

The second program of the present invention is the program of the first program of the present invention, wherein the history of the deposit request or the withdrawal request by the user terminal and the time stamp for the deposit or withdrawal request. A step of recording the execution result by the token storage server in the customer history database for each user account of the user terminal is executed by the computer of the storage agent device.

According to the second time stamp storage agent system and the second program of the present invention, regarding the deposit of the time stamp token file, automatic deposit through the storage agent apparatus and direct access to the time stamp token storage server are performed. It can be used together with manual deposit, and convenience can be improved.

A third time-stamp storage agency system of the present invention is the above-mentioned first or second time-stamp agency system of the present invention, wherein the user terminal is the original, with respect to the payout of the time stamp token file. When a management target file is designated, an indirect withdrawal agency request via the archive agency device can be selected for the time stamp token archive server.

A third program of the present invention is a user terminal for requesting deposit or withdrawal of a time stamp token file composed of a time stamp token added to a management target file that is a time stamp management target, and the user terminal. And a time stamp token storage server for performing the deposit or withdrawal of the time stamp token file in response to the deposit or withdrawal request by Regarding the deposit of the stamp token file, when the time stamp token file is specified on the user terminal, a direct deposit request to the time stamp token storage server and the use to the time stamp token storage server A computer of the user terminal to select an indirect deposit agent request via a storage agent device communicatively connected to a user terminal and the time stamp token storage server via a predetermined network. It is characterized in that

According to the third time stamp storage agent system and the third program of the present invention, automatic payment through the storage agent device can be selectively used for paying out the time stamp token file, which is convenient. Can be improved.

A fourth time stamp storage agent system according to the present invention is the time stamp storage agent system according to any one of the first to third aspects of the present invention, wherein the storage agent device performs the deposit or the withdrawal by the user terminal. Of the proxy request and the execution result by the time stamp token storage server for the deposit or withdrawal request are recorded for each user account of the user terminal.

A fourth program of the present invention is a user terminal for requesting deposit or withdrawal of a time stamp token file composed of a time stamp token added to a management target file that is a time stamp management target, and the user terminal. And a time stamp token storage server for performing the deposit or withdrawal of the time stamp token file in response to the deposit or withdrawal request by Regarding the payout of the stamp token file, when the original management target file is specified in the user terminal, the user terminal and the time stamp token storage server are provided with a predetermined value with respect to the time stamp token storage server. It is characterized in that the computer of the user terminal is caused to execute a step of selecting an indirect withdrawal agent request via a storage agent device communicatively connected via a network.

According to the fourth time stamp storage agent system and the fourth program of the present invention, the storage agent manages and confirms the customer history database for the time stamp token file deposited in the time stamp token storage server. The convenience of the user is improved, and it is possible to contribute to the prevention of mistakes in deposit and omission of deposit. Further, even if multiple time stamp token files are generated and stored for the same managed file, the storage agent device checks the time information of each time stamp token file by referring to the customer history database. be able to. Therefore, the storage agent can determine the oldest time stamp token file when paying out the time stamp token file, improving the convenience of the user paying out the time stamp token file, and paying out the time stamp token file. It can contribute to the prevention of mistakes.

According to the present invention, the time stamp storage agent system, the agent system management program, and the agent system utilization program can easily and appropriately deposit and withdraw the time stamp token added to the managed file to the time stamp authority. To be able to do.

It is a block diagram showing the composition of the time stamp storage agency system concerning the embodiment of the present invention. It is an explanatory view showing roughly the flow of processing in the time stamp storage agency system concerning an embodiment of the present invention. FIG. 3 is a block diagram showing configurations of a TST storage server, a storage agent device, and a user terminal in the time stamp storage agent system according to the embodiment of the present invention. 7 is a table showing an example of a history of deposit results of TST files by the TST storage server in the time stamp storage agent system according to the exemplary embodiment of the present invention. 7 is a table showing an example of a history regarding deposits stored in a customer history DB of a storage agent device in the time stamp storage agent system according to the embodiment of the present invention. FIG. 6 is an explanatory diagram showing an example of a context menu for executing a proxy system utilization program of a user terminal in the time stamp storage proxy system according to the embodiment of the present invention. FIG. 8 is a plan view showing an example of an environment setting screen executed by a proxy system utilization program of a user terminal in the time stamp storage proxy system according to the embodiment of the present invention. FIG. 8 is a plan view showing an example of a TST deposit target list screen executed by the agent system utilizing program of the user terminal in the time stamp storage agent system according to the embodiment of the present invention. It is a flow chart which shows operation in a user terminal of a time stamp storage agency system concerning an embodiment of the present invention. 9 is a flowchart showing an operation related to time stamp addition of a management target file in the time stamp storage agent system according to the exemplary embodiment of the present invention. 6 is a flowchart showing an operation related to batch verification of managed files in the time stamp storage agent system according to the embodiment of the present invention.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. The following embodiments are preferred specific examples of the present invention and disclose various preferable techniques, but the technical scope of the present invention is not limited to these aspects.

A time stamp storage agent system 1 according to an embodiment of the present invention will be described with reference to FIG. The time stamp storage agent system 1 deposits a time stamp token 72 (so-called time stamp) issued by using the time stamp token issuing server (TST issuing server) 2, the time distribution server 3, and the electronic authentication management server 4. The system is configured to perform storage processing such as withdrawal (storage processing), and includes a time stamp token storage server (TST storage server) 5, a storage agent device 6, and a user terminal 7. The TST storage server 5, the storage agent device 6 and the user terminal 7 are communicably connected to each other via a network 8 such as the Internet. In addition, the user terminal 7 is connected to the TST issuing server 2 via the network 8, and the TST issuing server 2 is connected to the time distribution server 3 and the electronic authentication management server 4 via the network 8. For convenience of explanation, the time stamp token 72 (see FIG. 2) may be referred to as “TST”.

In the present embodiment, the electronic file that is the target of time stamp management is referred to as the management target file 70 (see FIG. 2). The management target file 70 includes electronic data such as a document, an image, a moving image, and a sound, and is composed of, for example, a PDF file.

As shown in FIG. 2, a TST 72 based on a hash value 71 of electronic data can be added to the managed file 70 in order to prove the existence and integrity of the electronic data, that is, the managed file. It is possible to embed TST 72 in 70 to form one file. The TST 72 includes, for example, a hash value 71, time information indicating the issue time of the TST 72, an electronic signature for the hash value 71, time information, and the like, and an electronic certificate for verifying the electronic signature.

The TST issuing server 2 is provided and operated in a time certification authority (TSA) such as a time stamp authority, and provides a time certification technology for issuing the TST 72 added to the managed file 70. In this time authentication technology, the TST 72 proves that the electronic data existed at the issue date and time of the TST 72 (presence of existence), and proves that the electronic data has not been tampered with after the issue date and time of the TST 72 ( Completeness proof).

Specifically, the TST issuing server 2 receives a request to issue the TST 72 together with the hash value 71 of the electronic data of the managed file 70 from the user terminal 7 via the network 8. In response to the issuance request, the TST issuing server 2 generates time information indicating the issuing time of the TST 72, based on the time delivered from the time delivery server 3. The TST issuing server 2 generates the TST 72 including the received hash value 71 and the generated time information. The TST issuing server 2 encrypts the combined data such as the hash value 71 and the time information with a predetermined secret key to generate an electronic signature, and adds the electronic signature to the TST 72. The TST 72 also includes an electronic certificate issued by the electronic authentication management server 4 for the public key that is paired with the private key. Then, the TST issuing server 2 transmits the TST 72 thus generated to the user terminal 7 that is the transmission source of the issuance request.

The time distribution server 3 is provided and operated in the time distribution organization (TAA), distributes the time to the TST issuing server 2 of the time certification organization, and inspects the clock of the TST issuing server 2.

The electronic certification management server 4 is provided and operated in an electronic certification authority (CA), and issues and revokes an electronic certificate. Specifically, when the electronic authentication management server 4 receives a request for issuing a public key and an electronic certificate from the TST issuing server 2, the electronic authentication managing server 4 generates an electronic certificate for this public key and sends it to the TST issuing server 2. The electronic certificate includes the corresponding public key.

The TST storage server 5 will be described in detail. The TST storage server 5 is a device that is provided and operated in a time stamp storage organization (INPIT) and provides a time stamp storage service for performing storage processing such as depositing and withdrawing the TST 72. When the TST storage server 5 receives a deposit request for the TST file 73 from the storage agent device 6 or the user terminal 7 together with the time stamp token file 73 (hereinafter referred to as TST file) including the TST 72, the deposit is accepted, Save the TST file 73. When the TST storage server 5 receives the withdrawal request of the stored TST file 73 from the storage agent device 6 or the user terminal 7 and approves the withdrawal, the TST file 73 stores the TST file 73 as the storage agent device of the sender of the withdrawal request. 6 or to the user terminal 7.

The TST storage server 5 includes, for example, as shown in FIG. 3, an arithmetic processing unit 11, a storage unit 12, a communication unit 13, an operation unit 14, a display unit 15, and an input/output unit 16. Further, the TST storage server 5 includes functional units such as an account management unit 18, a login processing unit 19, a TST depositing unit 20, a TST payout unit 21, a certificate issuing unit 22, and a storage history processing unit 23. Further, the TST storage server 5 includes a company information database (DB) 25, a user information database (DB) 26, and a storage database (DB) 27.

The functional unit of the TST storage server 5 described above may be configured by a program stored in the storage unit 12 and executed by the arithmetic processing unit 11. That is, the storage unit 12 stores a program for causing the computer to function as the TST storage server 5 including these functional units. In other words, the arithmetic processing unit 11 and the storage unit 12 configure a control device of the TST storage server 5. Further, the TST storage server 5 may define an API for using each functional unit and provide it to the storage agent device 6.

The arithmetic processing unit 11 is composed of, for example, a CPU (central processing unit). The storage unit 12 includes, for example, a main storage device such as a semiconductor storage device and an auxiliary storage device such as a magnetic storage device. The communication unit 13 is a communication control circuit for communicating with an external device via the network 8. The operation unit 14 includes, for example, a keyboard and a pointing device. The display unit 15 is, for example, a display device such as a display. The input/output unit 16 is an interface that is connected to an external storage device such as a USB (Universal Serial Bus) memory or another device such as an optical disk drive device to input/output data to/from the other device.

When the time stamp storage organization concludes a contract permitting the storage agent of the storage agent apparatus 6 to store the TST, the account management unit 18 gives the agency company a business account (account ID, password, etc.). And the business account is registered and managed in the business information DB 25. In addition to the business operator account, the business operator information DB 25 also stores the business operator's identification number, name, and contact information (address, telephone number, email address, etc.) of the business operator. You may.

Also, the account management unit 18 creates a user account (account ID, password, etc.) for the user when the time stamp storage organization makes a contract to allow the user of the user terminal 7 to store the TST. The user account is added and registered and managed in the user information DB 26. In addition to the user account, the user identification number, name, and contact information (address, telephone number, mail address, etc.) may be registered in the user information DB 26 as user information for each user. .. For example, the account management unit 18 directly assigns a one-time password to the user who performs the storage process of the TST 72 to the TST storage server 5 as the password of the user account each time the storage process is permitted. Further, the account management unit 18 provides a long-term password that can be used for a long time (for example, several months) for the storage agent as a password of the user account for the user who uses the storage agent of the storage agent apparatus 6. Is given.

The login processing unit 19 authenticates the company account received from the storage agent device 6 and the user account received from the user terminal 7 by referring to the company information DB 25 and the user information DB 26. For example, the login processing unit 19 displays a login screen on the storage agent device 6 or the user terminal 7 according to a web page published on the network 8 or an application distributed to the storage agent device 6 or the user terminal 7, and the login screen The business account and the user account input to are received via the network 8. The storage agent device 6 and the user terminal 7, which have authenticated the business account and the user account, each function unit of the TST storage server 5 (TST depositing unit 20, TST issuing unit 21, certificate issuing unit 22, and storage history processing). Part 23) becomes available.

The TST deposit unit 20 receives a deposit request for the TST file 73 from the storage agent device 6 or the user terminal 7. For example, when receiving the deposit request from the logged-in user terminal 7, the TST depositing unit 20 identifies the user based on the user account of the user terminal 7. In this case, the deposit request includes, for example, the TST file 73 including the TST 72 added to the management target file 70. The TST depositing unit 20 assigns and assigns a management number to the TST file 73 and associates it with a user account, and deposits (stores) the TST file 73 and the user account in the storage DB 27.

Further, when the TST depositing unit 20 receives a deposit request from the storage agent device 6 that is logged in, the TST depositing unit 20 identifies the agency company based on the company account of the storage agent device 6. In this case, the deposit request includes, for example, the TST file 73 including the TST 72 added to the management target file 70 and the user account of the user who makes the deposit request. The TST depositing unit 20 assigns and assigns a management number to the TST file 73, and deposits the TST file 73, the user account and the enterprise account in the storage DB 27 in association with the user account and the enterprise account ( store).

The TST depositing unit 20 transmits the history of deposit results generated by the storage history processing unit 23 to the storage agent device 6 and the user terminal 7 as a response to the deposit request, regardless of whether the deposit is successful or unsuccessful. For example, as shown in FIG. 4, the history of deposit results includes deposit date and time, item number in transmission order, deposit result (OK or NG), management number, file name, account ID of user account, and the like.

The TST payout unit 21 receives a payout request for the TST file 73 from the storage agent device 6 and the user terminal 7. For example, when receiving the withdrawal request from the logged-in user terminal 7, the TST payout unit 21 identifies the user based on the user account of the user terminal 7. In this case, the withdrawal request includes, for example, withdrawal identification information such as the management number given to the TST file 73 at the time of deposit and the hash value 71 of the original managed file 70. The TST payout unit 21 refers to the storage DB 27 based on the user account and the payout identification information, and searches for the corresponding TST file 73. When the corresponding TST file 73 can be retrieved, the TST payout unit 21 pays out (transmits) the TST file 73 to the user terminal 7. On the other hand, if the corresponding TST file 73 cannot be retrieved, the TST payout unit 21 may return an error without the TST file 73.

In addition, when the TST payout unit 21 receives a payout request from the logged-in storage agent device 6, the TST payout unit 21 identifies the agent on the basis of the company account of the storage agent device 6. In this case, the payout request includes, for example, the payout identification information such as the management number given to the TST file 73 at the time of deposit and the hash value 71 of the original managed file 70, and the user of the user who requests the payout. Accounts and are included. The TST payout unit 21 refers to the storage DB 27 based on the user account and the payout identification information, and searches for the corresponding TST file 73. At this time, the business operator account may be used to narrow down the search. When the corresponding TST file 73 can be retrieved, the TST payout unit 21 pays out (transmits) the TST file 73 to the storage agent device 6. On the other hand, if the corresponding TST file 73 cannot be retrieved, the TST payout unit 21 may return an error without the TST file 73.

The TST payout unit 21 transmits the history of the payout result generated by the storage history processing unit 23 to the storage agent device 6 and the user terminal 7 as a response to the payout request, regardless of whether the payout is successful or unsuccessful.

When the TST issuing unit 21 can retrieve the TST file 73, the certificate issuing unit 22 creates a deposit certificate 74 certifying the deposit of the TST file 73, and stores the TST file 73 together with the storage agent device 6 and the use. It is transmitted to the person terminal 7.

The storage history processing unit 23 generates a history of deposit results by the TST deposit unit 20 and payout results by the TST dispensing unit 21. The storage history processing unit 23 may store the history of deposit results and withdrawal results in the storage DB 27 in association with the TST file 73.

The storage agent device 6 will be described in detail. The storage agent device 6 is a device that is operated by an agent that performs a storage process such as deposit and withdrawal of the TST file 73 (storage agent). Although one storage agent device 6 is illustrated in FIG. 1, a plurality of storage agent devices 6 may be connected to one TST storage server 5. Upon receipt of the deposit agent request for the TST file 73 from the user terminal 7, the storage agent device 6 accesses the TST storage server 5 instead of the user terminal 7 to proxy the deposit request. When the storage agent device 6 receives from the user terminal 7 the withdrawal agent request for the TST file 73 stored in the TST storage server 5, the storage agent device 6 accesses the TST storage server 5 instead of the user terminal 7 to perform the withdrawal request. ..

The storage agent device 6 includes, for example, an arithmetic processing unit 31, a storage unit 32, a communication unit 33, an operation unit 34, a display unit 35, and an input/output unit 36, like the TST storage server 5. Further, the storage agent device 6 includes functional units such as an account management unit 38, a login processing unit 39, a TST deposit agent unit 40, a TST withdrawal agent unit 41, and a storage history processing unit 42. Further, the storage agent device 6 includes a customer history database (DB) 44.

The functional unit of the storage agent device 6 may be configured by a program stored in the storage unit 32 and executed by the arithmetic processing unit 31. That is, the storage unit 32 stores a program (substitution system management program) for causing a computer to function as the storage substitution device 6 including these functional units. In other words, the arithmetic processing unit 31 and the storage unit 32 constitute a control device of the storage agent device 6. The agency system management program may be started up when the storage agency apparatus 6 is started up, or may be started up according to the operation of the storage agency apparatus 6.

The account management unit 38 stores and manages the business account used when the storage agent device 6 logs in to the TST storage server 5 in the storage unit 32. Further, the account management unit 38 gives a customer account (account ID, password, etc.) to the user when the agency business operator makes a contract to allow the user to store the TST file 73. The customer account is registered and managed in the storage unit 32 and the customer history DB 44.

The customer history DB 44 also stores a history of depositing and withdrawing the TST file 73 for each customer account. For example, as shown in FIG. 5, the deposit history includes deposit date and time of the TST file 73, management number, file name, user account account ID, TST issue date and time (time information), hash value, and the like. .. As the customer information for each user registered in the storage unit 32 or the customer history DB 44, in addition to the customer account, the user's identification number, name, contact information (address, telephone number, mail address, etc.) are also registered. Good. The customer information may be the same as the user information registered in the user information DB 26 of the TST storage server 5, or may be different information newly added by the storage agent device 6. In the latter case, the customer history DB 44 is associated with the customer account for the user to obtain the permission to use the storage agent device 6 and the user account for the user to obtain the permission to use the TST storage server 5. May be remembered.

The login processing unit 39 sends the business agent account stored in the storage unit 32 to the login processing unit 19 of the TST storage server 5 to log the storage agent device 6 into the TST storage server 5. For example, the login processing unit 39 executes such login processing when the storage agent device 6 is activated. The storage agent device 6 continues to log in during operation, that is, always maintains the logged-in state.

The login processing unit 39 authenticates the customer account received from the user terminal 7 by referring to the storage unit 32 and the customer history DB 44. For example, the login processing unit 39 displays a login screen on the user terminal 7 according to a web page published on the network 8 or an application distributed to the user terminal 7, and stores the customer account input on the login screen in the network 8 To receive via. The user terminal 7 that has authenticated the customer account can use each functional unit of the storage agent device 6 (TST deposit agent unit 40, TST withdrawal agent unit 41, and storage history processing unit 42).

The TST deposit agency unit 40 receives a deposit agency request for the TST file 73 from the user terminal 7. The deposit substitution request includes, for example, a TST file 73 including a TST 72 added to the management target file 70, and a user account of a user who requests the deposit. The TST deposit agent unit 40 may grasp the user account by the deposit agent request from the user terminal 7 in this way, but if the customer account and the user account are the same, the logged-in user The user account may be grasped based on the customer account of the terminal 7, or if the customer account and the user account are stored in the customer history DB 44 in association with each other, the logged-in user terminal 7 The user account may be grasped by referring to the customer history DB 44 based on the customer account.

The TST deposit agency 40 deposits the TST file 73 in the TST storage server 5 by transmitting a deposit request including the TST file 73 and the user account to the TST deposit unit 20 of the TST storage server 5. The TST deposit agent unit 40 refers to the customer history DB 44 based on the deposit agent request from the user terminal 7, and confirms that the TST file 73 targeted for the deposit agent request has already been deposited in the TST storage server 5. When the determination is made, it is advisable to notify the user terminal 7 that the deposit has been made and display and inform the user that the deposit has been made, without transmitting the deposit request.

The TST payout agency 41 receives a payout agency request for the TST file 73 from the user terminal 7. The withdrawal agency request includes, for example, withdrawal identification information such as the management number given to the TST file 73 at the time of deposit or the hash value 71 of the original managed file 70, and the user account of the user on behalf of which the withdrawal request is made. Is included. Although the TST payout agency unit 41 may grasp the user account by the payout agency request from the user terminal 7 in this way, when the customer account and the user account are the same, the logged-in user The user account may be grasped based on the customer account of the terminal 7, or if the customer account and the user account are stored in the customer history DB 44 in association with each other, the logged-in user terminal 7 The user account may be grasped by referring to the customer history DB 44 based on the customer account.

When the payout identification information has the hash value 71, the TST payout agency 41 refers to the deposit result history of the customer history DB 44 based on the hash value 71 to search for the management number of the TST file 73 corresponding to the hash value 71. To do. In addition, referring to the customer history DB 44, when the TST files 73 having the same hash value 71 and different time information are stored in the TST storage server 5, the TST payout agency unit 41 determines that the users included in the payout agency request. The TST file 73 to be paid out is determined based on the “TST file payout target” 92 (see FIG. 7) of the agency setting of the environment setting of the terminal 7. For example, when the “TST file payout target” 92 is the “oldest TST file”, the TST payout agency 41 targets the TST file 73 of the oldest time information based on the deposit result history of the customer history DB 44. Is determined as. The TST payout agency 41 sends a payout request including the management number of the TST file 73 and the user account to the TST payout unit 21 of the TST storage server 5.

The TST payout proxy unit 41 receives the TST file 73 from the TST payout unit 21 as a response to the payout request. In addition, the TST payout agency 41, when the “issue or not of deposit certificate” 93 (see FIG. 7) of the agency setting of the environment setting of the user terminal 7 included in the payout agency request is “issue”, A request for issuing the deposit certificate 74 is sent to the certificate issuing unit 22 of the TST storage server 5 together with the withdrawal request. The TST payout proxy unit 41 receives the deposit certificate 74 from the certificate issuing unit 22 as a response to the issuance request. The TST payout agency 41 sends the TST file 73 and the deposit certificate 74 received from the TST storage server 5 to the user terminal 7 as a response to the payout agency request from the user terminal 7. At this time, the TST paying agency 41 changes the file name of the deposit certificate 74 received from the certificate issuing unit 22 to a name including the file name of the corresponding managed file 70 and the issue date and time of the deposit certificate 74. Good.

The storage history processing unit 42 stores and manages the deposit request history in the customer history DB 44 when the TST deposit agent unit 40 transmits the deposit request to the TST storage server 5 in response to the deposit agent request from the user terminal 7. .. The deposit request history is information relating to the deposit request, for example, identification information of the TST file 73 (for example, hash value 71 and time information), reception date and time of the deposit agent request, transmission date and time of the deposit request, etc. are associated with the customer account. Will be remembered.

The storage history processing unit 42, when the TST deposit agency 40 receives the history of deposit results from the storage history processing unit 23 of the TST storage server 5, stores it in the customer history DB 44 and manages it. The deposit result history is, for example, identification information of the TST file 73 (for example, hash value 71, management number and time information), date and time of receipt of deposit request, date and time of deposit execution, success or failure of deposit, as information relating to deposit result. Are stored in association with the customer account. When the deposit result is successful, the storage history processing unit 42 counts the corresponding deposit agency request as a charging target, and stores and manages the charging status in the deposit result history of the customer history DB 44. Further, the storage history processing unit 42 may transmit the deposit result history to the user terminal 7 in response to a request from the user terminal 7.

The storage history processing unit 42 stores and manages the withdrawal request history in the customer history DB 44 when the TST withdrawal agent unit 41 transmits the withdrawal request to the TST storage server 5 in response to the withdrawal agent request from the user terminal 7. .. The payout request history includes, as information related to the payout request, for example, identification information of the TST file 73 (for example, hash value 71, management number and time information), reception date and time of the payment agency request, transmission date and time of the payment request, and the like. It is stored in association with the account.

When the TST payout proxy unit 41 receives the payout result from the storage history processing unit 23 of the TST storage server 5, the storage history processing unit 42 stores it in the customer history DB 44 and manages it. The payout result history is, for example, the identification information of the TST file 73 (for example, the hash value 71, the management number and the time information), the reception date and time of the payout request, the execution date and time of the payout, and the success or failure of the payout, as information related to the payout result. Are stored in association with the customer account. When the payout result is successful, the storage history processing unit 42 counts the corresponding payout agency request as a charge target, and stores and manages the charge status in the payout result history of the customer history DB 44. Further, the storage history processing unit 42 may transmit the payout result history to the user terminal 7 in response to a request from the user terminal 7.

The user terminal 7 will be described in detail. The user terminal 7 is a device such as a personal computer used by a user who uses the issuance and storage of the TST 72 for proof of existence and integrity proof of the managed file 70. Although one user terminal 7 is shown in FIG. 1, a plurality of user terminals 7 may be connected to one TST storage server 5, and a plurality of storage terminals 6 may be connected to one storage agent device 6. The user terminal 7 may be connected. The user terminal 7 manually communicates with the TST storage server 5 according to the operation of the user, or automatically communicates with the TST storage server 5 via the storage agent device 6 to manage the files to be managed. The TST file 73 including the TST 72 added to 70 is deposited or withdrawn.

The user terminal 7 includes an arithmetic processing unit 51, a storage unit 52, a communication unit 53, an operation unit 54, a display unit 55, and an input/output unit 56, similar to the TST storage server 5 and the storage agent device 6, for example. Further, the user terminal 7 has an account management unit 58, a time stamp adding unit 59, a TST deposit requesting unit 60, a TST deposit proxy requesting unit 61, a time stamp verifying unit 62, a TST payout requesting unit 63, and a TST paying proxy requesting unit 64. And other functional parts.

The functional unit of the user terminal 7 may be configured by a program stored in the storage unit 52 and executed by the arithmetic processing unit 51. That is, the storage unit 52 stores a program (substitution system use program) for causing a computer to function as the user terminal 7 having these functional units. In other words, the arithmetic processing unit 51 and the storage unit 52 configure a control device for the user terminal 7.

The proxy system utilization program may be activated upon activation of the user terminal 7, or may be activated in response to an operation of the user terminal 7. When started, the agent system utilization program sends the customer account of the user terminal 7 to the storage agent device 6 to log the user terminal 7 into the storage agent device 6.

The proxy system utilization program executes various processes such as time stamp addition, time stamp verification, certificate issuance, environment setting, etc. according to the user's operation. The proxy system utilization program makes it possible to select either manual deposit or substitute deposit as the time stamp addition, and makes it possible to select either manual dispense or substitute dispense as the time stamp verification. The agent system utilization program enables various setting conditions such as system setting, time stamp setting, file setting, batch verification setting, agent setting, etc. to be set as environment setting.

The proxy system utilization program provides the user with an interface such as a GUI (graphical user interface) that accepts the operations of the various processes described above, and, for example, in the context menu displayed on the display unit 55 by the operating system of the user terminal 7. The operation items of various processes are displayed and can be operated by the operation unit 54. For example, as shown in FIG. 6, in the context menu when a predetermined management target file 70 is specified in the operating system of the user terminal 7, an operation item of “agent system utilization program” is displayed.

In the context menu, if you select "Substitute system use program", "Image information selection", "Time stamp addition", "Search information setting CSV output", "Batch verification", "Deposit certificate issuance", " Operation items such as "Environment setting" are displayed.

When "Give time stamp" is selected, the selection items of "TST file manual deposit" and "TST file proxy deposit" are displayed. When the "TST file manual deposit" is selected, the proxy system utilization program executes the time stamp adding unit 59 and the TST deposit requesting unit 60, and when "TST file proxy deposit" is selected, the time stamp adding unit 59 is selected. And the TST deposit agency request unit 61 is executed.

When "Batch verification" is selected, further selection items of "TST file manual payout" and "TST file proxy payout" are displayed. When the "TST file manual payout" is selected, the proxy system utilization program executes the time stamp verification unit 62 and the TST payout request unit 63, and when "TST file proxy payout" is selected, the time stamp verification unit 62. And the TST payout agency request unit 64 is executed.

When "environment setting" is selected, the proxy system utilization program displays the environment setting screen 80 on the display unit 55 as shown in FIG. The environment setting screen 80 includes, for example, a system setting tab 81 for making system settings, a time stamp setting tab 82 for making time stamp settings, and a file/collective verification setting tab 83 for making file settings and collective verification settings. , A substitute business operator setting tab 84 for setting a substitute business operator is displayed.

In the system setting tab 81, for example, setting conditions regarding a license for using the substitute system use program in the context menu, communication of the TST issuing server 2, an Internet connection environment, an operation log of the substitute system use program, a time stamp generation log, and the like. Display the system setting screen that can be set.

On the time stamp setting tab 82, for example, a time stamp setting screen is displayed in which setting conditions can be set for a stamp imprint of a time stamp, verification at time stamp generation, date and time format, display of time zone, and the like.

On the file/collective verification setting tab 83, for example, a file/collective verification setting screen in which setting conditions can be set for the management target file 70, input person information, time stamp verification, and the like is displayed.

In the agency setting tab 84, as shown in FIG. 7, "designated agency" 85, "account ID" 86, "password" 87, "deposit TST file folder" 88, "payout TST file folder" 89, A proxy operator setting screen on which setting conditions such as “deposit certificate folder” 90, “TST file deposit target” 91, “TST file dispensing target” 92, and “issuance of deposit certificate” 93 can be displayed is displayed.

The “designated agency” 85 is used when a user who has a contract with the agency to deposit or withdraw the TST file 73 into the TST storage server 5 (time stamp storage organization) accesses the storage agent device 6. Set access information such as URL.

To the “account ID” 86 and the “password” 87, a user who has made a contract and registration in advance with the time stamp storage organization in order to use the TST storage server 5 is given by the time stamp storage organization for authentication. Set the user account in advance. The proxy system utilization program can access the TST storage server 5 via the storage proxy device 6 and deposit and withdraw the TST file 73 using a preset user account.

In the “account ID” 86, the user sets a unique ID given as a user account by the time stamp storage organization. The “account ID” 86 may be a common ID both when the user terminal 7 directly communicates with the TST storage server 5 and when indirectly communicating via the storage agent device 6. The “password” 87 sets a long-term password used when the user terminal 7 indirectly communicates with the TST storage server 5 via the storage agent device 6.

In the “deposited TST file folder” 88, the folder in which the user terminal 7 saves the TST file 73 deposited in the TST storage server 5 via the storage agent device 6 is set. The TST deposit agent requesting unit 61 transmits the TST file 73 from this folder to the storage agent device 6 as a deposit target.

In the “payout TST file folder” 89, the TST transmitted from the TST storage server 5 to the user terminal 7 via the storage agent device 6 as a result of the payment agent request by the TST payment agent request unit 64 of the user terminal 7. Set a save destination folder for the file 73.

In the “deposit certificate folder” 90, the deposit sent from the TST storage server 5 to the user terminal 7 via the storage agent device 6 as a result of the withdrawal agent request by the TST withdrawal agent requesting unit 64 of the user terminal 7. Set a folder for saving the certificate 74.

In “TST file deposit target” 91, selection items of “all TST files”, “selected TST files”, and “not deposit” are displayed. When "all TST files" is selected, all the TST files 73 of the management target files 70 designated by the user at the time of the deposit agency request are targeted for the deposit agency request. When "Only selected TST file" is selected, the TST deposit target list screen 95 (see FIG. 8) is displayed at the time of deposit deposit request, and only the TST file 73 selected on this screen is targeted for deposit deposit request. .. If "Do not deposit" is selected, the deposit agent request for the TST file 73 is not made.

In the “TST file payout target” 92, selection items of “oldest TST file” and “latest TST file” are displayed. When "Only the oldest TST file" is selected, when a plurality of TST files 73 are stored in the TST storage server 5 for the managed file 70 designated by the user, the TST73 file with the oldest time information is paid out. Be the subject of the request. When only the latest TST file is selected, when the TST storage server 5 stores a plurality of TST files 73 for the managed file 70 designated by the user, the TST file 73 with the latest time information is paid out. Be the subject of the request.

In “Issue/Issue of deposit certificate” 93, selection items of “issue” and “not issue” are displayed. When “Issue” is selected, the TST withdrawal agency request unit 64 of the user terminal 7 requests the issuance of the deposit certificate 74 in the withdrawal agency request, and the deposit certificate 74 is stored together with the TST file 73 from the TST storage server 5. It is transmitted to the user terminal 7 via the proxy device 6. When “Do not issue” is selected, in the withdrawal agency request by the TST withdrawal agency requesting unit 64 of the user terminal 7, the issuance of the deposit certificate 74 is not requested, and only the TST file 73 is transferred from the TST archive server 5 to the archive agent apparatus 6. Is transmitted to the user terminal 7 via.

The account management unit 58 stores and manages the user account used when the user terminal 7 logs in to the TST storage server 5 in the storage unit 52, and when the user terminal 7 logs in to the storage agent device 6. The customer account used for is stored in the storage unit 52 and managed. The account management unit 58 previously acquires and stores a long-term password from the TST storage server 5 as a user account.

The time stamp adding unit 59 acquires the TST 72 from the TST issuing server 2 for the management target file 70 designated by the user, adds the TST 72 to the management target file 70, and generates the TST file 73 including the TST 72. .. The time stamp adding unit 59 may specify a plurality of management target files 70 to the user, or may specify a folder including the plurality of management target files 70 to the user.

Specifically, the time stamp adding unit 59 calculates a hash value 71 using a predetermined hash function based on the electronic data of the management target file 70, and issues a request to issue the TST 72 together with the hash value 71 to the communication unit 13 and It is transmitted to the TST issuing server 2 via the network 8. The time stamp adding unit 59 receives the TST 72 corresponding to the issuance request from the TST issuing server 2 via the network 8 and the communication unit 13. The time stamp adding unit 59 temporarily stores the received TST 72 in the storage unit 52, adds the TST 72 to the management target file 70, and generates the TST file 73 including the TST 72. Also, the time stamp adding unit 59 deposits the generated TST file 73 in the TST storage server 5. The TST file 73 is deposited by the TST deposit requesting unit 60 and the TST deposit proxy requesting unit 61.

The TST deposit request unit 60 deposits the TST file 73 in the TST storage server 5 through direct communication between the user terminal 7 and the TST storage server 5. Specifically, the TST deposit requesting unit 60 first requests the TST storage server 5 to deposit the TST file 73 and acquires the one-time password from the TST storage server 5. The TST deposit requesting unit 60 transmits the user account of the user terminal 7 including the one-time password to the TST storage server 5, and logs the user terminal 7 into the TST storage server 5. The TST deposit request unit 60 deposits the TST file 73 in the TST storage server 5 by transmitting the deposit request to the TST storage server 5 together with the TST file 73 of the management target file 70 designated by the user.

The TST deposit substitution requesting unit 61 deposits the TST file 73 in the TST storage server 5 by indirect communication between the user terminal 7 and the TST storage server 5, that is, communication via the storage agent device 6. Specifically, the TST deposit agency requesting unit 61 first confirms “TST file deposit target” 91 in the agency setting of the environment setting. When the “TST file deposit target” 91 is “all TST files”, the TST deposit proxy request unit 61 creates all the TST files generated by the time stamp adding unit 59 for the management target file 70 designated by the user. All TST files 73 are deposited in the TST storage server 5 by transmitting a deposit agency request to the storage agent device 6 together with 73 and a user account including a long-term password.

When the “TST file deposit target” 91 is the “selected TST file”, the TST deposit proxy request unit 61 displays the TST deposit target list screen 95 on the display unit 55, as shown in FIG. 8. On the TST deposit target list screen 95, the file name of the management target file 70 designated by the user, the checkbox of the deposit target, the issue date and time (time information) of the TST file 73, the account ID of the user account at the time of deposit, and the like are displayed. Is displayed. The TST deposit substitution requesting unit 61 sets only the management target file 70 in which the check box of deposit target is checked as the TST file deposit target, and corresponds to the TST file deposit target among the TST files 73 generated by the time stamp adding unit 59. The selected TST file 73 is deposited in the TST storage server 5 by transmitting the deposit agency request together with the TST file 73 to be stored and the user account including the long-term password to the storage agent device 6.

The time stamp verification unit 62 compares the TST 72 added to the management target file 70 designated by the user with the TST 72 stored in the TST storage server 5 corresponding to this management target file 70, The presence proof and the integrity proof of the managed file 70 are verified. For example, the time stamp verification unit 62 calculates the hash value 71 of the management target file 70 using the hash function used by the time stamp adding unit 59. Further, the time stamp verification unit 62 pays out the TST file 73 corresponding to the management target file 70 from the TST storage server 5, and extracts the hash value 71 from the TST 72 of this TST file 73. Then, the time stamp verification unit 62 performs verification by comparing these hash values 71. The TST file 73 is paid out by the TST payout requesting unit 63 and the TST payout proxy requesting unit 64.

The TST payout request unit 63 pays out the TST file 73 from the TST storage server 5 through direct communication between the user terminal 7 and the TST storage server 5. Specifically, the TST payout request unit 63 first requests the TST storage server 5 to pay out the TST file 73, and acquires the one-time password from the TST storage server 5. The TST payout requesting unit 63 transmits the user account of the user terminal 7 including the one-time password to the TST storage server 5, and causes the user terminal 7 to log in to the TST storage server 5. The TST payout request unit 63 calculates the hash value 71 of the management target file 70 designated by the user as the payout identification information, and the hash value 71 and other information about the management target file 70 (file name, time information, etc.). At the same time, by sending a withdrawal request to the TST storage server 5, the TST file 73 corresponding to the managed file 70 is withdrawn from the TST storage server 5. The TST withdrawal request unit 63 receives the TST file 73 and the deposit certificate 74 transmitted from the TST storage server 5 in response to the withdrawal request.

The TST payout proxy request unit 64 pays out the TST file 73 from the TST storage server 5 by indirect communication between the user terminal 7 and the TST storage server 5, that is, communication via the storage proxy device 6. Specifically, the TST payout agency request unit 64 calculates a hash value 71 of the managed file 70 designated by the user as payout identification information, and the hash value 71, a user account including a long-term password, and The TST file 73 corresponding to the management target file 70 is paid out from the TST storage server 5 by transmitting a payout proxy request to the storage proxy device 6 together with other information regarding the management target file 70 (file name, time information, etc.). The withdrawal agency request includes the “TST file withdrawal target” 92 and the “presence/absence of issuance of deposit certificate” 93 set by the agency. The TST payout agency request unit 64 receives the TST file 73 and the deposit certificate 74 transmitted from the TST storage server 5 via the storage agency device 6 in response to the payout agency request.

Next, the operation of the time stamp storage agent system 1 of the present embodiment will be described with reference to the flowcharts of FIGS. 9, 10 and 11.

First, in the time stamp storage agency system 1, the user makes a contract with the time stamp storage organization and the agency for storage processing of the TST file 73 via the agency, and the user account given by the time stamp organization. It is also assumed that the customer account given by the agent and the agency is set in the user terminal 7.

At the user terminal 7, as shown in FIG. 9, verification software for verifying the management target file 70 is activated at the time of activation or in response to the user's operation (step S1). This verification software incorporates a substitute system utilization program, and also activates the substitute system utilization program.

In the user terminal 7, when the management target file 70 is specified using the operation unit 54 or the display unit 55 (step S2: YES), a context menu display operation (for example, right-clicking the mouse of the operation unit 54). ) Is performed, a context menu (see FIG. 6) for the managed file 70 is displayed on the display unit 55. By operating this context menu, the proxy system utilization program is executed.

In the following, with respect to the time stamp addition of the proxy system utilization program, the operation accompanied by the deposit proxy request of the TST file 73 will be described. When "time stamp addition" of the context menu displayed on the display unit 55 is operated (step S3: YES), a TST addition process is performed as an operation of adding a time stamp to the designated management target file 70. The process proceeds to (step S4).

As shown in FIG. 10, the TST adding process is started by the user terminal 7. First, the time stamp adding unit 59 calculates the hash value 71 of the management target file 70 (step S11), and the calculated hash value 71. At the same time, the issuance request of the TST 72 is transmitted to the TST issuing server 2 (step S12).

The TST issuing server 2 issues (assigns) the TST 72 to the hash value 71 (managed file 70) in response to the issue request received from the user terminal 7, and transmits it to the user terminal 7.

When the user terminal 7 receives the TST 72 issued by the TST issuing server 2 (step S13), the time stamp adding unit 59 adds the received TST 72 to the management target file 70, and further, the TST file 73 including the TST 72. Is generated (step S14). Further, in the user terminal 7, in order to store the generated TST file 73 in the TST storage server 5, the TST deposit agency request unit 61 sends a deposit agency request to the storage agency device 6 together with the TST file 73 and the user account. Yes (step S15). At this time, when the “TST file deposit target” 91 of the agency setting of the environment setting is the “selected TST file”, the TST deposit proxy request unit 61 displays the TST deposit target list screen 95 (see FIG. 8). The TST file 73 to be displayed and transmitted to the storage agent device 6 is selected.

When the storage agent device 6 receives the deposit agent request together with the TST file 73 and the user account from the user terminal 7 (step S21), the TST deposit agent unit 40 receives the TST file 73 in response to the deposit agent request. And a deposit request is transmitted to the TST storage server 5 together with the user account (step S22). At this time, the storage history processing unit 42 stores the deposit request history for the TST storage server 5 in the customer history DB 44.

When the TST storage server 5 receives the deposit request together with the TST file 73 and the user account from the storage agent device 6 (step S31), the TST deposit unit 20 selects the user who deposits the TST file 73 based on the user account. Ascertained, a management number is added to the TST file 73 (step S32). Further, the TST depositing unit 20 deposits the TST file 73 in the storage DB 27 together with the user account and the management number (step S33). At this time, the storage history processing unit 23 generates a history of deposit results (OK or NG) of the TST file 73 by the TST deposit unit 20, and transmits the deposit result history to the storage agent device 6 as a response to the deposit request. (Step S34).

When the storage agent device 6 receives the deposit result history from the TST storage server 5 (step S23), the storage history processing unit 42 stores the deposit result history in the customer history DB 44 (step S24). Further, the TST deposit agency 40 or the storage history processor 42 sends a history of deposit results to the user terminal 7 as a response to the deposit agency request (step S25).

When the user terminal 7 receives the deposit result history from the storage agent device 6 (step S16), the deposit result is displayed on the display unit 55 (step S17), and the TST giving process ends.

In this way, the user terminal 7 specifies the management target file 70 (step S2: YES) while the verification software is being activated (step S1, step S7: NO), and selects “time stamp addition” from the context menu. By the operation (step S3: YES), the TST 72 can be added to the managed file 70 and the TST file 73 can be deposited in the TST storage server 5 via the storage agent device 6.

Next, the operation related to the payout agency request of the TST file 73 using the agency system utilization program will be described. When "Batch verification" of the context menu displayed on the display unit 55 is operated (step S5: YES), the verification processing (step S6) is performed as an operation of verifying the designated managed file 70.

As shown in FIG. 11, the verification process is started by the user terminal 7. First, the time stamp verification unit 62 verifies the designated management target file 70, and therefore, the hash value 71 of the management target file 70. Is calculated (step S41). Further, the TST withdrawal request unit 63 issues a withdrawal agent request for the TST file 73 to the storage agent device 6 together with the calculated hash value 71 in order to withdraw the TST file 73 used for verification of the managed file 70 from the TST storage server 5. It is transmitted (step S42). The TST withdrawal requesting unit 63 includes the “presence/absence of issuance of deposit certificate” 93, which is set by the environment setting agency, in the withdrawal agency request.

When the storage agent device 6 receives the withdrawal agent request together with the hash value 71 from the user terminal 7 (step S51), the TST withdrawal agent unit 41 responds to the withdrawal agent request and based on the hash value 71, the customer history DB 44. With reference to, the management number of the TST file 73 corresponding to the hash value 71 (the management target file 70 to be verified) is searched (step S52). Further, the TST payout agency 41 sends a payout request for the TST file 73 to the TST storage server 5 together with the retrieved management number (step S53). At this time, the storage history processing unit 42 stores the payout request history for the TST storage server 5 in the customer history DB 44. Note that the TST payout agency unit 41 also includes, in the payout request, "issue or not of deposit certificate" 93 set by the agency business included in the payout agency request.

When the TST storage server 5 receives the withdrawal request together with the management number from the storage agent device 6 (step S61), the TST payout unit 21 refers to the storage DB 27 based on the management number and refers to the management number (the management target to be verified). The TST file 73 corresponding to the file 70) is searched (step S62). Further, the TST payout unit 21 transmits the searched TST file 73 to the storage agent device 6 as a response to the payout request (step S63). At this time, when the “issue or not of deposit certificate” 93 of the substitute business operator setting included in the withdrawal request is “issue”, the certificate issuing unit 22 creates and stores the deposit certificate 74 of the TST file 73. It transmits to the proxy device 6. Further, the storage history processing unit 23 generates a history of payout results (OK or NG) of the TST file 73 by the TST payout unit 21, and transmits the history to the storage agent device 6.

When the storage agent device 6 receives the TST file 73 from the TST storage server 5 (step S54), the TST payout agency unit 41 sends the received TST file 73 to the user terminal 7 as a response to the payout agency request ( Step S55). At this time, when the storage agent device 6 receives the deposit certificate 74 from the TST storage server 5, the TST withdrawal agent unit 41 similarly transmits the received deposit certificate 74 to the user terminal 7. Further, when the storage agent device 6 receives the history of payout results from the TST storage server 5, the storage history processing unit 42 stores the history of payout results in the customer history DB 44 (step S56).

When the user terminal 7 receives the TST file 73 (payout TST file 73) paid out from the TST storage server 5 from the storage agent device 6 (step S43), the time stamp verification unit 62 uses the payout TST file 73, The management target file 70 is verified.

Specifically, the time stamp verification unit 62 extracts the digital certificate included in the TST72 (payout TST72) of the payout TST file 73, and confirms that the electronic certificate has not expired and that the digital certificate has expired. Make sure you are not. The time stamp verification unit 62 verifies that the signature of the digital certificate is normal, and further verifies the signature of the payout TST 72 using the public key of the normal digital certificate. The time stamp verification unit 62 acquires the hash value 71 included in the payout TST 72 (step S44). Then, the time stamp verification unit 62 compares the hash value 71 calculated from the management target file 70 to be verified with the hash value 71 acquired from the payout TST 72, and the existence proof and integrity proof of the management target file 70, etc. Is verified (step S45).

The user terminal 7 displays the verification result of the managed file 70 on the display unit 55 (step S46), and the verification process ends. When the payout result of the TST file 73 from the TST storage server 5 is NG, the user terminal 7 displays the payout result on the display unit 55 as a verification result.

In this way, the user terminal 7 specifies the management target file 70 (step S2: YES) while the verification software is running (step S1, step S7: NO), and operates the “collective verification” on the context menu. By (step S5: YES), the TST file 73 can be paid out from the TST storage server 5 via the storage agent device 6 and the management target file 70 can be verified.

As described above, according to the present embodiment, the time stamp storage agent system 1 is a user who requests the deposit or withdrawal of the TST file 73 including the TST 72 added to the management target file 70 that is the time stamp management target. The terminal 7 and the TST storage server 5 that deposits or withdraws the TST file 73 in response to a deposit or withdrawal request from the user terminal 7 are provided. The time stamp storage agent system 1 further includes a storage agent device 6 communicably connected to the user terminal 7 and the TST storage server 5 via a predetermined network 8. When the storage agent device 6 receives the deposit request from the user terminal 7 together with the TST file 73, the storage agent device 6 deposits the TST file 73 for the TST storage server 5, and also stores the TST file 73 from the user terminal 7. When the payout agency request is received together with the payout identification information, the TST file 73 based on the payout identification information is paid out from the TST storage server 5.

With such a configuration, in the time stamp storage agent system 1 according to the present embodiment, the user obtains the one-time password and stores it in the TST storage server 5 every time the storage processing such as depositing and withdrawing the TST file 73 is performed. There is no need to log in and do other work. Therefore, the user can smoothly deposit and withdraw the TST file 73, and can use the time stamp storage service without feeling trouble and trouble, which promotes the use of the time stamp storage service. be able to. In this way, while maintaining the security of the time stamp storage organization, the TST 72 added to the management target file 70 can be easily and appropriately deposited and withdrawn to the TST storage server 5 of the time stamp storage organization. .

Further, in the present embodiment, in the time stamp storage agent system 1, the user terminal 7 directly requests the TST storage server 5 to deposit the TST file 73 when the corresponding managed file 70 is designated. And an indirect deposit agent request via the storage agent device 6 to the TST storage server 5 are selectable.

With such a configuration, with respect to the deposit of the TST file 73, it is possible to use both automatic deposit via the storage agent device 6 and manual deposit by directly accessing the TST storage server 5, which is convenient. Can be improved.

Further, in the present embodiment, in the time stamp storage agent system 1, the user terminal 7 instructs the TST storage server 5 to perform the storage agent device when the original managed file 70 is designated for the payout of the TST file 73. Indirect withdrawal agent request via 6 is selectable.

With such a configuration, with respect to the payout of the TST file 73, the automatic payout via the storage agent device 6 can be selectively used, and the convenience can be improved.

Further, in the present embodiment, in the time stamp storage agency system 1, the storage agency apparatus 6 stores the history of deposit or withdrawal agency requests by the user terminal 7 and the execution result by the TST archive server 5 for the deposit or withdrawal requests. Is provided for each user account of the user terminal 7 with a customer history DB 44.

With such a configuration, the storage agent manages and confirms the customer history DB 44 for the TST file 73 deposited in the TST storage server 5, so that the convenience of the user is improved and the mistaken deposit and the omission of deposit are prevented. Can contribute to. Further, even when a plurality of TST files 73 are generated and stored for the same management target file 70, the storage agent device 6 confirms the time information of each TST file 73 by referring to the customer history DB 44. be able to. Therefore, the storage agent device 6 can determine the oldest (first) TST file 73 at the time of paying out the TST file 73, and the convenience of paying out the TST file 73 by the user is improved, and the TST file 73 It can contribute to the prevention of payout errors. In addition, the customer history DB 44 can store the charging status regarding the use of the deposit agent and the withdrawal agent of the storage agent device 6, which can contribute to the operation of the storage agent device 6.

In the above embodiment, an example has been described in which the proxy system utilization program displays a context menu on the display unit 55 as an interface that receives operations of various processes, but the present invention is not limited to this example. For example, in another embodiment, the proxy system utilization program may operably display the same operation items as those in the context menu on the menu of software for verifying, browsing, and editing the managed file 70. .. Further, the proxy system utilization program may automatically execute any operation item when the management target file 70 is processed by this software. Further, in a further embodiment, the proxy system utilization program is configured by an application that displays an operation screen on the display unit 55 when activated on the user terminal 7, and even if operation keys for various processes are displayed on the operation screen. Good.

In the above-described embodiment, the TST deposit agency request unit 61 and the TST withdrawal agency request unit 64 of the user terminal 7 together with the deposit agency request and the withdrawal agency request together with the user account including the “account ID” 86 and the “password” 87. Although an example of transmitting a message has been described, the present invention is not limited to this example. For example, in another embodiment, the user terminal 7 includes a “account ID” 86 and a “password” 87 when the proxy system management program is activated or when the “account ID” 86 and the “password” 87 are set. The user account may be transmitted to the storage agent device 6 and stored in advance as customer information for each user.

In the above-described embodiment, the TST deposit agency request unit 61 or the TST withdrawal agency request unit 64 of the user terminal 7 transmits the “TST file withdrawal target” 92 and the “issue of deposit certificate” 93 together with the withdrawal agency request. However, the present invention is not limited to this example. For example, in another embodiment, the user terminal 7 sets the “TST file withdrawal target” 92 and the “deposit certificate” when the proxy system management program is activated or when the “account ID” 86 and the “password” 87 are set. It is also possible to transmit “issue or not” 93 to the storage agent device 6 and store it in advance as customer information for each user.

In the above-described embodiment, the storage agent device 6 has been described as an example of performing deposit and withdrawal of the TST file 73, but the present invention is not limited to this example, and the user terminal 7 is conventionally the TST storage server 5. The storage agent device 6 can act on behalf of various processes that have been performed directly by communication. For example, when issuing only a deposit certificate for the TST file 73 deposited in the TST storage server 5, the user terminal 7 sends a proxy request for issuing a certificate to the storage agent device 6. Good.

For example, the user terminal 7 can instruct a substitute certificate issuance request by the operation of “issue deposit certificate” in the context menu described above. The proxy request for issuing the certificate includes the payout identification information such as the hash value 71 of the original management target file 70 and the user account of the user who requests the payout, as in the case of the payout proxy. The storage agent device 6 grasps the management number of the TST file 73 based on the payout identification information, and requests the TST storage server 5 to issue a certificate based on this management number, as in the case of the payment agent. If the TST file 73 corresponding to this management number is deposited, the TST storage server 5 generates a deposit certificate and sends it to the user terminal 7 via the storage agent device 6. This improves the convenience of the user in issuing the deposit certificate of the TST file 73.

In another embodiment, when the user terminal 7 directly (manually) communicates with the TST storage server 5 to make a deposit request or withdrawal request for the TST file 73, the user terminal 7 receives a deposit result or a deposit result from the TST storage server 5. The history of payout results may be received and stored in the storage unit 52. The user terminal 7 communicates with the storage agent device 6 when the deposit result history is accumulated for a predetermined amount or for a predetermined period, and transmits the accumulated deposit result history to the storage agent device 6. When receiving the history of the deposit result from the user terminal 7, the storage agent device 6 stores the history of the deposit result while checking it against the history already stored in the customer history DB 44. As a result, the deposit result and the payout result of each TST file 73 of each user can be stored and managed in the customer history DB 44 without any shortage, regardless of whether it is manual or automatic.

Alternatively, in another embodiment, the storage agent device 6 and the TST storage server 5 are configured to periodically synchronize the history of deposit results and withdrawal results, and the storage agent device 6 is always provided to each user. The deposit result and the payout result of each TST file 73 may be stored and managed in the customer history DB 44 regardless of whether it is manual or automatic.

Further, in another embodiment, when the TST storage server 5 has a predetermined deadline (for example, 10 years) for depositing the TST file 73, the storage agent device 6 determines that the deposit deadline has been reached for each TST file 73. Previously, the deposit deadline approach notification is configured to be received from the TST storage server 5. In this case, the TST storage server 5 records the TST file 73 deposited from the storage agent device 6 in association with the storage agent device 6 (company account) using the company information DB 25 and the storage DB 27. .. As a result, the TST storage server 5 can determine which storage proxy device 6 should be notified of the TST file 73 whose deposit deadline is approaching.

When receiving the notice of approaching the deposit deadline of the TST file 73 from the TST storage server 5, the storage agent device 6 notifies the corresponding user terminal 7 of the approach of the deposit deadline. Further, the user terminal 7 can preset automatic updating of the storage agent device 6 for depositing the TST file 73. In this case, the storage agent device 6 automatically updates the deposit of the TST file 73 when it receives the deposit deadline approach notification of the TST file 73 from the TST storage server 5. The storage agent device 6 may notify the user terminal 7 of the schedule of the automatic update before the update, or notify the user terminal 7 of the completion of the automatic update after the update.

Further, the present invention can be appropriately modified without departing from the scope or spirit of the invention that can be read from the claims and the entire specification, and the time stamp storage agent system and agent system management program accompanied by such changes. Also, a substitute system utilization program is also included in the technical idea of the present invention.

INDUSTRIAL APPLICABILITY The present invention can be used for management and operation of digitized intellectual property documents, tax documents, medical documents, etc., and stores a time stamp token added to an electronic file in a time stamp storage organization. In this case, it can be used as a means for extracting the time stamp token from the electronic file.

1 Timestamp system 2 Timestamp token issuing server (TST issuing server)
5 Timestamp token storage server (TST storage server)
6 Storage agent device 7 User terminal 8 Network 18 Account management unit 19 Login processing unit 20 TST depositing unit 21 TST issuing unit 22 Certificate issuing unit 23 Storage history processing unit 25 Business information database (DB)
26 User Information Database (DB)
27 Storage database (DB)
38 Account Management Department 39 Login Processing Department 40 TST Deposit Agency Department 41 TST Withdrawal Agency Department 42 Storage History Processing Department 44 Customer History Database (DB)
58 account management unit 59 time stamp addition unit 60 TST deposit request unit 61 TST deposit agency request unit 62 time stamp verification unit 63 TST withdrawal request unit 64 TST withdrawal agency request unit 70 managed file 71 hash value 72 time stamp token (TST)
73 Time Stamp Token (TST) File 74 Deposit Certificate

Claims (8)

Depending on the user terminal requesting deposit or withdrawal of the time stamp token file consisting of the time stamp token added to the management target file to be time stamp managed, and the deposit or withdrawal request by the user terminal A time stamp storage agent system comprising a time stamp token storage server for depositing or withdrawing the time stamp token file,
A storage agent device further communicably connected to the user terminal and the time stamp token storage server via a predetermined network,
When the storage agent device receives the depositing request together with the time stamp token file from the user terminal, it delegates the depositing of the time stamp token file to the time stamp token storage server,
In addition, when receiving the payout identification request together with the payout identification information of the time stamp token file from the user terminal, the payout from the time stamp token storage server of the time stamp token file based on the payout identification information is performed. A time stamp storage agent system characterized by acting on your behalf. Regarding the deposit of the time stamp token file, the user terminal requests a direct deposit to the time stamp token storage server and the time stamp token storage server when the corresponding management target file is designated. The time stamp storage agent system according to claim 1, wherein an indirect deposit agent request via the storage agent device can be selected. Regarding the withdrawal of the time stamp token file, the user terminal indirectly requests the time stamp token storage server via the storage agent device when the original management target file is specified. 3. The time stamp storage agent system according to claim 1, wherein the time stamp storage agent system is configured to be selectable. The storage agent device displays the history of the deposit request or the withdrawal request by the user terminal and the execution result of the time stamp token storage server for the deposit or withdrawal request to the user of the user terminal. The time stamp storage agent system according to any one of claims 1 to 3, further comprising a customer history database for recording each account. Depending on the user terminal requesting deposit or withdrawal of the time stamp token file consisting of the time stamp token added to the management target file to be time stamp managed, and the deposit or withdrawal request by the user terminal A proxy system management program in a proxy system for time stamp storage, comprising: a time stamp token storage server for depositing or withdrawing the time stamp token file,
When a storage agent device communicatively connected to the user terminal and the time stamp token storage server via a predetermined network receives the deposit request together with the time stamp token file from the user terminal. Acting the depositing of the time stamp token file to the time stamp token storage server,
When the storage agent device receives the payout agency request together with the payout identification information of the time stamp token file from the user terminal, from the time stamp token storage server of the time stamp token file based on the payout identification information. A step of substituting the above-mentioned payout of
A program to be executed by a computer of the storage agent device. Customer history database for each user account of the user terminal, the history of the deposit or withdrawal proxy request by the user terminal, and the execution result of the time stamp token storage server for the deposit or withdrawal request. The steps to record in
The program according to claim 5, which is executed by a computer of the storage agent device. Depending on the user terminal requesting deposit or withdrawal of the time stamp token file consisting of the time stamp token added to the management target file to be time stamp managed, and the deposit or withdrawal request by the user terminal A proxy system using program in a proxy system for time stamp storage, comprising: a time stamp token storage server for depositing or withdrawing the time stamp token file,
Regarding the deposit of the time stamp token file, when the time stamp token file is specified in the user terminal, a direct deposit request to the time stamp token storage server, and to the time stamp token storage server, A step of causing the user terminal and the time stamp token storage server to select an indirect deposit service request via a storage service device communicatively connected via a predetermined network,
A program to be executed by a computer of the user terminal. Depending on the user terminal requesting deposit or withdrawal of the time stamp token file consisting of the time stamp token added to the management target file to be time stamp managed, and the deposit or withdrawal request by the user terminal A proxy system using program in a proxy system for time stamp storage, comprising: a time stamp token storage server for depositing or withdrawing the time stamp token file,
Regarding the payout of the time stamp token file, when the original managed file is specified in the user terminal, the user terminal and the time stamp token storage server are notified to the time stamp token storage server. A step of selecting an indirect withdrawal agent request via a storage agent device communicatively connected via a predetermined network,
A program to be executed by a computer of the user terminal.

Images