A research and development material blind code management method and system, an electronic device, and a storage medium

Abstract

The present application relates to the technical field of research and development material information security management, and more particularly to a research and development material blind code management method and system, electronic equipment and storage medium, comprising: obtaining a warehouse-out request carrying a request user identifier, a project identifier, an experimental task identifier and a material to be warehoused out; determining a field-level visible permission according to at least two factors in the request user identifier, the project identifier, the experimental task identifier, the material sensitivity level and the operation scene; generating a dynamic blind code corresponding to the current warehouse-out task; establishing an encrypted mapping relationship between the dynamic blind code and the real material identifier, the batch identifier, the supplier information and the quality traceability information; generating a material display view based on the field-level visible permission, writing the dynamic blind code into the material label and the experimental record; and in response to a blind solving request, outputting real material information and generating an audit record according to the approval result, the blind solving field range and the effective time limit.

Description

Technical Field

[0001] This invention relates to the field of R&D material information security management technology, and in particular to a method, system, electronic device and storage medium for R&D material blind code management. Background Technology

[0002] In materials research and development, chemical formulation development, electronic packaging material development, and other R&D activities involving core formulations, R&D materials typically include resins, monomers, fillers, additives, catalysts, curing agents, solvents, additives, functional powders, and other key raw materials. The actual names, brands, suppliers, batches, procurement sources, quality certificates, and usage methods of these materials in different projects often constitute core technical secrets or trade secrets of the enterprise. Current R&D material management typically relies on enterprise resource planning systems, laboratory information management systems, electronic experimental record systems, or inventory management systems to achieve material warehousing, warehousing, inventory, experimental records, and quality traceability. These systems usually use the actual material name, supplier, batch number, or fixed internal material code as identification criteria. During material requisition, packaging, experimental recording, test data entry, and report writing, experimental personnel often have direct access to the actual material name, supplier information, batch information, or brand information.

[0003] Meanwhile, fixed codes are easily linked and inferred across projects. Existing ERP and LIMS systems typically assign a fixed internal code to each material. This fixed code remains unchanged throughout the material's lifecycle, and all outbound records, experimental records, and quality records use the same code. Personnel authorized to view outbound or experimental records can, through long-term accumulation, establish associations between fixed codes and specific suppliers, specific batches, and specific performance characteristics, gradually inferring the complete identity information and formulation logic of core materials.

[0004] The granularity of access control is insufficient. Existing RBAC / ABAC mainly solves page-level or module-level access control, but cannot achieve independent visibility control of different fields in the same material record, nor can it independently match permission rules for different operation scenarios such as material receiving, issuing, packaging, experimental records, outsourcing testing, and report export.

[0005] The system lacks a unified blind coding and back-end traceability mechanism. Existing systems lack a unified blind coding scheme for outsourced testing, supplier blind testing, customer sample testing, and AI modeling data export, resulting in the continued presence of genuine material information in delivered documents. Furthermore, existing systems struggle to provide comprehensive audits of unblinding actions, field-level access actions, and batch export actions. Summary of the Invention

[0006] To address the shortcomings of existing technologies, this invention provides a method, system, electronic device, and storage medium for developing blind code management of materials, which solves the technical problems in existing technologies such as fixed material codes being easily inferred across projects, insufficient granularity of access control, lack of unified blind coding, and lack of back-end traceability mechanisms.

[0007] To achieve the above objectives, the present invention provides a method for managing blind codes of research and development materials, comprising: Obtain a material outbound request, which includes at least the requesting user identifier, project identifier, experimental task identifier, and information about the material to be outbound; Based on at least two factors among the requesting user identifier, project identifier, experimental task identifier, material sensitivity level, and operation scenario, determine the field-level visibility permissions corresponding to the requesting user; Based on the information of the materials to be shipped out, determine the real material identifier and the real batch identifier corresponding to the material shipping request from the material master data; Based on at least one of the following factors: real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key, a dynamic blind code corresponding to the current outbound task is generated. The dynamic blind code does not contain plaintext information in supplier information, batch information, material name information, brand information, inbound time information, and project name information. The same real material identifier corresponds to different dynamic blind codes in different outbound tasks, different experimental tasks, or different projects. Establish a mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information and quality traceability information, and encrypt and store the mapping relationship; Based on the field-level visibility permissions, a material display view corresponding to the requesting user is generated, wherein the material display view displays the dynamic blind code and hides at least one of the real material name, supplier information, batch information, and brand information; Write the dynamic blind code into at least one of the following: material label, experimental record, outbound record, and test data record; In response to the unblinding request, based on the approval result, the scope of the unblinding fields, and the effective time limit for unblinding, output some or all of the true material information and generate an audit record corresponding to the unblinding request.

[0008] Furthermore, the information on materials to be shipped includes the actual material identifier, actual material name, brand information, supplier information, batch information, quality inspection records, safety data sheet, storage conditions, expiration date, material sensitivity level, and project binding relationship; The real material identifier is used to uniquely index all basic information of the corresponding material in the material master database.

[0009] Furthermore, the process of determining the field-level visibility permissions corresponding to the requesting user based on at least two factors among the requesting user identifier, project identifier, experimental task identifier, material sensitivity level, and operation scenario includes: Based on the requesting user identifier, determine the user role information, department information, and project authorization information to determine the user's basic permission scope. The user's basic permission scope uses fields as the smallest control granularity to independently control the display or hiding status of the real material name field, brand field, supplier information field, batch information field, formula information field, and quality inspection document field. Based on the project identifier and the experimental task identifier, determine the experimental stage information and task type information to determine the dynamic permission adjustment factor; Based on the material sensitivity level and operation scenario, determine the current operation scenario type and material confidentiality level. The operation scenario includes at least one of the following: material warehousing, material outbound, sample packaging, experimental record, performance testing, quality traceability, supplier blind testing, customer sample testing, outsourcing testing, competitor analysis, report export, and artificial intelligence modeling dataset generation. Based on the user's basic permission scope, dynamic permission adjustment factor, and material confidentiality level, determine the field-level visibility permissions corresponding to the current requesting user in the stated operation scenario.

[0010] Furthermore, the process of generating the material display view corresponding to the requesting user based on the field-level visibility permissions includes: Based on the field-level visibility permissions, determine the target view type corresponding to the current requesting user. The target view types include the experimenter view, project manager view, R&D manager view, quality management view, procurement view, and intellectual property management view. The experimenter view displays the dynamic blind code, material category information, safe operation information, storage condition information, expiration date information, and protection requirement information, while hiding the real material name information, supplier information, and batch information. The R&D manager view displays the actual material name information and experimental performance data, while hiding supplier information and batch information; The quality management view displays real batch information and quality traceability records, and hides formula ratio information according to permissions; The procurement view displays supplier information and procurement price information, while hiding formula information and experimental performance data. The intellectual property management view does not display the mapping relationship between the dynamic blind code and the actual material identifier by default.

[0011] Furthermore, the process of generating a dynamic blind code corresponding to the current outbound task based on at least one factor among the real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key, establishing a mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information, and quality traceability information, and encrypting and storing the mapping relationship includes: Encryption is performed based on at least one of the following factors: real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key, to generate a dynamic blind code. A check bit character is appended to the end of the dynamic blind code. The check bit character is used for integrity verification when label printing, manual entry, barcode scanning, and experimental record entry. Perform a uniqueness check on the dynamic blind code. When the dynamic blind code collides with a blind code already stored in the blind code library, regenerate the dynamic blind code until it is unique. The blind code generation strategy is selected based on the sensitivity level of the material. For high-sensitivity materials, one code is used for each outbound shipment or one code for each experimental task. For medium-sensitivity materials, one code is used for each project. For low-sensitivity materials, a fixed-cycle code rotation is used. A hierarchical key encryption architecture is used to encrypt and store the mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information and quality traceability information. The hierarchical key encryption architecture includes a master key and a derived key. The master key is rotated according to a preset period or when a security event is detected. After rotation, the new key is used to re-encrypt all mapping data and the historical key is retained.

[0012] Furthermore, based on the completion status of the outbound task, the closing status of the experimental task, or the preset validity period, the corresponding dynamic blind code is automatically marked as invalid; when the risk of blind code leakage is detected, the associated dynamic blind code is invalidated and a new dynamic blind code is regenerated.

[0013] Furthermore, the process of responding to the unblinding request, outputting partial or complete true material information based on the approval result, the scope of the unblinding fields, and the effective time limit for unblinding, and generating an audit record corresponding to the unblinding request, includes: The unblinding request includes at least one of the following: applicant identifier, reason for unblinding, list of fields to be unblinded, object to be unblinded, validity period, and approver identifier; Based on the material sensitivity level corresponding to each field in the list of blind fields to be resolved, determine the number of approvers and the identity requirements of approvers for each field, and determine whether to output the real material information based on the approval results of at least two approvers. When the list of fields to be unblinded includes a formula association information field or a complete material identification field, it requires joint approval from at least three parties before it takes effect. After approval, a display time window for the real information is set according to the effective time limit. Access to the real information will be automatically closed after the effective time limit is exceeded. When the unblinding request is marked as an emergency security request, after verifying that the requesting user has emergency unblinding permissions, the security-related real information is output immediately, and a supplementary approval process is triggered after the output. When generating experimental reports, outsourced test forms, customer delivery documents, or artificial intelligence modeling datasets, replace at least one of the real material name, supplier information, batch information, and brand information with the corresponding dynamic blind code. The audit log includes at least one of the following: requesting user identifier, approver identifier, unblinding time, unblinding reason, unblinding field, unblinding object, access terminal, export behavior, and watermark identifier.

[0014] This invention also provides a dynamic blind code management system for R&D materials, used to implement the blind code management method for R&D materials described in any of the above claims, comprising: The request acquisition module is used to acquire material outbound requests, unblinding requests, data export requests, and test record requests. The permission determination module has a built-in field-level permission matrix, which is used to calculate and output the field-level visibility permissions corresponding to the requesting user based on at least two factors in the requesting user identifier, project identifier, experimental task identifier, material sensitivity level and operation scenario. The material master data module is used to persistently store the actual material identifier, actual material name, grade information, batch information, supplier information, quality inspection records, safety data sheets, storage conditions, expiration date, material sensitivity level, and project binding relationships. The blind code generation module is used to generate dynamic blind codes based on at least one of the following factors: real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key. The module also performs collision verification, sensitivity level coding strategy, and check bit concatenation on the dynamic blind codes. The mapping storage module is used to establish and encrypt the mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information and quality traceability information, and supports key rotation and historical decryption. The view generation module is used to render display pages for multiple types of differentiated materials based on the field-level visibility permissions. The label printing module is used to generate desensitized material labels, which display the dynamic blind code, material category information, safety identification information, storage condition information, expiration date information, and QR code information. The experiment record module is used to write the dynamic blind code into the electronic experiment record, test record, and outbound ledger. The unblinding audit module is used to perform approval flow verification, time-limited unblinding control, full behavior audit log generation, and document watermark embedding. The desensitization export module is used to replace at least one of the real material name, supplier information, batch information and brand information with the corresponding dynamic blind code when generating experimental reports, outsourced test forms, customer delivery documents or artificial intelligence modeling datasets. The abnormal access detection module is used to detect user access behavior to multiple dynamic blind codes, multiple experimental tasks, or multiple material display views within a preset time window. It calculates the association inference risk value based on access frequency, access scope, cross-project access, and field combination. When the association inference risk value exceeds a preset threshold, it restricts access permissions, triggers secondary approval, or generates an abnormal access alarm.

[0015] The present invention also provides an electronic device, comprising: processor; A memory that stores computer programs; When the processor executes the computer program stored in the memory, it performs the steps of the blind code management method for R&D materials as described in any of the above. The processor has the ability to perform key encryption and decryption operations, generate watermarks, and calculate risk values ​​in real time.

[0016] The present invention also provides a computer-readable storage medium storing computer-readable instructions, which, when executed by a processor, implement the steps of the blind code management method for R&D materials as described in any of the preceding claims; The storage medium persistently stores encrypted mapping relationship data objects, permission matrix data objects, full audit log data objects, and invalid blind code list data objects. The storage medium also stores historical key archive data, which is used to trace the actual material information corresponding to historical blind codes.

[0017] Compared with the closest existing technology, the present invention has the following advantages: This invention obtains material outbound requests and determines field-level visibility permissions based on at least two factors, including the requesting user identifier, project identifier, experimental task identifier, material sensitivity level, and operational scenario. This achieves fine-grained permission control with fields as the smallest control granularity, overcoming the shortcomings of traditional RBAC / ABAC, which can only control page or module-level permissions.

[0018] Furthermore, this invention generates a dynamic blind code corresponding to the current outbound task based on at least one of the following factors: real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key. The same real material identifier corresponds to different dynamic blind codes in different outbound tasks, different experimental tasks, or different projects, completely eliminating the possibility of fixed codes being associated and inferred over a long period of time.

[0019] Furthermore, by establishing an encrypted mapping relationship between dynamic blind codes and real material identifiers, real batch identifiers, supplier information, and quality traceability information, the present invention enables the front-end experimental execution end to only access the blinded material identity, while the back-end can still maintain the traceability relationship between real materials, batches, suppliers, quality documents, and experimental data, thereby reducing the risk of leakage of R&D material information without affecting experimental safety and quality management.

[0020] Furthermore, this invention avoids excessive information exposure by setting up multiple differentiated views such as experimenter view, R&D manager view, quality management view, procurement view, and intellectual property management view, generating different field display ranges for different roles, projects, experimental stages, and operational scenarios.

[0021] Furthermore, by responding to unblinding requests, this invention outputs some or all of the true material information based on the approval results, the scope of unblinding fields, and the effective time limit for unblinding, and generates audit records, thereby achieving controlled management and complete traceability of unblinding behavior.

[0022] Furthermore, the present invention detects user access behavior to multiple dynamic blind codes, multiple experimental tasks, or multiple material display views within a preset time window through an abnormal access detection module. It calculates the association inference risk value based on access frequency, access scope, cross-project access, and field combination. When the risk value exceeds a preset threshold, it restricts access permissions, triggers secondary approval, or generates an abnormal access alarm, thereby achieving proactive prevention and control of batch data scraping and association inference behavior. Attached Figure Description

[0023] Figure 1 This is an embodiment of the present invention. Detailed Implementation To make the objectives and advantages of the present invention clearer, the present invention will be further described below with reference to embodiments; it should be understood that the specific embodiments described herein are merely for explaining the present invention and are not intended to limit the present invention.

[0024] Preferred embodiments of the present invention will now be described with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are merely illustrative of the technical principles of the present invention and are not intended to limit the scope of protection of the present invention.

[0025] Please see Figure 1 The diagram shows a flowchart of a blind code management method for materials developed according to an embodiment of the present invention. This embodiment of the blind code management method for materials developed includes: In this embodiment, step S1 involves obtaining a material outbound request, which includes at least the requesting user identifier, project identifier, experimental task identifier, and information about the material to be outbound.

[0026] Specifically, when researchers request material release, the system retrieves the material release request. This request includes a requesting user identifier (to identify the applicant), a project identifier (to determine the associated R&D project), an experimental task identifier (to determine the specific experimental task), and information about the material to be released (including the category, quantity, and purpose of the requested material). This information includes the actual material identifier, actual material name, brand information, supplier information, batch information, quality inspection records, safety data sheet, storage conditions, expiration date, material sensitivity level, and project binding relationship. The actual material identifier is used to uniquely index all basic information of the corresponding material in the material master database.

[0027] In this embodiment, a material master database is pre-established, which includes at least the real material identifier, real material name, material category, grade information, supplier information, batch information, warehousing time, inventory location, quality certification documents, safety data files, storage conditions, expiration date, material sensitivity level, and project binding relationship.

[0028] In this embodiment, step S2 determines the field-level visibility permissions corresponding to the requesting user based on at least two factors among the requesting user identifier, project identifier, experimental task identifier, material sensitivity level, and operation scenario.

[0029] Specifically, the process of determining field-level visibility permissions includes the following sub-steps: S21. Based on the requesting user identifier, determine the user role information, department information, and project authorization information to determine the user's basic permission scope. The user's basic permission scope uses fields as the smallest control granularity to independently control the display or hiding status of the real material name field, brand field, supplier information field, batch information field, formula information field, and quality inspection document field.

[0030] S22. Based on the project identifier and the experimental task identifier, determine the experimental stage information and task type information to determine the dynamic permission adjustment factor.

[0031] S23. Based on the material sensitivity level and operation scenario, determine the current operation scenario type and material confidentiality level. The operation scenario includes at least one of the following: material warehousing, material outbound, sample packaging, experimental record, performance testing, quality traceability, supplier blind testing, customer sample testing, outsourcing testing, competitor analysis, report export, and artificial intelligence modeling dataset generation.

[0032] S24. Based on the user's basic permission range, dynamic permission adjustment factor, and material confidentiality level, determine the field-level visibility permissions corresponding to the current requesting user in the operation scenario.

[0033] In this embodiment, step S3 involves determining the actual material identifier and actual batch identifier corresponding to the material outbound request from the material master data based on the information of the material to be outbound.

[0034] Specifically, the system searches and matches the material information to be shipped in the outbound request in the material master database to determine the real material identifier (uniquely identifying a material) and the real batch identifier (uniquely identifying a batch) corresponding to this outbound shipment, which are used for subsequent dynamic blind code generation and mapping relationship establishment.

[0035] In this embodiment, step S4 generates a dynamic blind code corresponding to the current outbound task based on at least one of the following factors: the real material identifier, the real batch identifier, the experimental task identifier, the outbound task identifier, the time parameter, and the system key. The dynamic blind code does not contain plaintext information in the supplier information, batch information, material name information, brand information, warehousing time information, and project name information. The same real material identifier corresponds to different dynamic blind codes in different outbound tasks, different experimental tasks, or different projects.

[0036] Specifically, the generation process of dynamic blind codes includes the following sub-steps: S41. Perform encryption operation based on at least one factor among the real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter and system key to generate dynamic blind code. Concatenate a check bit character to the end of the dynamic blind code. The check bit character is used for integrity verification when label printing, manual entry, barcode scanning, and experimental record entry.

[0037] Dynamic blind codes can be formatted as follows: M-XXXX-XXXX-C, where M represents the material blind code category, XXXX-XXXX is a random or pseudo-random character field, and C is a check digit.

[0038] S42. Perform a uniqueness check on the dynamic blind code. When the dynamic blind code collides with a blind code already stored in the blind code library, regenerate the dynamic blind code until it is unique.

[0039] S43. Select a blind code generation strategy based on the material sensitivity level. For high-sensitivity materials, use one code per outbound shipment or one code per experimental task. For medium-sensitivity materials, use one code per project. For low-sensitivity materials, use a fixed-cycle code rotation.

[0040] S44. A hierarchical key encryption architecture is used to perform encrypted storage on the mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information and quality traceability information. The hierarchical key encryption architecture includes a master key and a derived key. The master key is rotated according to a preset period or when a security event is detected. After rotation, the new key is used to re-encrypt all mapping data and the historical key is retained.

[0041] In this embodiment, step S5 involves establishing a mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information, and quality traceability information, and then encrypting and storing the mapping relationship.

[0042] Specifically, the system establishes a mapping relationship between dynamic blind codes and actual material identifiers, actual batch identifiers, supplier information, and quality traceability information. This mapping relationship is stored in a mapping database and saved using encryption. Ordinary laboratory personnel cannot directly access this mapping database.

[0043] In this embodiment, step S6 generates a material display view corresponding to the requesting user based on the field-level visibility permission. The material display view displays the dynamic blind code and hides at least one of the real material name, supplier information, batch information, and brand information.

[0044] Specifically, the process of generating a material display view includes the following sub-steps: S61. Based on the field-level visibility permissions, determine the target view type corresponding to the current requesting user. The target view type includes the experimenter view, project manager view, R&D manager view, quality management view, procurement view, and intellectual property management view.

[0045] S62. The experimenter view displays the dynamic blind code, material category information, safe operation information, storage condition information, expiration date information, and protection requirement information, while hiding the real material name information, supplier information, and batch information.

[0046] S63. The R&D manager view displays the actual material name information and experimental performance data information, and hides the supplier information and batch information.

[0047] S64. The quality management view displays real batch information and quality traceability record information, and hides formula ratio information according to permissions.

[0048] S65. The procurement view displays supplier information and procurement price information, and hides formula information and experimental performance data information.

[0049] S66. The intellectual property management view does not display the mapping relationship between the dynamic blind code and the real material identifier by default.

[0050] In this embodiment, step S7 involves writing the dynamic blind code into at least one of the material label, experimental record, outbound record, and test data record.

[0051] Specifically, the system generates desensitized material labels. These labels display the dynamic blind code, material category information, safety identification information, storage condition information, expiration date information, and QR code information. When recording experiments in the electronic experimental record system, researchers use only the dynamic blind code as the material identification. Experimental data, formulation data, test data, and process records are all linked to the dynamic blind code.

[0052] In this embodiment, step S8 involves responding to the unblinding request by outputting some or all of the real material information based on the approval result, the unblinding field range, and the effective time limit for unblinding, and generating an audit record corresponding to the unblinding request.

[0053] Specifically, the unblinding approval process includes the following sub-steps: S81, the unblinding request includes at least one of the following: applicant identifier, reason for unblinding, list of fields to be unblinded, object to be unblinded, validity period, and approver identifier.

[0054] S82. Based on the material sensitivity level corresponding to each field in the list of fields to be unsealed, determine the number of approvers and the identity requirements of approvers for each field, and determine whether to output the real material information based on the approval results of at least two approvers.

[0055] S83. When the list of fields to be unblinded includes a formula association information field or a complete material identification field, it shall take effect only after joint approval by at least three parties.

[0056] S84. After approval, set a display time window for real information according to the effective time limit, and automatically close access to real information after the effective time limit is exceeded.

[0057] S85. When the unblinding request is marked as an emergency security request, after verifying that the requesting user has emergency unblinding authority, the relevant security information is output immediately, and a supplementary approval process is triggered after the output.

[0058] S86. When generating experimental reports, outsourced test forms, customer delivery documents, or artificial intelligence modeling datasets, replace at least one of the following: real material name, supplier information, batch information, and brand information with the corresponding dynamic blind code.

[0059] S87. The audit record includes at least one of the following: requesting user identifier, approver identifier, unblinding time, unblinding reason, unblinding field, unblinding object, access terminal, export behavior, and watermark identifier.

[0060] In this embodiment, a blind code failure management step is also included: based on the completion status of the outbound task, the closing status of the experimental task, or the preset validity period, the corresponding dynamic blind code is automatically marked as invalid; when the risk of blind code leakage is detected, the associated dynamic blind code is invalidated and a new dynamic blind code is regenerated.

[0061] This invention provides a structure for a dynamic blind code management system for R&D materials, comprising: The request acquisition module is used to acquire material outbound requests, unblinding requests, data export requests, and test record requests.

[0062] The permission determination module has a built-in field-level permission matrix, which calculates and outputs the field-level visibility permissions corresponding to the requesting user based on at least two factors, including the requesting user identifier, project identifier, experimental task identifier, material sensitivity level, and operation scenario.

[0063] The material master data module is used to persistently store the actual material identifier, actual material name, grade information, batch information, supplier information, quality inspection records, safety data sheets, storage conditions, expiration date, material sensitivity level, and project binding relationships.

[0064] The blind code generation module is used to generate dynamic blind codes based on at least one of the following factors: real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key. The module then performs collision verification, sensitivity level coding strategy, and check bit concatenation on the dynamic blind codes.

[0065] The mapping storage module is used to establish and encrypt the mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information and quality traceability information, and supports key rotation and historical decryption.

[0066] The view generation module is used to render display pages for various differentiated materials based on the field-level visibility permissions.

[0067] The label printing module is used to generate desensitized material labels, which display the dynamic blind code, material category information, safety identification information, storage condition information, expiration date information, and QR code information.

[0068] The experiment record module is used to write the dynamic blind code into the electronic experiment record, test record, and outbound ledger.

[0069] The unblinding audit module is used to perform approval flow verification, time-limited unblinding control, full behavior audit log generation, and document watermark embedding.

[0070] The desensitization export module is used to replace at least one of the following with a corresponding dynamic blind code when generating experimental reports, outsourced test forms, customer delivery documents, or artificial intelligence modeling datasets: the real material name, supplier information, batch information, and brand information.

[0071] The abnormal access detection module is used to detect user access behavior to multiple dynamic blind codes, multiple experimental tasks, or multiple material display views within a preset time window. It calculates the association inference risk value based on access frequency, access scope, cross-project access, and field combination. When the association inference risk value exceeds a preset threshold, it restricts access permissions, triggers secondary approval, or generates an abnormal access alarm.

[0072] In this embodiment, the system pre-establishes a field-level permission matrix. The field-level permission matrix includes at least user roles, project permissions, material sensitivity levels, experimental phases, operation scenarios, and field visibility ranges.

[0073] The visible range of fields can include: dynamic blind code, material category, actual material name, actual grade, actual supplier, actual batch, quality certificate, safety data file, purchase price, inventory location, experimental purpose, project name, formula ratio, historical performance data, customer name, and external supplier name.

[0074] The system generates different display views based on a field-level permission matrix. The Lab Technician view includes dynamic blind codes, material categories, status, safety labels, storage conditions, expiration dates, and personal protective equipment requirements, but excludes the actual material names, supplier information, and batch information. The R&D Manager view includes the actual material names, material categories, performance trends, and project usage records, but excludes the actual suppliers and batches. The Quality Management view includes the actual material names, batches, quality certification documents, incoming inspection data, and anomaly records, but excludes the complete formulation ratio. The Procurement view includes suppliers, quotations, delivery dates, and procurement batches, but excludes project formulation ratios and experimental performance data. The Intellectual Property Management view includes actual material mapping information related to patent drafting, technical disclosure, and infringement analysis, but does not display purchase prices and inventory locations by default. The System Administrator view includes user management, permission configuration, and system maintenance functions, but does not display the business mapping relationship between dynamic blind codes and actual materials by default.

[0075] In this embodiment, the system establishes a mapping relationship between dynamic blind codes and actual material identifiers, actual batch identifiers, supplier information, and quality traceability information. The mapping relationship is illustrated below: Dynamic blind code: M-7KQ9-LP2-C Authentic Material Identifier: MAT-2026-0058 Actual material name: Epoxy Resin EP-X Supplier: Supplier A Batch: LOT-20260501 Material category: Resin Sensitivity level: High Storage conditions: 5~10℃ This mapping relationship is stored in a mapping database and encrypted using a hierarchical key encryption architecture. Ordinary researchers cannot directly access this mapping database.

[0076] In this embodiment, when a user needs to view the actual material information due to reasons such as quality abnormalities, customer complaints, supplier claims, patent drafting, project review, or safety incidents, the user submits a deblinding request. The deblinding request includes at least one of the following: applicant identifier, deblinding object, deblinding reason, fields to be deblinded, deblinding time limit, project identifier, and approver identifier.

[0077] The system determines the required approval level based on the object to be unblinded and the fields to be unblinded. For example, viewing only the actual material name can be approved by the project manager; viewing the actual supplier and actual batch can be jointly approved by the project manager and the quality manager; viewing complete formula-related information can be jointly approved by the project manager, the intellectual property manager, and the department head.

[0078] After approval, the system displays the approved material information to the applicant within a specified time. After the unblinding validity period expires, the system automatically closes access permissions. The system generates an audit log. The audit log includes at least one of the following: requesting user ID, approver ID, unblinding time, reason for unblinding, unblinding fields, unblinding object, access terminal, export behavior, and watermark identifier.

[0079] In a preferred implementation, if a user exports a file containing real material information, the system automatically adds a watermark to the exported file. The watermark includes at least one of the following: request user identifier, export time, project identifier, and unblinding request identifier.

[0080] The technical solution of the present invention has been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after these changes or substitutions will all fall within the scope of protection of the present invention.

Claims

1. A method for managing blind codes of research and development materials, characterized in that, include: Obtain a material outbound request, which includes at least the requesting user identifier, project identifier, experimental task identifier, and information about the material to be outbound; Based on at least two factors among the requesting user identifier, project identifier, experimental task identifier, material sensitivity level, and operation scenario, determine the field-level visibility permissions corresponding to the requesting user; Based on the information of the materials to be shipped out, determine the real material identifier and the real batch identifier corresponding to the material shipping request from the material master data; Based on at least one of the following factors: real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key, a dynamic blind code corresponding to the current outbound task is generated. The dynamic blind code does not contain plaintext information in supplier information, batch information, material name information, brand information, inbound time information, and project name information. The same real material identifier corresponds to different dynamic blind codes in different outbound tasks, different experimental tasks, or different projects. Establish a mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information and quality traceability information, and encrypt and store the mapping relationship; Based on the field-level visibility permissions, a material display view corresponding to the requesting user is generated, wherein the material display view displays the dynamic blind code and hides at least one of the real material name, supplier information, batch information, and brand information; Write the dynamic blind code into at least one of the following: material label, experimental record, outbound record, and test data record; In response to the unblinding request, based on the approval result, the scope of the unblinding fields, and the effective time limit for unblinding, output some or all of the true material information and generate an audit record corresponding to the unblinding request.

2. The method for managing blind codes of R&D materials according to claim 1, characterized in that, The information on materials to be shipped out includes the actual material identifier, actual material name, brand information, supplier information, batch information, quality inspection records, safety data sheet, storage conditions, expiration date, material sensitivity level, and project binding relationship. The real material identifier is used to uniquely index all basic information of the corresponding material in the material master database.

3. The method for blind code management of R&D materials according to claim 1, characterized in that, The process of determining the field-level visibility permissions corresponding to the requesting user based on at least two factors, including the requesting user identifier, project identifier, experiment task identifier, material sensitivity level, and operation scenario, includes: Based on the requesting user identifier, determine the user role information, department information, and project authorization information to determine the user's basic permission scope. The user's basic permission scope uses fields as the smallest control granularity to independently control the display or hiding status of the real material name field, brand field, supplier information field, batch information field, formula information, and quality inspection document field. Based on the project identifier and the experimental task identifier, determine the experimental stage information and task type information to determine the dynamic permission adjustment factor; Based on the material sensitivity level and operation scenario, determine the current operation scenario type and material confidentiality level. The operation scenario includes at least one of the following: material warehousing, material outbound, sample packaging, experimental record, performance testing, quality traceability, supplier blind testing, customer sample testing, outsourcing testing, competitor analysis, report export, and artificial intelligence modeling dataset generation. Based on the user's basic permission scope, dynamic permission adjustment factor, and material confidentiality level, determine the field-level visibility permissions corresponding to the current requesting user in the stated operation scenario.

4. The method for managing blind codes of R&D materials according to claim 1, characterized in that, The process of generating a material display view corresponding to the requesting user based on the field-level visibility permissions includes: Based on the field-level visibility permissions, determine the target view type corresponding to the current requesting user. The target view types include the experimenter view, project manager view, R&D manager view, quality management view, procurement view, and intellectual property management view. The experimenter view displays the dynamic blind code, material category information, safe operation information, storage condition information, expiration date information, and protection requirement information, while hiding the real material name information, supplier information, and batch information. The R&D manager view displays the actual material name information and experimental performance data, while hiding supplier information and batch information; The quality management view displays real batch information and quality traceability records, and hides formula ratio information according to permissions; The procurement view displays supplier information and procurement price information, while hiding formula information and experimental performance data. The intellectual property management view does not display the mapping relationship between the dynamic blind code and the actual material identifier by default.

5. The method for managing blind codes of R&D materials according to claim 1, characterized in that, The process of generating a dynamic blind code corresponding to the current outbound task based on at least one factor among the real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key, establishing a mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information, and quality traceability information, and encrypting and storing the mapping relationship includes: Encryption is performed based on at least one of the following factors: real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key, to generate a dynamic blind code. A check bit character is appended to the end of the dynamic blind code. The check bit character is used for integrity verification when label printing, manual entry, barcode scanning, and experimental record entry. Perform a uniqueness check on the dynamic blind code. When the dynamic blind code collides with a blind code already stored in the blind code library, regenerate the dynamic blind code until it is unique. The blind code generation strategy is selected based on the sensitivity level of the material. For high-sensitivity materials, one code is used for each outbound shipment or one code for each experimental task. For medium-sensitivity materials, one code is used for each project. For low-sensitivity materials, a fixed-cycle code rotation is used. A hierarchical key encryption architecture is used to encrypt and store the mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information and quality traceability information. The hierarchical key encryption architecture includes a master key and a derived key. The master key is rotated according to a preset period or when a security event is detected. After rotation, the new key is used to re-encrypt all mapping data and the historical key is retained.

6. The method for managing blind codes of R&D materials according to claim 5, characterized in that, Based on the completion status of the outbound task, the closure status of the experimental task, or the preset validity period, the corresponding dynamic blind code is automatically marked as invalid; when the risk of blind code leakage is detected, the associated dynamic blind code is invalidated and a new dynamic blind code is regenerated.

7. The method for managing blind codes of R&D materials according to claim 1, characterized in that, The process of responding to a deblinding request, outputting partial or complete true material information based on the approval result, the scope of the deblinding fields, and the effective time limit for deblinding, and generating an audit record corresponding to the deblinding request includes: The unblinding request includes at least one of the following: applicant identifier, reason for unblinding, list of fields to be unblinded, object to be unblinded, validity period, and approver identifier; Based on the material sensitivity level corresponding to each field in the list of blind fields to be resolved, determine the number of approvers and the identity requirements of approvers for each field, and determine whether to output the real material information based on the approval results of at least two approvers. When the list of fields to be unblinded includes a formula association information field or a complete material identification field, it requires joint approval from at least three parties before it takes effect. After approval, a display time window for the real information is set according to the effective time limit. Access to the real information will be automatically closed after the effective time limit is exceeded. When the unblinding request is marked as an emergency security request, after verifying that the requesting user has emergency unblinding permissions, the security-related real information is output immediately, and a supplementary approval process is triggered after the output. When generating experimental reports, outsourced test forms, customer delivery documents, or artificial intelligence modeling datasets, replace at least one of the real material name, supplier information, batch information, and brand information with the corresponding dynamic blind code. The audit log includes at least one of the following: requesting user identifier, approver identifier, unblinding time, unblinding reason, unblinding field, unblinding object, access terminal, export behavior, and watermark identifier.

8. A dynamic blind code management system for research and development materials, characterized in that, The method for managing blind codes of R&D materials according to any one of claims 1-7 includes: The request acquisition module is used to acquire material outbound requests, unblinding requests, data export requests, and test record requests. The permission determination module has a built-in field-level permission matrix, which is used to calculate and output the field-level visibility permissions corresponding to the requesting user based on at least two factors in the requesting user identifier, project identifier, experimental task identifier, material sensitivity level and operation scenario. The material master data module is used to persistently store the actual material identifier, actual material name, grade information, batch information, supplier information, quality inspection records, safety data sheets, storage conditions, expiration date, material sensitivity level, and project binding relationships. The blind code generation module is used to generate dynamic blind codes based on at least one of the following factors: real material identifier, real batch identifier, experimental task identifier, outbound task identifier, time parameter, and system key. The module also performs collision verification, sensitivity level coding strategy, and check bit concatenation on the dynamic blind codes. The mapping storage module is used to establish and encrypt the mapping relationship between the dynamic blind code and the real material identifier, real batch identifier, supplier information and quality traceability information, and supports key rotation and historical decryption. The view generation module is used to render display pages for multiple types of differentiated materials based on the field-level visibility permissions. The label printing module is used to generate desensitized material labels, which display the dynamic blind code, material category information, safety identification information, storage condition information, expiration date information, and QR code information. The experiment record module is used to write the dynamic blind code into the electronic experiment record, test record, and outbound ledger. The unblinding audit module is used to perform approval flow verification, time-limited unblinding control, full behavior audit log generation, and document watermark embedding. The desensitization export module is used to replace at least one of the real material name, supplier information, batch information and brand information with the corresponding dynamic blind code when generating experimental reports, outsourced test forms, customer delivery documents or artificial intelligence modeling datasets. The abnormal access detection module is used to detect user access behavior to multiple dynamic blind codes, multiple experimental tasks, or multiple material display views within a preset time window. It calculates the association inference risk value based on access frequency, access scope, cross-project access, and field combination. When the association inference risk value exceeds a preset threshold, it restricts access permissions, triggers secondary approval, or generates an abnormal access alarm.

9. An electronic device, characterized in that, include: processor; A memory that stores computer programs; When the processor executes the computer program stored in the memory, it performs the steps of the blind code management method for R&D materials as described in any one of claims 1 to 7; The processor has the ability to perform key encryption and decryption operations, generate watermarks, and calculate risk values ​​in real time.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-readable instructions, which, when executed by a processor, implement the steps of the blind code management method for R&D materials as described in any one of claims 1 to 7. The storage medium persistently stores encrypted mapping relationship data objects, permission matrix data objects, full audit log data objects, and invalid blind code list data objects. The storage medium also stores historical key archive data, which is used to trace the actual material information corresponding to historical blind codes.

Images