KR102592322B1 - Validation system of test report based on blockchain network for identity authentication - Google Patents

Abstract

The test report validation system based on the blockchain network for identity authentication according to the embodiment is an app server that issues a manufacturer VC related to the manufacturer's original test report and records the issued manufacturer VC on the second blockchain network. ; and
A second manufacturer terminal that obtains the manufacturer VC through the second blockchain network and transmits a two-dimensional code of the test report to be compared corresponding to the original test report to the app server,
The app server extracts the second code value of the two-dimensional code received from the second manufacturer terminal, and sends a request for validation of the test report to be compared including the extracted second code value to the first blockchain. transmit on the network,
The second manufacturer terminal may receive a validation result of the test report to be compared based on the second code value performed through the first blockchain network from the first blockchain network.

Description

Validation system of test report based on blockchain network for identity authentication}

The present invention relates to a validation system for test reports based on a blockchain network for identity authentication. More specifically, it authenticates a manufacturer terminal using manufacturer VC information recorded through a blockchain network for identity authentication, and obtains information from the authenticated manufacturer terminal. This relates to a test report validation system based on a blockchain network for identity authentication that seeks to prevent forgery and falsification of test reports by ensuring that the requested test report is validated through a general blockchain network.

In accordance with the Act on Environmental Testing and Inspection, the Food Sanitation Act, the Food and Drug Safety Administration and Korea Disease Control and Prevention Agency test request rules, the Safety Management Act, and the Framework Act on National Standards, test subjects and test results are required to ensure the quality of all products delivered by manufacturers to suppliers. etc. are stipulated to be submitted to the place of delivery.

If these test results are forged or altered by the manufacturer or a third party, negative results may be conveyed not only to related organizations but also to general consumers.

The present invention was derived from the above-described problems, and its purpose is to prevent forgery and falsification of test results through a blockchain network and improve reliability.

In particular, the purpose of the present invention is to improve the accuracy and security performance of test report forgery inquiry results by providing a separate blockchain network for DID-based identity authentication.

The purpose of the present invention is also to enable transparent information management by allowing test progress or test results to be shared with each organization through a web server.

In addition, the purpose is to ensure that each institution is provided with a user interface that is easy to operate through a web page for the test progress process or test results.

The test report validation system based on the blockchain network for identity authentication according to the embodiment is an app server that issues a manufacturer VC related to the manufacturer's original test report and records the issued manufacturer VC on the second blockchain network. ; and

A second manufacturer terminal that obtains the manufacturer VC through the second blockchain network and transmits a two-dimensional code of the test report to be compared corresponding to the original test report to the app server,

The app server extracts the second code value of the two-dimensional code received from the second manufacturer terminal, and sends a request for validation of the test report to be compared including the extracted second code value to the first blockchain. transmit on the network,

The second manufacturer terminal may receive a validation result of the test report to be compared based on the second code value performed through the first blockchain network from the first blockchain network.

The second manufacturer terminal receives key information of the original test report from the first blockchain network if it is determined to be valid as a result of the validation of the test report to be compared performed through the first blockchain network, and determines that it is not valid. If it is determined that it is not, an error message can be received from the first blockchain network.

The manufacturer VC may include at least one of the manufacturer DID, tester DID, key information of the original test report, and a hash value.

The app server may further issue a connection DID to connect the manufacturer DID and the testing company DID.

1st manufacturer terminal; And extracting a second hash value of the test report to be compared uploaded from the first manufacturer terminal, and sending a request for validation of the test report to be compared including the extracted second hash value to the first blockchain network. It further includes a web server transmitting on the

The first manufacturer terminal may receive a validation result of the uploaded test report to be compared based on the second hash value performed through the first blockchain network from the first blockchain network.

The first manufacturer terminal receives key information of the original test report from the first blockchain network if it is determined to be valid as a result of the validation of the uploaded test report to be compared performed through the first blockchain network, If it is determined to be invalid, an error message may be received from the first blockchain network.

The web server may record at least one of the first hash value, first code value, and key information of the original test report on the first blockchain network.

According to the present invention, it is possible to prevent forgery and falsification of test results through a blockchain network and improve reliability.

In particular, the present invention allows transparent information management to be achieved by sharing the test progress or test results with each organization through a web server.

In addition, each institution will be provided with an easy-to-operate user interface through a web page for the test progress process or test results.

Figure 1 is a configuration diagram of a test report validation system 1 based on a blockchain network according to an embodiment.
Figure 2 is a block diagram of the web server 30 according to an embodiment.
Figure 3 is a block diagram of the app server 40 according to an embodiment.
Figure 4 is a diagram illustrating an electronic wallet according to an embodiment.
Figure 5 is a flowchart for explaining the DID registration process according to an embodiment.
Figure 6 is a flowchart explaining the issuance process of a connection DID according to an embodiment.
Figure 7 is a flowchart explaining the test report registration and manufacturer VC issuance process during the operation of the test report validation system 1 based on the blockchain network according to the embodiment.
Figure 8 is a flowchart explaining the process of checking test report forgery and alteration during the operation of the test report validation system 1 based on a blockchain network according to an embodiment.
Figure 9 is a flowchart illustrating a test report forgery inquiry process during the operation of a test report validation system 1 based on a blockchain network according to another embodiment.
Figure 10 is a flowchart illustrating a test report forgery inquiry process during the operation of a test report validation system 1 based on a blockchain network according to another embodiment.
Figures 11 to 14 are diagrams referenced to explain operations through the first blockchain network (N2).

The detailed description of the present invention described below refers to the accompanying drawings, which show by way of example specific embodiments in which the present invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different from one another but are not necessarily mutually exclusive. For example, specific shapes, structures and characteristics described herein with respect to one embodiment may be implemented in other embodiments without departing from the spirit and scope of the invention. Additionally, it should be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the invention. Accordingly, the detailed description that follows is not intended to be taken in a limiting sense, and the scope of the invention is limited only by the appended claims, together with all equivalents to what those claims assert, if properly described. Similar reference numbers in the drawings refer to identical or similar functions across various aspects.

Figure 1 is a configuration diagram of a test report validation system 1 based on a blockchain network according to an embodiment.

As shown in Figure 1, the test report validation system 1 based on the blockchain network according to the embodiment includes a first manufacturer terminal 10, a second manufacturer terminal 11, a tester terminal 20, and a web. It may be accomplished by transmitting and receiving data between the server 30 and the app server 40.

According to embodiments, some of the above components may be omitted or some components may be implemented in various ways, such as performing the role of other components.

The first manufacturer terminal 10 is provided for the manufacturer to submit tests and receive test reports, and can communicate with the web server 30.

The first manufacturer terminal 10 may include various devices such as desktops, PCs, smartphones, and tablets that can output web pages provided from the web server 30.

The second manufacturer's terminal 11 is equipped to obtain the two-dimensional code of the test report and can communicate with the app server 40.

The second manufacturer terminal 11 may include various devices such as smartphones and tablets that have a shooting function and can scan two-dimensional codes using an app.

The tester terminal 20 is equipped to approve the manufacturer's test reception request from the tester performing the test on the manufacturer's test subject and to register the issued test report with the web server 30. Communication can be performed with (30).

The tester terminal 20 may include various devices such as desktops, PCs, smartphones, and tablets that can output web pages provided from the web server 30.

The web server 30 provides a web page to the first manufacturer terminal 10 and the tester terminal 20 to manage test reception and is linked to the first blockchain network (N2) to ensure the validity of the test report using the hash value. It may be provided to ensure verification.

The app server 40 is provided to verify the validity of the test report using a two-dimensional code value and can be linked to the first blockchain network (N2).

Meanwhile, the network according to the embodiment may include a general network (N1), a first blockchain network (N2), and a second blockchain network (N3).

Here, the general network (N1) may be configured through various communication networks such as wired and wireless, for example, a local area network (LAN), a metropolitan area network (MAN), a wide area network ( It can be composed of various communication networks such as WAN (Wide Area Network).

According to an embodiment, a plurality of blockchain nodes forming one or more peer-to-peer (P2P) network structures may be interconnected through a first blockchain network (N2) and/or a second blockchain network (N3). there is. For example, at least some of the first manufacturer terminal 10, the second manufacturer terminal 11, the tester terminal 20, the web server 30, and the app server 40 are connected to the first blockchain network (N2). ) and/or form a plurality of blockchain network structures through the second blockchain network (N3), so that each can interact as a distributed blockchain node.

Each node linked through the first blockchain network (N2) stores the information of each node in the block ledger, creates one block, and transmits the created block through consensus to other related nodes connected to the blockchain. By doing so, multiple remaining nodes can have the same block.

The second blockchain network (N3) may be a blockchain platform created for identity authentication by establishing DID. According to an embodiment, the identity information of nodes participating in the network can be controlled and managed by storing DID in the client's wallet.

Figure 2 is a block diagram of the web server 30 according to an embodiment.

The web server 30 according to the embodiment may include a test report management unit 31, an extraction unit 32, a blockchain linking unit 33, and a VC issuance request unit 34.

The test report management department 31 can manage the registration of the original test report.

The test report management unit 31 receives a test reception request from the first manufacturer terminal 10, receives test reception approval from the tester terminal 20, and registers the original test report based on the test reception approval result. can be managed.

The test report management unit 31 may transmit a confirmation request signal for the registered original test report to the first manufacturer terminal 10, and receive a confirmation completion signal for the original test report from the first manufacturer terminal 10. .

The test report management unit 31 can insert a two-dimensional code such as a QR code or bar code into the original test report for which confirmation has been completed and transmit the test report with the two-dimensional code inserted to the tester terminal 20.

The test report management unit 31 may transmit the original test report with the final confirmed two-dimensional code inserted to the first manufacturer terminal 10 and/or the tester terminal 20.

The extraction unit 32 can extract the hash value (first hash value) of the original test report.

The extraction unit 32 may extract the first hash value based on the content data and/or metadata of the original test report.

The extraction unit 32 can extract the two-dimensional code value (first code value) of the original test report.

The blockchain interlocking unit 33 can record information related to the original test report on the first blockchain network (N2).

The blockchain interlocking unit 33 transmits the first hash value of the original test report, main information of the original test report, two-dimensional code value (first code value), and/or the unique value of the original test report to the first blockchain network. It can be recorded on (N2).

The extraction unit 32 can extract the hash value (second hash value) of the test report to be compared.

The extraction unit 32 may extract the second hash value based on the content data and/or metadata of the test report to be compared.

The VC issuance request unit 34 may transmit a manufacturer VC creation request signal to the app server 40. According to the embodiment, the hash value (first hash value) of the original test report and key information on the report can be included in the manufacturer VC creation request signal and transmitted to the app server 40.

According to the embodiment, the manufacturer VC may be created in the app server 40 to include a hash value (first hash value) of the original test report, key information on the report, manufacturer DID, and/or test company DID.

The blockchain linkage unit 33 can be linked with the first blockchain network (N2) to check for forgery and alteration of test reports.

The blockchain interlocking unit 33 transmits a request for validation of the test report to be compared including the extracted second hash value to the first blockchain network (N2), and receives the second hash value from the blockchain network. A validation result may be received through comparison of the first hash value.

The blockchain interlocking unit 33 receives key information of the original test report from the blockchain network when it is determined to be valid as a result of comparison between the second hash value and the first hash value by the blockchain network, If it is determined to be invalid, an error message may be received from the blockchain network.

Figure 3 is a block diagram of the app server 40 according to an embodiment.

The app server 40 according to the embodiment may include a DID management unit 41, a connection DID issuing unit 42, a VC issuing unit 43, a code value management unit 44, and a hash value management unit 45. .

The DID management unit 41 can issue a DID document (DID Doc) corresponding to the DID and then store it on the second blockchain network (N3).

The connection DID issuing unit 42 can issue a connection DID to connect the manufacturer DID and the testing company DID.

The connection DID issuing unit 42 may issue a connection DID with reference to the connection request signal received from the second manufacturer terminal 11 and then transmit the issued connection DID to the second manufacturer terminal 11.

The VC issuing unit 43 can issue a manufacturer VC.

The VC issuing department 43 can create a manufacturer VC by including the hash value (first hash value) of the original test report, key information on the report, manufacturer DID, and/or tester DID.

The code value management unit 44 can extract the code value (second code value) of the two-dimensional code of the test report to be compared.

The code value management unit 44 may receive a two-dimensional code from the second manufacturer terminal 11 and extract the code value (second code value) of the received two-dimensional code.

The code value management unit 44 can be linked with the first blockchain network (N2) to check for forgery and alteration of test reports.

The code value management unit 44 includes the extracted second code value in the validation request signal of the test report to be compared and transmits it to the first blockchain network (N2), and transmits the second code value from the blockchain network (N2). A validation result can be received through comparison of the first code value and the first code value.

According to the embodiment, when the first blockchain network (N2) determines that the second code value and the first code value are valid as a result of comparison, the code value management unit 44 receives the original from the first blockchain network (N2). If the main information of the test report is received and the comparison result is determined to be invalid by the first blockchain network (N2), the code value management unit 44 may receive an error message from the blockchain network (N2). You can.

The hash value management unit 45 may extract the second hash value of the test report to be compared.

The hash value management unit 45 may include the second hash value in the validation request signal of the test report to be compared and transmit it to the first blockchain network (N2).

According to the embodiment, when the first blockchain network (N2) determines that the second code value and the first code value are valid as a result of comparison, the hash value management unit 45 receives the original from the first blockchain network (N2). If the main information of the test report is received and the comparison result is determined to be invalid by the first blockchain network (N2), the hash value management unit 45 may receive an error message from the blockchain network (N2). You can.

Figure 4 is a diagram illustrating an electronic wallet according to an embodiment. The electronic wallet according to an embodiment may include a Decentralized ID (DID), Verified Credential (VC), and Connection DID.

Figure 5 is a flowchart for explaining the DID registration process according to an embodiment.

As shown in Figure 5, the second manufacturer's terminal 11 can run the electronic wallet app (s51) to check whether the DID has already been issued and stored in the electronic wallet (Wallet). If it has been issued, it goes to step s52. If it has not been issued, the DID can be issued and stored in the electronic wallet along with the private key. According to an embodiment, the DID may include at least one information of the manufacturer's corporate registration number and corporate address.

DID is a user identifier based on a decentralized identity verification service using blockchain technology. When using DID as an authentication method, the identity verification system utilizes blockchain technology to dispersely store and manage verification data to prevent forgery and falsification of identity and qualification information and to ensure accuracy. You can register DID by manufacturer.

According to the embodiment, since the second manufacturer's terminal 11 voluntarily creates and manages the DID, information that is judged to be unnecessary or that is not desired to be exposed through the above process can be managed so as not to be included in the public information. In addition, you can prove your identity by selecting only some DID information (e.g., manufacturer's corporate registration number) from the total DID information, registering it in the system, and being authenticated.

The second manufacturer terminal 11 can register the second manufacturer in the blockchain-based identity authentication service. In particular, you can perform the manufacturer authentication process and transmit the signature to the identity authentication service through the app provided by the identity authentication service.

Specifically, when the second manufacturer terminal 11 requests registration of a DID through the app server 40 (s52), the DID management unit 41 of the app server 40 creates a DID document (DID Doc) corresponding to the DID. After issuing, it can be stored on the second blockchain network (N3) (s52-1). According to an embodiment, the DID document may include information such as information related to the manufacturer, a method to verify it, the public key of the DID, an authentication protocol, and a service end point. For reference, the second blockchain network (N3) may include a Revocation Registry containing information for revocation of DID documents and various certificates. Afterwards, the DID document issuance completion information transmitted from the second blockchain network (N3) through the app server 40 can be shared with the second manufacturer terminal 11 (s53, s53-1, s53-2).

Figure 6 is a flowchart explaining the issuance process of a connection DID according to an embodiment.

According to the embodiment, the connection DID is for connecting the manufacturer DID and the testing company DID, and the app server 40 can transmit the manufacturer VC through the connection DID.

As shown in FIG. 6, the second manufacturer's terminal 11 can run the electronic wallet app to check whether a DID has already been issued (s61). If it has been issued, proceed to step s62. If not, the DID can be issued and stored in the electronic wallet along with the private key.

According to the embodiment, the second manufacturer terminal 11 may obtain a two-dimensional code (eg, bar code, QR code) for issuing a connection DID from the first manufacturer terminal 10 (s62). Specifically, the second manufacturer's terminal 11 can be obtained by scanning the two-dimensional code printed on the first manufacturer's terminal 10 using an app. However, this is an example, and the present invention can be applied equally/similarly even when obtaining a 2D code through another route, such as scanning a 2D code located on an offline paper document.

The second manufacturer terminal 11 can transmit a signal requesting a connection between the manufacturer DID and the testing company DID to the app server 40 using the obtained two-dimensional code (s63).

The connection DID issuing unit 42 of the app server 40 may issue a connection DID with reference to the connection request signal received from the second manufacturer terminal 11 and then transmit it to the second manufacturer terminal 11 (s64) , s64-1). Then, the second manufacturer terminal 11 can store the connection DID in the electronic wallet. And, the app server 40 can record the connection DID on the second blockchain network (N3) (s64-2). According to the embodiment, a separate database server (not shown) participates as a node in the second blockchain network (N3), and the manufacturer DID, tester DID, and/or connection DID are also stored and stored in the database server (not shown). It can be.

Figure 7 is a flowchart explaining the test report registration and manufacturer VC issuance process during the operation of the test report validation system 1 based on the blockchain network according to the embodiment.

As shown in FIG. 7, the first manufacturer terminal 10 may receive a test reception request from the user and transmit it to the web server 30 (s71). Specifically, a manufacturer requiring a test report can request a test application by transmitting a test reception request signal to the web server 30 through the first manufacturer terminal 10. For reference, in the present invention, testing may mean testing the performance or quality of a product.

The tester terminal 20, which has received a test application request through the web server 30, reviews the requirements of the first manufacturer terminal 10 and/or the suitability of the test request contents, etc. and satisfies predetermined conditions. An approval signal for test reception can be transmitted to the web server 30 (s72).

According to the embodiment, the tester terminal 20 sends a request signal to the first manufacturer terminal through the web server 30 to transmit as a submission the information required for the test, such as the test subject, test environment, and test application scope. It can be transmitted to (10). In response, the first manufacturer terminal 10 may submit a submission through the web server 30. Submissions according to embodiments may include test environments such as code, compiler, and operating system, or test cases for test performance.

Testers can design test plans, perform tests, and analyze test results considering the size and complexity of submissions, test subjects, and test performance schedules. In addition, the tester terminal 20 can issue an original test report based on the result of analyzing the test results.

According to an embodiment, the original test report may be stored as document data to form a document in electronic form. For example, it may include content data such as text/image to be displayed to the viewer, and metadata related to the test report (e.g. test report issuance date and time, issuer information, etc.) that is not displayed to the viewer.

According to the embodiment, the test report may include all of various forms stored in the form of a file, and may be issued in the form of a document having a format such as, for example, PDF, HWP, or WORD.

When the original test report issued by the tester terminal 20 is registered with the web server 30 (s73), the web server 30 sends a confirmation request signal for the registered original test report to the first manufacturer terminal 10. transmission, and the first manufacturer terminal 10 can transmit a confirmation completion signal for the original test report to the web server 30 (s74, s75)

According to the embodiment, the test report management unit 31 of the web server 30 may insert a two-dimensional code such as a QR code or barcode into the original test report for which confirmation has been completed (s76). According to an embodiment, the two-dimensional code may include information such as tester DID, manufacturer DID, and product serial number.

The web server 30 transmits the original test report with the two-dimensional code inserted to the tester terminal 20 (s76-1), and the tester terminal 20 sends the original test report with the received two-dimensional code inserted. A final confirmation completion signal can be transmitted to the web server 30 (s77).

In addition, the web server 30 may transmit the original test report with the final confirmed two-dimensional code inserted to the first manufacturer terminal 10 and/or the tester terminal 20 (s77-1).

And, according to the embodiment, the web server 30 may generate a first hash value based on content data and/or metadata of the original test report. The first hash value can be generated using various known algorithms such as SHA (Secure Hash Algorithm).

The blockchain interconnection unit 33 of the web server 30 uses the hash value (first hash value) of the original test report, main information of the report, two-dimensional code value (first code value), and/or the uniqueness of the original test report. The value can be recorded on the first blockchain network (N2) (s78).

For example, referring to FIGS. 11 to 14, each node of the first blockchain network (N2) stores the above information of each node in the block ledger to create one block, and other related nodes connected to the blockchain By transmitting the block created through consensus to the nodes, a plurality of remaining nodes can have the same block.

Each block according to the embodiment consists of a header, body data, and metadata, the header includes the block number, the hash value of the previous block header, and the hash value of the current block header, and the body data is the hash value of the original test report. , It includes unique values, 2D code values, and key information of the original test report, and metadata may include ID, block creation time, and the author's signature. In particular, according to an embodiment, the key information of the test report included in the body data may include at least one of the test report field, test report number, issuance date, test person in charge, technical manager, test standard, and product name.

According to the present invention, the first manufacturer terminal 10 and the tester terminal 20 go through processes such as test application and test report registration through the web server 30, so that each terminal through the website The user interface is easier to operate, and each result can be confirmed and managed reliably.

The VC issuance request unit 34 of the web server 30 may transmit a manufacturer VC creation request signal to the app server 40 (s79). According to the embodiment, the hash value (first hash value) of the original test report and key information on the report can be included in the manufacturer VC creation request signal and transmitted to the app server 40. Then, the VC issuing unit 43 of the app server 40 can issue a manufacturer VC according to the request. According to another embodiment, a manufacturer VC may be issued by directly receiving a manufacturer VC creation request signal from the first manufacturer terminal 10 in the app server 40.

According to an embodiment, the manufacturer VC may be written to include a hash value (first hash value) of the original test report, key information in the report, manufacturer DID, and/or tester DID.

According to the embodiment, the first hash value and key information on the report are received from the web server 30, the manufacturer DID refers to the DID document generated through the process of FIG. 5, and the test company DID is sent to the app server 40 in advance. A manufacturer VC can be created using what is stored in .

The VC issuing unit 43 records the issued manufacturer VC on the second blockchain network (N3) using the connection DID issued through the process of FIG. 6 (s79-1), and accordingly, the second manufacturer terminal ( 11) The manufacturer VC can also be stored in the electronic wallet, and the manufacturer DID, connection DID, and manufacturer VC can be stored together in the electronic wallet as shown in Figure 4.

According to the embodiment, the VC issuing unit 43 may further record the VC ID corresponding to the issued manufacturer VC on the second blockchain network (N3). Then, the node on the second blockchain network (N3) can verify the signature of the VC ID storage request transaction, record the VC ID in the blockchain to correspond to the manufacturer DID, and TXID (transaction ID) corresponding to the VC ID. can be transmitted to the app server 40. According to the embodiment, the TXID can be used later to determine whether the VC ID has been stored in the second blockchain network (N3) or to search for the VC ID in the second blockchain network (N3).

Figure 8 is a flowchart explaining the process of checking test report forgery and alteration during the operation of the test report validation system 1 based on a blockchain network according to an embodiment.

As shown in FIG. 8, the second manufacturer terminal 11 can obtain the two-dimensional code of the test report to be inquired (hereinafter referred to as the test report to be compared) from the first manufacturer terminal 10. (s81).

For reference, in Figure 8, the test report to be compared can be defined as being subject to validation in correspondence to the issued original test report.

According to the embodiment, the second manufacturer terminal 11 can be obtained by scanning the two-dimensional code of the test report to be compared on the web page printed on the first manufacturer terminal 10 using an app.

Specifically, the first manufacturer terminal 10 can receive the original test report with the two-dimensional code inserted through the process s77-1 of FIG. 7 from the web server 30, and check validity in response to the received original test report. The test report to be compared, which has been verified, is output on a web page, and the second manufacturer terminal 11 scans the two-dimensional code of the test report to be compared, thereby obtaining the two-dimensional code.

Meanwhile, according to another embodiment, the second manufacturer terminal 11 may obtain a two-dimensional code by scanning the test report to be compared, where the original test report is printed and subject to validation.

The second manufacturer terminal 11 may include the obtained two-dimensional code in a validation request signal for the test report to be compared and transmit it to the app server 40 (s82).

Upon receiving a validation request signal from the second manufacturer terminal 11, the code value management unit 44 of the app server 40 can extract the code value (second code value) of the received two-dimensional code (s83 ).

Specifically, the app server 40 may determine whether the second manufacturer's terminal 11 is a verified user, and extract the second code value if it determines that the second manufacturer's terminal 11 is a verified user.

According to the embodiment, whether the user is a verified user can be determined by determining whether the user has the manufacturer VC described above in FIG. 7.

For reference, Figure 8 illustrates that the app server 40 generates the second code value. According to another embodiment, when the first manufacturer's terminal 10 and/or the second manufacturer's terminal 11 generates a second code value, the app server 40 may receive the second code value therefrom.

The code value management unit 44 may include the second code value in the validation request signal of the test report to be compared and transmit it to the first blockchain network (N2) (s84).

Then, the first blockchain network (N2) can compare the first code value recorded in the block and the received second code value (s85).

Specifically, in the first blockchain network (N2), referring to FIG. 13, the first code value of the original test report corresponding to the test report to be compared included in the validation request signal can be derived and compared with the second code value. there is.

If it is determined that the code value is the same as a result of comparison, the test report to be compared is determined to be valid, and the key information in the report recorded in the block can be transmitted to the second manufacturer terminal 11 (s86). On the other hand, if it is determined that the comparison result is not the same, the test report to be compared is judged to have been forged and altered, and an error message indicating that it is a report not issued by the testing company can be sent to the second manufacturer terminal 11 (s86-1).

Meanwhile, Figure 8 illustrates that the validation result is directly transmitted from the first blockchain network (N2) to the second manufacturer's terminal 11, but according to another embodiment, the validation result is first sent to the app server 40. and may be transmitted from the app server 40 to the second manufacturer's terminal 11.

Figure 9 is a flowchart illustrating a test report forgery inquiry process during the operation of a test report validation system 1 based on a blockchain network according to another embodiment.

As shown in FIG. 9, the first manufacturer's terminal 10 can transmit a test report subject to comparison to the second manufacturer's terminal 11 (s91).

For reference, in Figure 9, the test report to be compared can be defined as being subject to validation in correspondence to the issued original test report.

Specifically, the first manufacturer's terminal 10 can receive the original test report from the web server 30 through process s77-1 in FIG. 7, and the comparison object subject to validation corresponding to the received original test report The test report can be transmitted to the second manufacturer's terminal (11).

Meanwhile, according to another embodiment, the second manufacturer's terminal 11 may obtain the original test report by scanning the test report to be compared for which the original test report has been printed and subject to validation.

The second manufacturer terminal 11 may include the test report to be compared in the validation request signal and transmit it to the app server 40 (s92).

Upon receiving a validation request signal from the second manufacturer terminal 11, the hash value management unit 45 of the app server 40 can extract the second hash value of the received test report to be compared (s93).

Specifically, the app server 40 may determine whether the second manufacturer's terminal 11 is a verified user, and extract the second hash value if it determines that the second manufacturer's terminal 11 is a verified user.

According to the embodiment, whether the user is a verified user can be determined by determining whether the user has the manufacturer VC described above in FIG. 7.

For reference, Figure 9 illustrates the app server 40 generating the second hash value. According to another embodiment, when the first manufacturer terminal 10 and/or the second manufacturer terminal 11 generates a second hash value, the app server 40 may receive the second hash value therefrom.

The hash value management unit 45 may include the second hash value in the validation request signal of the test report to be compared and transmit it to the first blockchain network (N2) (s94).

Then, the first blockchain network (N2) can compare the first hash value recorded in the block and the received second hash value (s95).

Specifically, in the first blockchain network (N2), referring to FIG. 13, the first hash value of the original test report corresponding to the test report to be compared included in the validation request signal can be derived and compared with the second hash value. there is.

If it is determined that the hash value comparison is the same, the test report to be compared is determined to be valid, and the key information in the report recorded in the block can be transmitted to the second manufacturer terminal 11 (s96). On the other hand, if it is determined that the comparison result is not the same, the test report to be compared is judged to have been forged and altered, and an error message indicating that it is a report not issued by the testing company can be sent to the second manufacturer terminal 11 (s96-1).

Meanwhile, Figure 9 illustrates that the validation result is directly transmitted from the first blockchain network (N2) to the second manufacturer's terminal 11. However, according to another embodiment, the validation result is first sent to the app server 40. and may be transmitted from the app server 40 to the second manufacturer's terminal 11.

Figure 10 is a flowchart explaining the test report forgery inquiry process during the operation of the test report validation system 1 based on a blockchain network according to another embodiment.

As shown in FIG. 10, the first manufacturer terminal 10 and/or the tester terminal 20 includes the test report to be inquired (hereinafter referred to as the test report to be compared) in the validation request and sends it to the web. It can be uploaded to the server 30 (s101).

For reference, in Figure 10, the test report to be compared can be defined as uploaded for validation in response to the issued original test report.

The extraction unit 32 of the web server 30 can extract the hash value (second hash value) of the test report to be compared (s102).

According to the embodiment, the extraction unit 32 may generate a second hash value based on content data and/or metadata of the test report to be compared. The second hash value can be generated using various known algorithms such as SHA (Secure Hash Algorithm).

For reference, FIG. 10 illustrates that the second hash value is generated by the web server 30, but according to another embodiment, the second hash value is generated by the first manufacturer terminal 10 and/or the tester terminal 20. After generating, when the test report to be compared is uploaded to the web server 30, the second hash value can be extracted from it.

The blockchain linking unit 33 of the web server 30 may include the second hash value in the validation request signal of the test report to be compared and transmit it to the first blockchain network (N2) (s103).

Then, the first blockchain network (N2) can compare the first hash value recorded in the block and the received second hash value (s104).

Specifically, in the first blockchain network (N2), referring to FIG. 12, the first hash value of the original test report corresponding to the test report to be compared included in the validation request signal can be derived and compared with the second hash value. there is.

If it is determined that the hash value comparison is the same, the test report to be compared is determined to be valid, and the main information of the report recorded in the block can be transmitted to the first manufacturer terminal 10 and/or the tester terminal 20 (s105 ). On the other hand, if it is determined that the comparison result is not the same, the test report to be compared is judged to have been forged and an error message indicating that it is a report not issued by the test company is sent to the first manufacturer terminal 10 and/or the test company terminal 20. Can be transmitted (s105-1).

Meanwhile, Figure 10 illustrates that the validation result is directly transmitted from the first blockchain network (N2) to the first manufacturer terminal 10 and/or the tester terminal 20, but according to another embodiment, the validation result is The results are first transmitted to the web server 30, and may be transmitted from the web server 30 to the first manufacturer terminal 10 and/or the tester terminal 20 (s55-1).

According to an embodiment of the present invention, as shown in FIG. 8, the test report forgery and falsification inquiry using a two-dimensional code value is performed through the first blockchain network (N2) via the app server 40, and the hash value as shown in FIG. 10 By allowing the test report forgery and forgery search using the web server 30 and the first blockchain network (N2), the accuracy of the test report forgery and forgery search results is higher and security performance is further improved.

Figure 14 is a configuration diagram of a first blockchain network (N2) according to an embodiment.

According to the example. As shown in FIG. 14, the minimum number of nodes included in one first blockchain network (N2) can be set and implemented. For example, the minimum number of nodes may be set to 4, but the scope of the present invention is not limited thereto.

Additionally, the number of active nodes and the number of standby nodes may be set in advance. For example, the number of active nodes may be set to 3 and the standby node may be set to 1, but the scope of the present invention is not limited thereto.

In the case of Figure 14, in normal times, only three active nodes process the consensus process while creating the block ledger, and the remaining standby node is in a standby state, and if some of the active nodes fail, it immediately agrees on behalf of the failed node. You can participate in handling the process.

The features, structures, effects, etc. described in the embodiments above are included in one embodiment of the present invention and are not necessarily limited to only one embodiment. Furthermore, the features, structures, effects, etc. illustrated in each embodiment can be combined or modified and implemented in other embodiments by a person with ordinary knowledge in the field to which the embodiments belong. Therefore, contents related to such combinations and modifications should be construed as being included in the scope of the present invention.

In addition, although the above description has been made focusing on the examples, this is only an example and does not limit the present invention, and those skilled in the art will understand the above examples without departing from the essential characteristics of the present embodiment. You will be able to see that various modifications and applications are possible. For example, each component specifically shown in the examples can be modified and implemented. And these variations and differences in application should be construed as being included in the scope of the present invention as defined in the appended claims.

Claims (7)

An app server that issues a manufacturer VC related to the manufacturer's original test report and records the issued manufacturer VC on a second blockchain network; and
A second manufacturer terminal that obtains the manufacturer VC through the second blockchain network and transmits a two-dimensional code of the test report to be compared corresponding to the original test report to the app server,
The app server extracts the second code value of the two-dimensional code received from the second manufacturer terminal, and sends a request for validation of the test report to be compared including the extracted second code value to the first blockchain. transmit on the network,
The second manufacturer terminal receives a validation result of the test report to be compared based on the second code value performed through the first blockchain network from the first blockchain network,
The manufacturer VC includes at least one of the manufacturer DID, tester DID, main information of the original test report, and a hash value,
The app server further issues a connection DID to connect the manufacturer DID and the testing company DID,
1st manufacturer terminal; and
The second hash value of the test report to be compared uploaded from the first manufacturer terminal is extracted, and a request for validation of the uploaded test report to be compared including the extracted second hash value is sent on the first blockchain network. It further includes a web server transmitting to,
The first manufacturer terminal receives, from the first blockchain network, a validation result of the uploaded test report to be compared based on the second hash value performed through the first blockchain network.
A test report validation system based on a blockchain network for identity authentication.
According to clause 1,
The second manufacturer's terminal is,
As a result of the validation of the test report to be compared through the first blockchain network, if it is determined to be valid, key information of the original test report is received from the first blockchain network, and if it is determined to be invalid, an error message is sent. Receiving from the first blockchain network,
A test report validation system based on a blockchain network for identity authentication.
delete delete delete According to clause 1,
The first manufacturer's terminal is,
As a result of the validation of the uploaded comparative test report performed through the first blockchain network, if it is determined to be valid, key information of the original test report is received from the first blockchain network, and if it is determined to be invalid, an error occurs. Receiving a message from the first blockchain network,
A test report validation system based on a blockchain network for identity authentication.
According to clause 1,
The web server is,
Recording at least one of the first hash value, first code value, and key information of the original test report on the first blockchain network,
A test report validation system based on a blockchain network for identity authentication.

Images