A platform and apparatus for motor vehicle emissions testing
Patent Information
- Application Number
- CN202611096110.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-22
- Publication Date
- 2026-10-16
AI Technical Summary
[0002]近年来,现有在年检场端的排放检测软件技术,通常未严格按照国家标准进行设计,检测流程和数据不规范
本申请提供了一种用于机动车排放检验平台及设备,应用层从服务端获取待检车辆的基本信息,设备接入层提供所有机动车环保检测设备的对接接口,应用层控制机动车环保检测设备的检测,实现上可以获取国家标准的有效车辆参数,下可以控制检测设备;数据层采用加密传输方式获取机动车环保检测设备的检测数据,且应用层按照机动车环保检测流程的执行顺序,依次显示检测任务和适用检测方法,并通过设备接入层和数据层获取当前检测任务的检测数据,待一项检测任务完成后才能显示下一检测任务,直至检测任务列表中所有检测任务的任务状态均为检测完成,最终采用加密传输方式将待检车辆的检测结果上传至监管平台,实现了防篡改功能和数据可溯源功能。因此,本申请提高了排放检测流程的标准化和有效性。
Smart Images

Figure CN122928256A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of motor vehicle emission inspection, and in particular, to a platform and device for motor vehicle emission inspection. Background Art
[0002] In recent years, existing emission inspection software technologies at annual inspection sites are generally not designed in strict accordance with national standards, leading to non-standard inspection procedures and data. Moreover, they do not have anti-tampering and data traceability functions, and problematic data can generate qualified inspection reports at the inspection station end.
[0003] Therefore, it is necessary to develop an emission inspection software technology that can obtain valid vehicle parameters from national standards at the upper end, control emission analysis equipment and chassis dynamometers at the lower end, and has certain anti-tampering functions, so as to be installed at annual inspection sites to replace existing inspection software and execute emission inspection procedures. Summary of the Invention
[0004] The objective of the present application is to provide a platform and device for motor vehicle emission inspection, which can improve the standardization and effectiveness of the emission inspection procedure.
[0005] To achieve the above objective, the present application provides the following solutions: In a first aspect, the present application provides a platform for motor vehicle emission inspection, comprising: a device access layer, a data layer, and an application layer; The device access layer is configured to provide docking interfaces for all motor vehicle environmental protection inspection devices; the data layer is configured to acquire inspection data of the motor vehicle environmental protection inspection devices through the device access layer by means of encrypted transmission; The application layer is configured to acquire basic information of a vehicle to be inspected, as well as applicable inspection methods and emission limit standards for the vehicle to be inspected from a server; display an inspection task list of the vehicle to be inspected, where the inspection task list includes the basic information of the vehicle to be inspected and the task status of each inspection task; before the inspection starts, verify the status and environmental conditions of the motor vehicle environmental protection inspection devices through the device access layer, and allow the inspection to start when both the status of the motor vehicle environmental protection inspection devices and the environmental conditions meet pre-inspection conditions; after the inspection starts, sequentially display the inspection tasks and applicable inspection methods according to the execution sequence of the motor vehicle environmental protection inspection procedure, and acquire the inspection data of the current inspection task through the device access layer and the data layer, wherein the next inspection task can only be displayed after one inspection task is completed until the task status of all inspection tasks in the inspection task list is inspection completed; automatically determine the inspection result of the vehicle to be inspected according to the inspection data and the emission limit standards, and upload the result to a supervision platform by means of encrypted transmission.
[0006] In a second aspect, the present application provides a computer device, wherein the computer device is configured to run the above-mentioned platform for motor vehicle emission inspection.
[0007] According to the specific embodiments provided in this application, this application has the following technical effects: This application provides a platform and equipment for motor vehicle emission testing. The application layer obtains basic information about the vehicle to be tested from the server. The equipment access layer provides interfaces for all motor vehicle environmental testing equipment. The application layer controls the testing of the motor vehicle environmental testing equipment, enabling the acquisition of valid vehicle parameters according to national standards and the control of the testing equipment. The data layer uses encrypted transmission to obtain the testing data from the motor vehicle environmental testing equipment. The application layer displays the testing tasks and applicable testing methods sequentially according to the execution order of the motor vehicle environmental testing process, and obtains the testing data of the current testing task through the equipment access layer and the data layer. The next testing task is only displayed after the previous one is completed, until all testing tasks in the testing task list are in the completed state. Finally, the testing results of the vehicle to be tested are uploaded to the regulatory platform using encrypted transmission, achieving anti-tampering and data traceability functions. Therefore, this application improves the standardization and effectiveness of the emission testing process. Attached Figure Description
[0008] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0009] Figure 1 This is a schematic diagram of the architecture of a motor vehicle emission testing platform provided in an embodiment of this application. Detailed Implementation
[0010] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0011] To make the above-mentioned objectives, features and advantages of this application more apparent and understandable, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments.
[0012] In one exemplary embodiment, such as Figure 1As shown, a vehicle emission testing platform is provided, comprising an equipment access layer, a data layer, and an application layer. The equipment access layer provides interfaces for all vehicle emission testing equipment. The data layer acquires testing data from the vehicle emission testing equipment via the equipment access layer using encrypted transmission. The application layer obtains basic information about the vehicle to be inspected, as well as the applicable testing methods and emission limits from the server; displays a list of testing tasks for the vehicle to be inspected; the testing task list includes basic information about the vehicle to be inspected and the task status of each testing task; before testing begins, the equipment access layer verifies the status and environmental conditions of the vehicle emission testing equipment, allowing testing to begin only when both the status and environmental conditions meet the pre-inspection conditions; after testing begins, testing tasks and applicable testing methods are displayed sequentially according to the execution order of the vehicle emission testing process, and the testing data for the current testing task is acquired through the equipment access layer and the data layer. The next testing task can only be displayed after one testing task is completed, until all testing tasks in the task list are in the "test completed" status; the testing results of the vehicle to be inspected are automatically determined based on the testing data and emission limits, and uploaded to the regulatory platform using encrypted transmission.
[0013] As an optional implementation, the device access layer adapts and collects the full amount of raw sampling data, command interaction frames, and self-test logs of gasoline vehicle five-gas analyzers, diesel vehicle opacity meters, nitrogen oxide analyzers, chassis dynamometers, flow meters, speed sensors, and OBD (On-Board Diagnostics) diagnostic instruments in terms of adapting to the acquisition of raw data from the devices.
[0014] Gasoline vehicle five-gas analyzer: original detection protocol frame (including original sampled values of CO, HC, CO2, O2, and NOx concentrations), standard gas calibration command interaction frame, and equipment self-test log.
[0015] Diesel vehicle opacity meter: raw sampling data of light absorption coefficient, raw records of free acceleration / load deceleration cycle detection, and raw data of optical system cleanliness detection.
[0016] Nitrogen oxide analyzer: raw detection frames of NO, NO2, and NOx concentrations, raw data of sampling temperature / pressure, and raw signals of the high-temperature heating module's operating status.
[0017] Chassis dynamometer: Raw pulse signal of drum speed / torque, interactive frame of load control command, raw parameters of inertia simulation, and raw signal of safety device trigger.
[0018] Flow meter: raw sampling data of exhaust flow, temperature, and pressure; raw signal for airflow stability monitoring.
[0019] Speed sensor: Real-time engine speed raw pulse data, speed signal stability detection and recording.
[0020] OBD diagnostic tool: original fault code messages, real-time data stream original frames (including parameters such as engine speed and intake pressure), and diagnostic protocol interaction logs.
[0021] Metadata uniformly includes: unique device identifier, data collection timestamp (millisecond level, unified time zone), detection task number, data verification code, and current device working status, ensuring that each piece of raw data can be accurately traced.
[0022] As an optional implementation method, refer to Figure 1 The platform in this application also includes: a support layer; the support layer includes: an identity authentication service module, a log service module, a permission / security management service module, a data communication service module, and a device communication service module.
[0023] As an optional implementation, the application layer includes: a self-test module, an equipment calibration module, an emissions testing module, a data management module, a log storage module, and a user management module, which are used to manage the testing agency's inspection and registration, vehicle testing, and other related tasks.
[0024] The self-test module sends self-test commands to the vehicle emissions testing equipment via the device access layer. These commands include self-tests for the chassis dynamometer, exhaust gas analyzer, flow meter, opacity meter, tachometer, environmental parameter analyzer, nitrogen oxide analyzer, basic equipment self-test, and oil temperature sensor. If the equipment fails more than three self-tests, it is locked and unlocked after repair and a second self-test.
[0025] The detailed functions of the equipment self-test are shown in Table 1.
[0026] Table 1 Detailed Self-Test Functions of the Equipment
[0027] For zero-point calibration checks of exhaust gas analyzers: define the number of calibrations and the time node information for each action, and ensure that the entire action does not exceed 2 minutes, meeting the requirements for zeroing / calibrating the equipment in the specifications. During the test, the results and process data of each action are recorded in the database, making the test process more standardized.
[0028] Zero-point calibration checks for smoke meters: Compare the daily filter self-test data to ensure the accuracy of zero-point and full-scale data. After full-scale calibration, perform another zero-point calibration comparison to ensure the accuracy of the "zero point" and guarantee the correctness of the entire smoke meter calibration process. This additional zero-point comparison during calibration prevents issues caused by the equipment being tested at full scale or under conditions of foreign interference, effectively ensuring the accuracy of the smoke meter.
[0029] The equipment calibration module is used to send calibration commands to the vehicle emission testing equipment through the equipment access layer, including chassis dynamometer speed calibration (static force calibration, basic inertia calibration, loaded coasting calibration, variable load loading calibration, internal loss power calibration, and response time calibration). It also calibrates the exhaust gas analyzer's indication error, stability, repeatability, response time, and NO2-NO conversion efficiency, and the flow meter's flow rate and drift. Equipment calibration is shown in Table 2.
[0030] Table 2 Equipment Calibration
[0031] The emissions testing module performs corresponding indicator testing through dual idle speed method, steady-state condition method, simplified transient method, free acceleration method, loaded deceleration method, and OBD testing. The emissions testing module displays a list of testing tasks for the vehicles to be inspected; this list includes basic information about the vehicles and the task status of each task. After testing begins, the testing tasks and applicable testing methods are displayed sequentially according to the execution order of the motor vehicle environmental protection testing process. The next testing task can only be displayed after the previous one is completed. Testing task management is shown in Table 3, testing business management in Table 4, and testing process control in Table 5.
[0032] Table 3 Detection Task Management
[0033] Table 4 Testing Business Management
[0034] Table 5 Detection Process Control
[0035] The system adds monitoring of engine speed, oil temperature, OBD connection status, and vehicle speed data during the testing process. If any logical inconsistencies are found with the testing process (such as the engine speed continuously reaching zero or a constant value), the test is stopped, and a pop-up message reminds the testing personnel to inspect and fix the sensor equipment to ensure the accuracy and authenticity of the testing process.
[0036] Among the improvements, the OBD connection status monitoring is as follows: From the start of the test to the end of the test process, if the OBD disconnection time exceeds 2 seconds continuously, a prompt box will pop up to remind you that the OBD connection is disconnected and ask you to check the OBD connection status. If the OBD disconnection status exceeds 2 seconds, the test will be paused and the inspector will be prompted to check the OBD. If the OBD disconnection status is less than or equal to 2 seconds and does not exceed 3 times, the test process will proceed normally; otherwise, the test will be stopped and the OBD status will be checked.
[0037] Oil temperature monitoring: After the test begins, the engine oil temperature is monitored to measure whether the oil temperature is ≥80℃. For vehicles whose oil temperature cannot reach 80℃, the data is compared with the vehicle model database. For vehicles in the vehicle model database without oil temperature protection, the operator records the reason. The minimum oil temperature limit is 60℃ (threshold) to ensure that the test vehicle is fully preheated.
[0038] Engine speed monitoring: After the test begins, the engine speed status is monitored to check for any obvious errors. When the speed sensor shows a zero value or a constant speed, the system will alarm to prompt the testing personnel to check the equipment.
[0039] The data management module mainly includes querying test data, querying self-test / calibration data, querying termination / suspension / interruption data, maintenance records, and vehicle model database data.
[0040] Vehicle inspection data query: The data management window allows users to query vehicle inspection results. Filtering criteria include license plate color, inspection time, fuel type, inspection method, and emission stage. Clicking on details allows viewing process data and graphs. Operators with limited access cannot query non-compliant vehicles. Once a vehicle inspection and repair are completed and it passes inspection, historical non-compliant data can be queried.
[0041] Self-test / calibration data query: In the data management menu, click on equipment inspection record, select the equipment to be inspected, inspection category, etc., and query and download the self-test / calibration data.
[0042] Terminated / Aborted / Interrupted Data Query: Added an automatic saving function for terminated / aborted / interrupted data, which can be queried in the data query.
[0043] Maintenance and repair records: Equipment locking, maintenance, and other registration information are automatically saved in the data management system for easy access by personnel.
[0044] Vehicle Model Database Data Query: In the Data Management menu, click Vehicle Model Database Data Query, select the brand, vehicle model, etc., to query and download vehicle model database data.
[0045] The data management functions are shown in Table 6.
[0046] Table 6 Data Management Functions
[0047] Data upload includes data comparison and automatic data upload. Data comparison: The completed test data is compared with the uploaded data. If inconsistencies are found, the upload process is terminated, effectively preventing human tampering during data storage and conversion. Data upload is only completed when data matches, allowing the inspection process to print the report, effectively preventing fraudulent testing. Automatic data upload: The unified software automatically uploads all collected data; manual upload is not enabled. Automatically uploaded data includes self-inspection data, calibration data, test operation data, and data from interrupted test operations.
[0048] The user management module enables the management and setting of permissions for different roles. The functional description of user management is shown in Table 7.
[0049] Table 7 User Management
[0050] As an optional implementation, the application layer also includes a log storage module. This module constructs a layered storage system combining edge-local caching and cloud-distributed archiving. The layered storage system employs a three-layer architecture: edge layer, transport layer, and core layer, to achieve layered data storage and collaborative data transfer. The edge layer directly interfaces with various vehicle emissions testing equipment for real-time data acquisition, encrypted caching, and preliminary preprocessing. The transport layer uses encrypted transmission and breakpoint resume mechanisms to facilitate data interaction between the edge layer and the core layer via an industrial-grade network link. The core layer receives and structures the test data, and archives, stores, and retrieves the data using a distributed architecture.
[0051] The log storage module addresses the log recording requirements of unified software in vehicle exhaust emission testing scenarios by constructing a layered storage system of "edge local caching + cloud distributed archiving." It clarifies the storage specifications for raw data from core testing equipment on the local industrial control computer and the distributed storage architecture for structured data on the station server. This achieves a balance between real-time data acquisition, storage security, traceability compliance, and efficient querying, fully complying with industry standards such as GB18285-2018 and GB3847-2018.
[0052] Overall architecture design: A three-layer architecture of "edge layer (local industrial control computer) - transmission layer - core layer (station server)" is adopted to realize layered storage and collaborative data flow. The architecture logic is as follows: Edge layer (local industrial control computer): As the core node for data acquisition and raw data storage, it directly connects to various testing equipment to complete the real-time acquisition, encrypted caching and preliminary preprocessing of raw data, and plays the role of "data buffer pool".
[0053] Transport layer: It adopts the "encrypted transmission + breakpoint resume" mechanism to realize data interaction between industrial control computer and station server through industrial-grade network link, so as to ensure the security and integrity of data transmission.
[0054] Core layer (site server): Composed of a distributed storage cluster and a data processing engine, it is responsible for receiving raw data, completing structured transformation, and realizing long-term archiving, high-availability storage and efficient retrieval of data through a distributed architecture.
[0055] The core logic of data flow is as follows: raw equipment data → encrypted storage on local industrial control computer → incremental upload to the station server after network recovery → data processing engine parses and parses the structured data → distributed cluster archiving → supporting regulatory reporting and business queries.
[0056] Tiered storage design: Adopting a tiered architecture of "local industrial control computer edge storage + station server distributed storage", differentiated storage methods are designed for different data types and business needs to ensure efficient, reliable and scalable data storage.
[0057] The local industrial control computer storage method is as follows: Core positioning: Real-time caching and local tracing, adapting to the need for immediate storage of on-site testing data. The storage method has the following characteristics: Storage medium: Industrial-grade SSD storage disks, with a single disk capacity of ≥1TB, avoiding the defects of mechanical hard drives such as poor shock resistance and high failure rate, and ensuring physical storage security in industrial environments; Storage format: "Binary raw frame + JSON metadata" combined storage. The raw frame fully preserves the details of the device communication protocol, and the metadata marks a unique traceability identifier, taking into account both originality and traceability. Management method: A dual strategy of cyclic overwrite + critical data backup, retaining 365 days of original data by default, and automatically cleaning up expired data when disk usage reaches 85%.
[0058] The range of original data compatible with the equipment includes: full original sampling data, command interaction frames and self-test logs of gasoline vehicle five-gas analyzers, diesel vehicle opacity meters, nitrogen oxide analyzers, chassis dynamometers, flow meters, speed sensors, and OBD diagnostic instruments.
[0059] Gasoline vehicle five-gas analyzer: original detection protocol frame (including original sampled values of CO, HC, CO2, O2, and NOx concentrations), standard gas calibration command interaction frame, and equipment self-test log; Diesel vehicle opacity meter: raw sampling data of light absorption coefficient, raw records of free acceleration / load deceleration cycle test, and raw data of optical system cleanliness test; Nitrogen oxides analyzer: raw detection frames of NO, NO2, and NOx concentrations; raw data of sampling temperature / pressure; raw signals of high-temperature heating module operating status; Chassis dynamometer: Raw pulse signal of drum speed / torque, interactive frame of loading control command, raw parameters of inertia simulation, raw signal of safety device trigger; Flow meter: raw sampling data of exhaust flow, temperature, and pressure; raw signals for airflow stability monitoring; Speed sensor: Real-time raw pulse data of engine speed, and speed signal stability detection and recording; OBD diagnostic tool: original fault code messages, real-time data stream original frames (including parameters such as engine speed and intake pressure), and diagnostic protocol interaction logs.
[0060] Metadata uniformly includes: unique device identifier, data collection timestamp (millisecond level, unified time zone), detection task number, data verification code, and current device working status, ensuring that each piece of raw data can be accurately traced.
[0061] The distributed storage method for the site server is as follows: Core positioning: Long-term archiving and efficient querying, suitable for centralized management of massive structured data. Storage characteristics are as follows: Architecture combination: HDFS distributed file system + ClickHouse time-series database" collaborative storage, HDFS is responsible for long-term archiving of cold data of more than 1 year, and ClickHouse is responsible for high-frequency querying of hot data of the past year. Sharding strategy: Sharding is performed according to three dimensions: "detection year - detection month - detection line number". The data block size is 128MB. Each data block has 3 redundant replicas distributed on different nodes to ensure that data is not lost when cluster nodes fail. Format adaptation: JSON format encapsulates all structured data; key business data is synchronously generated in a MySQL-compatible format to support SQL queries; historical archived data uses Parquet columnar storage to improve compression rate and batch query efficiency. Lifecycle management: Automatic migration of hot and cold data. Hot data from the past year is stored on high-performance nodes, while cold data older than one year is migrated to low-cost nodes. Data is retained for three years by default, and critical data is permanently archived, in line with environmental regulations.
[0062] As an optional implementation, the application layer also includes a training demonstration module and a system management module.
[0063] The training demonstration module simulates a real vehicle emissions testing environment. It includes a comparative experiment process, mirroring the testing procedure, but does not issue a legally valid report. The primary purpose of this module is to help new employees better master testing techniques and simulate a realistic testing environment. Simulated testing is shown in Table 8.
[0064] Table 8 Simulation Detection
[0065] The system management module is used to configure testing line information and testing equipment information, and to manage users and standard gases. The system management is broken down into separate modules: user management is separated, and equipment testing and equipment parameter management functions are added to the equipment management module. The system management is shown in Table 9.
[0066] Table 9 System Management
[0067] As an optional implementation method, the detection data is collected using a data acquisition security policy, transmitted using a data transmission security policy, stored using a data storage security policy, and used using a data usage and auditing policy.
[0068] 1. Data Acquisition Security Strategy Raw data, including emission concentration, flow rate, speed, and OBD data, must be continuously collected at a fixed frequency. No rounding, filtering, or interpolation is permitted to ensure the authenticity and completeness of the raw data. Each collected data entry must include a unique timestamp, device ID, and testing station ID, and be strictly aligned with the OBD data timeline to ensure data traceability. If any data loss or anomaly occurs during the collection process, the anomaly information must be recorded immediately, and the testing must be stopped. Missing data must not be supplemented or altered.
[0069] 2. Data transmission security strategy Communication between the testing software and provincial / national regulatory platforms and testing equipment uses TLS 1.3 or the national cryptographic standard SM4 for encrypted transmission to prevent data eavesdropping, tampering, and replay attacks. The testing data implements a "real-time upload, instant locking" mechanism, uploading to the regulatory platform 10 minutes after the test is completed. After uploading, modification is prohibited on both the platform and the local end. In the event of network interruption or transmission failure, the data is automatically encrypted and cached locally. The cached data adopts an unwritable mode. After the network is restored, the data is automatically resumed. After the resumed transmission, the data is checked for integrity against the data on the regulatory platform to ensure that no data is lost or tampered with.
[0070] 3. Data storage security strategy Local data is stored in encrypted form, and the storage medium is encrypted, allowing only authorized programs to read it; unauthorized access is prohibited. Test data, operation logs, and equipment calibration records are stored in an "irreversible / incremental log" mode, prohibiting deletion, modification, and overwriting. Hash verification is supported to ensure log integrity. Data storage cycles strictly comply with regulatory requirements; test data and logs are retained for at least 3-6 years, while equipment calibration records and software version records are permanently stored. Critical data is subject to "local + off-site dual backup," with backup data stored in encrypted form. Data recovery is regularly practiced to ensure the backup is effective.
[0071] 4. Data Usage and Auditing Strategies Data access and export require identity authentication and permission approval. Only authorized personnel (auditors, auditors, and supervisors) can access the data. Exported data must be watermarked and logged. Unauthorized export and dissemination are prohibited. A data auditing mechanism should be established to support the retrieval of audit data by time, user, device, and anomaly type. The collection, transmission, auditing, and access records of each piece of data should be traceable. It is prohibited to use the test data for business unrelated to exhaust gas testing. The sale and disclosure of test data are strictly prohibited. Those who violate the regulations will be held accountable.
[0072] As an optional implementation method, this application also sets out a risk warning and emergency response strategy: establish a security risk investigation, early warning and emergency response mechanism to prevent and resolve various security risks in a timely manner, ensure business continuity and reduce risk losses.
[0073] As an optional implementation, this application also includes anti-cheating measures, as shown in Table 10.
[0074] Table 10 Anti-cheating services
[0075] The detection platform described in this application employs an anti-tampering scheme for its core program: the detection software's computational package, core executable program, and configuration files are encrypted to generate a unique hash value (digital fingerprint), which is then registered on the regulatory platform. The registration information includes the software version, hash value, release date, and development organization. Before software startup and detection, the core program's hash value is automatically verified. If it differs from the registered value, operation is immediately terminated, the system is locked, and an alarm message is sent to the regulatory platform and the local administrator, prohibiting unauthorized replacement or downgrading of the software version.
[0076] As can be seen from the above, this application solves the following technical problems: 1. It is designed in full accordance with emission testing standards and has API interfaces and functions that allow management departments to customize regulatory items, as well as official OTA functions.
[0077] 2. It has traceable vehicle parameters, traceable data records, and traceable software versions.
[0078] 3. Fully compatible with mainstream testing equipment brands, providing standardized equipment interface. The workstation software should be compatible with mainstream operating system environments and support extended adaptation to domestic operating systems and hardware environments.
[0079] 4. It has anti-tampering and anti-cheating functions.
[0080] The key points of this application are: 1. Vehicle parameters are traceable to official platforms.
[0081] 2. Open data traceability permissions, and the data cannot be tampered with.
[0082] 3. Fully compatible with all market equipment, not just specific to a few manufacturers.
[0083] 4. Unique software anti-tampering technology.
[0084] Compared with the prior art, the advantages of this application are as follows: 1. This invention features software that is tamper-proof and only supports official OTA functionality.
[0085] 2. Vehicle parameters that affect the vehicle results can only be queried through the official national platform.
[0086] 3. The chassis dynamometer can be directly controlled via software to ensure true load performance, rather than indirectly controlling the dynamometer via a board.
[0087] 4. The software includes access and operation permission auditing and traceability functions, and has been improved in terms of device monitoring, data storage, and software anti-cracking and anti-tampering.
[0088] In one exemplary embodiment, a computer device is provided, which may be a server or a terminal, for running the aforementioned platform for motor vehicle emission testing.
[0089] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0090] This document uses specific examples to illustrate the principles and implementation methods of this application. The descriptions of the above embodiments are only for the purpose of helping to understand the methods and core ideas of this application. Furthermore, those skilled in the art will recognize that, based on the ideas of this application, there will be changes in the specific implementation methods and application scope. Therefore, the content of this specification should not be construed as a limitation of this application.
Claims
1. A platform for testing motor vehicle emissions, characterized in that, include: Device access layer, data layer, and application layer; The equipment access layer is used to provide interfaces for all motor vehicle environmental testing equipment; The data layer is used to acquire the test data of motor vehicle environmental protection testing equipment through the device access layer using encrypted transmission. The application layer is used to obtain basic information about the vehicles to be inspected from the server, as well as the applicable testing methods and emission limit standards for the vehicles to be inspected; display the testing task list for the vehicles to be inspected; the testing task list includes the basic information of the vehicles to be inspected and the task status of each testing task; before the testing begins, the status and environmental conditions of the motor vehicle environmental protection testing equipment are verified through the device access layer, and testing is allowed to begin when the status and environmental conditions of the motor vehicle environmental protection testing equipment meet the pre-inspection conditions; after the testing begins, the testing tasks and applicable testing methods are displayed sequentially according to the execution order of the motor vehicle environmental protection testing process, and the testing data of the current testing task is obtained through the device access layer and the data layer. The next testing task can only be displayed after one testing task is completed, until the task status of all testing tasks in the testing task list is "test completed"; the testing results of the vehicles to be inspected are automatically determined based on the testing data and emission limit standards, and uploaded to the regulatory platform using encrypted transmission.
2. The vehicle emission testing platform according to claim 1, characterized in that, Also includes: Support layer; The support layer includes: identity authentication service module, log service module, permission / security management service module, data communication service module, and device communication service module.
3. The vehicle emission testing platform according to claim 1, characterized in that, The application layer includes: a self-test module, an equipment calibration module, an emission detection module, a data management module, and a user management module; The self-test module is used to send self-test commands to the vehicle environmental protection testing equipment through the device access layer; The equipment calibration module is used to send calibration commands to the vehicle environmental protection testing equipment through the equipment access layer; The emissions testing module is used to display the testing task list of the vehicle to be tested; the testing task list includes the basic information of the vehicle to be tested and the task status of each testing task; after the testing starts, the testing tasks and applicable testing methods are displayed in sequence according to the execution order of the motor vehicle environmental protection testing process, and the next testing task can only be displayed after one testing task is completed; The data management module is used for querying test data, self-test data, calibration data, termination / suspension / interruption data, maintenance records, and vehicle model database data. The user management module is used to manage and set permissions for different roles.
4. The vehicle emission testing platform according to claim 3, characterized in that, The application layer also includes: a log storage module; The log storage module is used to build a layered storage system of edge local caching and cloud distributed archiving; the layered storage system adopts a three-layer architecture of edge layer - transport layer - core layer to realize layered storage and collaborative flow of data; The edge layer is used to directly interface with various motor vehicle environmental protection testing equipment to perform real-time data acquisition, encrypted caching, and preliminary preprocessing of testing data. The transport layer employs encrypted transmission and breakpoint resume mechanisms, and uses industrial-grade network links for data interaction between the edge layer and the core layer. The core layer is used to receive detection data and perform structured transformation, and archives, stores and retrieves data through a distributed architecture.
5. The vehicle emission testing platform according to claim 4, characterized in that, The storage medium for the edge layer is an industrial-grade SSD storage disk, with a single disk capacity of 1TB or greater. The data storage format for the edge layer is a combination of binary raw frames and JSON metadata; The data management approach at the edge layer is a dual strategy of cyclic overwrite and data backup; The core layer uses a collaborative storage method between the HDFS distributed file system and the ClickHouse time-series database.
6. The vehicle emission testing platform according to claim 3, characterized in that, The application layer also includes: a training demonstration module and a system management module; The training demonstration module is used to simulate a real vehicle emissions testing environment; The system management module is used to configure testing line information and testing equipment information, and to manage users and standard gas.
7. The vehicle emission testing platform according to claim 1, characterized in that, The basic information of the vehicle to be inspected includes: license plate number, vehicle identification number, vehicle type, fuel type, registration date, and baseline weight; The task status of the detection task includes: pending detection, detection in progress, detection completed, and detection interrupted.
8. The vehicle emission testing platform according to claim 1, characterized in that, The test data is collected using a data collection security strategy. The data collection security strategy refers to continuously collecting test data at a fixed frequency, adding a unique timestamp, device ID, and test station ID to the collected test data, and immediately recording the abnormal information and stopping the test if data is missing or abnormal during the collection process. Missing data must not be supplemented or tampered with. The detection data is transmitted using a data transmission security policy; The data transmission security strategy refers to the use of encrypted transmission of detection data, and the adoption of real-time upload and instant locking mechanisms. In the event of network interruption or transmission failure, the detection data is automatically encrypted and cached locally. The cached data adopts an unwritable mode. After the network is restored, the data is automatically resumed and then the data integrity is verified with the monitoring platform. The test data is stored using a data storage security policy; the data storage security policy means that local data is stored in encryption, and local data can only be read by authorized programs, and unauthorized access is prohibited; test data, operation logs, and equipment calibration records are stored in a non-erasable / incremental log mode, which prohibits deletion, modification and overwriting, and supports hash verification; Test data and logs shall be kept for at least a preset number of years, and equipment calibration records and software version records shall be kept permanently; data shall be backed up both locally and off-site, backup data shall be stored in encrypted form, and data recovery shall be practiced regularly. The detection data is used in accordance with the data usage and auditing strategy. The data usage and auditing strategy refers to the identification authentication and permission approval when viewing and exporting data, so that only authorized personnel can view or export the detection data, and watermarks and log records are added when exporting data. It supports the retrieval of audit data by time, user, device and anomaly type, and the tracing of the collection, transmission, review and viewing records of each piece of data.
9. The vehicle emission testing platform according to claim 1, characterized in that, The application layer is also used for: Record the start and end times of each step of the inspection, and calculate the time taken for each step and the total inspection time; When a detection interruption occurs, record the time, stage, and reason for the interruption, save the completed data, and upload the interruption record to the server for archiving.
10. A computer device, characterized in that, The computer equipment is used to run the motor vehicle emission testing platform as described in any one of claims 1-9.