A medical and electronic waste organic solvent source coding traceability method

Abstract

The present application relates to the technical field of data processing and hazardous waste traceability management, and discloses a medical and electronic waste organic solvent source coding traceability method; the method first collects source information, category declaration information, container information, filling quality information and on-site detection characteristic data at the waste source point, forms a source point self-certification code corresponding to the filling batch, and writes into an electronic tag and a traceability account book; during loading, transportation, plant handover, unloading and multi-source tank entry, continuously associate transfer slips, quality data, transportation tracks, handover time and tank entry contribution records, and update the mixed tank traceability account book and the quality proportion relationship according to the tank entry order and the tank entry quality; combined with the cross-industry category mapping relationship and the plant review information, determine the category attribution and disposal path of the mixed batch, and locate the abnormal source when the review is abnormal, so as to realize the data management of waste organic solvent source verification, mixed tank traceability and quality-based disposal.

Description

Technical Field

[0001] This invention relates to the field of data processing and hazardous waste traceability management technology, specifically a method for tracing the source of organic solvents in medical and electronic waste. Background Technology

[0002] Waste organic solvents are continuously generated during medical treatment activities, PCB (printed circuit board) cleaning in electronic manufacturing enterprises, and the production of wet electronic chemicals. These waste liquids typically fall under the management scope of hazardous waste. The authenticity, continuity, and verifiability of their source information directly affect collection and transportation scheduling, transfer manifest verification, responsibility tracing, and the selection of centralized disposal processes. Existing hazardous waste traceability methods largely rely on information declared by waste-generating units, container labels, barcode registration, or platform data recording for management. For example, the published invention patent application CN111977232B discloses an IoT-based intelligent medical waste transport vehicle that can identify, locate, and record the medical waste transport process. However, this solution mainly targets the medical waste transport stage, and the identification information still primarily comes from waste-generating end registration or label information, failing to include the density, conductivity, refractive index, and optical properties of the waste organic solvents. Establishing a verifiable correspondence between actual physicochemical characteristics such as spectra and source codes makes it difficult to reverse-verify the true source of waste liquid when labels are changed, labels do not correspond to actual waste liquid, or different types of waste liquid are mixed in. For example, the published invention patent application CN114417435B discloses a blockchain-based carbon emission data monitoring system and method for controlled emission enterprises, which can store monitoring data on the blockchain to improve data anti-tampering capabilities. However, this solution is mainly aimed at event-level monitoring data and does not establish a synchronous correlation mechanism between the quality, physicochemical characteristics and coding status of each entry into the tank and the continuous entry of waste organic solvents from multiple sources. As a result, after multi-source mixing, existing methods can usually only record the source information involved in the mixing, and it is difficult to accurately retain and restore the actual quality contribution ratio of each source to the mixed waste liquid, resulting in insufficient basis for subsequent responsibility division and disposal decisions.

[0003] Meanwhile, waste organic solvents from the medical and electronics industries differ in hazardous waste categories, waste-generating processes, and disposal compatibility. When mixed across industries, unclear category classifications can easily arise, making it difficult for centralized disposal sites to determine differentiated resource recovery disposal plans in a timely manner. Therefore, it is necessary to propose a waste organic solvent source coding traceability method that can associate the physicochemical characteristics of the source with the source code, retain the mass proportion of each source during the mixing process, and unify the semantics of cross-industry categories, in order to improve the accuracy of source verification, mixing traceability, and differentiated disposal. Summary of the Invention

[0004] To address the shortcomings of existing technologies, this invention provides a method for tracing the source of organic solvents in medical and electronic waste, which solves the problems mentioned in the background section.

[0005] To achieve the above objectives, the present invention provides the following technical solution:

[0006] A method for tracing the source of organic solvents in medical and electronic waste includes:

[0007] S1. Obtain source information, category declaration information, container information, filling quality information, and on-site characteristic data of waste organic solvents at the waste source point, and associate all data with the same filling batch;

[0008] S2. Generate a source self-certification code based on the associated data of the same filling batch, write the source self-certification code into the container electronic tag, and write the corresponding batch data into the traceability ledger.

[0009] S3. Read the source self-certification code at the loading, transportation, factory handover and unloading nodes, and associate the transfer manifest, loading quality, transportation trajectory, unloading quality and handover time with the source self-certification code.

[0010] S4. During the multi-source tank entry process, update the mixing tank traceability ledger according to the order of entry and the quality of each source, and form the quality proportion relationship of each source in the mixing tank batch.

[0011] S5. Based on the mixed tank traceability ledger, cross-industry category mapping relationship and incoming verification information, determine the category affiliation and disposal path of mixed batches, and trace the corresponding source when verification is abnormal.

[0012] Preferably, S1 includes:

[0013] Read the waste source registration data, category declaration data, container identification data, filling quality data, and on-site detection characteristic data respectively;

[0014] A temporary batch identifier is generated after the filling operation is triggered;

[0015] The filling start time and filling end time are determined based on the valve opening degree and mass change;

[0016] The collected data is written to the source point cache table according to a unified time base.

[0017] Data from the same filling batch is processed by status identification, outlier removal, median smoothing, representative interval extraction, and quality increment weighting to form a batch data table.

[0018] Preferably, S2 includes:

[0019] Perform coding status verification on batch data tables and identify prohibited coding flags and missing key fields;

[0020] The data that passes the verification is standardized and quantified according to field order, unit format, and device resolution;

[0021] Normalized data is digested and signed to obtain a source self-certification code consisting of a logical declaration segment, a data digest segment, a signature verification segment, and a ledger index segment.

[0022] After verifying the consistency of the source self-certification code, write it into the container electronic tag, and write the batch record into the traceability ledger according to the event partition;

[0023] In the event of a network anomaly, the records to be written are locally cached, sequentially retransmitted, and compared with digests.

[0024] Preferably, the data that passes the verification is normalized and quantified according to field order, unit format, and device resolution, including:

[0025] Arrange the source data, category declaration data, and container data according to a preset field sequence;

[0026] Standardize the quality data to the same unit of measurement and numerical precision;

[0027] The on-site detection feature data are quantized according to the equipment acquisition sequence, field number, and detection type. Density data is quantized using significant digits, conductivity data is quantized using fixed-point quantization or graded quantization, spectral response data is quantized using channel number and normalized intensity, and temperature data and flash point data are quantized using decimal places or integer graded quantization.

[0028] Preferably, S3 includes:

[0029] Match the source self-certification code with the manifest summary and authorized loading list;

[0030] A vehicle loading list is generated after signature verification;

[0031] Based on the differences in loading quality, valid judgments, re-weighing, or abnormal interception shall be carried out;

[0032] During transportation, the trajectory record is linked to the loading list summary, and events such as stopping, route deviation, abnormal weighing, or abnormal liquid level are recorded.

[0033] Upon arrival at the factory, the consistency of the vehicle number, manifest, vehicle identification number, receiving unit, and loading list summary is verified. Before unloading, the source self-certification code is read again and the unloading quality is reviewed.

[0034] Preferably, during transportation, the trajectory record is linked to the loading manifest summary, and events such as stopping, route deviation, abnormal weighing, or abnormal liquid level are recorded, including:

[0035] Generate trajectory records based on train number, location time, vehicle position, speed, vehicle status, and a summary of the loading list;

[0036] The loading list summary is obtained by summarizing the in-vehicle source point self-certification codes according to the loading order;

[0037] Based on parking duration, route deviation distance, and changes in weighing or liquid level data at non-unloading locations, a transportation anomaly record is generated.

[0038] Preferably, S4 includes:

[0039] The entry permit is determined based on the status of the receiving tank, the remaining capacity, the status of the inlet valve, the status of the weighing equipment, and the status of the ledger connection.

[0040] Read the source self-certification code, unloading quality, handover records, and ledger index;

[0041] Based on the tank entry operation time, the difference in receiving tank quality, or the difference between container unloading quality and residual quality, a tank entry contribution record is generated and updated in a chain according to the previous summary;

[0042] Simultaneously calculate the mass percentages at the container level, source point level, waste-generating unit level, and category declaration level;

[0043] Records of signature verification, manifest permission, quality difference, tank entry time, or duplicate tank entry verification anomalies are written to the abnormal tank entry cache table. Batch suspension is executed according to the abnormal tank entry status, and tank sealing is executed according to tank capacity, source quantity, or scheduling instructions.

[0044] Preferably, the mass percentages at the container level, source point level, waste-generating unit level, and category declaration level are calculated simultaneously, including:

[0045] After each batch is added to the tank, the cumulative mass of the current batch is used as the calculation basis.

[0046] The cumulative mass of waste entering the tank is aggregated from each source according to container, source point, waste generating unit, and category declaration code;

[0047] The cumulative mass of the batch entering the tank under each merging dimension is calculated as a ratio to the cumulative mass of the current batch in the mixing tank, forming a corresponding mass percentage record, which is then written to the mixing tank event record partition.

[0048] Preferably, S5 includes:

[0049] Perform integrity checks on the mixing tank traceability ledger, source contribution list, and quality percentage relationship table;

[0050] The main category, secondary category, and warning category are determined based on the management rule table and semantic mapping table;

[0051] Disposal paths should be matched according to risk priority, quality ratio, and scope of disposal permits;

[0052] Compare the results of the incoming inspection with the expected batch characteristics to identify any discrepancies.

[0053] When reviewing anomalies, a list of candidate anomaly sources is generated based on the proportion of source quality and the degree of deviation of batch characteristics. An evidence chain is then formed along the source batch data, shipping handover records, and tank entry contribution records to generate a revised version.

[0054] Preferably, the incoming inspection results are compared with the expected batch characteristics to identify discrepancies, including:

[0055] Read the review time, sampling location, review items, review results, and status of review personnel and equipment;

[0056] Generate expected batch characteristics based on the source contribution list and quality percentage relationship table;

[0057] Numerical review items are compared according to their deviation ratio, and graded review items are compared according to their grade difference. Abnormal review status is marked based on the threshold corresponding to each review item.

[0058] Compared with existing technologies, this invention provides a method for tracing the source of organic solvents in medical and electronic waste, which has the following advantages:

[0059] 1. This invention collects source information, category declaration information, container information, filling quality information, and on-site detection characteristic data at waste generation points. Based on the above data, it generates a source self-certification code and writes it into an electronic tag and traceability ledger, so that the source code corresponds to the actual filling batch data. By continuously associating transfer manifests, quality data, transportation trajectory, and tank entry contribution records during loading, transportation, factory handover, unloading, and multi-source tank entry, and using chain-based summary updates to the mixed tank traceability ledger and graded quality proportion relationship, it retains the tank entry order and quality contribution of each source in the mixed batch. Through cross-industry category mapping relationship and factory verification information, it performs category classification, disposal path matching, and abnormal source backtracking for mixed batches, thereby improving the accuracy of waste organic solvent source verification, mixed tank ratio traceability, and cross-industry graded disposal decision-making.

[0060] 2. This invention standardizes, summarizes, and signs source batch data, and writes source events, transportation events, handover events, and mixing events into a traceability ledger, creating verifiable records of key operations of waste organic solvents from waste generation, loading, transportation, and entry into the plant to mixing. By locally caching, sequentially retransmitting, and summarizing records in case of network anomalies, and locking the original mixing traceability ledger and adding records with a revised version in case of verification anomalies, this invention avoids breakage of the traceability chain due to communication interruptions, label replacements, post-event modifications, or record overwriting. This improves the data tamper-proofing capabilities, evidence integrity, and regulatory review operability in the cross-unit and cross-industry collection and disposal process of waste organic solvents. Attached Figure Description

[0061] Figure 1 This is a schematic diagram of the process for tracing the source of organic solvents in medical and electronic waste according to the present invention;

[0062] Figure 2 This is a schematic diagram illustrating the batch data collection and correlation of waste generation sources in this invention;

[0063] Figure 3 This is a schematic diagram illustrating the relationship between the generation and writing of the source point self-certification code in this invention;

[0064] Figure 4 This is a schematic diagram illustrating the continuous connection between loading, transportation, factory handover, and unloading of the present invention.

[0065] Figure 5 This is a schematic diagram illustrating the updated mass ratio of multi-source tank entry and mixing tank operation according to the present invention.

[0066] Figure 6 This diagram illustrates the classification, handling path matching, and anomaly source tracing of the present invention. Detailed Implementation

[0067] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0068] Example 1: Figure 1 - Figure 6 A method for tracing the source of organic solvents in medical and electronic waste is presented, including:

[0069] S1. Obtain source information, category declaration information, container information, filling quality information, and on-site characteristic data of waste organic solvents at the waste source point, and associate all data with the same filling batch;

[0070] S2. Generate a source self-certification code based on the associated data of the same filling batch, write the source self-certification code into the container electronic tag, and write the corresponding batch data into the traceability ledger.

[0071] S3. Read the source self-certification code at the loading, transportation, factory handover and unloading nodes, and associate the transfer manifest, loading quality, transportation trajectory, unloading quality and handover time with the source self-certification code.

[0072] S4. During the multi-source tank entry process, update the mixing tank traceability ledger according to the order of entry and the quality of each source, and form the quality proportion relationship of each source in the mixing tank batch.

[0073] S5. Based on the mixed tank traceability ledger, cross-industry category mapping relationship and incoming verification information, determine the category affiliation and disposal path of mixed batches, and trace the corresponding source when verification is abnormal.

[0074] This method is applied to a cross-industry collection and disposal scenario of waste organic solvents involving medical institutions and electronic manufacturing enterprises. Participants include at least the waste-generating source, dedicated hazardous waste transport vehicles, centralized disposal enterprises, regulatory platforms, and provincial solid waste information platforms. Input information includes at least the following fields: waste-generating unit identity information, waste-generating process information, hazardous waste category declaration information, container number, filling start and end times, filling quality change data, on-site detection characteristic data, transfer manifest information, transportation trajectory, loading and unloading quality data, on-site verification data, and disposal enterprise process adaptation data. On-site detection characteristic data is used as a data field for batch identification association, source code generation, and on-site verification, and is not used for individual component detection. The method focuses on protection by generating source codes corresponding to actual filling batch data at the waste source point, maintaining continuous association between source codes and transfer manifests, quality data, and trajectory data during transportation and handover, updating the mixing traceability ledger according to the order of entry and quality contribution during multi-source tank entry, and determining the category, disposal path, and abnormal source of mixed batches based on category mapping relationships and factory entry verification data after cross-industry mixing. Ultimately, this results in source self-certification codes written into container electronic tags, source event records, transportation event records, handover event records, mixing event records, mixed batch quality ratio tables, mixed batch category records, disposal path matching records, and abnormal source traceability records.

[0075] Specifically, such as Figure 2As shown: In S1, after the filling operation is initiated at the waste-generating source, the filling valve can return an opening signal, the weighing platform completes zero-point calibration and is in a stable acquisition state, and the container number can be identified, then the acquisition of data corresponding to the current filling batch begins; the source information is read by the waste-generating unit registration system, and includes at least the unified social credit code, waste-generating unit name, source number, waste-generating process code, and operator identification field; the category declaration information is entered by the waste-generating unit according to the hazardous waste management ledger, and includes at least the category declaration code, source industry code, and process category code field; the container information is read by QR code, RFID (radio frequency identification) tag, or container electronic ledger, and includes at least the container number, container type, container capacity, and container activation time field; the filling quality information is collected in real time by the weighing platform below the container; the on-site detection characteristic data is obtained by online detection equipment, edge acquisition terminal, or authorized manual review records, and includes at least the density, conductivity, refractive index, spectral response, moisture content, temperature, flash point, or equivalent detection data that can characterize the stable state of the same filling batch;

[0076] Figure 2 Both medical and electronic sources are considered waste sources. Medical sources indicate the location where medical institutions generate waste organic solvents, while electronic sources indicate the location where electronic manufacturing companies generate waste organic solvents. Waste liquid containers are used to hold the waste organic solvents of the current filling batch. Weighing platforms are used to collect filling quality data, and detection terminals are used to collect on-site characteristics such as density, conductivity, refractive index, spectral response, temperature, or flash point. During the data collection process, source information, category declaration, container information, filling quality, and on-site characteristics are the data items that need to be collected for the current filling batch. Source information and category declaration can come from the registration system, container information can come from the container identification device, filling quality can come from the weighing platform, and on-site characteristics can come from the detection terminal. After the above data enters the source edge computing unit, it is aligned and associated according to a unified time reference, batch identifier, and the same filling operation relationship, so that data from different sources can be mapped to the same filling batch. After the alignment and association are completed, a batch data table corresponding to the same filling batch is formed. This batch data table is used to store data such as source, category, container, quality, and on-site characteristics. The time reference is used to determine the collection order of each data, and the batch identifier is used to distinguish different filling operations.

[0077] The data acquisition cycle for filling quality information can be selected as 2 seconds, or adjusted within the range of 1 to 5 seconds depending on the on-site filling speed, the response speed of the weighing platform, and the communication bandwidth. The 2-second acquisition cycle is based on the fact that changes in the filling flow rate at the source point are usually reflected on a second-by-second basis, and the amount of quality change during the filling process of drums or small cans can be reliably identified by the industrial weighing platform. When the filling flow rate is fast and higher resolution of quality change is required, the acquisition cycle can be shortened to 1 second. When the filling process is relatively stable and communication bandwidth or local storage space is limited, the acquisition cycle can be extended to 5 seconds. When the acquisition cycle exceeds 5 seconds, it is easy to reduce the ability to identify changes during the filling stage. When the acquisition cycle is less than 1 second, it is easy to increase the amount of invalid data and communication load. Therefore, the acquisition range of 1 to 5 seconds can balance batch identification accuracy, data processing load, and engineering implementation cost.

[0078] To ensure that source information, category declaration information, container information, filling quality information, and on-site detection characteristic data are consistently attributed to the same filling batch, the source point edge computing unit generates a temporary batch identifier at the start of filling. This temporary batch identifier is formed by concatenating the source point number, date, container number, and daily serial number. The start of filling employs a dual-trigger determination based on valve opening and mass change: if the valve opening is greater than 50% for 10 consecutive seconds, and the mass increase on the weighing platform is greater than 0.2 kg within the same 10-second window, the filling data acquisition state is confirmed. A valve opening greater than 50% is used to exclude valve jogging, trial opening, or false triggering. The 10-second window is used to exclude short-term transient actions. The 0.2 kg threshold is set at 20 times the resolution of the commonly used on-site weighing platform (0.01 kg) to exclude minor mass fluctuations caused by container shaking, platform vibration, and personnel passing by. When the resolution of the on-site weighing platform differs from 0.01 kg, the mass increase threshold at the start of filling can be determined at 10 to 20 times the resolution of the weighing platform.

[0079] The completion of filling is determined by a dual stability criteria: valve closure and stable mass. Specifically, the valve opening is zeroed and held for 30 seconds, and the mass change on the weighing platform within those 30 seconds is no greater than 0.05 kg. When the weighing platform resolution is 0.01 kg, the mass stability threshold can be set to 0.05 kg. When using a weighing platform with other resolutions, the mass stability threshold can be determined as 3 to 5 times the platform resolution. The 30-second holding time covers the backflow of residual liquid in the pipeline after valve closure and the stabilization of the liquid level in the container. The mass stability threshold is used to prevent premature batch termination due to platform micro-vibrations. The time boundary of the current filling batch is formed through the filling start and end determination criteria.

[0080] During the data acquisition process, each data record is written to the source cache table according to a unified time reference. Time synchronization can be achieved using local edge computing units to keep the time deviation between multiple acquisition devices within 100 milliseconds. When the waste source has industrial Ethernet or private network capabilities, the time deviation can be kept within 100 microseconds. When the network is interrupted, the local clock of the edge computing unit is used as a temporary time reference, and a compensation timestamp is written after the network is restored. 100 milliseconds is used to meet the data alignment requirements under the second-level acquisition conditions in the filling process, while 100 microseconds is suitable for scenarios with high-precision time synchronization capabilities, which can further reduce batch characteristic deviations caused by sampling misalignment of multiple devices. Each data record in the source cache table includes at least the following fields: temporary batch identifier, acquisition time, data type, data value, device number, and device status identifier.

[0081] Equipment status indicators include four categories: normal, drift, missing, and manually entered. "Normal" indicates the data acquisition equipment has passed self-test; "drift" indicates the acquired value continuously deviates from the historical baseline but has not reached the shutdown condition; "missing" indicates the equipment has not returned valid data; "manually entered" indicates data has been entered by authorized personnel. The historical baseline and historical repeatability standard deviation are calculated based on similar data from the most recent 30 qualified filling batches from the same waste source. When the number of qualified batches is less than 30, historical data from similar waste sources or equipment factory calibration data are used as the initial baseline and initial standard deviation. The drift threshold can be set to twice the historical repeatability standard deviation of similar test data, and the shutdown threshold can be set to three to five times the historical repeatability standard deviation. When the equipment factory calibration or verification document specifies allowable error, the upper limit of the equipment's allowable error is used as the shutdown threshold. For data with abnormal status indicators, the source edge computing unit retains the corresponding data and abnormality indicator and writes it into the subsequent batch data table for verification during coding generation, incoming inspection, and abnormality tracing.

[0082] After the current filling batch is completed, the source edge computing unit aggregates and processes the data within the same filling batch; quality data is arranged in chronological order to form a filling quality sequence, and on-site inspection feature data is arranged along the same time axis to form an on-site inspection feature sequence; for continuously collected data, outlier removal is performed first, followed by median smoothing; the outlier removal rule is: when the median deviation of a sampling point from the median of the three sampling points before and after it exceeds three times the historical repeatability standard deviation, the sampling point is marked as an outlier; three times the standard deviation corresponds to the normal discrete boundary of on-site inspection data, which can identify abrupt changes while preserving normal fluctuations;

[0083] When the number of outliers does not exceed 10% of the total number of sampling points in the current filling batch, interpolation is performed using adjacent valid sampling points to complete the result. When the number of outliers exceeds 10%, the current filling batch is marked as a batch to be reviewed. The 10% setting is based on the fact that short-term pumping pulsations, equipment transient interference, or communication jitter usually only affect a small number of sampling points. When this proportion is exceeded, the collection quality may already affect the batch's representative value. The median smoothing window can be selected as 5 sampling points, corresponding to a 10-second time window under a 2-second collection cycle. When the collection cycle is adjusted, the median smoothing window can be adjusted to 3 to 7 sampling points. The 5-point window can suppress pumping pulsations and instantaneous jitter of the weighing platform without significantly masking the actual filling changes.

[0084] After outlier handling and median smoothing, the source edge computing unit extracts the middle section data, excluding the first 10% after filling begins and the last 10% before filling ends, as the representative data interval. The first 10% period usually corresponds to the pipeline replacement, valve gradual opening, and flow ramp-up process; the last 10% period usually corresponds to the valve closing, tail liquid dripping, and flow decay process. The middle section data is more representative of the stable state of the same filling batch. If the number of sampling points for the current filling batch is small and it is not possible to remove the first 10% and last 10% of the data at the same time, then at least the data interval with the longest continuous stable time is retained as the representative data interval, and a low sample identifier is written in the batch data table.

[0085] The data correspondence within the same filling batch is fixed through a batch data table. The batch data table uses the official batch identifier as the primary key, which is generated from the temporary batch identifier after integrity verification. The batch data table includes at least the following fields: source information, category declaration, container, filling quality, on-site inspection feature, time, equipment status, and verification identifier. The filling quality field is the difference between the final filling quality and the initial filling quality. The on-site inspection feature field is the representative value obtained by weighting each on-site inspection feature data within the representative data range according to its quality increment. The quality increment weight is determined by the ratio of the quality increment corresponding to each sampling point to the total filling quality; that is, the weight of a sampling point is the quality increment of that sampling point divided by the total filling quality of the current batch. Therefore, even when the filling speed changes, the contribution of the on-site inspection feature data to the batch representative value still corresponds to the actual quality of the material entering the container. After the batch data table is generated, it is used for subsequent source point self-certification coding.

[0086] Specifically, such as Figure 3As shown: In S2, after the batch data table is formed, the source edge computing unit performs a coded status verification on the batch data table. A coded status means that the required fields in the source information, category declaration information, container information, filling quality information, and on-site detection feature data are complete, the equipment status does not show any prohibited coding indicators, the filling quality is greater than 0, and the binding relationship between the container number and the waste source point passes the verification. Prohibited coding indicators include at least the following situations: missing official batch identifier, unreadable container number, filling quality less than or equal to 0, inconsistent source information with the waste source point, all missing key on-site detection feature data, and manually entered data failing authorization verification. For data with a drifting equipment status or manually entered data, the source edge computing unit writes a status identifier in the coding extension field. For data with a missing equipment status and the missing field is a key field, the current batch is marked as a batch to be reviewed, and no official source self-certification code is generated for the time being. Key fields include at least the official batch identifier, container number, source information, filling quality, and at least one on-site detection feature data.

[0087] Figure 3 The batch data table in the middle is Figure 2 The data results generated in step S1 are used for coded verification, which uses field completeness, equipment status, and quality validity as the criteria. Field completeness is used to determine whether key fields such as source, category, container, quality, and on-site characteristics are complete. Equipment status is used to determine whether the data acquisition equipment is in normal, drifting, missing, or manually supplemented state. Quality validity is used to determine whether the filling quality is greater than zero and meets measurement requirements. After passing the coded verification, source self-certification codes are allowed to be generated. Subsequently, the batch data table is standardized and quantified to unify the field order, unit of measurement, numerical precision, and expression of on-site characteristics. Then, summary processing is performed. A batch summary value is generated and signed to produce a signature value used to verify the identity of the waste-generating unit and the authenticity of the batch data. The source point self-certification code includes a declaration segment, a summary segment, a signature segment, and an index segment. The declaration segment is used for on-site identification, the summary segment is used for batch data verification, the signature segment is used to prevent unauthorized coding, and the index segment is used to retrieve the traceability ledger. After generating the source point self-certification code, it is written to an electronic tag, and the corresponding source point event record is saved to the traceability ledger. In case of network anomalies, local caching, sequential retransmission, and summary comparison are used to ensure that the records to be written can be rewritten in the original order, and the consistency of the rewrite results is checked.

[0088] The source point self-certification code is generated based on the batch data table. Before generation, the source point edge computing unit first standardizes the fields in the batch data table. The source information is arranged in the order of unified social credit code, source point number, and waste generation process code. The category declaration information is arranged in the order of industry code, category declaration code, and process category code. The container information is arranged in the order of container number, container type, and container capacity. The quality information is uniformly converted to kilograms and retained to 3 decimal places. The on-site detection feature data is arranged in the order of equipment acquisition and field number, and quantized according to the effective resolution of the corresponding equipment. Through field standardization, it is possible to avoid generating different codes for the same batch of data due to differences in field order, unit format, or low-bit noise.

[0089] Quantization rules are set according to data type; density data can be quantized with 4 significant digits; conductivity data can be quantized by fixed-point integers or logarithms; spectral response data can be quantized by channel number and normalized intensity; temperature and flash point data can be quantized by 1 decimal place or integer. The above quantization bit depth is based on the effective resolution of commonly used on-site testing equipment, the data capacity that electronic tags can carry, and the coding stability requirements. This can reduce the impact of low-level random fluctuations on the summary value while retaining the batch characteristics required to distinguish different filling batches. When the waste source does not have the conditions to collect all on-site testing features, a downgrade code can be generated using filling quality sequence, time series, temperature data, and at least one stability test data. The downgrade level and missing field identifier are written in the coding status field.

[0090] The normalized fields are concatenated in a fixed order to form a string to be encoded. The string to be encoded includes at least the following fields: version number, source information, category declaration information, container information, filling start time, filling end time, total filling quality, representative value of on-site detection features, equipment status identifier, and batch official identifier. The version number is used to support subsequent field expansion, and the batch official identifier is used for reverse association with the aforementioned batch data table. The source edge computing unit performs digest processing on the string to be encoded to obtain the batch digest value. The digest algorithm can be the national cryptographic SM3 (national commercial cryptographic hash algorithm), or an equivalent digest algorithm that meets the requirements of the regulatory platform. Subsequently, the source edge computing unit uses the private key of the waste generation unit to sign the batch digest value and key logical fields to generate a signature value. The signature algorithm can be the national cryptographic SM2 (national commercial elliptic curve public key cryptography algorithm), or an equivalent digital signature algorithm recognized by the regulatory platform.

[0091] The source-point self-certification code's data structure consists of a logical declaration segment, a data digest segment, a signature verification segment, and a ledger index segment. The logical declaration segment provides information readable by on-site personnel and includes at least the abbreviation of the waste-generating unit, container number, category declaration code, and filling date. The data digest segment is a batch digest value used to correspond to the batch data table in the traceability ledger. The signature verification segment includes at least the waste-generating unit's signature value and public key index. The ledger index segment records the write position of batch data in the traceability ledger. The logical declaration segment is used for rapid on-site identification, the data digest segment prevents batch data from being replaced, the signature verification segment prevents unauthorized entities from forging the code, and the ledger index segment is used for rapid retrospective checking during subsequent loading, transportation, arrival at the plant, unloading, and mixing processes. The source-point self-certification code can be written to an RFID electronic tag or generated as a QR code and written to a paper tag. The RFID electronic tag is suitable for rapid machine reading, while the QR code is suitable for manual or mobile terminal reading.

[0092] Before writing the electronic tag to the container, the source edge computing unit performs a tag consistency check. The tag consistency check includes at least container number consistency check, tag content consistency check, and write time check. The container number consistency check is used to confirm that the container number corresponding to the tag is consistent with the container number in the batch data table. The tag content consistency check is used to confirm that the read value after the tag is written is consistent with the value to be written byte by byte. The write time check is used to confirm that the tag writing time is later than the filling end time but earlier than the loading start time. When the tag read value is inconsistent with the value to be written, the source edge computing unit automatically rewrites it once. If two consecutive write failures occur, the container is marked as a tag fault state, and the tag is manually replaced and rewritten. The two write failures are used as a tag fault judgment condition. The engineering source of this condition is that a single failure may be caused by communication jitter, tag attachment posture, or instantaneous reading interference, while consecutive failures usually indicate that the tag is damaged, the writing device is abnormal, or the container tag position does not meet the reading requirements.

[0093] After the tag is successfully written, the source edge computing unit writes the batch data table, batch summary value, signature value, tag number, and writing time into the traceability ledger. The traceability ledger can be a consortium blockchain ledger or a regulatory database with tamper-proof auditing capabilities. The traceability ledger is internally divided into record partitions according to event type, including at least source event record partitions, transportation event record partitions, handover event record partitions, and mixing tank event record partitions. Waste-generating unit nodes, transportation company nodes, disposal company nodes, and regulatory nodes can jointly maintain the traceability ledger. The written records are indexed using the waste-generating unit code, date, and container number to enable subsequent nodes to quickly locate the corresponding batch data through the source self-certification code.

[0094] When the network is normal, the ledger index number is returned after the trace ledger is written, and the ledger index number is written back to the ledger index segment of the source point self-certification code. When the network is abnormal, the source point edge computing unit stores the records to be written into the local buffer queue. The local buffer capacity is sufficient to store data for continuous operation for at least 72 hours. The 72-hour setting is based on the continuous data retention scenarios caused by common network maintenance, regional power outages, extreme weather, and holiday shutdowns at hazardous waste collection and transportation sites, which can cover most short-term communication interruptions. The buffer queue adopts a first-in-first-out rule. After the network is restored, the data is retransmitted in the order of the original collection time. The retransmitted records retain two time fields: the original collection time and the retransmission time, to avoid being mistaken for subsequent tampering. After the retransmission is completed, the source point edge computing unit performs a bidirectional comparison between the local record summary and the ledger record summary. If the comparison is consistent, the local cache is released. After the above processing, the source point self-certification code and the ledger index together serve as the data basis for continuous association of loading, transportation, handover at the plant, and unloading nodes.

[0095] Specifically, such as Figure 4 As shown: In S3, after the transfer manifest becomes effective at the waste-generating unit and the dedicated hazardous waste transport vehicle arrives at the loading area of ​​the waste-generating source, the on-board edge computing unit enters the loading verification state. The transfer manifest information is read by the hazardous waste management platform and includes at least the manifest number, waste-generating unit, transport unit, receiving unit, planned loading time, planned receiving time, planned category, planned quality, and vehicle identification number. Before loading, the on-board edge computing unit downloads the manifest summary and authorized loading list and matches the authorized loading list with the source self-certification code. The matching content includes at least whether the waste-generating unit is consistent, whether the category declaration code is within the scope of the manifest, whether the container number exists in the authorized loading list, and whether the ledger index can retrieve a valid batch record. If any matching content fails, the handheld terminal generates a loading prohibition prompt and writes the interception time, container number, source self-certification code, and reason for failure into the interception event record.

[0096] Figure 4The waste source storage area is used to temporarily store waste liquid containers with electronic tags. Hazardous waste transport vehicles are used to carry out transportation tasks according to the transfer manifest. The disposal company entrance is used for onboard handover. The unloading area is used for unloading verification and waiting before tank loading. The source self-certification code runs through the entire process of loading, transportation, onboard handover, and unloading, and is used to continuously bind the batch identity of each container with subsequent circulation records. After reading the source self-certification code, the loading node matches it with the authorized loading list and records the loading quality when the container enters the transport vehicle. The transportation node associates the vehicle positioning trajectory with the loading list summary and records transportation anomalies such as parking, route deviation, weighing anomalies, or liquid level anomalies. The onboard handover node performs consistency verification on the vehicle number, transfer manifest, vehicle identification number, receiving unit, and loading list summary, and records the onboard time and handover completion time. The unloading node reads the source self-certification code again to confirm the container identity and compares the unloading quality with the loading quality to determine whether there are any quality anomalies in the container before and after transportation.

[0097] During loading, operators use handheld terminals or vehicle-mounted RFID readers to read the source point self-certification code in the container's electronic tag; the vehicle-mounted edge computing unit obtains the waste-generating unit's public key based on the public key index in the source point self-certification code and verifies the correspondence between the signature value and the batch digest value; after successful verification, the vehicle-mounted edge computing unit reads the source point event record in the traceability ledger and adds the corresponding container to the vehicle loading list; the loading quality is collected by the vehicle-mounted weighing platform or the loading area weighing platform, which can be obtained by the difference in the total vehicle weight before and after the container enters the vehicle, or by weighing the container individually; the loading quality is compared with the filling quality in the batch data table, and the difference ratio is calculated by dividing the absolute value of the difference between the loading quality and the filling quality by the filling quality;

[0098] When the difference ratio is no greater than 0.5%, the loading quality is deemed valid; when the difference ratio is greater than 0.5% but no greater than 1%, a re-weighing process is triggered, and the median value is taken after two re-weighings as the loading quality; when the difference ratio is greater than 1%, the container enters an abnormal loading state, an abnormal loading record is generated, and entry into the transportation chain is suspended; the 0.5% setting is based on the common cumulative indication error of commercial weighing instruments under loading and unloading vibration, slight vehicle tilting, and on-site operational disturbance conditions, and is applicable to the normal measurement deviation range; 1% is used as a manual verification threshold to distinguish between normal measurement errors and possible leakage, replacement, or inconsistencies in registration; taking the median value after two re-weighings can reduce the random deviation caused by ground slope, vehicle vibration, or personnel operation in a single weighing;

[0099] During transportation, the vehicle-mounted edge computing unit continuously associates the source point self-certification codes with the transportation trajectory. The transportation trajectory is collected by a GPS positioning module or a Beidou positioning module, with a collection interval of 30 seconds, which can also be adjusted within the range of 10 to 60 seconds depending on the complexity of the route, the level of supervision, and network resources. The 30-second interval can meet the usual requirements of hazardous waste transportation supervision for trajectory continuity and avoid excessive communication load caused by excessive frequency. The 10-second interval is suitable for complex urban routes or high-risk batches. The 60-second interval is suitable for ordinary batches with stable routes and limited network resources. Each trajectory record includes at least the following fields: vehicle number, positioning time, latitude and longitude, speed, direction of travel, vehicle status, and current loading list summary. The current loading list summary is obtained by concatenating all source point self-certification codes in the vehicle according to the container loading order and then performing summary processing, so that the trajectory record is bound to the current loading batch.

[0100] When a vehicle is parked for more than 30 minutes and the parking location is outside the declared route, legal rest area, or receiving unit area, the onboard edge computing unit generates an abnormal parking record. The 30-minute setting is based on the reasonable time limit for regular driving rest, temporary waiting, and short-term traffic control. If this time limit is exceeded and the location does not conform to the transportation plan, there is a risk of abnormal stay or illegal transfer. When the vehicle's location deviates from the declared route by more than 1 kilometer for more than 5 minutes, the onboard edge computing unit generates a route deviation record. The 1-kilometer deviation distance is used to accommodate detour errors and positioning on ordinary urban roads. Drift, with a duration of 5 minutes, is used to exclude instantaneous GPS or BeiDou drift; when the transportation route is a short route within the park, the route deviation threshold can be reduced to 300 to 500 meters; when the transportation route includes mountain roads, overpasses, tunnels, or areas with positioning obstruction, the route deviation threshold can be relaxed to 1 to 2 kilometers; when the vehicle weighing data or liquid level data shows a continuous drop at a non-unloading location, the vehicle edge computing unit generates a suspected abnormal transfer record and writes the time of the abnormality, the location of the abnormality, a summary of the current loading list, and the vehicle status into the transportation event record partition of the traceability ledger;

[0101] After the transport vehicle arrives at the centralized disposal enterprise, the receiving end of the disposal enterprise reads the vehicle number, manifest number, and all source point self-certification codes inside the vehicle. The receiving end first verifies whether the vehicle loading list summary is consistent with the loading list summary uploaded last during the transportation process, and then verifies whether the manifest number, vehicle identification number, arrival time, and receiving unit match. If the arrival time exceeds the planned receiving time by less than 2 hours, it is recorded as a late arrival. If it exceeds 2 hours and there is no record on the regulatory platform, it is recorded as an abnormal late arrival. The engineering source of the 2-hour threshold is common urban traffic fluctuations, highway delays, and queuing time in the hazardous waste transportation process, which can distinguish between general delays and abnormal delays that may affect the authenticity of the handover. The handover time is taken as the time when the receiving end reads the source point self-certification code of the first container as the handover start time, and the handover completion time is taken as the time when all containers have been read and passed the manifest verification. The handover record is written to the handover event record section of the traceability ledger, which includes at least the fields of manifest number, vehicle number, source point self-certification code list, loading quality list, transportation trajectory summary, arrival time, handover completion time, and receiving end signature.

[0102] Before unloading or dumping, the disposal company rereads the source certification code of each container and associates the unloading quality with the corresponding code. The unloading quality is collected by the unloading platform, container weighing equipment, or receiving tank weighing equipment. The unloading quality is compared with the loading quality. If the difference ratio is no greater than 0.5%, the container enters the tank entry candidate queue. If the difference ratio is greater than 0.5%, unloading verification is performed according to the re-weighing and manual verification rules of the loading process. The unloading verification confirms at least the container appearance, label status, manifest status, and weighing record, and the confirmation conclusion is written into the handover event record section of the traceability ledger. After the above processing, each source certification code is continuously associated with the transfer manifest, loading quality, transportation trajectory, arrival time, unloading quality, and handover time, serving as the data basis for subsequent updates to the mixed tank traceability ledger according to the tank entry order and tank entry quality.

[0103] Specifically, such as Figure 5 As shown: In S4, when the receiving end of the disposal enterprise completes the handover and unloading verification, and the receiving tank is in the allowed tank entry state, the tank entry control end starts multi-source tank entry recording; the allowed tank entry state is jointly determined by the receiving tank batch status, remaining capacity, tank entry valve status, weighing equipment status, and traceability ledger connection status; the receiving tank batch status can be divided into 5 categories: empty tank, new batch, receiving, sealing tank, and abnormal isolation, among which the empty tank, new batch, and receiving states allow tank entry to be performed; the remaining capacity can be selected as not less than 110% of the planned tank entry mass, and this value is set based on the receiving tank liquid level fluctuation, metering error, and on-site operation safety margin; when the remaining capacity is less than 110% of the planned tank entry mass, the tank entry control end will transfer the corresponding container to the next receiving tank candidate queue or wait for scheduling;

[0104] Figure 5 Source 1, Source 2, and Source 3 are exemplary identifiers for different sources. Each source can correspond to a container, a waste source point, or a waste-generating unit. The code and unloading quality represent the source point self-certification code that each source needs to read before entering the tank, as well as the quality data after unloading verification. First entry, second entry, and third entry indicate that each source enters the receiving tank sequentially according to its actual entry time. Each time entry occurs, the mixing traceability ledger generates a corresponding entry contribution record. The entry contribution record records the source code, entry quality, and entry time for this entry. The pre-order summary is used to inherit from the previous entry record, and the chained update is used to continuously associate the current entry contribution record with the previous record, preventing errors in entry order or quality. The quantity or source code is arbitrarily modified; after each tank entry is completed, the system recalculates the cumulative mass of the current mixing tank batch and calculates the cumulative mass of each source that has entered the mixing tank batch; the mass percentage relationship table is used to record the mass percentage results at different levels; among them, the container-level mass percentage represents the mass percentage of a specific container in the mixing tank batch, the source-level mass percentage represents the mass percentage of a specific waste-generating source in the mixing tank batch, the unit-level mass percentage represents the mass percentage of a waste-generating unit in the mixing tank batch, and the category-level mass percentage represents the mass percentage of the corresponding source declared in the same category in the mixing tank batch; the mixing tank batch code and source contribution list represent the mixing tank batch results formed after sealing, which are used for subsequent category attribution judgment, disposal path matching, and abnormal source tracing;

[0105] Before each source enters the tank, the tank entry control terminal reads the corresponding source self-certification code, unloading quality, handover record, and ledger index. The tank entry sequence is determined by the actual time of opening the tilt valve or pumping operation, with the tank entry sequence number increasing from 1. The tank entry quality is primarily determined by the total mass difference before and after tank entry using the receiving tank's weighing equipment; this difference is used as the tank entry quality increment. When the receiving tank's weighing equipment is temporarily unavailable, the tank entry quality increment can be determined by subtracting the container's residual mass from the container's unloading quality. When two quality sources coexist, the tank entry control terminal compares their differences. If the difference ratio is no greater than 0.5%, the mass difference corresponding to the receiving tank's weighing equipment is used; if the difference ratio is greater than 0.5%, a re-weighing or manual confirmation is performed. The 0.5% setting is based on the common cumulative indication error of commercial weighing equipment under loading, unloading, tilting, and on-site vibration conditions. When the tank entry quality increment is 0 or less than 0, the corresponding tank entry record is not written to the formal mixed tank traceability ledger but to the abnormal tank entry cache table.

[0106] The mixing tank traceability ledger adopts a time-series chained data structure. Each tank entry generates a tank entry contribution record, which includes at least the following fields: mixing tank batch number, tank entry sequence number, source self-certification code, manifest number, container number, tank entry start time, tank entry end time, tank entry quality increment, cumulative batch quality before tank entry, cumulative batch quality after tank entry, operator identification, tank entry equipment status, and summary of the previous record. The summary of the previous record for the first tank entry contribution record is the initial batch summary, which is generated by the receiving tank number, batch creation time, and disposal enterprise node signature. Starting from the second tank entry contribution record, the current record summary is obtained by concatenating the normalized fields of the current tank entry contribution record with the summary of the previous record.

[0107] The chained update relationship can be represented as:

[0108]

[0109] in This represents the cumulative summary after the i-th time the substance is added to the container. This represents the cumulative summary before the i-th time the substance is added to the container. This represents the normalized data of the i-th contribution record, and Hash (hash digest function) represents the digest processing function. This indicates field cascading; through the above chained update relationship, when any entry quality, entry order, or source code is modified, the subsequent cumulative summary will change; thus, the mixing tank traceability ledger not only records the list of sources participating in mixing, but also records the time position and quality contribution of each source entering the mixing tank batch, avoiding the source relationship being saved only in the form of a static list after multi-source mixing.

[0110] The mass percentage relationship is updated synchronously after each batch is loaded into the tank; for the i-th batch loading, the cumulative mass of the batch up to the current time is recorded as . The cumulative mass of the j-th source entering the tank within the current batch is denoted as . Then the quality percentage of the j-th source for:

[0111]

[0112] When multiple containers correspond to the same waste-generating unit, the same process, or the same category declaration code, the container-level percentage, source-level percentage, waste-generating unit-level percentage, and category declaration-level percentage should be saved separately. The container-level percentage is used to trace the responsibility of specific containers, the source-level percentage is used to identify specific waste-generating processes, the waste-generating unit-level percentage is used for cross-unit responsibility allocation, and the category declaration-level percentage is used for subsequent category attribution and disposal path matching. The quality percentage should be calculated internally in the ledger and retained to at least 6 decimal places, and retained to 2 to 4 decimal places when displayed externally or in reports. Retaining 6 decimal places internally can avoid the loss of small quality sources during continuous calculations. Retaining 2 to 4 decimal places when displayed externally is in line with management reports and regulatory viewing habits.

[0113] During the tank entry process, a source consistency check is performed simultaneously. This check is not solely based on barcode scanning results, but rather on a multi-dimensional verification process involving the source self-certification code, manifest information, unloading quality, tank entry quality, and tank entry order. Verification content includes at least: whether the source self-certification code passes signature verification; whether the manifest number is within the permitted range for the receiving batch; whether the difference between unloading quality and tank entry quality does not exceed 1%; whether the tank entry time is later than the factory handover time; and whether the tank entry container is not reused within the same batch. The 1% threshold is based on the comprehensive quality deviation that may arise from unloading, transfer, dumping, and container residue. Exceeding this threshold may indicate excessive container residue, abnormal weighing, or inconsistent source. If any verification fails, the tank entry control terminal does not write the corresponding source into the formal mixing traceability ledger, but instead writes it into the abnormal tank entry cache table. Records in the abnormal tank entry cache table have three states: pending confirmation, confirmed abnormal, and manual release. The pending confirmation state is automatically generated by the system; the confirmed abnormal state is confirmed by the reviewer; and the manual release state simultaneously records the releaser's identity, release reason, and regulatory filing number.

[0114] When three consecutive tank entry records enter the abnormal tank entry cache table, or when the quality of abnormal tank entry exceeds 15% of the cumulative quality of the current batch, a batch suspension policy is triggered. Three consecutive abnormal entries are used to identify potential systemic problems in the operation process or source coding. The 15% threshold is used to identify that the abnormal contribution has already had a significant impact on the overall batch. After the batch is suspended, the receiving tank status changes to abnormal isolation, and subsequent sources are not allowed to enter the receiving tank. The tank entry control terminal generates a batch suspension record and pushes it to the disposal company's dispatch terminal and monitoring terminal. If the abnormal source is ruled out after review, the receiving tank status is restored to receiving. If the abnormality is confirmed after review, the portion that has already entered the tank enters the isolation batch, and the original mixed tank traceability ledger uses the cumulative summary at the time of suspension as the isolation batch summary. Through this rollback process, the abnormal source can be prevented from continuing to affect subsequent normal batches, and the established traceability chain can be preserved.

[0115] When the cumulative mass of the receiving tank reaches 90% of its maximum capacity, or the number of sources entering the tank reaches the batch threshold, or the dispatch system issues a batch end command, the tank sealing process is triggered. The 90% maximum capacity is reserved for liquid level fluctuations, temperature changes, foam space, and safety margin. The batch threshold can be set according to the receiving tank capacity and average daily collection volume. For example, a 5000-liter receiving tank can be set to 20 to 30 sources. This range is based on the common batch size of barrelled collection and the efficiency of receiving tank management. When sealing the tank, the mixed tank traceability ledger locks the last cumulative summary and generates the overall code of the mixed tank batch, the source contribution list, the quality proportion relationship table, and the batch status record. The source contribution list and the quality proportion relationship table are written into the batch file of the disposal company and simultaneously written into the mixed tank event record section of the traceability ledger. After the above processing, a mixed tank traceability ledger that reflects the order of multiple sources entering the tank, quality contribution, and source correlation is formed, which serves as the data basis for subsequent category classification, disposal path matching, and abnormal source traceability.

[0116] Specifically, such as Figure 6 As shown: In S5, after the mixed tank batch is sealed, the disposal company's processing end performs integrity verification on the mixed tank traceability ledger, source contribution list, and quality proportion relationship table. The integrity verification includes at least whether the chain summary is continuous, whether the difference between the sum of the source contribution quality and the total batch quality does not exceed 0.5%, and whether each source can be traced back to the source self-certification code and handover record. The 0.5% engineering source is the cumulative error of the weighing equipment, the residual error of the container, and the on-site measurement deviation during the tank entry process. When the difference exceeds 0.5%, it indicates that there may be missing quality records, duplicate tank entry records, or abnormal measuring equipment. If the integrity verification fails, the mixed batch enters the pending verification state, and automatic category classification and disposal path matching are not performed temporarily.

[0117] Figure 6The mixed tank ledger refers to the mixed tank traceability ledger formed in step S4; the proportion relationship refers to the quality proportion relationship table; the verification information refers to the incoming verification data; and the category mapping refers to the cross-industry category mapping relationship. These data serve as input, first entering the integrity verification and category determination process. The integrity verification and category determination process checks whether the chain summary of the mixed tank traceability ledger is continuous, whether the source contribution list and quality proportion relationship are complete, and determines the main category, auxiliary category, and warning category of the mixed batch by combining the management rule table and semantic mapping table. After the category is determined, the disposal path matching selects a disposal path suitable for the mixed batch based on risk priority, quality proportion, and disposal permit scope. Separate disposal means disposing of the mixed batch according to the matched path. The system will send the mixed batches to the corresponding treatment process according to the treatment path. When the incoming verification results are inconsistent with the expected batch characteristics, it is judged as a verification anomaly. At this time, the system will screen candidate anomaly sources based on the quality proportion of each source and the degree of deviation of batch characteristics, and further call the source record, handover record and tank entry record to form an anomaly evidence chain. Among them, the source record is used to check the original waste generation batch, the handover record is used to check the loading, transportation, arrival and unloading process, and the tank entry record is used to check the order and quality contribution of each source entering the mixed tank batch. The append record indicates that the anomaly treatment result, category revision result or treatment path reconfiguration result is written to the batch file as a revised version in order to retain the original record and subsequent processing.

[0118] The cross-industry category mapping relationship is established through a two-layer structure of a management rule table and a semantic mapping table. The management rule table records at least the following fields: hazardous waste category declaration code, industry source code, waste-generating process code, regulatory permit scope, and disposal enterprise receiving permit scope. The semantic mapping table records at least the following fields: source industry, process category, category declaration, on-site detection characteristic range, risk level, disposal path, and priority. The mapping relationship is not centered on a single substance judgment, but rather forms a decision chain based on source data, category data, quality proportion data, verification data, and disposal resource data. The disposal enterprise's processing end first reads the quality proportion relationship table and summarizes it according to waste-generating unit, industry source, and category declaration; then it reads the cross-industry category mapping relationship and maps each summarized item to the candidate category set and candidate disposal path set; subsequently, it sorts them according to risk priority, quality proportion, and disposal permit scope.

[0119] Risk priority is determined based on the hazardous waste category declaration, industry source, disposal company's acceptance permit conditions, regulatory rules table, and on-site verification items, and can be set to levels 1 to 5. Among them, level 1 represents routine acceptance risk, level 2 represents risk requiring ordinary verification, level 3 represents risk requiring key verification, level 4 represents risk requiring restricted acceptance or adjustment of disposal route, and level 5 represents high risk requiring priority isolation or regulatory verification. The risk priority level rules are written into a semantic mapping table, and corresponding version records are generated as regulatory rules or disposal company permit conditions change, so that the applicable rule version can be checked back when making subsequent category determinations.

[0120] Category attribution is generated using a combination of primary category, secondary category, and warning category. The primary category is determined first based on risk priority. When multiple candidate categories are at the same risk level, the primary category is determined based on quality percentage. The quality percentage ranking threshold can be set to 30%, with alternatives ranging from 20% to 50%. The 30% threshold is only used for quality percentage ranking within the same risk level and is not used to exclude high-risk categories. Categories that do not reach the quality percentage threshold but have a higher risk priority than other sources are written into the primary control category or warning category field. The adjustable range of 20% to 50% is used to adapt to different regional regulatory rules, disposal company acceptance rules, and differences in mixed batch size. Secondary categories are determined based on the quality percentage ranking of the remaining sources, with the first two secondary categories preferred. The category attribution record must include at least the mixed batch number, primary category, secondary category, warning category, category source basis, quality percentage of each category, mapping rule version, and generation time.

[0121] Disposal path matching is performed based on category attribution records, quality percentage relationship tables, and the process resource status of the disposal enterprise. The process resource status of the disposal enterprise is provided by the production scheduling system and includes at least the following fields: process line number, permitted category range, current load, acceptable quality, planned activation time, process line acceptance conditions, and maintenance status. The processing end of the disposal enterprise matches the mixed batch with the candidate disposal path set, prioritizing process lines whose permitted range covers the main category, auxiliary category, and warning category, whose current load can accept the batch, and whose process line acceptance conditions match the batch management characteristics. The batch management characteristics include at least the total mass of the mixed batch, main category, auxiliary category, warning category, and incoming verification status. The system includes information such as the scope of disposal permits and scheduling priorities. When multiple disposal paths exist for a mixed batch, they are prioritized in the following order: safety priority, compliance priority, resource utilization priority, and scheduling priority. Safety priority is used to exclude paths that do not meet the risk level requirements; compliance priority is used to exclude paths that do not meet the scope of permits; resource utilization priority is used to prioritize paths that can be recycled; and scheduling priority is used to select paths with shorter waiting times when the aforementioned conditions are the same. The disposal path matching results form a disposal path record, which includes at least the following fields: mixed batch number, matching path, process line number, entry time, path basis, key constraints, and scheduling status.

[0122] The incoming verification information is used to correct the category attribution and disposal path. The incoming verification data comes from the incoming verification records of the disposal company and includes at least the fields of verification time, sampling location, verification items, verification results, verification personnel, and verification equipment status. The incoming verification information does not change the established source contribution chain, but is used to determine whether the actual status of the mixed batch is consistent with the status derived from the traceability ledger. The disposal company's processing end generates expected batch characteristics based on the source contribution list and quality proportion relationship table, and compares the deviation between the incoming verification results and the expected batch characteristics. The deviation ratio is calculated by dividing the absolute value of the difference between the verification result and the expected result by the expected result. For graded results that cannot be expressed as a ratio, the grade difference is used for comparison.

[0123] Deviation thresholds are set separately for each review item. For quality-related reviews, the deviation threshold can be selected from 0.5% to 1%, and its engineering sources are the cumulative impact of weighing equipment errors, transfer residual errors, and tank metering errors on site. For on-site inspection feature-related reviews, the deviation threshold can be selected from 5% to 10%, with 5% used for numerical inspection data that has high stability, and 10% used for inspection data that is greatly affected by sampling location, batch uniformity, or equipment repeatability. For grade-related reviews, the deviation threshold can be selected as Level 1, and its setting is based on regulatory classification or internal risk classification of enterprises, which usually adopts grade management. Level 1 and below can be regarded as the allowable range for review. Different review items have different error sources. Using itemized thresholds can avoid using a single threshold to cover all data types and improve the accuracy of review judgment.

[0124] When the verification deviation does not exceed the corresponding threshold, the disposal company's processing end confirms the validity of the category attribution record and disposal path record, and writes the confirmation status into the batch file; when the verification deviation exceeds the corresponding threshold, it enters the abnormal source tracing process; the abnormal source tracing is based on the quality proportion relationship table as the initial basis, first screening the source set with high contribution to the abnormal verification project, and then tracing back level by level according to the source batch data, source self-certification code, loading and handover record, and tank entry contribution record; the contribution can be calculated using the weighted difference method, the contribution of a certain source is the product of the quality proportion of the source and the deviation degree of the batch characteristics of the source; the disposal company's processing end generates a candidate abnormal source list according to the contribution from high to low, and verifies the code signature, loading quality, unloading quality, tank entry quality and handover time of each candidate abnormal source; when a certain source has a high verification deviation contribution, quality difference exceeding the threshold or incomplete code handover chain, the source is marked as a key abnormal source;

[0125] The results of anomaly source tracing are output in the form of an evidence chain. The evidence chain starts from the overall code of the mixed tank batch and traces backward to the tank entry contribution record, unloading handover record, transportation trajectory record, loading record, source point self-certification code, and source point batch data table. Each level of evidence records a data summary, ledger index, generation time, and signature subject. The anomaly source tracing record includes at least the following fields: mixed tank batch number, anomaly review item, deviation value, candidate anomaly source list, key anomaly source, tracing path, evidence summary, and handling suggestions. The handling suggestions are divided into four categories: batch review, batch isolation, path reconfiguration, and regulatory verification. Batch review is applicable when the deviation is close to the threshold and the specific source has not been located. Batch isolation is applicable when the deviation exceeds the threshold and may affect the safety of disposal. Path reconfiguration is applicable when the category classification has changed but can still be disposed of through other paths. Regulatory verification is applicable when the code chain is broken, the source is replaced, or the manifest is inconsistent.

[0126] When the category attribution or disposal path changes due to an anomaly during review, a recalculation process is executed. The recalculation process first locks the original mixing traceability ledger to prevent original evidence from being overwritten. Then, it generates a batch file to be recalculated, using the review results and anomaly source screening results as new inputs, and re-executes the category attribution and disposal path matching. The recalculated record does not replace the original record but is appended to the batch file as a revised version. The revised version includes at least the following fields: revision reason, revision time, revision input, category before revision, category after revision, path before revision, and path after revision. If the recalculated disposal path still meets the permissible range, the production scheduling system executes according to the revised disposal path. If no available disposal path is found after recalculation, the mixed batch enters an isolation waiting state and is pushed to the regulatory platform for manual disposal decision-making.

[0127] Through the above processing, source batch data, source self-certification codes, transportation handover data, mixed tank quality ratio, cross-industry category mapping, and inbound verification data are connected into the same traceability link. This makes the source code no longer rely solely on waste-generating end declaration information, but is continuously bound to batch data, handover process, and mixed tank contribution relationship. As a result, the reliability of source verification, the accuracy of mixed tank ratio traceability, and the stability of disposal path matching can be improved in multi-source mixed tank and cross-industry disposal scenarios.

[0128] Example 2: Based on Example 1, the specific application process of a source coding and traceability method for organic solvents in medical and electronic waste is further explained:

[0129] In a specific application scenario, medical institution A, medical institution B, and electronics manufacturing companies C and D coexist within a certain area. Centralized disposal company E is responsible for the unified reception, mixing, verification, and disposal of waste organic solvents generated within this area. Medical institution A sets up a temporary storage point for pathological waste liquid, medical institution B sets up a temporary storage point for laboratory waste liquid, electronics manufacturing company C sets up a temporary storage point for PCB (printed circuit board) cleaning waste liquid, and electronics manufacturing company D sets up a temporary storage point for precision component cleaning waste liquid. Each waste source is equipped with container electronic tags, a weighing platform, an on-site detection data acquisition interface, and a source edge computing unit. The hazardous waste transport vehicle V01 is equipped with onboard weighing equipment, a positioning module, an onboard edge computing unit, and a handheld reader / writer terminal. Centralized disposal company E is equipped with an inbound receiving terminal, receiving tank T01, receiving tank weighing equipment, inbound control terminal, inbound verification terminal, and production scheduling terminal. The monitoring platform and the provincial solid waste information platform are used for recording inbound source events, transportation events, handover events, mixing events, and abnormal source tracing records.

[0130] On the same workday, medical institution A fills container A01, medical institution B fills container B01, electronics manufacturing company C fills container C01, and electronics manufacturing company D fills container D01. Before the filling operation begins, each waste-generating point reads the waste-generating unit's identity information, waste-generating process information, category declaration information, and container information. It also obtains filling quality change data through a weighing platform and acquires on-site detection characteristic data reflecting the current batch's stable state through an on-site detection data acquisition interface. Taking container A01 as an example, the source point edge computing unit... Once the valve opening continuously meets the data acquisition conditions and the weighing platform shows a stable increase in mass, a temporary batch identifier A-A01-20260101-001 is generated. The source information, category declaration information, container information, filling quality information, and on-site detection feature data of this batch are written into the source point cache table. After filling is completed, the source point edge computing unit performs time alignment, outlier removal, and representative interval extraction on the acquired data to form the batch data table corresponding to container A01. Containers B01, C01, and D01 form their respective batch data tables in the same manner.

[0131] After generating the batch data table, the source edge computing unit performs a coded status verification on each batch. Taking container A01 as an example, if the batch's official identifier, container number, source information, filling quality, and at least one on-site detection feature data are all complete, the filling quality is greater than 0, and the binding relationship between the container number and the pathological waste liquid temporary storage point of medical institution A passes the verification, then the batch is deemed to meet the coding conditions. Subsequently, the source edge computing unit standardizes the fields in the batch data table according to unified rules, converts the quality information into kilograms, quantifies the on-site detection feature data according to the effective resolution of the equipment, and integrates the version number, source information, category declaration information, and container... Information, filling start and end times, total filling quality, on-site detection characteristic representative values, equipment status identifiers, and batch official identifiers are concatenated into a string to be encoded; the source point edge computing unit performs digest processing on the string to be encoded to obtain a batch digest value, and then uses the signature key corresponding to medical institution A to generate a signature value, thereby forming the source point self-certification code of container A01; the source point self-certification code is written into the RFID electronic tag and QR code tag of container A01, and at the same time, the batch data table, batch digest value, signature value, tag number, and writing time are written into the source point event record partition of the traceability ledger; containers B01, C01, and D01 generate their respective source point self-certification codes in the same way;

[0132] After the transfer manifest L001 becomes effective on the hazardous waste management platform, transport vehicle V01 sequentially arrives at the loading areas of medical institution A, medical institution B, electronic manufacturing enterprise C, and electronic manufacturing enterprise D. Before loading, the onboard edge computing unit downloads the manifest summary and authorized loading list, and reads the source point self-certification codes of containers A01, B01, C01, and D01 one by one. The onboard edge computing unit performs signature verification on each source point self-certification code and verifies whether the waste-generating unit, category declaration code, container number, and ledger index match the transfer manifest. Taking container C01 as an example, if the unit information of electronic manufacturing enterprise C matches the manifest permit information, container C01 is stored... Container C01 is added to the loading list when it is on the authorized loading list and the ledger index can retrieve a valid source event record. During loading, the on-board weighing equipment collects the loading weight of each container and compares the loading weight with the corresponding source filling weight. If the source filling weight of container C01 is 149.8 kg and the loading weight is 149.5 kg, the difference is approximately 0.20%, which is lower than the normal measurement deviation range of 0.5%. The on-board edge computing unit determines that the loading weight is valid. If the loading weight difference of any container exceeds 1%, the on-board edge computing unit generates an abnormal loading record and suspends the container from entering the transportation chain.

[0133] After transport vehicle V01 completes loading, the onboard edge computing unit generates a loading list summary according to the self-certification code sequence of the in-vehicle source points, and continuously binds the loading list summary to the trajectory record during transportation. The trajectory record includes at least the vehicle number, positioning time, latitude and longitude, speed, driving direction, vehicle status, and current loading list summary. When vehicle V01 travels along the route declared on the transfer manifest, the positioning data is continuously uploaded, and there is no abnormal drop in quality or liquid level at non-unloading locations, the transportation event record remains in a normal state. When vehicle V01 stops for more than 30 minutes, and the stopping location is not within the declared route, legal rest area, or receiving unit area, the onboard edge computing unit generates an abnormal parking record. When the vehicle location deviates from the declared route by more than 1 kilometer for more than 5 minutes, a route deviation record is generated. All of the above transportation events are written to the transportation event record partition of the traceability ledger and bound to the current loading list summary.

[0134] After transport vehicle V01 arrives at centralized disposal company E, the receiving end of the disposal company reads the vehicle number, manifest number, and all source point self-certification codes inside the vehicle. The receiving end first verifies whether the vehicle loading list summary is consistent with the loading list summary uploaded last during transportation, and then verifies whether the vehicle identification number, arrival time, receiving unit, and manifest number match. When the arrival time exceeds the planned receiving time but does not exceed 2 hours, the receiving end records a late status. When the arrival time exceeds the planned receiving time by 2 hours and there is no record on the regulatory platform, the receiving end records an abnormal late status. After the handover is completed, the disposal company reads the source point self-certification code of each container again before unloading or dumping, and collects the unloading weight. Taking containers A01, B01, C01, and D01 as examples, the unloading weights are 120.3 kg, 79.8 kg, 149.5 kg, and 100.1 kg, respectively, all of which are no more than 0.5% different from the loading weight. Therefore, the four containers enter the tank entry candidate queue.

[0135] When receiving tank T01 is in the new batch status, and the remaining capacity meets more than 110% of the planned tank entry mass, and the tank entry valves, weighing equipment, and traceability ledger connections are all normal, the tank entry control terminal initiates multi-source tank entry recording. Container A01 first enters receiving tank T01. The tank entry control terminal reads its source self-certification code, unloading mass, handover record, and ledger index, and records the tank entry start time and tank entry end time. The receiving tank weighing equipment determines the tank entry mass increment of container A01 to be 120 based on the total mass difference before and after tank entry. 3 kg; The first tank entry contribution record is generated at the tank entry control terminal, and an initial batch summary is generated with the receiving tank number, batch creation time, and disposal enterprise node signature; Containers B01, C01, and D01 enter receiving tank T01 in sequence, with tank entry mass increments of 79.8 kg, 149.5 kg, and 100.1 kg, respectively; Each tank entry generates a tank entry contribution record, and the current tank entry contribution record is concatenated with the previous record summary for summary processing, thereby forming a mixed tank traceability ledger that is continuously updated according to the tank entry order;

[0136] After all four containers were loaded into the tank, the total batch mass of receiving tank T01 was 449.7 kg. The loading control terminal calculated the mass percentage relationship based on the cumulative loading mass from each source. Container A01 accounted for approximately 26.75% of the mass, container B01 for approximately 17.75%, container C01 for approximately 33.24%, and container D01 for approximately 22.26%. When summarizing by industry source, medical institution A and medical institution B accounted for approximately 44.50% of the total mass, and electronic manufacturing enterprise C and electronic manufacturing enterprise D accounted for approximately 55.50% of the total mass. The above mass percentage relationships were recorded at the container level, source level, waste-generating unit level, and category declaration level, and written into the mixed tank event record partition of the disposal enterprise's batch file and traceability ledger. Since the mass percentage relationship was directly calculated from the mass of each loading, and each loading contribution record was bound by a chain summary, the overall code of the mixed tank batch would change if the loading order, loading mass, or source code of any source was modified.

[0137] After receiving tank T01 is sealed, the disposal company's processing terminal performs integrity verification on the mixed tank traceability ledger, source contribution list, and quality proportion relationship table. When the chained summaries are continuous, the difference between the sum of the source contribution quality and the total batch quality does not exceed 0.5%, and each source can be traced back to its source self-certification code and handover record, the disposal company's processing terminal enters the category attribution and disposal path matching process. The disposal company's processing terminal reads the management rule table and semantic mapping table, and associates the medical industry source, the electronics industry source, category declaration, on-site detection feature range, risk level, and disposal path. Since this batch includes both medical institution sources and electronics manufacturing enterprise sources, the system generates a candidate category set and a candidate disposal path set according to the cross-industry category mapping relationship, and sorts them according to risk priority, quality proportion, and disposal permission scope. When the quality proportion of the source corresponding to electronics manufacturing enterprise C is the highest under the same risk level, its category can be used as an important basis for judging the main category. When the risk level of the source corresponding to medical institution A is higher, even if its quality proportion does not reach 30%, it is written into the main control category or warning category field to avoid ignoring high-risk sources simply based on quality proportion.

[0138] When matching disposal paths, the production scheduling system provides the permitted category range, current load, acceptable quality, planned activation time, process line acceptance conditions, and maintenance status for each process line. The disposal enterprise's processing end prioritizes process lines whose permitted range covers the main category, auxiliary category, and warning category, and whose current load is acceptable. When multiple optional paths exist, the system sorts them in the order of safety priority, compliance priority, resource priority, and scheduling priority, and generates disposal path records. The disposal path record includes at least the mixing tank batch number, matching path, process line number, path basis, key constraints, and scheduling status, and is written to the batch file.

[0139] Before executing the disposal route, the incoming verification end verifies the mixed batch in receiving tank T01 and compares the verification results with the expected batch characteristics generated based on the source contribution list and quality proportion relationship table. When the quality-related verification deviation does not exceed 0.5% to 1%, the on-site detection characteristic-related verification deviation does not exceed 5% to 10%, and the grade-related verification deviation does not exceed level 1, the disposal company's processing end confirms that the category attribution record and disposal route record are valid and allows the production scheduling system to execute subsequent disposal according to the matching results. The above deviation thresholds correspond to weighing equipment error, transfer residue error, tank entry measurement error, sampling location difference, batch uniformity difference, and risk level management error, respectively, which can cover reasonable deviations in on-site verification.

[0140] When the incoming inspection results show that the deviation of a certain on-site detection feature reaches 12%, exceeding the corresponding inspection threshold, the handling enterprise's processing end enters the anomaly source tracing process. The anomaly source tracing is based on the quality proportion relationship table as the initial basis, and the set of sources with high contribution to the anomaly inspection items is selected. The contribution is calculated as the product of the source quality proportion and the deviation degree of the source batch feature. If the contribution of container C01 is the highest, the system continues to trace back the source batch data, source self-certification code, loading quality, unloading quality, tank entry quality and handover time corresponding to container C01. When the source self-certification code signature verification of container C01 passes, but the difference between the unloading quality and the tank entry quality exceeds 1%, or there is a gap in the code handover chain corresponding to the container, the source corresponding to electronic manufacturing enterprise C is marked as a key anomaly source. The system then generates an anomaly source tracing record, which includes at least the mixing tank batch number, anomaly inspection item, deviation value, candidate anomaly source list, key anomaly source, tracing path, evidence summary and handling suggestions.

[0141] Once the source of the anomaly is located, the disposal company's processing end generates batch review, batch isolation, route reconfiguration, or regulatory verification suggestions based on the degree of anomaly. When the review deviation is close to the threshold and the specific source cannot be clearly identified, a batch review suggestion is generated. When the deviation significantly exceeds the threshold and may affect disposal safety, a batch isolation suggestion is generated. When the category classification changes but disposal can still be achieved through other routes, a route reconfiguration suggestion is generated. When there are broken coding chains, source replacements, or inconsistent manifests, a regulatory verification suggestion is generated. If the category classification or disposal route changes due to a review anomaly, the disposal company's processing end locks the original mixed tank traceability ledger, copies it to generate a batch file to be recalculated, and re-executes category classification and disposal route matching using the review results and anomaly source screening results as new inputs. The recalculated record does not replace the original record but is appended to the batch file as a revised version, thus preserving the original traceability evidence and revision process.

[0142] Through the above-described operational process, the filling batch data, source self-certification codes, transportation handover data, mixed tank quality ratio, cross-industry category mapping data, and inbound verification data of the waste-generating source are continuously connected into the same traceability link. This traceability link ensures that the source code no longer exists merely as a waste-generating end declaration label, but is continuously bound to the actual batch data, transportation handover process, and mixed tank quality contribution relationship. In multi-source mixed tank and cross-industry disposal scenarios, centralized disposal companies can restore the quality contribution ratio of each source based on the mixed tank traceability ledger, determine the category affiliation and disposal path of the mixed batch based on the category mapping relationship, and trace back to the specific waste-generating source, container, and handover node along the evidence chain when verification is abnormal, thereby improving the reliability of source verification, mixed tank ratio traceability, and disposal path matching.

[0143] It should be noted that this invention can be deployed on the device itself to realize embedded applications, or it can run on a PC or other terminal with a user interface, thereby meeting various hardware environments and usage requirements.

[0144] The above embodiments can be implemented in whole or in part by software, hardware, firmware, or any other combination. When implemented in software, the above embodiments can be implemented in whole or in part by a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, the processes or functions of the embodiments of this application are implemented in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted wirelessly or wiredly from one website, computer, server, or data center to another website, computer, server, or data center. Wired methods include optical fiber, twisted pair, coaxial cable, etc. Wireless methods include infrared, microwave, etc. Available media include any available media that can be accessed by a computer or data storage devices such as servers and data centers that contain one or more sets of available media. Available media can be magnetic media (floppy disks, hard disks, magnetic tapes), optical media (DVDs), or semiconductor media. Semiconductor media can be solid-state drives.

[0145] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0146] In conclusion, the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for tracing the source of organic solvents in medical and electronic waste, characterized in that, include: S1. Obtain source information, category declaration information, container information, filling quality information and on-site characteristic data of waste organic solvents at the waste source point, and associate all data with the same filling batch. The category declaration information shall be entered by the waste generating unit according to the hazardous waste management ledger, and shall include at least the category declaration code, source industry code and process category code fields. S2. Generate a source self-certification code based on the associated data of the same filling batch, write the source self-certification code into the container electronic tag, and write the corresponding batch data into the traceability ledger. S3. Read the source self-certification code at the loading, transportation, factory handover and unloading nodes, and associate the transfer manifest, loading quality, transportation trajectory, unloading quality and handover time with the source self-certification code. S4. During the multi-source tank entry process, update the tank entry traceability ledger according to the entry order and entry quality of each source, and form the quality proportion relationship of each source in the tank entry batch. S5. Based on the mixed tank traceability ledger, cross-industry category mapping relationship and incoming verification information, determine the category affiliation and disposal path of mixed batches, and trace the corresponding source when verification is abnormal; Cross-industry category mapping relationships are established through a two-layer structure: a management rule table and a semantic mapping table. The management rules table must record at least the fields for hazardous waste category declaration code, industry source code, waste-generating process code, regulatory permit scope, and disposal company receiving permit scope; The semantic mapping table records at least the source industry, process category, category declaration, on-site detection feature range, risk level, disposal path, and priority fields; the disposal enterprise's processing end first reads the quality proportion relationship table and summarizes it according to the waste generating unit, industry source, and category declaration; Then read the cross-industry category mapping relationship and map each summary item to the candidate category set and the candidate disposal path set; Category assignment is generated using a combination of primary category, secondary category, and warning category; the primary category is determined primarily based on risk priority. When multiple candidate categories are at the same risk level, the main category is determined based on the quality percentage. Categories that do not meet the quality percentage threshold but have a higher risk priority than other sources should be written into the warning category field; Sub-categories are determined based on the quality percentage of remaining sources; the category attribution record includes at least the batch number of the mixing tank, the main category, the sub-category, the warning category, the basis for the category source, the quality percentage of each category, the mapping rule version, and the generation time field; the disposal path matching is performed based on the category attribution record, the quality percentage relationship table, and the process resource status of the disposal enterprise; The status of process resources at the disposal enterprise is provided by the production scheduling system, including at least the process line number, permitted category range, current load, acceptable quality, planned activation time, process line receiving conditions, and maintenance status fields. The disposal enterprise's processing end matches the mixed batch with the candidate set of disposal paths, prioritizing process lines whose permitted range covers the main category, auxiliary category, and warning category, whose current load can accept the batch, and whose process line receiving conditions match the batch management characteristics. The batch management characteristics include at least the total mass of the mixed tank batch, main category, auxiliary category, warning category, incoming verification status, disposal permitted range, and scheduling priority. The quality proportion table records the quality proportion results at different levels. Among them, the container-level quality proportion represents the quality proportion of a specific container in the mixed tank batch, the source-level quality proportion represents the quality proportion of a specific waste-generating source in the mixed tank batch, the unit-level quality proportion represents the quality proportion of a waste-generating unit in the mixed tank batch, and the category-level quality proportion represents the quality proportion of the corresponding source declared in the same category in the mixed tank batch. The incoming verification information is used to correct the category attribution and disposal path.

2. The method for tracing the source of organic solvents in medical and electronic waste according to claim 1, characterized in that, S1 includes: Read the waste source registration data, category declaration data, container identification data, filling quality data, and on-site detection characteristic data respectively; A temporary batch identifier is generated after the filling operation is triggered; The filling start time and filling end time are determined based on the valve opening degree and mass change; The collected data is written to the source point cache table according to a unified time base. Data from the same filling batch is processed by status identification, outlier removal, median smoothing, representative interval extraction, and quality increment weighting to form a batch data table.

3. The method for tracing the source of organic solvents in medical and electronic waste according to claim 1, characterized in that, S2 includes: Perform coding status verification on batch data tables and identify prohibited coding flags and missing key fields; The data that passes the verification is standardized and quantified according to field order, unit format, and device resolution; Normalized data is digested and signed to obtain a source self-certification code consisting of a logical declaration segment, a data digest segment, a signature verification segment, and a ledger index segment. After verifying the consistency of the source self-certification code, write it into the container electronic tag, and write the batch record into the traceability ledger according to the event partition; In the event of a network anomaly, the records to be written are locally cached, sequentially retransmitted, and compared with digests.

4. The method for tracing the source of organic solvents in medical and electronic waste according to claim 3, characterized in that, The data that passes the verification is then normalized and quantified according to field order, unit format, and device resolution, including: Arrange the source data, category declaration data, and container data according to a preset field sequence; Standardize the quality data to the same unit of measurement and numerical precision; The on-site detection feature data are quantized according to the equipment acquisition sequence, field number, and detection type. Density data is quantized using significant digits, conductivity data is quantized using fixed-point quantization or graded quantization, spectral response data is quantized using channel number and normalized intensity, and temperature data and flash point data are quantized using decimal places or integer graded quantization.

5. The method for tracing the source of organic solvents in medical and electronic waste according to claim 1, characterized in that, S3 includes: Match the source self-certification code with the manifest summary and authorized loading list; A vehicle loading list is generated after signature verification; Based on the differences in loading quality, valid judgments, re-weighing, or abnormal interception shall be carried out; During transportation, the trajectory record is linked to the loading list summary, and events such as stopping, route deviation, abnormal weighing, or abnormal liquid level are recorded. Upon arrival at the factory, the consistency of the vehicle number, manifest, vehicle identification number, receiving unit, and loading list summary is verified. Before unloading, the source self-certification code is read again and the unloading quality is reviewed.

6. The method for tracing the source of organic solvents in medical and electronic waste according to claim 5, characterized in that, During transportation, the trajectory record is linked to the loading manifest summary, and events such as stopping, route deviation, abnormal weighing, or abnormal liquid level are recorded, including: Generate trajectory records based on train number, location time, vehicle position, speed, vehicle status, and a summary of the loading list; The loading list summary is obtained by summarizing the in-vehicle source point self-certification codes according to the loading order; Based on parking duration, route deviation distance, and changes in weighing or liquid level data at non-unloading locations, a transportation anomaly record is generated.

7. The method for tracing the source of organic solvents in medical and electronic waste according to claim 1, characterized in that, S4 includes: The entry permit is determined based on the status of the receiving tank, the remaining capacity, the status of the inlet valve, the status of the weighing equipment, and the status of the ledger connection. Read the source self-certification code, unloading quality, handover records, and ledger index; The order of tank entry is determined by the actual time of opening the tilt valve or pumping in, and the tank entry number starts from 1 and increments. The mass entering the tank is primarily determined by the difference in total mass before and after entering the tank using the weighing equipment of the receiving tank; this difference is used as the mass increment for this entry. When the weighing equipment of the receiving tank is temporarily unavailable, the increase in the mass entering the tank can be determined by subtracting the residual mass of the container from the unloading mass of the container. The mixing tank traceability ledger adopts a time-series chained data structure; Each tank entry generates a tank entry contribution record. The tank entry contribution record includes at least the mixing batch number, tank entry sequence number, source self-certification code, manifest number, container number, tank entry start time, tank entry end time, tank entry quality increment, cumulative quality of the batch before tank entry, cumulative quality of the batch after tank entry, operator identification, tank entry equipment status, and a summary field of the previous record. The summary of the record preceding the first tank entry contribution record is the initial batch summary, which is generated by the receiving tank number, batch creation time, and disposal enterprise node signature. Starting from the second tank entry contribution record, the current record summary is obtained by concatenating the normalized fields of the current tank entry contribution record with the summary of the previous record; Simultaneously calculate the mass percentages at the container level, source point level, waste-generating unit level, and category declaration level; Records of signature verification, manifest permission, quality difference, tank entry time, or duplicate tank entry verification anomalies are written to the abnormal tank entry cache table. Batch suspension is executed according to the abnormal tank entry status, and tank sealing is executed according to tank capacity, source quantity, or scheduling instructions.

8. The method for tracing the source of organic solvents in medical and electronic waste according to claim 7, characterized in that, Simultaneously calculate the quality percentages at the container level, source point level, waste-generating unit level, and category declaration level, including: After each batch is added to the tank, the cumulative mass of the current batch is used as the calculation basis. The cumulative mass of waste entering the tank is aggregated from each source according to container, source point, waste generating unit, and category declaration code; The cumulative mass of the batch entering the tank under each merging dimension is calculated as a ratio to the cumulative mass of the current batch in the mixing tank, forming a corresponding mass percentage record, which is then written to the mixing tank event record partition.

9. The method for tracing the source of organic solvents in medical and electronic waste according to claim 1, characterized in that, S5 includes: Perform integrity checks on the mixing tank traceability ledger, source contribution list, and quality percentage relationship table; Compare the results of the incoming inspection with the expected batch characteristics to identify any discrepancies. When reviewing anomalies, a list of candidate anomaly sources is generated based on the proportion of source quality and the degree of deviation of batch characteristics. An evidence chain is then formed along the source batch data, shipping handover records, and tank entry contribution records to generate a revised version.

10. The method for tracing the source of organic solvents in medical and electronic waste according to claim 9, characterized in that, The results of the incoming inspection are compared with the expected batch characteristics to identify discrepancies, including: Read the review time, sampling location, review items, review results, and status of review personnel and equipment; Generate expected batch characteristics based on the source contribution list and quality percentage relationship table; Numerical review items are compared according to their deviation ratio, and graded review items are compared according to their grade difference. Abnormal review status is marked based on the threshold corresponding to each review item.

Images