JP2005242910A - Validity guarantee system, third party document conversion guarantee server and validity guarantee method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a validity guarantee system for guaranteeing the validity of conversion processing for an electronic document, and to provide a third party document conversion guarantee server and a validity guarantee method. <P>SOLUTION: An unconverted document acquiring part 41 of a third party organization server 40 acquires an XML document D 21 issued by an SP 10 from a document conversion server 20. A conversion specification acquiring part 42 acquires an XSL document D 12 from the SP 10. A converted document acquiring part 43 acquires an HTML (hypertext markup language) document 33 obtained by using the XSL document D 12 to apply conversion processing to the XML document D 21 from an electronic signature terminal 30. A second converting part 45 uses the XSL document D 12 to apply conversion processing to the XML document D 21, and a matching part 46 matches a conversion processing result to the HTML document 33. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to an electronic document conversion validity guarantee system, a third-party document conversion guarantee server, and a validity guarantee method in a client-server electronic signature scheme.

In recent years, electronic commerce using the Internet has become popular, and between a server (hereinafter referred to as “SP”) owned by an SP (service provider) or CP (content provider) and a communication terminal owned by a user. Electronic documents, such as contracts and application forms, that need to be signed by the user are exchanged. Under such circumstances, the format of the electronic document issued by the SP is mainly the XML format (for example, Patent Document 1). However, current mobile devices do not support XML documents, but only HTML documents. For this reason, even if the mobile device or the like receives the XML document from the SP, it cannot display the XML document on the screen. As a method for stamping an electronic signature in such a mobile device or the like, a method is adopted in which a document conversion server for performing electronic document conversion processing is interposed between the mobile device and the SP. In this method, the document conversion server performs processing for converting the XML-format electronic signature request document received from the SP into an HTML document, and then transmits it to the mobile device or the like. Accordingly, the mobile device or the like can display the received signature request document in the HTML format on the display, and the user confirms whether or not the displayed electronic signature request document can be signed.
JP 2002-91303 A (summary)

The problem here is whether or not the signature request document displayed on the mobile device or the like is the same as the signature request document issued by the SP, and it may have been altered in the middle. This is the point. When a server that performs conversion processing of an electronic document is interposed between the SP and the mobile device, the legitimacy of document correspondence before and after the conversion processing becomes a problem.
The present invention has been made in view of the technical problems such as the above-described background, and includes a validity guarantee system, a third party document conversion guarantee server, and a legitimacy server for guaranteeing the validity of conversion processing for an electronic document. The purpose is to provide a sex guarantee method.

  In order to solve the above-mentioned problem, the invention described in claim 1 is the electronic document conversion validity assurance system including a first conversion unit that performs conversion processing of an electronic document using a predetermined conversion specification document. Second conversion means for performing conversion processing on the same electronic document as the electronic document using the same conversion specification document as the conversion specification document in an apparatus different from the apparatus including the first conversion means; A matching unit that matches a result of the conversion process by the first conversion unit and a result of the conversion process by the second conversion unit, and guarantees the validity of the electronic document conversion by the matching result by the matching unit; The validity guarantee system characterized by this is provided.

  According to the first aspect of the present invention, an apparatus different from the apparatus including the first conversion unit converts the same electronic document by using the same conversion specification document by the second conversion unit. And confirming whether or not the results of the conversion processing performed by the two devices match in order to match the result of the conversion processing by the first conversion means and the result of the conversion processing by the second conversion means. it can. For this reason, even when the reliability of the conversion result by the first conversion means is low, it is possible to detect processing errors, tampering, etc. by the first conversion means, and to prevent the user from excluding repudiation A server-type electronic signature method can be realized.

  According to a second aspect of the present invention, there is provided a third-party document conversion assurance server that guarantees the validity of conversion processing for an electronic document, a pre-conversion document acquisition means for acquiring a first electronic document, and the first electronic document Conversion specification acquisition means for acquiring a conversion specification document used to perform conversion processing on the electronic document, and an external device for the same electronic document as the first electronic document acquired by the pre-conversion document acquisition means A post-conversion document acquisition unit that acquires a post-conversion electronic document that is a result of performing a conversion process using the same conversion specification document as the conversion specification document acquired by the conversion specification acquisition unit; and the pre-conversion document acquisition unit Conversion means for performing conversion processing on the first electronic document acquired by the conversion specification document acquired by the conversion specification acquisition means, the result of the conversion processing by the conversion means, and the post-conversion Providing a third-party document conversion assurance server, characterized in that it comprises a butting means that Tsukiawasu the converted electronic document acquired by writing acquisition means.

  According to the second aspect of the invention, the third-party document conversion assurance server performs the same conversion process as the conversion process performed by the external apparatus using the same document as the document used by the external apparatus, In order to match the result of the conversion process performed by the apparatus, the validity of the electronic document conversion process performed by the external apparatus can be confirmed. For this reason, it is possible to prevent the electronic document from being falsified by the external device and to ensure the validity.

According to a third aspect of the present invention, in the third-party document conversion assurance server according to the second aspect, the predetermined electronic document is an XML document, the predetermined conversion specification document is an XSL document, and the post-conversion The electronic document is an HTML document.
According to the third aspect of the present invention, when the external device generates an HTML document by performing conversion processing on the XML document using the XSL document, the third-party document conversion assurance server A similar conversion process is performed to confirm the validity of the HTML document generated by the external device. Thereby, for example, it is possible to prevent the portable terminal from receiving and displaying an illegal HTML document from an external device, and to prevent the user from signing the illegal document.

According to a fourth aspect of the present invention, there is provided a third-party document conversion assurance server that guarantees the validity of the conversion process in an external device including a first conversion unit that performs conversion processing of an electronic document using a one-way function. A conversion process using the same function as the one-way function used by the first conversion unit for the same electronic document as that used by the first conversion unit included in the external device. Second conversion means for performing the above, and a butt means for matching the result of the conversion process by the first conversion means and the result of the conversion process by the second conversion means, and depending on the butt result by the butt means Provided is a third-party document conversion assurance server characterized by ensuring the validity of conversion processing.
According to the invention described in claim 4, when the external device generates a calculation value using a one-way function, the third-party document conversion assurance server performs the same process as the external device, so that the external device The correctness of the generated calculation value can be confirmed.

The invention according to claim 5 is the validity guarantee method for guaranteeing the validity of the conversion process in the first conversion step of performing the conversion process on a predetermined electronic document using a predetermined conversion specification document. A second apparatus, which is different from the apparatus that executes the first conversion step, performs a conversion process on the same electronic document as the predetermined electronic document using the same conversion specification document as the predetermined conversion specification document. And the different device has a butt step for matching the result of the conversion process in the first conversion step and the result of the conversion process in the second conversion step, and the butt result in the butt step The validity guarantee method is characterized by guaranteeing the validity of the conversion process.
The operation and effect of the invention of claim 5 are the same as those of claim 1.

  According to a sixth aspect of the present invention, there is provided an electronic document issuing server that requests an electronic signature to be issued to an electronic document issued by the server, an electronic signature terminal that assigns an electronic signature to the electronic document, and the electronic document issuing server. In a validity assurance system comprising: a document conversion server that performs conversion processing of an electronic document exchanged with the electronic signature terminal, wherein a third-party document conversion assurance server guarantees the validity of the conversion processing of the electronic document The third-party document conversion assurance server is used for pre-conversion document acquisition means for acquiring an electronic document issued by the electronic document issuance server, and for conversion processing of the electronic document issued by the electronic document issuance server. Conversion specification acquisition means for acquiring a conversion specification document, and the electronic document issued by the electronic document issuance server A converted specification document acquired by the conversion specification acquiring unit with respect to the electronic document acquired by the converted document acquiring unit that acquires a converted electronic document that is a result of conversion processing using Conversion means for performing a conversion process using the conversion means, and a matching means for matching the result of the conversion process by the conversion means with the converted electronic document acquired by the converted document acquisition means Provide the system.

  According to the invention described in claim 6, since the third-party document conversion guarantee server matches the result of the same conversion processing in the server and the document conversion server, the electronic document conversion server is valid for the electronic document conversion processing. Sex can be confirmed. For this reason, it can be ensured that the electronic document provided by the electronic document issuing server is transmitted to the electronic signature terminal as intended, and the post-processing of the falsification of the document in the document conversion server and the signature of the malicious user Denial can be prevented. In this way, it is possible to improve the security of the client server type digital signature method with the document conversion server interposed therebetween.

  According to the present invention, an apparatus different from the apparatus including the first conversion unit performs the same conversion process as the conversion process performed by the first conversion unit by the second conversion unit, and performs the first conversion. Since the conversion result by the means and the conversion result by the second conversion means are matched, it can be confirmed whether or not the results of the conversion processing in the two apparatuses match, and the validity of the conversion processing of the electronic document is guaranteed. can do. For this reason, even when the reliability of the conversion result by the first conversion means is low, it is possible to detect processing errors, tampering, etc. by the first conversion means, and to prevent the user from excluding repudiation A server-type electronic signature method can be realized.

Next, the best mode for carrying out the present invention will be described with reference to the drawings. In each drawing referred to in the following description, the same reference numerals are given to the same parts as in the other drawings.
[1. Constitution]
[1.1. overall structure]
FIG. 1 is a diagram showing an overall configuration of an electronic document conversion validity assurance system according to the present embodiment. The legitimacy guarantee system is a system for guaranteeing legitimacy of electronic document conversion in the client-server type digital signature method. As shown in the figure, the validity assurance system includes an SP 10 that is a server managed and operated by an SP or CP, a document conversion server 20 that performs an electronic document conversion process, and an electronic signature issued to an electronic document issued by the SP 10. And a third-party organization server 40 managed and operated by a notary public authority that is a third-party organization. Between these devices, communication with a high security level by SSL (Secure Socket Layer) is performed.

  In such a validity guarantee system, the SP 10 transmits an electronic document issued to the electronic signature terminal 30 to the document conversion server 20 as a relay server. The document conversion server 20 transmits the received electronic document to the electronic signature terminal 30 after performing format conversion and extraction of characteristic portions. In the present embodiment, the document conversion server 20 reduces the document processing burden on the electronic signature terminal 30 by converting an XML document into an HTML document. In the present invention, the third party server 40 ensures the validity of the electronic document displayed on the electronic signature terminal 30 by guaranteeing the validity of the document conversion process performed by the document conversion server 20. .

The SP 10, the document conversion server 20, the electronic signature terminal 30, and the third party institution server 40 are configured to include a CPU (Central Processing Unit), a memory, and a communication interface, and have a general computer hardware configuration. Have.
The SP 10 is a server that issues an electronic document described in XML format, such as a contract or an application, and requests the user of the electronic signature terminal 30 to sign the issued electronic document. The SP 10 requests the third party server 40 to store and guarantee the electronic document issued by the own device 10.

The document conversion server 20 includes a conversion unit (first conversion unit) 21 for performing conversion processing of the electronic document received from the SP 10.
The electronic signature terminal 30 is a general mobile device equipped with a UIM (User Identity Module). The UIM stores a secret key for performing a signature calculation. The electronic signature terminal 30 cannot display an XML document because it does not support an XML document, but can display an HTML document because it corresponds to an HTML document.
The third-party organization server 40 is a server managed and operated by a reliable third-party organization, and is a server (third-party document conversion assurance server) for guaranteeing the validity of electronic document conversion.

(Prerequisite client-server digital signature method)
Next, a premise of the client server type digital signature method will be described with reference to FIG.
First, the SP 10 issues an XML document D11 such as an application form or a contract to the electronic signature terminal 30. Further, the SP 10 issues an XSL document D12 that is a conversion specification of the XML document D11. The SP 10 transmits the XML document D11 and the XSL document D12 to the document conversion server 20 (step S1).

  The document conversion server 20 receives the XML document D11 and the XSL document D12 transmitted by the SP 10 (hereinafter, the XML document D11 received by the document conversion server 20 is referred to as “XML document D21”, and the document conversion server 20 receives the XML document D11. XSL document D12 is referred to as “XSL document D22”). The first conversion unit 21 of the document conversion server 20 performs conversion processing on the XML document D21 using the XSL document D22, and generates an HTML document D23. The document conversion server 20 transmits the generated HTML document D23 to the electronic signature terminal 30 (step S3).

The electronic signature terminal 30 receives the HTML document D23 transmitted from the document conversion server 20 (hereinafter, the HTML document D23 received by the electronic signature terminal 30 is referred to as “HTML document D33”). The electronic signature terminal 30 displays the received HTML document D33 on the display of the terminal 30 itself. The user confirms the contents displayed on the display and inputs necessary items such as an address, name, and amount.
As a result, the electronic signature terminal 30 embeds the input data D341 input by the user in a predetermined position of the HTML document D33, thereby generating the input HTML document D34 (step S4). The electronic signature terminal 30 transmits the input HTML document D34 to the document conversion server 20.

  The document conversion server 20 receives the input HTML document D34 transmitted by the electronic signature terminal 30 (hereinafter, the input HTML document D34 received by the document conversion server 20 is referred to as “input HTML document D24”). The document conversion server 20 extracts the input data D241 embedded in a predetermined part from the input HTML document D24. (Step S5). The document conversion server 20 generates the input XML document D25 by embedding the extracted input data D241 in the XML document D21. The document conversion server 20 transmits the generated input XML document D25 to the SP10.

The SP 10 receives the input XML document D25 transmitted from the document conversion server 20 (hereinafter, the input XML document D25 received by the SP 10 is referred to as “input XML document D15”). The SP 10 confirms the content of the input data based on the input XML document D15 (step S6).
On the other hand, the document conversion server 20 generates a hash value D26 by performing an operation on the input XML document D25 using a hash function in a public key cryptosystem known in the art (step S7). The document conversion server 20 transmits the generated hash value D26 to the electronic signature terminal 30 (step S8).

  The electronic signature terminal 30 receives the hash value D26 transmitted from the document conversion server 20 (hereinafter, the hash value D26 received by the electronic signature terminal 30 is referred to as “hash value D36”). The electronic signature terminal 30 generates a signature value D37 by performing a signature operation on the received hash value D26 using a secret key (step S9). The electronic signature terminal 30 transmits the generated signature value D37 to the document conversion server 20 (step S10).

The document conversion server 20 receives the signature value D37 transmitted from the electronic signature terminal 30 (hereinafter, the signature value D37 received by the document conversion server 20 is referred to as “signature value D27”). The document conversion server 20 generates an XML signature D28 that includes the received signature value D27 and the input XML document D25 (step S11). The document conversion server 20 transmits the generated XML signature D28 to the SP 10 (step S12).
The SP 10 receives the XML signature D28 transmitted from the document conversion server 20 (hereinafter, the XML signature D28 received by the SP 10 is referred to as “XML signature D18”, and the signature value D27 included in the XML signature D28 received by the SP 10). Is referred to as “signature value D17”). The SP 10 verifies the received XML signature D18 (step S13).

(Role of third-party organization)
Next, the role of the third party organization server 40 in the client server type electronic signature method will be described. In the electronic signature method, there are two items to be certified by the third party institution server 40: (1) presence / absence of falsification of the document by the document conversion server 20 and (2) post-repudiation by the user.
The following two points can be said to prove (1).
(A) The electronic document D11 sent by the SP 10 has correctly arrived at the user's electronic signature terminal 30. (a) The signature D37 signed by the user is securely stamped on the target signature target document D25.

As for (a), the XML document D21 received by the document conversion server 20 from the SP10 and the XSL document D12 issued by the SP10 and the HTML document D33 received by the electronic signature terminal 30 used by the user are converted into a third party server. It can be assured by depositing them at 40 and taking their correspondence (see FIG. 3 and FIG. 4A).
As a method of taking the correspondence, the third-party server 40 again confirms that the expression method of the document by the XSL document D12 and the XML document D21 as the document contents and the HTML document D33 as these two conversions are equal. Confirm by performing the conversion process, and guarantee the correctness of document correspondence before and after conversion.

Also, in (A), whether the signature D37 that the user has made is securely applied to the target signature target document D25, that is, whether any signature value D27 has been tampered with in the document conversion server 20. Explain how to guarantee what you say.
First, the electronic signature terminal 30 stores the input HTML document D34 in which the input data D341 is embedded in the HTML document D33 in the third party server 40. Further, the electronic signature terminal 30 stores the hash value D36 transmitted from the document conversion server 20 in the third party institution server 40. Also, the SP 10 stores the input XML document D15 sent from the document conversion server 20 as a part of the XML signature D18 in the third party server 40. (See FIG. 3 and FIG. 4 (b))

  As a guarantee method, the third-party organization server 40 again generates an input XML document from the input HTML document D34 in the same procedure as the document conversion server 20. Then, the generated input XML document D15 collates with the stored input XML document D15, and by confirming that it matches, the validity of the input XML document D15 can be guaranteed.

Further, the third party server 40 generates a hash value by applying the hash function to the input XML document D15 again in the same procedure as the document conversion server 20. Then, the validity of the hash value D36 can be guaranteed by matching the generated hash value with the stored hash value D36 and confirming that they match.
In addition, it can be said that the signature value D37 generated by the electronic signature terminal 30 using the secret key based on the hash value D36 has correctly arrived at the SP 10 because the above (a) can be said.

Next, the following three points can be considered for the item (2) of the refusal by the user, and the following measures can be considered for each.
(A) Denying the identity (denying the connection between the user and the private key stored in the UIM attached to the electronic signature terminal 30)
(B) Denial of signed document (claim for falsification of document)
(C) Denial of the fact of signing

As for (a), since the connection between the person and the private key stored in the UIM can be guaranteed by the PIN (Personal Identification Number) code, there is no need for other measures by using the PIN code. Absent.
With regard to (a), it is possible to take a denial measure by guaranteeing that the document conversion server 20 has not tampered with the fact that the fact that the signature has been made is guaranteed by the system.
As for (c), a guarantee is made systematically by guaranteeing that the document conversion server 20 has not tampered with and a model in which the user holds the secret key and has the authority to determine the signature. Can take.

[1.2. Third party server]
Next, the configuration of the third party organization server 40 will be described in detail. Software such as various programs and data is stored in a memory such as a hard disk provided in the third party organization server 40. The function unit shown in FIG. 5 is realized by the function realized by the CPU of the third-party server 40 executing a program stored in the memory and the software and hardware functions of the third-party server 40. It is realized in the third party server 40.

The pre-conversion document acquisition unit 41 acquires a first electronic document before conversion processing. The “first electronic document” in the present embodiment is an XML-format electronic document issued by the SP 10.
The conversion specification acquisition unit 42 acquires a conversion specification document for performing conversion processing on the first electronic document. The “conversion specification document” in the present embodiment is an XSL document issued by SP10.

  The converted document acquisition unit 43 converts the same electronic document as the first electronic document acquired by the pre-conversion document acquisition unit 43 into the same conversion specification document acquired by the conversion specification acquisition unit 42 in the external device. Using the specification document, a converted electronic document that is a result of the conversion process is acquired. The “converted electronic document” in the present embodiment is an HTML document generated by the document conversion server 20 performing conversion processing on the XML document using the XSL document.

  The document storage unit 44 includes a database (DB) provided on the hard disk. The document storage unit 44 stores each electronic document acquired by the pre-conversion document acquisition unit 41, the conversion specification acquisition unit 42, and the post-conversion document acquisition unit 43 in association with each other. At this time, the document storage unit 44 stores the electronic document together with the sender's ID. In addition to the sender ID, the electronic document may be managed together with information shared in advance between the SP 10 and the electronic signature terminal 30 (for example, the electronic document ID, transaction ID, etc.). Further, the document storage unit 44 may store the document after applying a signature such as a time stamp.

  The conversion unit (second conversion unit) 45 is a document conversion server for assuring the validity of the document conversion process of the document conversion server 20 based on requests from the SP 10, the user of the digital signature terminal 30, and other organizations. The same document conversion processing is performed using the same data as that of the first 20 conversion unit 21. Specifically, the second conversion unit 45 uses the conversion specification document acquired by the conversion specification acquisition unit 42 to perform conversion processing on the electronic document acquired by the pre-conversion document acquisition unit 41. In the present embodiment, the second conversion unit 45 generates an HTML document by performing conversion processing on the XML document using the XSL document.

The collation unit 46 collates the converted electronic document generated as a result of the conversion processing by the conversion unit 45 and the converted electronic document acquired by the converted document acquisition unit 43. Here, “match” is to confirm whether or not they match by comparing two electronic documents.
The abutment result output unit 47 outputs the result of the abutment unit 46 abutting. Specifically, the matching result output unit 47 determines that the converted document when the conversion processing result of the second conversion unit 45 matches the converted electronic document acquired by the converted document acquisition unit 43. Information that proves the authenticity of the converted electronic document acquired by the acquisition unit 43 is output. On the other hand, if the conversion processing result of the second conversion unit 45 and the converted electronic document acquired by the converted document acquisition unit 43 do not match, the converted electronic document acquired by the converted document acquisition unit 43 is Outputs information indicating that the file has been tampered with.

  Further, the memory of the third-party organization server 40 includes a program for generating a hash value by performing an operation using a hash function, similar to the document conversion server 20. Here, the hash function is a function / procedure for summarizing an electronic document into data of a certain length in a public key encryption method. A hash function is a kind of one-way function (also called a one-way function). The one-way function is a function in which it is easy to calculate y from x in the function y = f (x), but it is practically impossible to calculate x from y.

[2. Operation]
Next, with reference to FIG. 2 and FIG. 6, a procedure for guaranteeing the electronic document of the third-party organization server 40 when generating the electronic signature will be described.
As shown in steps S1 to S3 in FIG. 2, in order for the document conversion server 20 to perform processing for converting the XML-format electronic document D21 into the HTML-format electronic document D23, conversion is possible by using an XSL file. is there. For this reason, the XSL file for conversion is shared between the SP 10 and the document conversion server 20. Further, the third-party organization server 40 shares the XSL file shared by the SP 10 and the document conversion server 20. The second conversion unit 45 of the third-party server 40 generates an HTML-format electronic document using the XML-format electronic document D21 and the XSL file D12. Then, the collation unit 46 collides the generated HTML-format electronic document with the HTML-format electronic document D33 sent from the digital signature terminal 30 and managed by the document storage unit 44, whereby the document conversion server 20. The validity of the document conversion process in the first conversion unit 21 is guaranteed.

  A mechanism for storing the electronic document before and after conversion in the third-party organization server 40 and guaranteeing its validity will be described in further detail using the flow shown in FIG. First, the SP 10 makes an electronic signature request to the electronic signature terminal 30 (step S201). Specifically, the SP 10 transmits, to the document conversion server 20, an XML document D11 that is an electronic document to be signed and an XSL document D12 that is a conversion specification of the XML document D11 to the document conversion server 20 ( Step S1) in FIG. The SP 10 sends the XSL document D12, which is the conversion specification document of the electronic document provided to the document conversion server 20, to the third party organization server 40 (step S202). The conversion specification acquisition unit 42 of the third party organization server 40 receives the XSL document D12 from the third party organization server 40.

On the other hand, when the document conversion server 20 receives the XML document D21 from the SP 10, the document conversion server 20 sends the XML document D21 to the third-party organization server 40 (step S203). The pre-conversion document acquisition unit 41 of the third party institution server 40 receives the XML document D21 from the document conversion server 20.
The first conversion unit 21 of the document conversion server 20 generates an HTML document D23 by performing conversion processing on the XML document D21 using the XSL document D22 (step S2 in FIG. 2). The document conversion server 20 transmits the generated HTML document D23 to the electronic signature terminal 30 (step S3 in FIG. 2).

Upon receiving the HTML document D33, the electronic signature terminal 30 sends the HTML document D33 to the third party server 40 (step S204 in FIG. 6). The post-conversion document acquisition unit 43 of the third party institution server 40 receives the HTML document D33.
The third party server 40 receives the XML document D21 received by the pre-conversion document acquisition unit 41, the XSL document D12 received by the pre-conversion document acquisition unit 41, and the HTML document D33 received by the post-conversion document acquisition unit 43. Correspondingly, the document is stored in the document storage unit 44 (step S205).

  Next, the procedure in which the third party server 40 confirms the authenticity (validity) of the HTML document D33 according to an external request will be described. As shown in FIG. 6B, first, the third-party organization server 40 receives an authenticity confirmation request for the HTML document D33 from the outside (step S301). As a result, the third-party organization server 40 performs an authentication process using the user ID included in the authenticity confirmation request (step S302).

The third-party institution server 40 acquires a pair of the XML document D21 and the XSL document D12 corresponding to the HTML document D33 that has received the authenticity confirmation request from the DB of the document storage unit 44 (step S303).
The second conversion unit 45 of the third party institution server 40 generates an HTML ′ document based on the XML document D21 and the XSL document D12 (step S304).

The collation unit 46 of the third-party organization server 40 collates the generated HTML ′ document with the HTML document 33 stored in the document storage unit 44 in association with the XML document D21 and the XSL document D12 (step S305). .
If the HTML 'document and the HTML document 33 match as a result of the matching (step S305; OK), the third party server 40 authenticates the authenticity of the HTML document 33 to the sender of the authenticity assurance request. Data that proves sex is returned (step S306).

On the other hand, when the HTML ′ document and the HTML document D33 do not match (step S305; NO), the third party server 40 has altered the HTML document 33 with respect to the sender of the authenticity guarantee request. (Step S307).
As another method for confirming authenticity, the following methods are conceivable. That is, the XML-format electronic document D11 sent from the SP 10 and the HTML-format electronic document D33 sent from the digital signature terminal 30 and the document conversion server 20 are managed by the third-party server 40. The third-party organization server 40 uses the XML-format electronic document D21 and HTML document D23 sent to the three-party organization server 40 to ensure the validity of the document conversion processing of the document conversion server 20.

  As a procedure after the converted HTML document D33 is displayed on the electronic signature terminal 30, for example, in order to set the displayed electronic document D33 as the electronic signature target document D34, as assumed in an electronic contract or the like. In some cases, the user needs to input the name, the total deposit amount, and the like. In this case, the user inputs necessary data for the electronic document D33 displayed on the electronic signature terminal 30. As a result, the electronic signature terminal 30 embeds the user input data D341 in a predetermined position of the HTML-format electronic document D33, thereby generating the input HTML document D34 (step S4 in FIG. 2). The electronic signature terminal 30 sends the generated input HTML document D34 generated to the document conversion server 20 and the third party organization server 40.

The document conversion server 20 extracts user input data D241 from the received HTML-formatted user input document D24 (step S5), and embeds it in a predetermined position of the XML-format electronic document D21 obtained from SP10. An electronic signature target document D25 is generated.
Here, in order to guarantee the validity of the generation of the electronic signature target document D25 in the above process, the third party institution server 40 receives the user input from the HTML-type user-input electronic document D24 obtained from the electronic signature terminal 30. Data D241 is extracted. The third party institution server 40 embeds the extracted input data D241 in a predetermined position of the XML document D21 to generate an XML-formatted user-input electronic document. The third-party organization server 40 guarantees the validity of document generation by making the generated XML-formatted user-input electronic document collide with the electronic signature target document D25 obtained from the document conversion server 20.

Further, as shown in steps S7 to S9 in FIG. 2, the document conversion server 20 applies a hash function to the electronic signature target document D25 generated by embedding the user input data D241 in the electronic document D21 provided from the SP10. Is applied to generate a hash value D26.
As a method for assuring the validity of the hash value D26, the XML document electronic document D11 sent from the SP 10 and the HTML format sent from the electronic signature terminal 30 managed by the third-party organization server 40 are used. The third-party institution server 40 has the input electronic document D34 and the hash value D36, and the XML-format electronic document D21, the input HTML document D24, and the hash value D26 sent from the document conversion server 20. Thus, the validity of the document conversion process of the document conversion server 20 is guaranteed.

Alternatively, the third party server 40 generates a hash value by applying a hash function to the input electronic document D15 obtained from SP10, and collates with the hash value D36 obtained from the electronic signature terminal 30, thereby converting the document. The validity of the hash value D36 provided from the server 20 to the electronic signature terminal 30 is guaranteed.
Next, as shown in steps S10 to S12 of FIG. 2, the XML signature D28 generated by the document conversion server 20 is provided to the SP10. The SP 10 sends the received XML signature D18 to the third-party organization server 40. The third-party server 40 manages the XML signature D18, so that the XML signature D28 generation of the document conversion server 20 and the fact that the XML signature D18 is sent to the SP 10 in response to an inquiry from the user of the electronic signature terminal 30 Can be confirmed.

  As described above, it is possible to realize a validity guarantee system for document format conversion that can detect and prevent falsification / processing errors of the document conversion server 20 and prevent denial of the user's digital signature generation. Further, it is possible to provide a trust model in the third-party organization server 40 without bothering each entity (SP10, document conversion server 20, electronic signature terminal 30) in the conventional client server type electronic signature method. Further, since the electronic signature terminal 30 can deposit various electronic documents in the third-party organization server 40, it can compensate for functional limitations such as a small storage capacity of the electronic signature terminal 30.

[3. Modified example]
Although the embodiments of the present invention have been described above, the present invention is not limited to such embodiments, and various modifications can be made within the scope of the technical idea. As modifications, for example, the following can be considered.
(1) In the above-described embodiment, the “first electronic document” is an XML document, the “conversion specification document” is an XSL document, and the “converted document” is an HTML document. It is not limited to. For example, the “first electronic document” may be a PDF (Portable Document Format) or an HTML document. For the “conversion specification document”, all style sheets and conversion rules such as CSS (Cascading Style Sheet) for converting an HTML document are conceivable.

In the above-described embodiment, only the procedure for confirming the validity of the conversion process of the electronic document sent from the SP 10 to the electronic signature terminal 30 is “first electronic document”, “conversion specification document”, “ The correspondence relationship with the “converted document” has been described, but the following correspondence relationship is also conceivable.
For example, when the validity of the hash value D26 generated by the document conversion server 20 is confirmed, the input XML document D15 corresponds to the “first electronic document”, and the hash function is included in the “conversion specification document”. Correspondingly, the hash value D36 corresponds to the “converted electronic document”.

In this case, the second conversion unit 45 of the third-party organization server 40 converts the input XML document D15 (first electronic document) into a hash value using a hash function (conversion specification document). Next, the matching unit 46 matches the generated hash value with the hash value D36 (converted electronic document), thereby guaranteeing the validity of the hash value D36 provided from the document conversion server 20 to the electronic signature terminal 30. To do.
In addition to this example, the third-party organization server 40 acquires various “first electronic document”, “conversion specification document”, and “post-conversion document” pairs used by the external device for the conversion process. Thus, the validity of the conversion process in the external device can be confirmed.

(2) The above-described validity guarantee system may be a system in which a proxy server that is a business trip agency of the third party agency server 40 exists between the electronic signature terminal 30 and the document conversion server 20. In this case, the following measures are taken as countermeasures against falsification of the document conversion server 20 and the user's subsequent denial.
As described above, the guarantee for falsification of the document conversion server 20 is that (a) the XML document issued by the SP 10 has reached the electronic signature terminal 30 of the user safely, and (a) the signature signed by the user. It is guaranteed that the document to be signed is surely hit. As a guarantee of the XML document (a), the XML document on the SP 10 side and the HTML document acquired by the proxy server are stored in the third party server 40. Here, by preventing the document conversion server 20 from being falsified, the user cannot make a falsification of the document falsification, so that the user can be assured of subsequent denial. Further, regarding the guarantee of the document to be signed in (a), the proxy server deposits the input HTML document and the hash value issued by the document conversion server 20 to the third party server 40, and the SP 10 has already been input. This can be guaranteed by depositing the XML document to the third-party server 40.

(3) In the above-described embodiment, the XSL document D12 acquired by the third-party organization server 40 has been described as a file generated and sent by the SP 10, but may be a file generated by the document conversion server 20. . In the above-described embodiment, the third-party organization server 40 has been described as storing the HTML document D33 sent from the digital signature terminal 30, but communication between devices adopts a communication method with high security by SSL. Therefore, the HTML document D23 sent from the document conversion server 20 may be stored.

(4) The XSL document D12 sent by the SP 10 to the third party server 40 may be given an electronic signature by the SP 10. The XML document D21 sent from the document conversion server 20 to the third party server 40 may be given an electronic signature by the document conversion server 20. Similarly, the HTML signature D33 sent from the electronic signature terminal 30 to the third party institution server 40 may be given an electronic signature by the electronic signature terminal 30. Furthermore, the electronic document to which the electronic signature is given by the SP 10, the document conversion server 20, and the electronic signature terminal 30 may be sent to the third party server 40 via the document conversion server 20.
(5) In the above-described embodiment, the hash function is used as the one-way function. However, the present invention is not limited to the hash function, and any function that is difficult to perform back calculation can be used.

  The present invention can be used in any system that needs to ensure the validity of the electronic document conversion process.

It is a block diagram which shows the whole structure of the validity guarantee system which concerns on embodiment of this invention. It is a sequence diagram which shows the procedure of the electronic signature production | generation concerning the embodiment. It is a figure for demonstrating the electronic document which a 3rd party organization server keeps in the process of the electronic signature production | generation concerning the embodiment. It is a figure for demonstrating the electronic document which the third party organization server which concerns on the embodiment stores. It is a block diagram which shows the function structure of the third party organization server which concerns on the embodiment. (A) is a figure which shows the conversion document registration and storage flow concerning the embodiment. (B) is a diagram showing a document conversion confirmation flow according to the embodiment.

Explanation of symbols

10 SP (electronic document issuing server)
20 Document Conversion Server 21 First Conversion Unit 30 Electronic Signature Terminal 40 Third Party Institution Server (Third Party Document Conversion Assurance Server)
41 Pre-conversion document acquisition unit 42 Conversion specification acquisition unit 43 Pre-conversion document acquisition unit 43 Post-conversion document acquisition unit 44 Document storage unit 45 Conversion unit (second conversion unit)
46 Matching part 47 Matching result output part D11, D21 XML document D12, D22 XSL document D23, D33 HTML document D24, D34 Input completed HTML document (user input completed electronic document, electronic signature target document)
D241, D341 Input data D15, D25 Input XML document (document for electronic signature)
D17, D27, D37 Signature value D26, D36 Hash value D18, D28 XML signature

Claims (6)

In an electronic document conversion validity assurance system having first conversion means for performing conversion processing of an electronic document using a predetermined conversion specification document,
Second conversion means for performing conversion processing on the same electronic document as the electronic document by using the same conversion specification document as the conversion specification document in an apparatus different from the apparatus including the first conversion means; ,
A matching unit that matches the result of the conversion process by the first conversion unit and the result of the conversion process by the second conversion unit, and guarantees the validity of the electronic document conversion by the matching result by the matching unit A validity guarantee system characterized by that. In the third-party document conversion assurance server that guarantees the validity of the conversion process for electronic documents,
A pre-conversion document acquisition means for acquiring a first electronic document;
Conversion specification acquisition means for acquiring a conversion specification document used for performing conversion processing on the first electronic document;
An external device converts the same electronic document as the first electronic document acquired by the pre-conversion document acquisition unit using the same conversion specification document as the conversion specification document acquired by the conversion specification acquisition unit A post-conversion document acquisition means for acquiring a post-conversion electronic document that is the result of processing;
Conversion means for performing conversion processing on the first electronic document acquired by the pre-conversion document acquisition means using the conversion specification document acquired by the conversion specification acquisition means;
A third-party document conversion assurance server, comprising: a matching unit that matches a result of the conversion process by the conversion unit with the converted electronic document acquired by the converted document acquisition unit. The predetermined electronic document is an XML (eXtensible Markup Language) document,
The predetermined conversion specification document is an XSL (eXtensible Stylesheet Language) document,
3. The third-party document conversion assurance server according to claim 2, wherein the converted electronic document is an HTML (HyperText Markup Language) document. In a third-party document conversion assurance server that guarantees the validity of the conversion process in an external device including a first conversion unit that performs conversion processing of an electronic document using a one-way function,
A conversion process is performed on the same electronic document as that used by the first conversion unit included in the external device using the same function as the one-way function used by the first conversion unit. A second conversion means;
A butt means for matching the result of the conversion process by the first conversion means and the result of the conversion process by the second conversion means, and guaranteeing the correctness of the conversion process by the butt result by the butt means A third-party document conversion assurance server characterized by In a validity guarantee method for guaranteeing the validity of the conversion process in the first conversion step of performing a conversion process using a predetermined conversion specification document for a predetermined electronic document,
A device that is different from the device that executes the first conversion step performs conversion processing on the same electronic document as the predetermined electronic document by using the same conversion specification document as the predetermined conversion specification document. Two conversion steps;
The different device has a butt step for matching the result of the conversion process in the first conversion step and the result of the conversion process in the second conversion step, and according to the butt result in the butt step, A method for guaranteeing validity, characterized by guaranteeing validity. An electronic document issuing server that requests an electronic signature to be issued to an electronic document issued by its own server, an electronic signature terminal that gives an electronic signature to the electronic document, and exchange between the electronic document issuing server and the electronic signature terminal And a document conversion server that performs conversion processing of the electronic document, and a third party document conversion assurance server guarantees the validity of the conversion processing of the electronic document,
The third-party document conversion assurance server
Pre-conversion document acquisition means for acquiring an electronic document issued by the electronic document issuance server;
Conversion specification acquisition means for acquiring a conversion specification document used for conversion processing of the electronic document issued by the electronic document issuance server;
A post-conversion document acquisition unit that acquires a post-conversion electronic document that is a result of the electronic document issued by the electronic document issuance server being converted using the conversion specification document by the document conversion server;
Conversion means for performing conversion processing on the electronic document acquired by the pre-conversion document acquisition means using the conversion specification document acquired by the conversion specification acquisition means;
A validity guarantee system comprising: a matching unit that matches a result of the conversion process by the conversion unit and the converted electronic document acquired by the converted document acquisition unit.

Images