A mass spectrometry data auditing processing method, device, equipment, medium and product

Abstract

The application discloses an audit processing method, device and equipment of mass spectrum data, a medium and a product, and relates to the technical field of data processing. The method comprises the following steps: when an operation request of a data operation on mass spectrum data is captured in a kernel layer, it is verified whether the request carries a compliance token; if the request carries the compliance token, compliance information of the operation and a physical address of the mass spectrum data are collected; a data fingerprint of the mass spectrum data is generated based on the physical address; an audit record corresponding to a previous historical operation is obtained from a linear audit chain; an audit record corresponding to the operation is generated according to the compliance information, the data fingerprint of the mass spectrum data and the audit record corresponding to the previous historical operation; the content of the audit record corresponding to the operation is spliced and hash calculated to obtain an integrity check value; the audit record corresponding to the operation is added to the linear audit chain; when the operation is a high-risk operation, the integrity check value is notarized by using a block chain; and the operation is performed on the mass spectrum data after the notarization.

Description

Technical Field

[0001] This application relates to the field of data processing technology, and in particular to a method, apparatus, equipment, medium and product for auditing mass spectrometry data. Background Technology

[0002] Liquid chromatography-mass spectrometry (LC-MS) and gas chromatography-mass spectrometry (GC-MS) are core tools for biomedical research and development. With increasingly stringent regulatory requirements, data integrity of mass spectrometry data has become crucial for compliance. Laws and regulations in some countries and regions impose stringent requirements on the authenticity, reliability, and legal validity of electronic records and electronic signatures.

[0003] Existing mass spectrometry data auditing systems suffer from the following fundamental defects:

[0004] Application-layer defense failure: Existing auditing is mostly based on the application software layer, which cannot prevent users with high-level operating system privileges (such as Root / Admin) from bypassing the software and directly tampering with the underlying mass spectrometry data. This architecture fails to meet the definition of a closed system in auditing.

[0005] The chain of evidence is fragile: the audit logs of traditional relational databases lack strong cryptographic bindings at the micro level, making them easy to be silently deleted or modified. Summary of the Invention

[0006] This application provides a method, apparatus, equipment, medium, and product for auditing mass spectrometry data, in order to solve or at least partially solve the defects or deficiencies in related technologies.

[0007] Firstly, this application provides a method for auditing mass spectrometry data, the method comprising:

[0008] When an operation request for data manipulation of mass spectrometry data is captured at the kernel layer, verify whether the operation request carries a compliance token indicating that the data operation is a preset operation from a preset trusted source.

[0009] If the operation request carries the compliance token, collect the electronic signature of the data operation, the operation intent, and the physical address of the mass spectrometry data to be operated;

[0010] Based on the physical address of the mass spectrometry data, a data fingerprint of the mass spectrometry data is generated;

[0011] The audit record corresponding to the previous historical data operation is obtained from the linear audit chain; the linear audit chain records the audit record corresponding to each historical data operation in chronological order of the operation request time.

[0012] Based on the electronic signature, the operation intent, the data fingerprint of the mass spectrometry data, and the audit record corresponding to the previous historical data operation, an audit record corresponding to the data operation is generated.

[0013] The contents of the audit record corresponding to the data operation are concatenated and hashed to obtain the integrity verification value of the audit record corresponding to the data operation;

[0014] Add the audit records corresponding to the data operations to the linear audit chain;

[0015] In the case that the data operation is a preset high-risk operation, the integrity verification value of the audit record corresponding to the data operation is taken from the linear audit chain and stored on the blockchain as a transaction.

[0016] After the integrity verification value of the audit record corresponding to the data operation is stored on the blockchain, the data operation is performed on the mass spectrometry data.

[0017] Optionally, in some embodiments of this application, the auditing method for the mass spectrometry data further includes:

[0018] If the data operation is not a preset high-risk operation, the data operation is performed on the mass spectrometry data;

[0019] Monitor whether the conditions for aggregation and on-chain processing are met;

[0020] When the aggregation conditions are met, all audit records that have not been stored on the blockchain, including the audit records corresponding to the data operations contained in the linear audit chain, are stored on the blockchain.

[0021] Optionally, in some embodiments of this application, generating the audit record corresponding to the data operation based on the electronic signature, the operation intent, the data fingerprint of the mass spectrometry data, and the audit record corresponding to the previous historical data operation includes:

[0022] Generate a first component representing the storage location of the audit record corresponding to the data operation;

[0023] A second component representing the data operation subject is generated based on the electronic signature;

[0024] A third component representing the data operation is generated based on the operation information of the data operation;

[0025] A fourth component representing the operation object information of the data operation is generated based on the descriptive information of the mass spectrometry data.

[0026] Based on the operation request of the data operation and the data fingerprint of the mass spectrometry data, a fifth component representing the data change details of the mass spectrometry data is generated;

[0027] A sixth component representing the generation time of the audit record corresponding to the data operation is generated based on the current system timestamp.

[0028] A seventh component representing the operation intent and extended context of the data operation is generated based on the operation intent and the current operating environment of the data operation.

[0029] Based on the integrity verification value of the audit record corresponding to the previous historical data operation, an eighth component representing the preceding audit record information of the audit record corresponding to the data operation is generated.

[0030] The audit record corresponding to the data operation is obtained by fusing the first component, the second component, the third component, the fourth component, the fifth component, the sixth component, the seventh component, and the eighth component.

[0031] Optionally, in some embodiments of this application, generating a seventh component representing the operation intent and extended context of the data operation based on the operation intent and the current runtime environment of the data operation includes:

[0032] For the data operation, an external trusted timestamp is obtained, and a seventh component representing the operation intent, extended context, and generation time of the audit record corresponding to the data operation is generated based on the operation intent, the current running environment of the data operation, and the external trusted timestamp.

[0033] Adding the audit record corresponding to the data operation to the linear audit chain includes:

[0034] Determine whether the system timestamp in the audit record corresponding to the data operation differs from the external trusted timestamp by no more than a preset time deviation;

[0035] If the system timestamp in the audit record corresponding to the data operation differs from the external trusted timestamp by no more than a preset time deviation, the audit record corresponding to the data operation is added to the linear audit chain.

[0036] Optionally, in some embodiments of this application, the auditing method for the mass spectrometry data further includes:

[0037] When a deletion operation is received for a target audit record in the linear audit chain, an audit record corresponding to the deletion operation is generated; in the audit record corresponding to the deletion operation, the operation type of the deletion operation is deletion, the operation intent of the deletion operation is invalidation, and the associated object of the deletion operation is the integrity verification value of the target audit record;

[0038] Add the audit record corresponding to the deletion operation to the linear audit chain.

[0039] Optionally, in some embodiments of this application, generating a data fingerprint of the mass spectrometry data based on the physical address of the mass spectrometry data includes:

[0040] Using the physical address of the mass spectrometry data as the input source, an incremental hash calculation is performed based on the mass spectrometry data and the intermediate state variable obtained from the previous incremental hash calculation using a streaming hash algorithm to obtain the intermediate state variable corresponding to the current time node, and the intermediate state variable corresponding to the current time node is determined as the data fingerprint of the mass spectrometry data.

[0041] Secondly, this application provides an audit processing apparatus for mass spectrometry data, the mass spectrometry data audit processing apparatus comprising:

[0042] The compliance verification module is configured to verify whether an operation request for a data operation on mass spectrometry data carries a compliance token indicating that the data operation is from a preset trusted source when an operation request for a data operation on mass spectrometry data is captured at the kernel layer.

[0043] The information collection module is configured to collect the electronic signature of the data operation, the operation intent, and the physical address of the mass spectrometry data to be operated if the operation request carries the compliance token.

[0044] A fingerprint generation module is configured to generate a data fingerprint of the mass spectrometry data based on the physical address of the mass spectrometry data;

[0045] The audit chain reading module is configured to retrieve the audit record corresponding to the previous historical data operation from the linear audit chain; the linear audit chain records the audit record corresponding to each historical data operation in chronological order of the operation request.

[0046] The record generation module is configured to generate an audit record corresponding to the data operation based on the electronic signature, the operation intent, the data fingerprint of the mass spectrometry data, and the audit record corresponding to the previous historical data operation.

[0047] The hash calculation module is configured to concatenate and hash the contents of the audit record corresponding to the data operation to obtain the integrity verification value of the audit record corresponding to the data operation.

[0048] The record addition module is configured to add the audit records corresponding to the data operations to the linear audit chain;

[0049] The on-chain evidence storage module is configured to, in the case that the data operation is a preset high-risk operation, retrieve the integrity verification value of the audit record corresponding to the data operation from the linear audit chain as the transaction and store it on the blockchain for on-chain evidence storage.

[0050] The operation execution module is configured to perform the data operation on the mass spectrometry data after the integrity verification value of the audit record corresponding to the data operation is stored on the blockchain.

[0051] Thirdly, this application provides a computer device, including: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the mass spectrometry data audit processing method described in the first aspect above.

[0052] Fourthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the mass spectrometry data auditing processing method described in the first aspect.

[0053] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the mass spectrometry data auditing processing method described in the first aspect.

[0054] According to the specific embodiments provided in this application, the following technical effects are disclosed:

[0055] This application provides a method, apparatus, device, medium, and product for auditing mass spectrometry data. It manages all data operation requests related to mass spectrometry data at the device kernel layer, preventing any data operation (whether from application software or a user with high-level operating system privileges) from being executed directly. Instead, compliance verification and recording are performed at the kernel layer, including verifying compliance tokens and generating audit records. If the data operation is high-risk, the corresponding audit record must be immediately uploaded to the blockchain for notarization. Only after notarization is completed will the data operation be executed locally. This establishes a closed system that meets audit requirements, preventing direct tampering with the underlying mass spectrometry data and ensuring its immutability. Furthermore, this application provides a linear audit chain for recording audit records corresponding to each historical data operation in chronological order of operation request time. For operation requests for mass spectrometry data captured by the kernel layer, after confirming that the request carries a compliance token, the compliance elements of the data operation, namely the electronic signature and operation intent, can be collected. Based on the aforementioned compliance elements, the mass spectrometry data fingerprint generated based on the physical address of the mass spectrometry data, and the audit record corresponding to the previous historical data operation, an audit record corresponding to the data operation is generated and added to the linear audit chain. Each audit record contains information from the previous audit record, forming a cryptographic linear evidence chain that satisfies recursive dependencies. This ensures that each data operation step for the mass spectrometry data is cryptographically locked within this linear chain structure, thereby forming a strong cryptographic binding at the micro level for the audit record corresponding to each mass spectrometry data operation, enhancing the legal adversarial capability of electronic evidence. Subsequently, by concatenating and hashing the contents of the audit record corresponding to the data operation, the integrity verification value of the audit record corresponding to the data operation can be obtained. In the case of a high-risk data operation, the integrity verification value of the audit record corresponding to the data operation needs to be submitted to the blockchain for on-chain notarization. After on-chain notarization, the interception of the data operation is released, and the data operation is executed on the mass spectrometry data. In this way, all data operations on mass spectrometry data can be reliably traced. Attached Figure Description

[0056] Figure 1 A flowchart illustrating an audit processing method for mass spectrometry data provided in an embodiment of this application;

[0057] Figure 2 A schematic diagram of the functional modules of a mass spectrometry data audit processing device provided in an embodiment of this application;

[0058] Figure 3 This is a schematic diagram of the structure of a computer device provided in an embodiment of this application. Detailed Implementation

[0059] The present application will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0060] In one exemplary embodiment, such as Figure 1 As shown, a method for auditing mass spectrometry data is provided. This method is executed by computer equipment, specifically by a terminal or server alone, or by both a terminal and a server. The terminal can be, but is not limited to, various desktop computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, and smart vehicle systems. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted devices. The server can be a standalone server, a server cluster consisting of multiple servers, or a cloud server.

[0061] In the embodiments of this application, such as Figure 1 As shown, the auditing process for this mass spectrometry data includes steps 101 to 109. Wherein:

[0062] Step 101: When an operation request for data operation on mass spectrometry data is captured at the kernel layer, verify whether the operation request carries a compliance token indicating that the data operation is a preset operation from a preset trusted source.

[0063] In this embodiment of the application, a mass spectrometer control software is installed in the computer device. The mass spectrometer control software is connected to the mass spectrometer. The raw mass spectrometry data (in streaming data form, also known as raw mass spectrometry data stream) collected by the mass spectrometer can be transmitted to the mass spectrometer control software for storage and processing in the computer device. The computer device is also connected to the blockchain for on-chain evidence storage.

[0064] In the embodiments of this application, mass spectrometry data includes one or more of the following: raw mass spectrometry data, mass spectrometry metadata, and mass spectrometry analysis result data.

[0065] In this embodiment, a file system filter driver can be loaded at the operating system kernel layer of the computer device to establish a closed system environment that complies with electronic record regulatory standards, forcibly taking over all file I / O requests for mass spectrometry data, and serving as the sole trusted trigger source for audit log generation.

[0066] When a data operation request targeting mass spectrometry data is captured at the kernel level, it needs to verify whether the request carries a compliance token indicating that the data operation originates from a pre-defined trusted source (e.g., a data write operation from the mass spectrometer control software). If the request does not carry a compliance token, the kernel-level file system filter driver will directly intercept the request and throw a compliance exception signal, thus achieving absolute blocking before the data operation is physically executed. Even direct file operations on mass spectrometry data initiated by operating system administrators (Root / Admin) with privileges will be directly rejected by the kernel level if they do not carry a compliance token, in order to meet the security requirements of a closed system.

[0067] If an operation request for mass spectrometry data is captured at the application layer, it will first verify whether the data operation comes from a preset trusted source. If so, a compliance token will be generated for the operation request, and the operation request carrying the compliance token will be passed to the kernel layer for verification.

[0068] Step 102: If the operation request carries a compliance token, collect the electronic signature of the data operation, the operation intent, and the physical address of the mass spectrometry data to be operated.

[0069] In this step, if the file system filter driver verifies that the operation request carries a compliance token, it will forcibly collect the electronic signature of the data operation, the operation intent that represents the legal effect of the data operation, and the physical address of the mass spectrometry data to be operated. All of the above-mentioned content can be read from the data request.

[0070] Step 103: Generate a data fingerprint of the mass spectrometry data based on the physical address of the mass spectrometry data.

[0071] Optionally, this step can be implemented in the following way: using the physical address of the mass spectrometry data as the input source, performing incremental hash calculation based on the mass spectrometry data and the intermediate state variable obtained from the previous incremental hash calculation using a streaming hash algorithm to obtain the intermediate state variable corresponding to the current time node, and determining the intermediate state variable corresponding to the current time node as the data fingerprint of the mass spectrometry data.

[0072] When the file system filter driver captures an operation request, it can parse the Memory Descriptor List (MDL), which directly points to the physical memory page containing the mass spectrometry data to be operated on. In this step, the file system filter driver can calculate the data fingerprint of the mass spectrometry data based on a zero-copy mechanism. Specifically, the file system filter driver does not perform memory copying operations (i.e., it does not copy data to the file system filter driver's private data buffer), but directly uses the physical address mapped by the MDL as the input source and calculates the data fingerprint of the mass spectrometry data through a streaming hash algorithm (such as SHA-256 Update). The streaming hash algorithm can perform incremental hash calculation based on the mass spectrometry data to be operated on and the intermediate state variables obtained from the previous incremental hash calculation. That is, each time, the mass spectrometry data is added to the result of the previous incremental hash calculation for incremental hash calculation, avoiding the blockage of the mass spectrometry data operation process caused by the full hash calculation of the mass spectrometry data in the existing technology. The operating system can maintain a hash context state machine, which only retains the calculated intermediate state variables (i.e., temporary context variables generated by the streaming hash algorithm), thereby ensuring that the audit process does not cause delays or packet loss in the initial write operation of non-high-risk real-time mass spectrometry raw data streams.

[0073] Step 104: Obtain the audit record corresponding to the previous historical data operation from the linear audit chain; the linear audit chain records the audit record corresponding to each historical data operation in chronological order of the operation request time.

[0074] In this embodiment, the operating system maintains a linear audit chain. This chain records audit records for each historical data operation in chronological order of the operation request. Each audit record for a data operation is recursively generated based on the relevant information of the current data operation and the audit record of the previous data operation. Therefore, this linear audit chain embodies the linear dependency relationship of each data operation, ensuring that each data operation step of the mass spectrometry data is cryptographically locked within this linear chain structure, guaranteeing the immutability of the data operation steps. Furthermore, this linear audit chain is configured to allow only append-only writes, meaning that deletion of audit records is not permitted.

[0075] Step 105: Generate the audit record corresponding to the data operation based on the electronic signature, operation intent, data fingerprint of mass spectrometry data and the audit record corresponding to the previous historical data operation.

[0076] In this step, an audit record for the current data operation can be generated based on the electronic signature, operation intent, data fingerprint of the mass spectrometry data, and audit record corresponding to the previous historical data operation. Specifically, this includes:

[0077] Generate an audit record R corresponding to data operation i. i The first component R of the storage location id ;

[0078] Based on the electronic signature, a second component R representing the subject of data operation i is generated. user ;

[0079] Generate a third component R representing data operation i based on the operation information of data operation i. action ;

[0080] A fourth component R is generated based on the descriptive information of the mass spectrometry data, representing the information of the operation object of data operation i. target ;

[0081] Based on the operation request of data operation i and the data fingerprint of mass spectrometry data, a fifth component R representing the data change details of the mass spectrometry data is generated. diff ;

[0082] Generate an audit record R corresponding to data operation i based on the current system timestamp. i The sixth component R of the generation time time ;

[0083] Based on the operation intent and the current runtime environment of data operation i, a seventh component R is generated representing the operation intent and extended context of data operation i. context ;

[0084] Based on the audit record R corresponding to the previous historical data operation (i-1) i-1 Integrity check value H(R) i-1 Generate an audit record R corresponding to data operation i. i The eighth component of the preceding audit record information, R prev ;

[0085] The first component R id The second component R user The third component R action Fourth component R target Fifth component R diff The sixth component R time The seventh component R context and the eighth component R prev The fusion yields the audit record R corresponding to data operation i. i .

[0086] Among them, the audit record R corresponding to data operation i i It can be a vector of one-tuples, represented as:

[0087] R i = (R id ,R user ,R action ,R target ,R diff ,R time ,R context ,R prev ).

[0088] Among them, the audit record R corresponding to data operation i i It includes 8 components. Optionally, the first component R id This can include the audit record R corresponding to data operation i. i The database primary key represents the audit record R assigned to the data operation i. i Storage location; second component R user This may include the signer identifier (e.g., signer id) of data operation i, the signer name, the network address of the client (i.e., software) that generated the operation request, and the device name of the current computer device; the third component R action This can include information such as the operation type of data operation i and whether data operation i is a system operation (e.g., 1 indicates that data operation i is a system operation, and 0 indicates that data operation i is not a system operation); the fourth component R target This can include the entity type and entity identifier of the data entity to be operated on (i.e., the pointer to the mass spectrometry data); the fifth component R diff This can include the data fingerprint of the mass spectrometry data, the fields to be changed in data operation i (i.e., the fields involved in the mass spectrometry data), and the field values ​​before and after the change (which can be read from the data request). For data write operations, the field value before the change is empty; the sixth component R time This can include the current system timestamp, i.e., the timestamp provided by the local machine, used to represent the audit record R corresponding to data operation i. i Generation time; seventh component R context This can include the operational intent of data operation i and the current operating environment information of data operation i. Optionally, the current operating environment information of data operation i can include at least one of the following: the hardware serial number of the current computer device, the network MAC (Media Access Control Address) address, the operating system patch version, the hash value of the operating system critical files, the mass spectrometer control software version number and checksum, thereby forming an extended context. If a change in the operating environment is detected and it is consistent with the seventh component R recorded in the previous audit record... contextIf the situation differs, the operating system can issue a warning indicating unauthorized system changes and require mandatory electronic signature confirmation before continuing operations on mass spectrometry data, such as the acquisition of raw mass spectrometry data; the eighth component R prev This can include the audit record R corresponding to the previous historical data operation (i-1). i-1 Integrity check value H(R) i-1 This adds the audit log information of the previous data operation to the audit log of the current data operation, forming a cryptographic linear evidence chain that satisfies the recursive dependency relationship.

[0089] In an optional embodiment, the step of generating the seventh component representing the operation intent and extended context of the data operation based on the operation intent and the current runtime environment of the data operation can be implemented in the following ways:

[0090] For data operation i, obtain an external trusted timestamp, and based on the operation intent, the current running environment of data operation i, and the external trusted timestamp, generate an operation intent, extended context, and corresponding audit record R for data operation i. i The seventh component R of the generation time context .

[0091] In this embodiment, when generating the seventh component R context At that time, the operating system can obtain an external trusted timestamp from an external trusted time source (the computer device communicates with the external trusted time source), such as an NTP (Network Time Protocol) server or an atomic clock service, for data operation i, and use this external trusted timestamp as the seventh component R. context A portion of the data is recorded, thereby cryptographically securing the external authenticity of the timestamp. This facilitates the subsequent verification of the audit record R corresponding to data operation i. i Add it to the linear audit chain to perform timestamp verification before evidence storage, preventing unreliable evidence storage due to system time tampering.

[0092] Step 106: Concatenate and hash the contents of the audit record corresponding to the data operation to obtain the integrity verification value of the audit record corresponding to the data operation.

[0093] In this step, the audit record R corresponding to data operation i can be... i The first component R in id The second component R user The third component R action Fourth component R target Fifth component R diff The sixth component R timeThe seventh component R context and the eighth component R prev Convert each number to binary and concatenate them in order to obtain the concatenated data (R). id ∥R user ∥R action ∥R target ∥R diff ∥R time ∥R context ∥R prev Then, the concatenated data (R) can be processed using a collision-resistant one-way hash function. id ∥R user ∥R action ∥R target ∥R diff ∥R time ∥R context ∥R prev Perform hash calculation to obtain the audit record R corresponding to data operation i. i Integrity check value H(R) i =Hash(R) id ∥R user ∥R action ∥R target ∥R diff ∥R time ∥R context ∥R prev ).

[0094] Step 107: Add the audit record corresponding to the data operation to the linear audit chain.

[0095] In this step, the audit record R corresponding to data operation i can be... i Add to the tail of the linear audit chain to provide evidence for data operation i.

[0096] In an optional embodiment, the audit record R corresponding to data operation i... i The seventh component R in context When an external trusted timestamp is included, this step can be implemented in the following ways:

[0097] Determine the audit record R corresponding to data operation i. i Whether the difference between the system timestamp and the external trusted timestamp does not exceed the preset time deviation;

[0098] If the audit record R corresponding to data operation i i If the system timestamp and the external trusted timestamp differ by no more than a preset time deviation, the audit record R corresponding to data operation i will be recorded. i Add to the linear audit chain.

[0099] In this embodiment, before adding each audit record to the linear audit chain, the operating system needs to determine whether the difference between the system timestamp in the audit record and the external trusted timestamp does not exceed a preset time deviation. If the system time has not been tampered with, the difference between the system timestamp and the external trusted timestamp will not exceed the preset time deviation. If the difference between the system timestamp and the external trusted timestamp exceeds the preset time deviation, the system time is highly likely to have been tampered with. In this case, the system can refuse to write the audit record into the linear audit chain and throw a time synchronization failure exception for the audit record.

[0100] In this embodiment of the application, for the head audit record R0 in a linear audit chain, optionally, the eighth component R in R0... prev It can be a vector of all zeros.

[0101] In an optional embodiment, the auditing method for the mass spectrometry data may further include the following steps:

[0102] When a deletion operation is received for a target audit record in a linear audit chain, an audit record corresponding to the deletion operation is generated. The audit record corresponding to the deletion operation includes the operation type of the deletion operation as deletion, the operation intent of the deletion operation, and the associated object of the deletion operation. In the audit record corresponding to the deletion operation, the operation type of the deletion operation is deletion, the operation intent of the deletion operation is invalidation, and the associated object of the deletion operation is the integrity verification value of the target audit record.

[0103] Add the audit record corresponding to the deletion operation to the linear audit chain.

[0104] In this embodiment, the audit records in the linear audit chain are designed to be physically non-deletable.

[0105] When a deletion operation is received for an audit record already stored in a linear audit chain, the operating system prohibits the deletion operation from being performed at the physical level. Instead, it generates a new audit record to record the deletion operation. The operation type can be marked as DELETE, and the operation intent can be marked as VOID (void). The integrity check value of the audit record to be deleted is written into the audit record as an associated object. The audit record corresponding to the deletion operation in the linear audit chain is only appended to the end of the linear audit chain as a new record. Thus, the compliance process of the audit record removal is proved through the continuity of the chain structure.

[0106] Step 108: If the data operation is a preset high-risk operation, the integrity verification value of the audit record corresponding to the data operation is recorded on the blockchain as a transaction and stored as evidence.

[0107] In this embodiment of the application, the audit record R corresponding to data operation i is... i After being added to the linear audit chain, it can be determined whether data operation i is a preset high-risk operation. If data operation i is a preset high-risk operation, the operating system can add the audit record R corresponding to data operation i. i Integrity check value H(R) i The transaction is sent to the blockchain, packaged into a block by the consensus of the blockchain nodes, and a transaction receipt (i.e., transaction confirmation hash value) is returned, completing the on-chain notarization. After confirming that the transaction has obtained irrevocable legal effect, the operating system releases the interception of data operation i and executes data operation i, that is, performs data operation i on the disk, such as writing the raw mass spectrometry data to the disk.

[0108] Optionally, high-risk operations may include one or more of the following: overwriting, deleting, and truncation of raw mass spectrometry data; changes to spectral library and method parameters (e.g., modifications to mass spectrometer tuning parameters, integration parameters, or calibration curve calculation logic; integration operations involving manual intervention of chromatographic peaks); and the export and signing / publishing of qualitative and quantitative results. By excluding high-frequency initial data stream writing from high-risk operations, on-chain consensus blocking during real-time data acquisition is avoided.

[0109] Step 109: After the integrity verification value of the audit record corresponding to the data operation is stored on the blockchain, the data operation is performed on the mass spectrometry data.

[0110] In this embodiment of the application, when a preset high-risk operation is captured, after the audit record corresponding to the high-risk operation is stored locally on the computer device through a linear audit chain, the integrity verification value of the audit record corresponding to the high-risk operation is immediately sent to the blockchain for on-chain storage. This step is only executed after the transaction confirmation hash value returned by the blockchain is obtained, thereby allowing the high-risk operation to take effect locally, that is, to physically execute the high-risk operation.

[0111] In an optional embodiment, the auditing method for the mass spectrometry data may further include the following steps:

[0112] Perform data operation i on the mass spectrometry data if data operation i is not a preset high-risk operation.

[0113] Monitor whether the conditions for aggregation and on-chain processing are met;

[0114] When the aggregation on-chain conditions are met, the audit record R corresponding to data operation i in the linear audit chain is included. i All audit records, including those not yet stored on the blockchain, will be stored on the blockchain.

[0115] In this embodiment, the audit record R corresponding to data operation i is...i After being added to the linear audit chain, if it is determined that data operation i is not a preset high-risk operation, data operation i can be executed on the mass spectrometry data immediately. That is, for non-high-risk operations, it is not necessary to immediately put them on the chain for evidence storage. They can be executed immediately. After execution, wait for the opportunity to meet the aggregation and on-chain conditions, and then put them on the chain for evidence storage together with other audit records in the linear audit chain that have not been put on the chain for evidence storage.

[0116] In this embodiment, tiered on-chain evidence storage can be performed for both high-risk and non-high-risk operations. For high-risk operations, on-chain evidence storage is performed immediately, and the operation is executed after on-chain evidence storage. For non-high-risk operations, the operation is executed immediately, and subsequent on-chain evidence storage can be performed after aggregation. This balances both operation execution efficiency and operation compliance.

[0117] Optionally, the aggregation on-chain can be set to be triggered at regular intervals (e.g., once per hour), and / or triggered when the number of audit records not on-chain in the linear audit chain reaches a preset number. That is, the aggregation on-chain conditions may include reaching the next aggregation on-chain cycle, and / or the number of audit records not on-chain in the linear audit chain reaching a preset number.

[0118] Optionally, for the audit record R corresponding to data operation i in the linear audit chain... i All audit records that have not been stored on the blockchain can be stored on the blockchain using the Merkle tree aggregation method. The Merkle tree aggregation method can aggregate the integrity verification values ​​of a batch of audit records into a root hash value for storage on the blockchain, thereby improving the efficiency of storage on the blockchain and reducing the cost of storage on the blockchain.

[0119] In this embodiment, the auditor can export a linear audit chain from the local database to obtain a complete sequence of audit records. Then, the head audit record R0 of the linear audit chain is read, and the result is processed according to the formula H(R... i =Hash(R) id,i ∥R user,i ∥R action,i ∥R target,i ∥R diff,i ∥R time,i ∥R context,i ∥R prev,i The integrity check value of the tail audit record is calculated and then compared with the integrity check value of the tail audit record of the record. If the two are consistent, it means that the local data has not been tampered with in any way since its creation, because any change in any bit will cause the avalanche effect of all subsequent hash values.

[0120] The mass spectrometry data auditing method provided in this application takes over all data operation requests for mass spectrometry data at the device kernel layer. This prevents any data operation on mass spectrometry data (whether from application software or from a user with high-level operating system privileges) from being executed directly. Instead, compliance verification and recording are performed at the kernel layer first, including verifying compliance tokens and generating audit records. If the data operation is high-risk, the corresponding audit record must be immediately uploaded to the blockchain for notarization. Only after the notarization is completed will the data operation be executed locally. This establishes a closed system that meets audit requirements, preventing direct tampering with the underlying mass spectrometry data by bypassing the software and ensuring the immutability of the underlying mass spectrometry data. Furthermore, this application provides a linear audit chain for recording audit records corresponding to each historical data operation in chronological order of operation request time. For operation requests for mass spectrometry data captured by the kernel layer, after confirming that the request carries a compliance token, the compliance elements of the data operation, namely the electronic signature and operation intent, can be collected. Based on the aforementioned compliance elements, the mass spectrometry data fingerprint generated based on the physical address of the mass spectrometry data, and the audit record corresponding to the previous historical data operation, an audit record corresponding to the data operation is generated and added to the linear audit chain. Each audit record contains information from the previous audit record, forming a cryptographic linear evidence chain that satisfies recursive dependencies. This ensures that each data operation step for the mass spectrometry data is cryptographically locked within this linear chain structure, thereby forming a strong cryptographic binding at the micro level for the audit record corresponding to each mass spectrometry data operation, enhancing the legal adversarial capability of electronic evidence. Subsequently, by concatenating and hashing the contents of the audit record corresponding to the data operation, the integrity verification value of the audit record corresponding to the data operation can be obtained. In the case of a high-risk data operation, the integrity verification value of the audit record corresponding to the data operation needs to be submitted to the blockchain for on-chain notarization. After on-chain notarization, the interception of the data operation is released, and the data operation is executed on the mass spectrometry data. In this way, all data operations on mass spectrometry data can be reliably traced.

[0121] Based on the same inventive concept, this application also provides a mass spectrometry data auditing processing apparatus for implementing the mass spectrometry data auditing processing method described above. The solution provided by this apparatus is similar to the implementation scheme described in the above method; therefore, the specific limitations of one or more mass spectrometry data auditing processing apparatus embodiments provided below can be found in the limitations of the mass spectrometry data auditing processing method described above, and will not be repeated here.

[0122] In one exemplary embodiment, such as Figure 2As shown, a mass spectrometry data audit processing device is provided, which includes:

[0123] The compliance verification module is configured to verify whether an operation request for a data operation on mass spectrometry data carries a compliance token indicating that the data operation is from a preset trusted source when an operation request for a data operation on mass spectrometry data is captured at the kernel layer.

[0124] The information collection module is configured to collect the electronic signature of the data operation, the operation intent, and the physical address of the mass spectrometry data to be operated if the operation request carries the compliance token.

[0125] A fingerprint generation module is configured to generate a data fingerprint of the mass spectrometry data based on the physical address of the mass spectrometry data;

[0126] The audit chain reading module is configured to retrieve the audit record corresponding to the previous historical data operation from the linear audit chain; the linear audit chain records the audit record corresponding to each historical data operation in chronological order of the operation request.

[0127] The record generation module is configured to generate an audit record corresponding to the data operation based on the electronic signature, the operation intent, the data fingerprint of the mass spectrometry data, and the audit record corresponding to the previous historical data operation.

[0128] The hash calculation module is configured to concatenate and hash the contents of the audit record corresponding to the data operation to obtain the integrity verification value of the audit record corresponding to the data operation.

[0129] The record addition module is configured to add the audit records corresponding to the data operations to the linear audit chain;

[0130] The on-chain evidence storage module is configured to, in the case that the data operation is a preset high-risk operation, retrieve the integrity verification value of the audit record corresponding to the data operation from the linear audit chain as the transaction and store it on the blockchain for on-chain evidence storage.

[0131] The operation execution module is configured to perform the data operation on the mass spectrometry data after the integrity verification value of the audit record corresponding to the data operation is stored on the blockchain.

[0132] Optionally, in some embodiments of this application, the auditing method for the mass spectrometry data further includes:

[0133] If the data operation is not a preset high-risk operation, the data operation is performed on the mass spectrometry data;

[0134] Monitor whether the conditions for aggregation and on-chain processing are met;

[0135] When the aggregation conditions are met, all audit records that have not been stored on the blockchain, including the audit records corresponding to the data operations contained in the linear audit chain, are stored on the blockchain.

[0136] Optionally, in some embodiments of this application, generating the audit record corresponding to the data operation based on the electronic signature, the operation intent, the data fingerprint of the mass spectrometry data, and the audit record corresponding to the previous historical data operation includes:

[0137] Generate a first component representing the storage location of the audit record corresponding to the data operation;

[0138] A second component representing the data operation subject is generated based on the electronic signature;

[0139] A third component representing the data operation is generated based on the operation information of the data operation;

[0140] A fourth component representing the operation object information of the data operation is generated based on the descriptive information of the mass spectrometry data.

[0141] Based on the operation request of the data operation and the data fingerprint of the mass spectrometry data, a fifth component representing the data change details of the mass spectrometry data is generated;

[0142] A sixth component representing the generation time of the audit record corresponding to the data operation is generated based on the current system timestamp.

[0143] A seventh component representing the operation intent and extended context of the data operation is generated based on the operation intent and the current operating environment of the data operation.

[0144] Based on the integrity verification value of the audit record corresponding to the previous historical data operation, an eighth component representing the preceding audit record information of the audit record corresponding to the data operation is generated.

[0145] The audit record corresponding to the data operation is obtained by fusing the first component, the second component, the third component, the fourth component, the fifth component, the sixth component, the seventh component, and the eighth component.

[0146] Optionally, in some embodiments of this application, generating a seventh component representing the operation intent and extended context of the data operation based on the operation intent and the current runtime environment of the data operation includes:

[0147] For the data operation, an external trusted timestamp is obtained, and a seventh component representing the operation intent, extended context, and generation time of the audit record corresponding to the data operation is generated based on the operation intent, the current running environment of the data operation, and the external trusted timestamp.

[0148] Adding the audit record corresponding to the data operation to the linear audit chain includes:

[0149] Determine whether the system timestamp in the audit record corresponding to the data operation differs from the external trusted timestamp by no more than a preset time deviation;

[0150] If the system timestamp in the audit record corresponding to the data operation differs from the external trusted timestamp by no more than a preset time deviation, the audit record corresponding to the data operation is added to the linear audit chain.

[0151] Optionally, in some embodiments of this application, the auditing method for the mass spectrometry data further includes:

[0152] When a deletion operation is received for a target audit record in the linear audit chain, an audit record corresponding to the deletion operation is generated; in the audit record corresponding to the deletion operation, the operation type of the deletion operation is deletion, the operation intent of the deletion operation is invalidation, and the associated object of the deletion operation is the integrity verification value of the target audit record;

[0153] Add the audit record corresponding to the deletion operation to the linear audit chain.

[0154] Optionally, in some embodiments of this application, generating a data fingerprint of the mass spectrometry data based on the physical address of the mass spectrometry data includes:

[0155] Using the physical address of the mass spectrometry data as the input source, an incremental hash calculation is performed based on the mass spectrometry data and the intermediate state variable obtained from the previous incremental hash calculation using a streaming hash algorithm to obtain the intermediate state variable corresponding to the current time node, and the intermediate state variable corresponding to the current time node is determined as the data fingerprint of the mass spectrometry data.

[0156] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0157] The aforementioned computer device may be, for example, a server or a terminal, and its internal structure diagram may be as follows: Figure 3As shown, this computer device includes a processor, memory, input / output (I / O) interfaces, and a communication interface. The processor, memory, and I / O interfaces are connected via a system bus, and the communication interface is also connected to the system bus via the I / O interfaces. The processor provides computational and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and a database. The internal memory provides the environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The database stores data. The I / O interfaces are used for exchanging information between the processor and external devices. The communication interface is used for communicating with external terminals via a network connection. When executed by the processor, the computer program implements a method for auditing mass spectrometry data.

[0158] Those skilled in the art will understand that Figure 3 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0159] In one exemplary embodiment, a computer-readable storage medium is provided storing a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0160] In one exemplary embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above-described method embodiments.

[0161] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0162] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments described above. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM).

[0163] The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0164] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0165] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A method for auditing mass spectrometry data, characterized in that, The audit processing method for the mass spectrometry data includes: When an operation request for data manipulation of mass spectrometry data is captured at the kernel layer, verify whether the operation request carries a compliance token indicating that the data operation is a preset operation from a preset trusted source. If the operation request carries the compliance token, collect the electronic signature of the data operation, the operation intent, and the physical address of the mass spectrometry data to be operated; Based on the physical address of the mass spectrometry data, a data fingerprint of the mass spectrometry data is generated; The audit record corresponding to the previous historical data operation is obtained from the linear audit chain; the linear audit chain records the audit record corresponding to each historical data operation in chronological order of the operation request time. Based on the electronic signature, the operation intent, the data fingerprint of the mass spectrometry data, and the audit record corresponding to the previous historical data operation, an audit record corresponding to the data operation is generated. The contents of the audit record corresponding to the data operation are concatenated and hashed to obtain the integrity verification value of the audit record corresponding to the data operation; Add the audit records corresponding to the data operations to the linear audit chain; In the case that the data operation is a preset high-risk operation, the integrity verification value of the audit record corresponding to the data operation is taken from the linear audit chain and stored on the blockchain as a transaction. After the integrity verification value of the audit record corresponding to the data operation is stored on the blockchain, the data operation is performed on the mass spectrometry data.

2. The method for auditing mass spectrometry data according to claim 1, characterized in that, The auditing process for the mass spectrometry data also includes: If the data operation is not a preset high-risk operation, the data operation is performed on the mass spectrometry data; Monitor whether the conditions for aggregation and on-chain processing are met; When the aggregation conditions are met, all audit records that have not been stored on the blockchain, including the audit records corresponding to the data operations contained in the linear audit chain, are stored on the blockchain.

3. The method for auditing mass spectrometry data according to claim 1, characterized in that, The step of generating an audit record corresponding to the data operation based on the electronic signature, the operation intent, the data fingerprint of the mass spectrometry data, and the audit record corresponding to the previous historical data operation includes: Generate a first component representing the storage location of the audit record corresponding to the data operation; A second component representing the data operation subject is generated based on the electronic signature; A third component representing the data operation is generated based on the operation information of the data operation; A fourth component representing the operation object information of the data operation is generated based on the descriptive information of the mass spectrometry data. Based on the operation request of the data operation and the data fingerprint of the mass spectrometry data, a fifth component representing the data change details of the mass spectrometry data is generated; A sixth component representing the generation time of the audit record corresponding to the data operation is generated based on the current system timestamp. A seventh component representing the operation intent and extended context of the data operation is generated based on the operation intent and the current operating environment of the data operation. Based on the integrity verification value of the audit record corresponding to the previous historical data operation, an eighth component representing the preceding audit record information of the audit record corresponding to the data operation is generated. The audit record corresponding to the data operation is obtained by fusing the first component, the second component, the third component, the fourth component, the fifth component, the sixth component, the seventh component, and the eighth component.

4. The method for auditing mass spectrometry data according to claim 3, characterized in that, The generation of a seventh component representing the operation intent and extended context of the data operation based on the operation intent and the current runtime environment of the data operation includes: For the data operation, an external trusted timestamp is obtained, and a seventh component representing the operation intent, extended context, and generation time of the audit record corresponding to the data operation is generated based on the operation intent, the current running environment of the data operation, and the external trusted timestamp. Adding the audit record corresponding to the data operation to the linear audit chain includes: Determine whether the system timestamp in the audit record corresponding to the data operation differs from the external trusted timestamp by no more than a preset time deviation; If the system timestamp in the audit record corresponding to the data operation differs from the external trusted timestamp by no more than a preset time deviation, the audit record corresponding to the data operation is added to the linear audit chain.

5. The method for auditing mass spectrometry data according to claim 1, characterized in that, The auditing process for the mass spectrometry data also includes: When a deletion operation is received for a target audit record in the linear audit chain, an audit record corresponding to the deletion operation is generated; in the audit record corresponding to the deletion operation, the operation type of the deletion operation is deletion, the operation intent of the deletion operation is invalidation, and the associated object of the deletion operation is the integrity verification value of the target audit record; Add the audit record corresponding to the deletion operation to the linear audit chain.

6. The method for auditing mass spectrometry data according to claim 1, characterized in that, The step of generating a data fingerprint of the mass spectrometry data based on the physical address of the mass spectrometry data includes: Using the physical address of the mass spectrometry data as the input source, an incremental hash calculation is performed based on the mass spectrometry data and the intermediate state variable obtained from the previous incremental hash calculation using a streaming hash algorithm to obtain the intermediate state variable corresponding to the current time node, and the intermediate state variable corresponding to the current time node is determined as the data fingerprint of the mass spectrometry data.

7. A mass spectrometry data auditing and processing device, characterized in that, The mass spectrometry data audit processing device includes: The compliance verification module is configured to verify whether an operation request for a data operation on mass spectrometry data carries a compliance token indicating that the data operation is from a preset trusted source when an operation request for a data operation on mass spectrometry data is captured at the kernel layer. The information collection module is configured to collect the electronic signature of the data operation, the operation intent, and the physical address of the mass spectrometry data to be operated if the operation request carries the compliance token. A fingerprint generation module is configured to generate a data fingerprint of the mass spectrometry data based on the physical address of the mass spectrometry data; The audit chain reading module is configured to retrieve the audit record corresponding to the previous historical data operation from the linear audit chain; the linear audit chain records the audit record corresponding to each historical data operation in chronological order of the operation request. The record generation module is configured to generate an audit record corresponding to the data operation based on the electronic signature, the operation intent, the data fingerprint of the mass spectrometry data, and the audit record corresponding to the previous historical data operation. The hash calculation module is configured to concatenate and hash the contents of the audit record corresponding to the data operation to obtain the integrity verification value of the audit record corresponding to the data operation. The record addition module is configured to add the audit records corresponding to the data operations to the linear audit chain; The on-chain evidence storage module is configured to, in the case that the data operation is a preset high-risk operation, retrieve the integrity verification value of the audit record corresponding to the data operation from the linear audit chain as the transaction and store it on the blockchain for on-chain evidence storage. The operation execution module is configured to perform the data operation on the mass spectrometry data after the integrity verification value of the audit record corresponding to the data operation is stored on the blockchain.

8. A computer device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor executes the computer program to implement the steps of the audit processing method for mass spectrometry data according to any one of claims 1-6.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the computer program implements the steps of the mass spectrometry data auditing method according to any one of claims 1-6.

10. A computer program product, comprising a computer program, characterized in that, When executed by a processor, the computer program implements the steps of the mass spectrometry data auditing method according to any one of claims 1-6.

Images