Education data evidence storage method and system based on alliance chain

Abstract

The invention discloses an alliance chain-based education data evidence storage method and system. The method comprises the following steps: constructing a dynamic certificate configuration mechanism based on metadata driving, and realizing zero-code dynamic definition of a certificate style through separation and association of a style column table and a certificate data table; a structured data evidence storage carrier is designed to flexibly bear diversified education data; an extensible XML character string is adopted to display full-amount evidence storage data, and credible verification of authenticity and integrity of the certificate is completed through multi-link Hash comparison; a four-level architecture is established, a data hierarchical storage strategy is implemented, data abstracts are linked, and lightweight evidence storage and privacy protection are achieved; and implementing a password-free authentication mechanism. According to the invention, the flexibility, the safety, the efficiency and the expandability of educational data evidence storage can be improved.

Description

Technical Field

[0001] This invention relates to the field of blockchain technology, and more specifically, to a method and system for storing educational data based on a consortium blockchain. Background Technology

[0002] Blockchain technology integrates distributed ledgers, cryptographic algorithms, and network technology, possessing characteristics such as tamper-proofness, traceability, and decentralization. Applying it to educational data storage can fundamentally enhance the credibility and circulation value of the data. Consortium blockchains, due to their advantages such as controllable participating nodes and flexible privacy protection mechanisms, are considered an ideal technology choice for building cross-institutional and cross-departmental educational data storage systems.

[0003] Existing blockchain-based educational certificate storage solutions still have many limitations: First, they lack flexibility, making it difficult to adapt to diverse scenarios such as holistic education, project-based learning, educational research, and data transfer; second, their storage capabilities are weak, lacking effective support for electronic documents and structured detailed data; third, resource efficiency is low, with the common practice of uploading all data to the blockchain leading to high storage pressure and maintenance costs; and fourth, the verification experience is poor, as the verification process relies heavily on account passwords, making it cumbersome and prone to leaking students' sensitive information. Furthermore, in cross-system and cross-departmental data collaboration, the heterogeneity of systems and the difficulty in mutually recognizing data credibility create "data silos."

[0004] For example, Chinese patent application CN113592677A discloses an education certificate management system based on consortium blockchain. It incorporates roles such as students, certificate issuers, and verifiers into the same system layer for processing. The certificate data is not preprocessed in layers, resulting in a heavy on-chain storage burden. Furthermore, it requires the maintenance of a large number of student accounts in an external system, which is not conducive to the localized control of sensitive information and privacy protection. Summary of the Invention

[0005] Technical problem to be solved: In order to solve the problems of inflexible certificate structure, weak data carrying capacity, heavy on-chain storage burden, cumbersome verification process and privacy risks in the existing technology, this invention proposes an educational data notarization method and system based on consortium blockchain.

[0006] In a first aspect, this disclosure provides a method for storing educational data based on a consortium blockchain, comprising the following steps:

[0007] Step S1: Construct a metadata-driven dynamic certificate configuration mechanism, which specifically includes: creating a certificate data table for storing certificate instance data, and a style column table for defining the certificate column structure, hierarchy and processing rules, and establishing the association between the certificate data table and the style column table through style identifiers;

[0008] Step S2 involves using the certificate as a structured data storage medium, with its column structure dynamically generated based on predefined style metadata. The certificate includes multiple columns, specifically:

[0009] Record the hash code of the certificate holder's identity in the regular column;

[0010] Record the hash code and attribute information of the electronic document to be stored in the remarks column;

[0011] The full data of the regular columns and the notes columns are encapsulated into an extensible structured data format and recorded in the full data detail storage column.

[0012] Perform a hash operation on the data in the full data detail storage field and record the generated hash value in the certificate hash code field;

[0013] Write back the index number, transaction ID and timestamp generated after on-chain evidence storage to the on-chain evidence storage data column;

[0014] The Uniform Resource Locator (URL) encoding used for certificate lookup and display is recorded in the QR code section;

[0015] Record the relevant information of the evidence storage unit and platform in other columns; It should be noted that the names “regular column”, “notes column”, “full data details storage column”, “certificate hash code column”, “on-chain storage data column”, “other columns” and “QR code column” mentioned in this invention are merely exemplary names used for ease of understanding, and their scope of protection should not be limited to these specific terms.

[0016] The core of this invention lies in the functions it achieves. Those skilled in the art will understand that any different naming conventions, structural combinations, or logical variations that achieve the same function should be considered equivalent to the corresponding sections in this invention. For example, referring to "regular sections" as "basic sections" or "main sections," referring to "remarks sections" as "extended sections" or "details sections," or integrating the functions of "full data detail storage section" and "certificate hash code section" into a single "integrity verification section"—these variations that do not depart from the core idea of ​​this invention all fall within the protection scope of this invention.

[0017] Step S3 involves constructing a four-tiered evidence storage architecture consisting of a consortium blockchain platform layer, an evidence storage business layer, a certificate issuance management layer, and a certificate verification layer, employing a layered data storage strategy. Among these,

[0018] The consortium blockchain platform layer is configured with a consortium blockchain platform, which consists of a cluster of consortium blockchain nodes and is responsible for the on-chain distributed storage of certificate data digests.

[0019] The evidence storage service layer can be configured with one or more evidence storage service nodes. Each evidence storage service node is equipped with a certificate data processing system, which is responsible for the preprocessing of certificate data before it is uploaded to the blockchain and the postprocessing of certificate data after it is uploaded to the blockchain.

[0020] The certificate management layer is configured with one or more certificate issuance nodes, which are responsible for the collection, review and full lifecycle management of certificate data;

[0021] The certificate verification layer provides a verification website and interface to support certificate holders and authorized verification parties in performing verification operations.

[0022] Step S4: In the certificate data processing system of the evidence storage business node, a dynamic certificate configuration mechanism based on metadata is adopted to perform the pre-processing before uploading to the chain, including generating a structured data string, calculating the certificate hash code, and completing the on-chain evidence storage according to the style column table rules; the post-processing after uploading to the chain includes synchronizing the on-chain evidence storage information, generating a query QR code, and exporting multi-format certificates.

[0023] Step S5: Implement a passwordless certificate verification mechanism. By comparing the on-chain evidence information, recalculating the data hash code, and verifying the certificate holder's identity hash code, the authenticity and integrity of the certificate are verified.

[0024] Furthermore, the certificate serves as a structured data storage carrier, and the certificate types include, but are not limited to, award certificates, course certificates, skill certificates, achievement certificates, project certificates, and data storage certificates; and explicitly excludes academic certificates and professional qualification certificates uniformly issued or certified by national education administrative departments or human resources and social security departments.

[0025] Furthermore, the certificate serves as a structured data storage carrier, and the data includes, but is not limited to, learning practice data, teaching and research data, and education management data; the learning practice data includes, but is not limited to, learning processes, practical experiences, innovative designs, experimental reports, and growth records; the teaching and research data includes, but is not limited to, lesson plans, courseware, project reports, and research data; and the education management data includes, but is not limited to, status data and cross-departmental or cross-system transfer data.

[0026] Furthermore, the certificate serves as a structured data storage carrier, and its column structure is divided into two parts: a data content column group and a storage verification column group.

[0027] The data content column group is used to record various attribute information of the certificate, specifically including a regular column for recording basic attributes and a supplementary column for recording extended attributes.

[0028] The evidence verification section group consists of a full data detail evidence section, a certificate hash code section, an on-chain evidence data section, a QR code section, and other sections.

[0029] The evidence verification section is linked to the data content section, working together to achieve complete evidence storage and convenient verification of certificate data.

[0030] Furthermore, the core of the certificate integrity preservation and verification lies in the synergistic effect of the full data detail preservation section and the certificate hash code section. The full data detail preservation section stores the full data of the data content section group in plaintext using an extensible structured data format such as XML or JSON, including the hash code of the preserved electronic file. The certificate hash code section records the hash value generated after performing a hash algorithm on the string data in the aforementioned full data detail preservation section. This hash value is synchronously uploaded to the consortium blockchain platform to complete distributed preservation. Thus, by comparing the real-time hash calculation result of the off-chain full data with the original hash value stored on-chain, efficient and reliable verification of the certificate content integrity can be achieved.

[0031] It is important to emphasize that the "Full Data Details Preservation Column" and the "Certificate Hash Code Column" in this invention together constitute an inseparable certificate full data integrity verification mechanism. This mechanism is the core of this invention for achieving data trustworthiness and traceability. The "Full Data Details Preservation Column," as the data source, completely preserves the original information of the certificate; while the "Certificate Hash Code Column," as the "digital fingerprint" of this data source, has a unique value that depends on the full data. During verification, by recalculating the hash value of the full data and comparing it with the value in the certificate hash code column, it is possible to confirm with a very high degree of confidence whether the certificate content has been tampered with since its issuance. Any technical solution that aims to achieve the same or similar integrity verification function but adopts different naming or structural combinations, such as merging the two for storage or storing them in other associated ways, as long as its core logic is still based on generating a "hash fingerprint" from the "full data" for verification, should be considered equivalent to the integrity verification mechanism of this invention and fall within the protection scope of this invention.

[0032] Furthermore, to more clearly describe the core functions of the present invention, the structured data storage carrier and its processing system can be functionally abstracted into multiple logical modules. The data storage carrier includes a data content portion and a credibility anchoring portion.

[0033] In its specific implementation, the data content section corresponds to the data content column group described in the specification, including a regular column for recording basic attributes and a supplementary column for recording extended attributes, used to record various attribute information of the certificate.

[0034] The credibility anchoring section, in its specific implementation, corresponds to the evidence storage and verification section group described in the specification. Its core function is to achieve complete evidence storage and convenient verification of certificate data. This section further includes:

[0035] A data source unit, in a specific implementation, corresponds to the full data detail evidence section, and is used to store the full data of the data content part in plaintext in an extensible structured data format, including the hash code of the evidenced electronic file;

[0036] In a specific implementation, a fingerprint unit corresponds to the certificate hash code field and is used to record the hash value generated after performing a hash algorithm on all the data in the data source unit.

[0037] Through this functional abstraction, the scope of protection of this invention is not limited to specific column names or module combinations, but covers any technical solution that implements the same core logic.

[0038] Furthermore, the "regular section" is used to record multiple basic attributes of the certificate, and can be dynamically added or removed according to the application scenario. The section labels are configurable and can be hidden.

[0039] Furthermore, the "Notes" section is used to record certificate extended attributes and specifically supports the following functions: it adopts a tree-like hierarchical structure, which can achieve at least two levels of nested sub-sections; it supports the hiding settings of section labels and content to avoid affecting certificate display and layout; and for electronic document storage scenarios, it can directly record file hash values.

[0040] Furthermore, the "Full Data Details Evidence Storage Section" is used to store all certificate evidence data in a structured format in plaintext. The full data from the regular sections and the supplementary sections are concatenated into XML or JSON strings and then stored and displayed in plaintext.

[0041] Furthermore, the "Certificate Hash Code" field is used to record and display specific hash values. These hash values ​​are generated by performing a hash algorithm on the string data in the full data detail storage field and are simultaneously uploaded to the consortium blockchain platform for on-chain storage. This forms a complete mechanism for full data hashing, recording, display, distributed on-chain storage of hash codes, and on-chain and off-chain collaborative verification, ensuring data integrity and traceability.

[0042] Furthermore, the "On-Chain Evidence Data" section is used to record and display the transaction ID, on-chain timestamp, and certificate index number obtained from the consortium blockchain platform after the certificate is stored on the blockchain.

[0043] Furthermore, the "Other Columns" section is used to record relevant information to assist in verification and enhance credibility, such as the name of the certificate storage unit, the website address of the certificate storage platform, the website address of the query platform, and the website address of the display platform, thereby providing a traceability channel for certificate verification and improving its credibility.

[0044] Furthermore, the "QR code section" contains an encoded certificate query link, which, after parsing, can obtain the Uniform Resource Locator (URL) of the certificate storage information disclosure webpage, certificate query platform, or achievement display webpage.

[0045] Furthermore, in the certificate data processing system of the evidence storage business node, a metadata-driven dynamic certificate configuration mechanism is adopted. This mechanism achieves zero-code dynamic configuration of the certificate structure by separating and storing the certificate's style metadata (i.e., column structure, hierarchical relationship, display and processing rules) from the instance data (i.e., the specific certificate content). System administrators can define new certificate types and styles by manipulating the "style column table," and the system will automatically generate corresponding data templates and processing logic, thereby overcoming the technical difficulties of high maintenance costs and inability to quickly respond to business changes caused by hard-coded certificate formats in traditional systems.

[0046] Furthermore, the data tiered storage strategy includes: the certificate holder's contact information is stored only at the certificate issuance management level and is not uploaded to the blockchain or the evidence storage business layer; electronic documents are stored at the certificate issuance management level and the certificate holder; the full certificate data is stored at the evidence storage business layer, the certificate issuance management level, and the certificate holder; the consortium blockchain platform layer only stores the data digest of the full certificate data; and the personal identification number in the certificate is stored in the form of a hash code instead of plaintext.

[0047] Furthermore, the passwordless verification mechanism includes: the verifier obtains certificate information by scanning a QR code or accessing a verification page; retrieves on-chain evidence data and compares it with the content displayed in the certificate; recalculates the hash value of the certificate content and compares it with the certificate hash code; verifies the certificate holder's identity hash code; and verifies the hash code of the electronic document; the verification is deemed successful only if all comparison steps pass.

[0048] Secondly, this disclosure provides an educational data storage system based on a consortium blockchain, characterized by comprising a four-level storage architecture consisting of a consortium blockchain platform layer, a storage business layer, a certificate issuance management layer, and a certificate verification layer.

[0049] The consortium blockchain platform layer is configured with a consortium blockchain platform, which is jointly maintained by multiple entities with educational certificate issuing qualifications. The consortium blockchain platform includes a network node cluster formed by server nodes and consortium blockchain software. Software modules can be deployed on server nodes; the software includes a client module, at least two peer node modules, and at least three sorting node modules. The client module is configured with a relational database, data uplink interface, and query verification interface; the peer node modules act as on-chain ledger nodes, deploying a NoSQL database; and the sorting node modules perform time-series sorting of all transactions on the network.

[0050] The evidence storage service layer is configured with one or more evidence storage service nodes. Each evidence storage service node includes server hardware and certificate data processing system software deployed on it.

[0051] The certificate management layer configures certificate issuance nodes, which are responsible for the collection of certificate data, compliance review, and full lifecycle management. Certificate issuance nodes are managed by the certificate issuing unit and include computers and their management software. Certificate issuance nodes are connected to certificate storage business nodes to serve certificate holders in the certificate verification layer.

[0052] The certificate verification layer is configured to support certificate holders and authorized verification parties to perform verification operations through a visual interface or API call.

[0053] The layers and nodes in the four-level evidence storage architecture work together to implement the educational data evidence storage method as described in any one of the first aspects.

[0054] Furthermore, the certificate data processing system is used to perform preprocessing before certificate data is uploaded to the blockchain and postprocessing after it is uploaded, and includes:

[0055] A database module is used to store the certificates, full certificate data, certificate hash codes, consortium blockchain notarization information, certificate style data, and user data for on-chain notarization.

[0056] A dynamic certificate model definition module, configured to create and maintain a metadata-driven dynamic certificate configuration model;

[0057] A data carrier generation module is configured to generate a structured data storage carrier based on the dynamic certificate configuration model;

[0058] A data source generation module is configured to extract the full data from the data content portion and encapsulate it into a structured data format;

[0059] A hash calculation module is configured to perform hash calculations on the entire dataset to generate fingerprint units;

[0060] A consortium blockchain interaction module is configured to submit hash values ​​to the consortium blockchain platform for notarization and write back on-chain information;

[0061] A tiered processing module configured to execute a data tiered storage strategy;

[0062] A certificate export module configured to generate certificates in structured XML, Word, or PDF formats;

[0063] A certificate QR code module, configured to encode the certificate query or display link as a QR code;

[0064] A login management module, configured to manage system users and permissions;

[0065] A passwordless verification interface configured to verify the authenticity and integrity of certificates by comparing on-chain and off-chain hash values.

[0066] Beneficial effects: Compared with the prior art, the present invention has the following effects:

[0067] Highly flexible and scalable: Through a dynamically configurable certificate section structure and support for nested notes sections, it effectively adapts to the diverse and non-standardized educational scenarios.

[0068] High configuration efficiency and low maintenance cost: With the metadata-driven dynamic certificate configuration mechanism, the certificate style can be dynamically defined and adjusted with zero code, which greatly reduces the development and long-term maintenance costs of the system.

[0069] Convenient and highly reliable verification: By leveraging a full data integrity verification mechanism and a passwordless on-chain and off-chain collaborative verification mechanism, the user experience is optimized. At the same time, multiple hash comparisons ensure the authenticity and integrity of the certificate content and identity.

[0070] Lightweight storage and high security: Through a four-level evidence storage architecture and a data tiered storage strategy, data summaries are stored on-chain and all data is stored off-chain, which significantly reduces the on-chain burden. Furthermore, data privacy protection is enhanced through the localization and hashing of sensitive information.

[0071] Facilitating data flow: Supporting electronic document hash storage and standardized data export provides a technical solution for building a trusted collaborative network for educational data across systems and institutions. Attached Figure Description

[0072] Figure 1 This is a schematic diagram of the certificate section structure for this invention;

[0073] Figure 2 This is a schematic diagram of the consortium blockchain education data storage system of the present invention;

[0074] Figure 3 This is a structural diagram of the certificate data processing system module of the present invention;

[0075] Figure 4 This is a flowchart illustrating the certificate verification process for educational data storage in the consortium blockchain of this invention. Detailed Implementation

[0076] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that these embodiments are only used to illustrate the present invention and are not intended to limit the present invention. Any educational data storage method and system based on the core ideas of the present invention, employing the same or similar full data integrity verification mechanism, metadata-driven dynamic certificate configuration mechanism, data hierarchical storage strategy, and evidence storage verification mechanism in a consortium blockchain, despite differences in naming and structural combination, falls within the protection scope of the present invention.

[0077] Example 1: Method for Constructing Certificate Section Structure

[0078] Figure 1 A schematic diagram illustrating the certificate section structure of an embodiment of this disclosure is shown. Figure 1 As shown, the certificate column structure includes a regular column 101, a notes column 102, a full data details storage column 103, a certificate hash code column 104, an on-chain storage data column 105, other columns 106, and a QR code column 107.

[0079] The standard column 101 is used to record the basic attributes of the certificate, specifically including multiple columns such as certificate name, certificate type, number, certificate holder information, and project name. The standard column 101 is flexible in its configuration, supporting dynamic addition or removal of columns based on actual application scenarios, and allows for custom column labels. Furthermore, the standard column supports control over the display or hiding of column labels and content.

[0080] For example, the "Certificate Category" field in the regular categories includes, but is not limited to, award certificates, course certificates, skill certificates, achievement certificates, project certificates, growth records, research records, or data storage certificates. This field's tag can be set to hidden, preventing it from being displayed in the regular certificate category area. However, to ensure data integrity and verifiability, its full tag name and specific value will be forcibly concatenated into an XML or JSON string and simultaneously displayed in the full data detailed storage certificate field.

[0081] The appendix column 102 adopts a tree-like hierarchical structure, supports at least two levels of nested sub-columns (for example, "Sub-Appendix 1" can be further set as "Sub-Appendix 11", "Sub-Appendix 12", etc.), and supports the hiding control of column labels and content.

[0082] The following examples illustrate the structure of the notes section:

[0083] Application Scenario 1: Award Certificates

[0084] For award certificates containing submitted entries, the remarks section can have first-level sub-sections, including but not limited to: event name, event overview, winning entries, awarding organization, and hash algorithm. The "winning entries" section can be further subdivided into second-level sub-sections, including but not limited to: entry name, entry description, demonstration document hash code, production document hash code, and instructor. The "entry description" section can be further subdivided into tertiary sub-sections, including but not limited to: innovation points, key technologies, and technology platform, providing a fine-grained description of the technical content of the winning entries.

[0085] For award certificates that include entries, the “Awarded Works” sub-section can be replaced with “Entry”, the “Work Description” sub-section can be replaced with “Project Description”, and the other sub-sections can be replaced accordingly.

[0086] Application Scenario 2: Course Certificates

[0087] The remarks section may include first-level sub-sections, including but not limited to: course name, course type, course overview, credits, grade point average, issuing institution, and the hash algorithm used for the certificate. The "course overview" can be further subdivided into second-level sub-sections, including but not limited to: knowledge domain, key knowledge points, learning methods, and course instructor.

[0088] For project-based learning courses, the notes section can include a "Course Project" section, which can be further subdivided into second-level sub-sections, including but not limited to: project theme, project deliverables, and project document hash codes.

[0089] Application Scenario 3: Skills Certificates

[0090] The remarks section may include first-level sub-sections, including but not limited to: assessment items, relevant fields, assessment unit / department, assessment teachers, certification issuing unit, and hash algorithm. The "assessment items" section can be further subdivided into second-level sub-sections, including but not limited to: assessment content, assessment method, assessment conclusion, assessment time, and corresponding supporting documentation hash codes for the assessment process, thus achieving an objective, reliable, and verifiable evaluation of an individual's technical abilities.

[0091] Application Scenario 4: Certificate of Achievement

[0092] The remarks section may contain first-level sub-sections, including but not limited to: type of output, name of output, description of output, reviewer, issuing authority, and hash algorithm. The "description of output" can be further subdivided into second-level sub-sections, including but not limited to: significance of the output, hash code of the output presentation document, and hash code of the original output document. The values ​​for the "type of output" section include but are not limited to: work, software, project report, design document, lesson plan, and courseware.

[0093] Application Scenario 5: Project Certificates

[0094] The remarks section may contain first-level sub-sections, including but not limited to: project type, project name, project description, reviewer, issuing authority, and hash algorithm. The "project description" can be further subdivided into second-level sub-sections, including but not limited to: project overview, project records, and hash codes of project documents. The "project type" section may contain, but is not limited to: cultural and ideological work, arts and sports, labor practice, scientific and technological research, social service, growth records, and research records.

[0095] Application Scenario 6: Data Storage Certificate

[0096] The remarks section may include first-level sub-sections, including but not limited to: data type, file keywords, file name, file hash code, file details, issuing authority, and hash algorithm. "Data type" can be further subdivided into second-level sub-sections, including but not limited to: research data, status data, data flow, data sharing, and data archiving; "File details" can be further subdivided into second-level sub-sections, including but not limited to: file version and reviewer.

[0097] The full data detail storage column 103 stores and displays the full data of the regular column 101 and the supplementary column 102 in plaintext in XML or JSON string format. The full data includes column labels and column content, which is convenient for machine reading and extraction, and provides a data foundation for subsequent integrity hash verification of certificate content.

[0098] The certificate hash code field 104 is used to record and display the certificate hash value generated after performing a hash algorithm on the string in the full data detail storage field 103.

[0099] The on-chain evidence storage data field 105 is used to record the transaction ID, on-chain timestamp, and certificate index number obtained from the consortium blockchain platform after the certificate is stored on the blockchain.

[0100] The other columns 106 are used to record relevant information such as the name of the certificate storage unit, the website address of the certificate storage platform, the website address of the query platform, and the website address of the display platform, so as to enhance the traceability and credibility of the certificate.

[0101] The QR code section 107 contains an encoded certificate query link, which, after parsing, can obtain the Uniform Resource Locator (URL) of the certificate storage information disclosure webpage, certificate query platform, or achievement display webpage.

[0102] Example 2: Layered Architecture for Consortium Blockchain Educational Data Storage

[0103] Figure 2 This diagram illustrates a layered architecture for consortium blockchain educational data notarization according to embodiments of the present disclosure. Figure 2As shown, the architecture is divided into the consortium blockchain platform layer 201, the evidence storage business layer 202, the certificate issuance management layer 203, and the certificate verification layer 204 from top to bottom.

[0104] Consortium blockchain platform 211 is located at consortium blockchain platform layer 201 and is jointly maintained by multiple entities with educational certificate issuance qualifications. These entities are institutions or government departments that have passed the consortium blockchain access mechanism review, including schools, educational institutions, and educational administrative departments. The platform consists of server hardware and consortium blockchain software. The software can use a mature and compliant consortium blockchain notarization system or can be built independently based on open-source frameworks such as Hyperledger Fabric. Its modules can be deployed on independent servers or virtual servers. The software has a client module, no less than two peer node modules, and no less than three sorting node modules. The client module is configured with data uplink interfaces, query and verification interfaces, and corresponding databases. The peer node modules, as on-chain ledger nodes, are responsible for the distributed storage of transaction data, block synchronization, and consistency maintenance, and each node maintains a complete copy of the ledger. The sorting node modules sort the transactions of the entire network in chronological order and support fault tolerance for up to one-third of the nodes.

[0105] The evidence storage service node 221 is located in the evidence storage service layer 202. Node 221 is the core service node for implementing evidence storage of educational data on the consortium blockchain, responsible for preprocessing certificate data before it is uploaded to the blockchain and post-processing after it is uploaded. Node 221 is operated and maintained by the evidence storage unit, and consists of server hardware and certificate data processing system software. Node 221 connects to the consortium blockchain platform 211 and to the certificate issuing nodes of multiple services.

[0106] The certificate issuance node 231 is located in the certificate issuance management layer 203. The certificate issuance node 231 is managed by the certificate issuing unit. The certificate issuance node 231 consists of a computer and the management software it uses. Each certificate issuing unit can choose different management software according to its own situation.

[0107] The certificate holder 241 and its authorized certificate verifier 242 are located in the certificate verification layer 204.

[0108] Example 3: Certificate Data Processing System Module Structure

[0109] It should be noted that the certificate data processing system described in this embodiment can be functionally abstracted into multiple logical modules to collaboratively implement the educational data storage method as described in the claims.

[0110] The database module is used to store certificate data, full certificate data, evidence storage information written back from the consortium blockchain, certificate style data, and user data. The function of the dynamic certificate model definition module can be achieved by the certificate style module (used to define the column structure) and the data import module (used to receive instance data) working together to complete the separate storage of structure definition and instance data;

[0111] The function of the data carrier generation module can be implemented by the data concatenation hashing and chaining module when performing data encapsulation.

[0112] The function of the data source generation module can be implemented by the data concatenation hashing and chaining module when concatenating the full data string;

[0113] The function of the hash calculation module can be implemented by the data concatenation hash chaining module when performing hash operations;

[0114] The function of the consortium blockchain interaction module is implemented by the data uploading and on-chain evidence storage data write-back module.

[0115] The functionality of the layered processing module is reflected in the data processing flow of the entire system within the four-level architecture;

[0116] The functionality of the certificate export module is implemented by the certificate printing and file export modules;

[0117] The functionality of the certificate QR code module is implemented by the certificate QR code module;

[0118] The functions of the login management module are implemented by the login management module; The functionality of the passwordless verification interface is implemented by the verification website and interface provided by the system.

[0119] Figure 3 A specific modular structure diagram of a certificate data processing system according to an embodiment of the present disclosure is shown. Figure 3 As shown, the system includes a login management module 301, a certificate style module 302, a data import module 303, a data concatenation and hashing on-chain module 304, an on-chain evidence storage data write-back module 305, a certificate QR code module 306, a certificate printing and file export module 307, and a database module 308. It should be noted that... Figure 3 The module structure shown is a specific implementation of the present invention. The functional module described in claim 7 can be implemented through... Figure 3 It is achieved through the collaborative work of one or more specific modules.

[0120] The database module 308 is the system's local database, employing a structured relational database format. It stores certificates used for on-chain evidence storage, full certificate data, certificate hash codes, consortium blockchain evidence storage information, certificate style data, and user data. This database includes at least a certificate data table and a style category table.

[0121] The certificate data table is used to store instance data for each certificate, and each record corresponds to a unique certificate.

[0122] The style column table is used to predefine the column structure of the certificate. Each record corresponds to the attributes and processing rules of a column field, including but not limited to column labels, display order, nesting level, data format and processing logic.

[0123] The style category table and the certificate data table are linked through the "style number" key field, forming a relationship where a certificate style (corresponding to a set of records in the style category table) can be referenced by multiple specific certificates (corresponding to multiple records in the certificate data table).

[0124] The style table is the core of this invention for implementing dynamic certificate configuration, concatenating full XML strings, and exporting electronic certificates. It is a configuration table that stores certificate "metadata" and defines the complete structure, style, and processing rules for a certificate type. By manipulating this table, a certificate type can be created, modified, or deleted without modifying the program code.

[0125] In a preferred embodiment, the style column table includes, but is not limited to, the fields (columns) shown in Table 1: Table 1 Field Name Data types Function Description Field ID (Field_ID) Integer Unique identifier. This ID is the unique primary key for this record. Style ID (Style_ID) String Style identifier. All sections belonging to the same certificate style share the same Style_ID. Category order (Field_SN) Integer The order in which fields are processed. Parent field ID (Parent_ID) String Hierarchical relationship identifier. Used to construct nested structures. If this category is a top-level category, this field is 1; if it is a sub-category, this field records the Field_ID of its parent category. Field key name (Key_Name) String Internal system key name. Column Labels String The category name is also the category tag in the XML string. Category level Integer Construct a nested hierarchy. The top-level category is 1, the first-level sub-category is 2, the second-level sub-category is 3, and so on. Processing attribute (Pro_Attr) String Define the processing attributes for this column, such as whether it is displayed or whether it is a supplementary column.

[0126] It should be noted that the embodiments are only used to illustrate the present invention and are not intended to limit the present invention.

[0127] In a preferred embodiment, a certificate of type "Award Certificate" may have a style ID of "S006". The administrator configures multiple records in the style column table through the certificate style module 301. Example records for the data content column group are shown in Table 2. Table 2 Field_ID Style_ID Field_SN Key_Name Label Parent_ID level Pro_ Attr 450 S006 1 certTitle Title 1 1 Half-display, regular 451 S006 2 certType Certificate Type 1 1 Half-display, regular 452 S006 3 certCode Certificate Number 1 1 Display, Normal, 453 S006 4 holderName Award winner's name 1 1 Display, standard 454 S006 5 holderID ID number (hash code) 1 1 Display, Normal, 455 S006 6 projectName Award-winning projects 1 1 Display, standard 460 S006 10 postScript1 Postscript 1 1 Display, notes 461 S006 11 postScript2 Title of the work postScript1 2 Hidden, Postscript 462 S006 12 postScript3 Display document hash code postScript2 3 Hidden, Postscript 463 S006 13 postScript4 Display URL postScript2 3 Hidden, Postscript 464 S006 14 postScript5 Description of the work postScript2 3 Hidden, Postscript 465 S006 15 postScript6 Innovation postScript5 4 Hidden, Postscript 466 S006 16 postScript7 Key technologies postScript5 4 Hidden, Postscript 467 S006 17 postScript8 Technology Platform postScript5 4 Hidden, Postscript 468 S006 18 postScript9 Instructor postScript2 3 Hidden, Postscript 469 S006 19 issueTime Certificate Issuance Time postScript1 2 Hidden, Postscript 470 S006 20 issueUnit Issuing Authority postScript1 2 Hidden, Postscript 471 S006 21 hashAlgorithm Hash Algorithm postScript1 2 Hidden, Postscript

[0128] In Table 2, the Pro_Attr column has the following settings: "Partially Displayed" means only the column content is displayed, and the column label is hidden; "Display" means both the column label and content are displayed; "Hidden" means both the column label and content are hidden; "Regular" is the regular column; "Notes" is the notes column; "Full" is the full data details column; "Hash Code" is the certificate hash code column; "On-Chain" is the on-chain evidence data column; "Other" is the other column; and "QR Code" is the QR code column.

[0129] It should be noted that this embodiment is only used to illustrate the present invention and is not intended to limit the present invention.

[0130] In a preferred embodiment, the certificate for the "data transfer certificate" can have a style ID of "S800". The administrator configures multiple records in the style column table through the certificate style module 301. Example records for the data content column group are shown in Table 3. Table 3 Field_ID Style_ID Field_SN Key_Name Label Parent_ID level Pro_ Attr 600 S800 1 certTitle Title 1 1 Half-display, regular 601 S800 2 certType voucher type 1 1 Half-display, regular 602 S800 3 certCode voucher number 1 1 Display, standard 603 S800 4 holderName Responsible person 1 1 Display, standard 604 S800 5 holderID Responsible Department 1 1 Display, standard 605 S800 6 projectName Project Name 1 1 Display, standard 610 S800 10 postScript1 Postscript 1 1 Display, notes 611 S800 11 postScript2 Data types postScript1 2 Hidden, Postscript 612 S800 12 postScript3 Keywords postScript1 2 Hidden, Postscript 613 S800 13 postScript4 file name postScript1 2 Hidden, Postscript 614 S800 14 postScript5 File hash code postScript1 2 Hidden, Postscript 615 S800 15 postScript6 Document Details postScript1 2 Hidden, Postscript 616 S800 16 postScript7 Document Version postScript6 3 Hidden, Postscript 617 S800 17 postScript8 Circulation Records postScript6 3 Hidden, Postscript 618 S800 18 postScript8 Reviewer postScript6 3 Hidden, Postscript 619 S800 19 postScript9 Certificate Issuance Time postScript1 2 Hidden, Postscript 620 S800 20 postScript 10 Issuing Authority postScript1 2 Hidden, Postscript 621 S800 21 hashAlgorithm Hash Algorithm postScript1 2 Hidden, Postscript

[0131] The annotations for the Pro_Attr column in Table 3 are the same as those in Table 2.

[0132] Example values ​​for the data type field can be: scientific research data, status data, data flow, data sharing, and data archiving.

[0133] It should be noted that this embodiment is only used to illustrate the present invention and is not intended to limit the present invention.

[0134] The certificate style module 302 is used to manipulate the style column table and generate new data upload templates according to the application scenario requirements after system deployment.

[0135] The data import module 303 imports data from the uploaded data table, which has been filled out and approved by the issuing authority, into the certificate data table in the database, based on the style column table.

[0136] The data concatenation and hashing on-chain module 304, based on the style column table, concatenates the data from the corresponding regular and supplementary columns in the certificate data table to generate an XML string, and assigns it to the full data detail storage column. This module further executes a specified hash algorithm on the XML string in the full data detail storage column, storing the generated hash code in the certificate hash code column of the certificate data table. Subsequently, the module fills the certificate number, certificate hash code, and other data into the on-chain data table and exports it.

[0137] The certificate storage unit submits the exported on-chain data table to the client of the consortium blockchain platform layer 201 to complete the consortium blockchain certificate storage.

[0138] After the on-chain evidence storage data write-back module 305 completes the evidence storage, it synchronizes the transaction ID, on-chain timestamp, and certificate index number from the consortium blockchain platform node database and writes them back to the local database. This module provides a passwordless verification interface, configured to respond to verification requests, and verifies the authenticity and integrity of the data storage carrier by comparing the hash value stored on-chain with the hash value calculated off-chain in real time.

[0139] The certificate QR code module 306 encodes the query URL on the certificate chain into a QR code image.

[0140] The certificate printing and file export module 307 is used to generate archiveable structured XML certificates, Word / PDF certificates with digital signatures and anti-modification marks, and supports batch printing of paper certificates through a local printer connected to the certificate storage business node.

[0141] The login management module 301 is responsible for system user login, user account management, role allocation and access control.

[0142] Example 4: Certificate verification flowchart for consortium blockchain education data storage.

[0143] Figure 4 This diagram illustrates a certificate verification flowchart for consortium blockchain educational data storage according to an embodiment of this disclosure. The process is as follows: Figure 4 As shown, the specific steps include:

[0144] Step S401: The verification process begins with accessing the certificate information. You can access the public webpage by scanning the certificate QR code or directly access the verification page of the consortium blockchain evidence storage platform.

[0145] Step S402, Verification of on-chain certificate hash code without password: Verify whether the certificate hash code, on-chain timestamp and other information stored on the consortium blockchain platform are consistent with the information displayed on the off-chain certificate. The key point is to confirm that the certificate hash code actually exists on the consortium blockchain and is consistent.

[0146] Step S403, Certificate Content Integrity Verification: Copy the string from the certificate's full data detail storage field to a built-in or trusted online hash tool for calculation, and compare the resulting hash code with the hash code displayed on the certificate. If they match, it proves that the certificate text content is complete and has not been tampered with.

[0147] Step S404, ID number verification: Input the ID number of the certificate holder in plaintext into the system's built-in or trusted online hashing tool, and compare the generated hash code with the ID number hash code displayed on the certificate. If they match, it proves that the ID number information is accurate;

[0148] Step S405: Determine if electronic document evidence exists. If it exists, proceed to step S406; otherwise, skip this step.

[0149] Step S406, Electronic document integrity verification: Drag the original electronic document into the system's built-in or trusted online file hashing tool, calculate the hash code, and compare it with the file hash code recorded in the certificate field. If they match, it proves that the original electronic document is complete and has not been tampered with;

[0150] Step S407: If all verifications from steps S402 to S406 are successful, the certificate verification is deemed successful and the certificate is valid.

[0151] Step S408: If any of the above verification steps fails, the verification is deemed to have failed and the certificate is invalid.

Claims

1. A method for storing educational data based on a consortium blockchain, characterized in that, Includes the following steps: Step 1: Define a metadata-driven dynamic certificate configuration model that separates the certificate structure definition from the certificate instance data for storage, so as to achieve dynamic configuration of certificate styles. Step 2: Based on the dynamic certificate configuration model, generate a structured data storage carrier; The data storage medium includes: A data content portion; and a credibility anchoring portion, the credibility anchoring portion comprising: A data source unit for storing the full data of the data content portion in an extensible structured data format; and A fingerprint unit is used to store a unique hash value calculated from the full dataset; Step 3: Distribute and store the hash value in the fingerprint unit on the consortium blockchain to establish a global root of trust for the data storage carrier; Step 4: Process and store the data storage carrier in a hierarchical architecture, wherein sensitive data is kept off-chain and only the hash value is uploaded on-chain as a digest. Step 5: Perform a passwordless verification process to verify the authenticity and integrity of the data storage carrier by comparing the hash value stored on the chain with the hash value calculated off-chain based on the data source unit in real time.

2. The method according to claim 1, characterized in that, The data storage carrier is used to carry non-academic educational data, including one or more of the following: award certificates, course certificates, skill certificates, achievement certificates, project certificates, or data transfer vouchers.

3. The method according to claim 1, characterized in that, The data content portion includes a basic attribute unit and an extended attribute unit; The basic attribute unit is used to record basic information about the certificate, and supports dynamic addition, deletion and custom display. The extended attribute unit adopts a tree-like hierarchical structure, supports nesting, and is used to record the hash value of electronic documents.

4. The method according to claim 1, characterized in that, The data source unit stores all the data, including all column labels and content of the data content section.

5. The method according to claim 1, characterized in that, The layered architecture includes a consortium blockchain platform layer, an evidence storage business layer, a certificate issuance management layer, and a certificate verification layer.

6. The method according to claim 1, characterized in that, The passwordless verification process also includes: verifying the hash code of the certificate holder's identity identifier, and, if there is an electronic document stored as evidence, verifying the hash value of the original electronic document.

7. A certificate data processing system deployed on a second-to-top-level certificate storage service node in a layered architecture, used to implement educational data certificate storage based on a consortium blockchain, characterized in that, The layered architecture features a consortium blockchain platform at the top layer, certificate management nodes at the bottom layer, and certificate holders and validators at the bottom layer; the system includes: A database module is used to store certificate data, full certificate data, evidence storage information written back from the consortium blockchain, certificate template data, and user data; A dynamic certificate model definition module is configured to create and maintain a metadata-driven dynamic certificate configuration model that separates the certificate's structural definition from the instance data. A data carrier generation module is configured to generate the data content portion of the data storage carrier based on the dynamic certificate configuration model; A data source generation module is configured to extract full data from the data content portion and encapsulate it in an extensible structured data format to form the data source unit of the credibility anchoring portion; A hash calculation module is configured to perform hash calculation on all data in the data source unit, generate a unique hash value, and form a fingerprint unit of the trust anchoring part. A consortium blockchain interaction module is configured to submit the hash value in the fingerprint unit to the consortium blockchain platform for distributed notarization, and write back the transaction ID, timestamp and certificate index number obtained from the consortium blockchain platform to the database module; A hierarchical processing module is configured to execute a hierarchical data storage strategy to ensure that sensitive data is kept off-chain and that only the hash value is uploaded to the chain as a digest. A certificate export module configured to generate certificates in structured XML, Word, or PDF formats; A certificate QR code module, configured to encode the certificate query or display link as a QR code; A login management module, configured to handle system user login, account management, role assignment, and access control; A passwordless verification interface is configured to respond to verification requests and verify the authenticity and integrity of the data storage carrier by comparing the hash value stored on the blockchain with the hash value calculated off-chain in real time.

8. The system according to claim 7, characterized in that, The dynamic certificate model definition module defines the certificate's column structure, hierarchical relationship, and processing rules by manipulating a style column table.

9. The system according to claim 7, characterized in that, The data source generation module is further configured to encapsulate the full data into an XML or JSON string.

10. The system according to claim 7, characterized in that, The system is configured to implement the educational data notarization method as described in any one of claims 1 to 6.

Images