Meteorological data source credibility certification method based on block chain

Abstract

The invention discloses a meteorological data source credibility proving method based on a block chain, and provides a new data source credibility proving mechanism by utilizing the characteristics of tamper resistance, forgery resistance and loss resistance of the block chain and combining signature verification and hash operation algorithms in cryptography. According to the mechanism, credibility and data delivery validity verification can be accurately carried out on delivery data recorded by a data provider; according to the patent, transaction / shared data is converted into a pre-agreed intermediate format (a character set, a coding mode and an XML / JSON data structure expression mode) and is stored in a file form. And after receiving the data, the data user converts the data into a self system format according to self system requirements, so that the correctness of data information expression is ensured. Through the overall transmission of the data packet, the accidental missing and tampering of the data in the transmission process between the two handover parties are effectively avoided.

Description

Technical Field

[0001] The present invention relates to the technical field of meteorological data, and more specifically, to a method for proving the credibility of the source of meteorological data based on blockchain. Background Art

[0002] With the continuous maturity and standardization process of the meteorological data trading market, ensuring the authority and credibility of data sources has become an essential core link in the meteorological data value chain. Against this background, meteorological data trading activities have naturally been incorporated into the strict supervision framework of the National Data Bureau, aiming to build a fair, transparent, and legal data trading environment.

[0003] For users, processors, and service providers of meteorological data, obtaining and using meteorological data legally and compliantly is a fundamental prerequisite for carrying out relevant business activities and effectively avoiding potential legal risks. This requires them to obtain data through formal channels - such as meteorological bureaus - and obtain clear authorization permits to ensure the legality of data use.

[0004] In this process, the credible proof of the source of meteorological data issued by the meteorological bureau to data users is not only a strong evidence for the legality of data transactions, but also an authoritative certification of data quality, accuracy, and authenticity.

[0005] However, in the current meteorological data trading process, there are still many deficiencies in the credible proof mechanism of data sources. Although the China Meteorological Administration has built a meteorological data circulation and trading security supervision platform and, relying on the meteorological digital object identifier (MOID) technology, constructed a platform system with national and provincial hierarchical management and a "1+31" deployment architecture according to the requirements of relevant industry standards, realizing the unique identification, flexible traceability, security review, and effective supervision of meteorological data results. But at the actual operation level, when the meteorological bureau provides meteorological data sets to data users, only the corresponding MOIDs are marked for the data in the data sets, and the key information of data consistency verification, data source credibility verification, and data use authorization proof is not provided.

[0006] This situation results in that after receiving the data set, data users cannot effectively verify whether the received data has been tampered with, forged, or lost; nor can they provide legal intellectual property authorization vouchers in case of disputes or regulatory audits afterwards. This not only brings unnecessary troubles and risks to data providers, users, and regulators, but also seriously hinders the wide application and in-depth exploration of meteorological data. Summary of the Invention

[0007] The present invention provides a method for proving the credibility of the source of meteorological data based on blockchain to solve the problems in the prior art that after the user receives the data set, the existing data source credibility proof mechanism cannot effectively verify whether the received data has been tampered with, forged or lost; nor can it provide a legal intellectual property authorization certificate when disputes occur or regulatory audits are conducted afterwards.

[0008] To achieve the above object, the present invention provides the following technical solutions:

[0009] A method for proving the credibility of the source of meteorological data based on blockchain includes 2 core processes and 2 formatted files. The 2 core processes respectively include a process for authenticating the credibility of the data record source and a process for credibly filing the information related to data delivery. The 2 formatted files respectively include a letter of authenticity verification for the data source and a report on the authenticity verification of the data source.

[0010] Preferably, the process for authenticating the credibility of the data record source specifically includes the following steps:

[0011] S1: When the data provider receives the letter of authenticity verification for the data source submitted by the data user, it first verifies whether the applicant for the authenticity verification is permitted to use the authenticity verification service, and whether the authenticity verification letter has been tampered with, forged or damaged;

[0012] S2: Read the list of unique identifiers for data delivery to be verified in the authenticity verification letter, and determine whether the data delivery information is filed on the blockchain. If not, generate a statement declaring the invalidity of the corresponding data delivery information verification.

[0013] S3: Sequentially obtain each piece of on-chain filed data related to data delivery from the blockchain, such as data user information, data service contract element information, data delivery information, data authorization files, and data packet files.

[0014] S4: Obtain the data usage permission statement information from the data authorization statement file of the on-chain data related to the data delivery to be verified.

[0015] S5: Generate a data delivery validity statement based on the filed service contract related to the data delivery to be verified and the data delivery information.

[0016] S6: Generate a data user identity validity statement based on the data delivery information related to the data delivery to be verified and the data user identity information.

[0017] S7: According to the file path name and file record serial number in the data packet to be verified in the authenticity verification letter, read the specified file / data record content from the data packet file corresponding to the data delivery and calculate the hash value, and compare it with the corresponding file / data record hash value in the authenticity verification letter to form a data existence statement.

[0018] S8: After all data deliveries in the authentication letter are completed and the existence of corresponding documents / data records is verified, generate a data source credibility appraisal report based on the data delivery validity / invalidity statement, data usage permission statement, data user identity validity statement, and data existence statement, and use the digital identity of the data provider to digitally sign and confirm the appraisal report.

[0019] S9: Send the generated data source credibility appraisal report to the submitter of the data source credibility authentication letter.

[0020] Preferably, the trustworthy filing process for the data delivery related information includes the following steps:

[0021] (1) When establishing a data transaction / sharing service relationship with a data user, the data provider uploads the data provider identity information and data service contract information to the blockchain for deposit and evidence, and uses the anti-tampering, anti-forgery, and anti-loss characteristics of the blockchain to achieve trustworthy filing of the data related to the data service relationship.

[0022] (2) During the validity period of the data transaction / sharing service, when the data provider receives a data delivery application from the data user and constructs a data packet file and the corresponding data authorization statement file according to the user's needs, the data packet file, the data authorization statement file, and the data delivery operation information are delivered.

[0023] Preferably, the data source credibility verification party generates a data source credibility authentication letter based on the data packet file and the data authorization statement file to be verified in its own hands, and signs the authentication letter.

[0024] Preferably, after verifying the credibility of the data delivery related information in the authentication letter based on the data delivery data stored and filed in its own blockchain, the data provider generates a data source credibility appraisal report and uses the data provider digital certificate for signature confirmation.

[0025] Preferably, the data is converted into a pre-agreed intermediate format (character set, encoding method, XML / JSON data structure expression method) and stored in the form of a data packet file. The data packet is a zip compressed file containing 1 data packet composition list file, multiple data record set files, and multiple data record attachment files.

[0026] Preferably, the data packet composition list file includes instructions on which data record set files the structured data records contained in the data packet are respectively saved in and how to find the corresponding files in the data packet; which data record attachment files the unstructured data involved in all data records in the data packet are respectively saved in and how to find the corresponding files in the data packet.

[0027] Preferably, the data record set file is used to save structured data records of the same business data type (such as surface meteorological data, marine meteorological data);

[0028] Each data record is constructed in a pre-agreed character set, encoding method, and data structure expression method (XML, JSON), and the data records are sequentially saved in the data record set file separated by line breaks (\n); If the data provider needs to send data of multiple data service types simultaneously during the same data transaction / sharing process, it is included in the data packet in the form of different data record set files.

[0029] Preferably, the data record attachment file is used to save the unstructured data involved in the structured data record, such as pdf, doc, jpg.

[0030] Preferably, the information related to the data authorization statement is saved in a file, which is convenient to be sent to the data user together with the data packet and is persistently saved by both parties of the data transaction / sharing; The data authorization statement mainly includes three parts: the content of the data authorization statement, the digital signature of the data provider, and the identity certificate of the data provider.

[0031] Preferably, the content of the data authorization statement includes:

[0032] Unique identifier for data delivery: A globally unique identifier written by the data provider for the current data transaction / sharing, used to accurately mark a specific data transaction / sharing;

[0033] Hash value of the data packet: Calculate the hash value of the data packet file using the SM3 algorithm, which is convenient for the data user to quickly verify whether the received data packet is the same as that sent by the data provider and has not been tampered with, forged, or damaged;

[0034] Data packet generation time: The time when the data provider generates the current data packet file;

[0035] Data usage permission statement in the data packet: The data provider's statement of the usage permission granted to the data user for the data in the data packet; Such as data reading and processing, reselling to others; Set the effective time limit of the permission according to the time range and number of uses;

[0036] Hash list of files in the data packet: The hash values of all files in the data packet. Through the file path name and file hash value in the hash list of files in the data packet, the data user can quickly verify the consistency of specific files in the data packet;

[0037] Digital signature of the data provider: The data user uses the private key corresponding to the digital certificate issued by an authoritative certificate certification agency to digitally sign the hash value obtained by the SM3 algorithm for the content of the data authorization statement, which represents the data provider's confirmation of the content of the data authorization statement;

[0038] Data provider identity certificate: A digital certificate issued by an authoritative certificate certification agency for the data user.

[0039] Principle and beneficial effects of this technical solution:

[0040] (1) The present invention proposes an innovative blockchain-based mechanism for proving the credibility of the source of term data, aiming to improve the verification efficiency of the data user for the legality and consistency of each data record in the dataset; ensure that the data provider and the user can reach an indisputable consensus on the credibility of the dataset without relying on the endorsement of a third party; provide conclusive confirmation for the integrity of the data records included in the dataset, effectively preventing business decision-making mistakes caused by data loss and the determination of responsibilities in potential disputes; precisely define the legitimate data usage rights from the data category level limited when the two parties sign the contract to the specific data level of each exchange, making it easier to obtain evidence afterwards.

[0041] (2) The data user in the present invention submits a request for the required data to the data user through the connected data exchange technical means; the data provider generates a corresponding dataset according to the data acquisition request conditions and sends the dataset to the data user through the connected data exchange technical means. During the process of sending the dataset, the dataset is encrypted and the MD5 value corresponding to the sent dataset is provided; the data user can verify the consistency of the received data through MD5 after receiving the dataset, which can avoid data breakage, tampering, and forgery during the transmission process. Description of the drawings

[0042] Figure 1 It is a content description diagram of the data packet in the present invention;

[0043] Figure 2 It is a content description diagram of the data authorization statement document in the present invention;

[0044] Figure 3 It is a content description diagram of the letter of authenticity verification of data source in the present invention;

[0045] Figure 4 It is a content description diagram of the authenticity identification report of data source in the present invention;

[0046] Figure 5 It is a flowchart of the credible filing process of data delivery-related information in the present invention;

[0047] Figure 6 It is a flowchart of the authenticity verification process of data record source in the present invention;

[0048] Figure 7 It is the overall flowchart of the present invention;

[0049] The reference numerals in the accompanying drawings of the specification include: 1, a strap; 2, a guide wire; 3, a puncture needle; 4, a transfer cylinder; 5, a fixing block; 6, a catch; 7, a leading head; 8, a cannula; 9, a connecting cylinder; 10, a pipe support; 11, a compression airbag; 12, a fixed angle ruler; 13, a pointer; 14, a sliding groove; 15, a fixing sleeve; 16, a first spring; 17, a limiting plate; 18, a knob; 19, a clamping block; 20, a clamping block; 21, an orientation plate; 22, a guide block; 23, a guide groove; 24, a fixed cylinder; 25, a positioning groove; 26, an L-shaped groove; 27, a connecting sleeve; 28, a pressing plate; 29, a second spring; 30, a guide plate; 31, a control block; 32, a third spring; 33, a sliding button; 34, a baffle; 35, a rotating plate; 36, a spherical plug; 37, an elastic membrane. Detailed implementation manners

[0050] The present invention will be further described in detail below in conjunction with the accompanying drawings and implementation manners:

[0051] Embodiment:

[0052] When the data provider signs a data service contract with the data user and completes each data delivery, the data provider's identity information, data service contract information, data delivery information, data packet file, and data authorization statement information are chained and stored for record and filing. When the data source credibility certification service of the data provider receives the data source credibility authentication letter, it verifies the credibility of the data delivery-related information in the authentication letter based on the data delivery data stored for record in its own blockchain, and generates a data source credibility identification report and returns it to the data source credibility verification party.

[0053] The present invention utilizes the characteristics of anti-tampering, anti-forgery, and anti-loss of the blockchain, and combines the signature verification and hash operation algorithms in cryptography to propose a new data source credibility certification mechanism. This mechanism can accurately verify the credibility of the delivery data filed by the data provider and the validity of data delivery.

[0054] The specific usage mode and function of this embodiment:

[0055] As Figures 1 to 7 shown, the present invention provides a method for proving the credibility of meteorological data sources based on the blockchain, including 2 core processes and 2 formatted files. The 2 core processes respectively include a process for authenticating the credibility of the data record source and a process for credibly filing the data delivery-related information. The 2 formatted files respectively include a data source credibility authentication letter and a data source credibility identification report.

[0056] As Figure 6 shown, the process for authenticating the credibility of the data record source specifically includes the following steps:

[0057] S1: When the data provider receives the data source credibility authentication letter submitted by the data user, it first verifies whether the applicant for authentication submission is permitted to use the authentication service, and whether the authentication letter has been tampered with, forged, or damaged.

[0058] S2: Read the list of unique identifiers for data delivery to be verified in the authentication letter, and determine whether the data delivery information is recorded on the blockchain. If not, generate a corresponding statement declaring the verification of the data delivery information invalid.

[0059] S3: Sequentially obtain each piece of on-chain recorded data related to data delivery from the blockchain, such as data user information, data service contract element information, data delivery information, data authorization documents, and data packet files.

[0060] S4: Obtain the data usage permission statement information from the on-chain data authorization statement file related to the data delivery to be verified.

[0061] S5: Generate a data delivery validity statement based on the recorded service contract related to the data delivery to be verified and the data delivery information.

[0062] S6: Generate a data user identity validity statement based on the data delivery information and the data user identity information related to the data delivery to be verified.

[0063] S7: According to the file path name within the data packet to be verified in the authentication letter and the record serial number within the file, read the specified file / data record content from the data packet file corresponding to the data delivery, calculate the hash value, and compare it with the corresponding file / data record hash value in the authentication letter to form a data existence statement.

[0064] S8: After completing the verification of the existence of all data deliveries and the corresponding files / data records in the authentication letter, generate a data source credibility appraisal report based on the data delivery validity / invalidity statement, data usage permission statement, data user identity validity statement, and data existence statement, and digitally sign and confirm the appraisal report using the digital identity of the data provider.

[0065] S9: Send the generated data source credibility appraisal report to the submitter of the data source credibility authentication letter.

[0066] As Figure 5 shown, the process for trustworthy recording of information related to the data delivery includes the following steps:

[0067] (1) When the data provider establishes a data transaction / sharing service relationship with the data user, it records the data provider identity information and data service contract information on the blockchain, and uses the anti-tampering, anti-forgery, and anti-loss characteristics of the blockchain to achieve trustworthy recording of data related to the data service relationship.

[0068] (2) During the validity period of the data trading / sharing service, when the data provider receives a data delivery application from the data user and constructs a data packet file and the corresponding data authorization statement file according to the user's requirements, the data packet file, the data authorization statement file, and the data delivery operation information are delivered.

[0069] As Figure 3 shown, the data source credibility verification party generates a data source credibility authentication letter based on the data packet file and the data authorization statement file to be verified in its own hands, and signs the authentication letter.

[0070] As Figure 4 shown, the data provider verifies the credibility of the data delivery-related information in the authentication letter based on the data delivery data stored and filed in its own blockchain, generates a data source credibility appraisal report, and uses the data provider's digital certificate to sign and confirm.

[0071] As Figure 1 shown, the data is converted into a pre-agreed intermediate format (character set, encoding method, XML / JSON data structure expression method) and stored in the form of a data packet file. The data packet is a zip compressed file, which contains 1 data packet composition list file, multiple data record set files, and multiple data record attachment files.

[0072] As Figure 1 shown, the data packet composition list file includes instructions on which data record set files the structured data records included in the data packet are saved respectively, and how to find the corresponding files in the data packet; for the unstructured data involved in all data records in the data packet, it indicates which data record attachment files they are saved respectively, and how to find the corresponding files in the data packet.

[0073] As Figure 1 shown, the data record set files are used to save structured data records of the same business data type (such as surface meteorological data, marine meteorological data);

[0074] Each data record is constructed in a pre-agreed character set, encoding method, and data structure expression method (XML, JSON), and the data records are sequentially saved in the data record set file separated by line breaks (\n); if the data provider needs to send data of multiple data business types in the same data trading / sharing process, they are included in the data packet in the form of different data record set files.

[0075] As Figure 1 shown, the data record attachment files are used to save the unstructured data involved in the structured data records, such as pdf, doc, jpg.

[0076] AsFigure 2 As shown, the information related to the data authorization statement is saved in a file, which is convenient to be sent to the data user together with the data packet and is persistently saved by both parties of the data transaction / sharing. The data authorization statement mainly includes three parts: the content of the data authorization statement, the digital signature of the data provider, and the identity certificate of the data provider.

[0077] As Figure 2 shown, the content of the data authorization statement includes:

[0078] Unique identifier for data delivery: A globally unique identifier written by the data provider for the current data transaction / sharing, used to accurately mark a specific data transaction / sharing;

[0079] Hash value of the data packet: The hash value of the data packet file calculated using the SM3 algorithm, which is convenient for the data user to quickly verify whether the received data packet is the same as that sent by the data provider and has not been tampered with, forged, or damaged;

[0080] Generation time of the data packet: The time when the data provider generates the current data packet file;

[0081] Statement of data usage rights within the data packet: The statement of usage rights granted by the data provider to the data user for the data in the data packet; such as the right to read and process data, resell to others; set the effective time limit of the right according to the time range and number of uses;

[0082] List of file hash values within the data packet: The hash values of all files in the data packet. Through the file path names and file hash values in the list of file hash values within the data packet, the data user can quickly verify the consistency of specific files within the data packet;

[0083] Digital signature of the data provider: The data user uses the private key corresponding to the digital certificate issued by an authoritative certificate certification agency to perform a digital signature on the hash value obtained through the SM3 algorithm for the content of the data authorization statement, which represents the confirmation of the data provider for the content of the data authorization statement;

[0084] Identity certificate of the data provider: The digital certificate issued by an authoritative certificate certification agency for the data user.

[0085] The above are only the embodiments of the present invention, and the specific technical solutions and / or common knowledge of the features well known in the solution are not described in detail here. It should be noted that for those skilled in the art, without departing from the technical solution of the present invention, several deformations and improvements can be made, which should also be regarded as the protection scope of the present invention, and these will not affect the implementation effect of the present invention and the practicability of the patent. The protection scope required by this application should be based on the content of its claims, and the specific implementation manners recorded in the specification can be used to interpret the content of the claims.

Claims

1. A method for proving the credibility of meteorological data sources based on blockchain, characterized in that: It includes 2 core processes and 2 formatted documents. The 2 core processes respectively include the process for authenticating the credibility of the data record source and the process for credibly filing the information related to data delivery. The 2 formatted documents respectively include the letter of authenticity verification of the data source and the report on the authenticity appraisal of the data source.

2. The method for proving the credibility of meteorological data sources based on blockchain according to claim 1, characterized in that, The process for authenticating the credibility of the data record source specifically includes the following steps: S1: When the data provider receives the letter of authenticity verification of the data source submitted by the data user, it first verifies whether the applicant for authentication is permitted to use the authentication service, and whether the authentication letter has been tampered with, forged, or damaged. S2: Read the list of unique identifiers for data delivery to be verified in the authentication letter, and determine whether the data delivery information is filed on the blockchain. If not, generate a statement declaring the invalidity of the verification of the corresponding data delivery information.

3. A method for authenticating the credibility of meteorological data sources based on blockchain according to claim 2, characterized in that, The process for authenticating the credibility of the data record source specifically includes the following steps: S3: Sequentially obtain each piece of on-chain filed data related to data delivery from the blockchain, such as data user information, data service contract element information, data delivery information, data authorization documents, and data packet files. S4: Obtain the data usage permission statement information from the on-chain data authorization statement file related to the data delivery to be verified. S5: Generate a statement of the validity of data delivery based on the filed service contract related to the data delivery to be verified and the data delivery information. S6: Generate a statement of the validity of the data user's identity based on the data delivery information and the data user's identity information related to the data delivery to be verified. S7: According to the file path name in the data packet and the record serial number in the file to be verified in the authentication letter, read the specified file / data record content from the data packet file corresponding to the data delivery and calculate the hash value, and compare it with the corresponding file / data record hash value in the authentication letter to form a statement of data existence.

4. The method for proving the credibility of meteorological data sources based on blockchain according to claim 3, characterized in that, The process for authenticating the credibility of the data record source specifically includes the following steps: S8: After completing the verification of the existence of all data deliveries and the corresponding files / data records in the authentication letter, generate a report on the authenticity appraisal of the data source based on the statement of the validity / invalidity of data delivery, the data usage permission statement, the statement of the validity of the data user's identity, and the statement of data existence, and digitally sign and confirm the appraisal report using the digital identity of the data provider. S9: Send the generated report on the authenticity appraisal of the data source to the submitter of the letter of authenticity verification of the data source.

5. A method for authenticating the credibility of meteorological data sources based on blockchain according to claim 1, characterized in that, The process for credibly filing the information related to data delivery includes the following steps: (1) When the data provider establishes a data transaction / sharing service relationship with the data user, it stores the data provider's identity information and data service contract information on the chain for evidence preservation, and uses the anti-tampering, anti-forgery, and anti-loss characteristics of the blockchain to achieve the credible filing of the data related to the data service relationship. (2) During the validity period of the data transaction / sharing service, when the data provider receives the data delivery application from the data user and constructs a data packet file and the corresponding data authorization statement file according to the user's requirements, it delivers the data packet file, the data authorization statement file, and the data delivery operation information.

6. The method for proving the credibility of the source of meteorological data based on blockchain according to claim 1, characterized in that: The data source credibility verification party generates a data source credibility authentication letter based on the data packet file and the data authorization statement file to be verified in its own hands, and signs the authentication letter.

7. A method for proving the credibility of meteorological data sources based on blockchain according to claim 1, characterized in that: The data provider delivers data based on the data stored and filed in its own blockchain. After verifying the credibility of the data delivery-related information in the authentication letter, the data provider generates a data source credibility appraisal report and signs and confirms it using the data provider's digital certificate.

8. A method for proving the credibility of meteorological data sources based on blockchain according to claim 1, characterized in that: The data is converted into a pre-agreed intermediate format and stored in the form of a data packet file. The data packet is a zip compressed file, containing 1 data packet composition list file, multiple data record set files and multiple data record attachment files.

9. A method for proving the credibility of meteorological data sources based on blockchain according to claim 8, characterized in that: The data packet composition list file includes instructions on which data record set files the structured data records contained in the data packet are saved respectively, and how to find the corresponding files in the data packet; The unstructured data involved in all data records in the data packet are saved in which data record attachment files respectively, and how to find the corresponding files in the data packet.

10. A method for proving the credibility of meteorological data sources based on blockchain according to claim 8, characterized in that: The data record set file is used to save structured data records of the same business data type; Each data record is constructed in a pre-agreed character set, encoding method, and data structure expression method (XML, JSON), and the data records are sequentially saved in the data record set file separated by line breaks (\n); if the data provider needs to send data of multiple data service types simultaneously during the same data transaction / sharing process, it is included in the data packet in the form of different data record set files.

11. A method for proving the credibility of meteorological data sources based on blockchain according to claim 8, characterized in that: The data record attachment file is used to save the unstructured data involved in the structured data record.

12. A method for proving the credibility of meteorological data sources based on blockchain according to claim 11, characterized in that: The data authorization statement-related information is saved in a file for easy transmission to the data user together with the data packet, and is persistently saved by both parties of the data transaction / sharing; the data authorization statement mainly includes 3 parts: the content of the data authorization statement, the digital signature of the data provider, and the identity certificate of the data provider.

13. A method for proving the credibility of meteorological data sources based on blockchain according to claim 12, characterized in that, The content of the data authorization statement includes: Unique data delivery identifier: a globally unique identifier written by the data provider for the current data transaction / sharing, used to accurately mark a specific data transaction / sharing; Data packet hash value: the hash value of the data packet file calculated using the SM3 algorithm, which facilitates the data user to quickly verify whether the received data packet is the same as that sent by the data provider and has not been tampered with, forged, or damaged; Data packet generation time: the time when the data provider generates the current data packet file; Data usage permission statement in the data packet: the usage permission statement granted by the data provider to the data user for the data in the data packet; the permission validity period is set according to the time range and the number of uses; File hash list in the data packet: the hash values of all files in the data packet. Through the file path name and file hash value in the file hash list in the data packet, the data user can quickly verify the consistency of specific files in the data packet. Digital signature of the data provider: The data user uses the private key corresponding to the digital certificate issued by an authoritative certificate certification authority to digitally sign the hash value obtained through the SM3 algorithm for the content of the data authorization statement, which represents the confirmation of the data provider for the content of the data authorization statement; Identity certificate of the data provider: A digital certificate issued by an authoritative certificate certification authority for the data user.

Images