Adaptive compatible protocol and gateway system of multi-source heterogeneous parking system

Abstract

The invention provides a self-adaptive compatible protocol of a multi-source heterogeneous parking system and a gateway system, and belongs to the technical field of Internet of Things communication. According to the scheme, manufacturer equipment protocols such as Bosch, Gifcian and Haikang are identified through a protocol fingerprint feature library, heterogeneous data are converted into a unified JSON Schema format by utilizing a self-adaptive field mapping rule, and a multi-source heterogeneous parking system is obtained. Seamless access of multi-source equipment data is realized by combining fault-tolerant mechanisms such as off-network storage and rule hot update, the system adopts a three-layer protocol conversion architecture, the protocol identification accuracy is greater than or equal to 99.2%, the new system access time is shortened to 2 hours from 15 people days, the integration cost is reduced by 92%, the problems of protocol fragmentation, data splitting and high docking cost in the prior art can be solved, and the system has a wide application prospect. And access to an intelligent wheel parking platform is supported, and zero loss of data conversion is ensured.

Description

Technical Field

[0001] The present invention belongs to the technical field of Internet of Things communication, and particularly relates to an adaptive compatibility protocol and gateway system for a multi-source heterogeneous parking system. Background Art

[0002] Currently, the multi-source heterogeneous parking system field faces significant technical barriers: Firstly, mainstream parking lot equipment manufacturers (such as Bosch, Jieshun, Hikvision, etc.) generally adopt private communication protocols, and the protocol field difference rate is as high as 78%, forming a serious "protocol fragmentation" phenomenon, resulting in difficult data interaction between devices of different manufacturers. Secondly, there is no unified standard for data formats. Taking license plate recognition data as an example, the Bosch system uses the format {"plate": "粤B12345", "time": "2025-06-20 14:30:22"}, while the Jieshun system uses {"license_plate": "粤B12345", "cap_time": "2025 / 06 / 20 14.30.22"}. This "data fragmentation" problem makes cross-system data integration extremely complex. Thirdly, traditional docking methods need to be customized and developed for each manufacturer. The adaptation of a single system requires 15 person-days, and the integration cost of the TOP10 manufacturers exceeds 3 million yuan, presenting the industry pain point of "high docking cost".

[0003] To break through the above technical bottlenecks, the present invention proposes an adaptive compatibility protocol and gateway system for a multi-source heterogeneous parking system. By constructing a three-layer protocol conversion architecture, designing an adaptive field mapping algorithm and a fault-tolerant communication mechanism, it realizes the automatic recognition and conversion of protocols of devices from different manufacturers, unifies heterogeneous data into the standard JSON Schema format. This solution can seamlessly access devices of TOP10 manufacturers, with a protocol recognition accuracy rate ≥ 99.2%. The access time of the new system is shortened from 15 person-days to 2 hours, significantly reducing the integration cost by 92%. At the same time, through mechanisms such as edge storage and rule hot update, it ensures zero loss of data conversion, effectively solving the problems of protocol fragmentation, data fragmentation and high docking cost in the existing technology. Summary of the Invention

[0004] The purpose of the present invention is to provide an adaptive compatibility protocol and gateway system for a multi-source heterogeneous parking system, aiming to solve the problems of protocol fragmentation, non-uniform data format (data fragmentation) and high system docking cost caused by private protocols of parking devices of different manufacturers in the existing technology.

[0005] To achieve the above purpose, the present invention provides the following technical solutions:

[0006] An adaptive compatibility method for a multi-source heterogeneous parking system, characterized by comprising: identifying the device manufacturer type through a protocol fingerprint feature library; loading corresponding field mapping rules according to the manufacturer type; and converting heterogeneous data into a unified JSON Schema standard format.

[0007] As a preferred solution of the present invention, the protocol fingerprint feature library includes: - Bosch BIS protocol identification field `parking_status`; - Jieshun JOS protocol identification field `jos_version`; - Hikvision protocol identification field `hik_car_info`.

[0008] As a preferred solution of the present invention, the protocol fingerprint feature library includes:

[0009] - Bosch BIS protocol identification field `parking_status`;

[0010] - The Jieshun JOS protocol identification field `jos_version`; - The Hikvision protocol identification field `hik_car_info`.

[0011] As a preferred solution of the present invention, the fault tolerance mechanism includes:

[0012] - Local storage of ≥72 hours of data when disconnected from the Internet;

[0013] -Dynamic hot update rule base when protocol changes;

[0014] - AI semantic completion is enabled for exception fields. - Multi-protocol communication interface (RS485 / TCP / IP / 4G);

[0015] -Edge computing module (including rule engine);

[0016] - Self-healing storage unit (prevents data loss).

[0017] Compared with the prior art, the present invention has the following beneficial effects:

[0018] 1. This solution achieves automatic recognition and conversion of protocols between devices from different manufacturers by building a three-layer protocol conversion architecture and designing an adaptive field mapping algorithm. The protocol recognition accuracy rate is as high as ≥99.2%. This enables devices from different manufacturers to exchange data and communicate within the same parking system, breaking down the barriers brought about by protocol fragmentation and improving the efficiency of collaborative work between devices.

[0019] The protocol-aware gateway within the three-layer protocol conversion architecture receives data from devices in real time. The protocol type identification engine analyzes this data using a protocol fingerprint library to quickly identify the device's vendor type. Based on the identification results, the corresponding protocol parser is loaded to convert the device's native protocol data into a unified data model, which is ultimately uploaded to the cloud platform via the Zhilunbo cloud API. An adaptive field mapping algorithm converts heterogeneous data into a unified format based on the field mapping rules of different vendors, ensuring data consistency and compatibility across different systems.

[0020] 2. This solution converts heterogeneous data into a standard JSON Schema format, effectively resolving data fragmentation and ensuring smooth cross-system data integration. Whether it's license plate recognition data, time data, or other types of data, they can all be stored and transmitted according to a unified standard, improving data availability and manageability.

[0021] During the protocol conversion process, field mapping rules are used to convert fields from different manufacturers into a unified field name and format. For example, the "plate" field of the Bosch system and the "license_plate" field of the Jieshun system are converted into the standard "license_plate" field. Different time formats are uniformly converted into the international standard time format "YYYY-MM-DDTHH:MM:SSZ". At the same time, the converted data is strictly verified through a data verification mechanism to ensure data integrity and accuracy. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings are used to provide a further understanding of the present invention and constitute a part of the specification. Together with the embodiments of the present invention, they are used to explain the present invention and do not constitute a limitation of the present invention. In the accompanying drawings:

[0023] Figure 1 A flow chart of the three-layer protocol conversion architecture of the present invention;

[0024] Figure 2 It is a flow chart of the protocol conversion process of the present invention;

[0025] Figure 3 This is a flowchart of the fault tolerance mechanism processing of the present invention. DETAILED DESCRIPTION

[0026] The following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of the present invention.

[0027] Example 1

[0028] See also Figure 1-Figure 3 , the present invention provides the following technical solutions:

[0029] An adaptive compatibility method for a multi-source heterogeneous parking system, characterized by comprising: - identifying the device manufacturer type through a protocol fingerprint feature library;

[0030] -Load corresponding field mapping rules according to manufacturer type; -Convert heterogeneous data into a unified JSON Schema standard format.

[0031] In a specific embodiment of the present invention, 1. Feature library construction logic: The feature library is like a "device ID database" that stores the "unique identification" of each manufacturer's device: the feature of Bosch devices contains a "parking_status" field;

[0032] The characteristic of Jieshun devices is that they contain the "jos_version" (protocol version number) field;

[0033] Hikvision devices are characterized by the inclusion of a "hik_car_info" (vehicle information) field.

[0034] Storage method: The signature database is stored in the gateway device in a standardized format and supports remote updates, similar to mobile phone system upgrades.

[0035] 2. Protocol identification process: When the gateway receives device data, it acts like a detective to check whether the data contains the identification fields in the feature library: it extracts all fields in the data (such as "parking_status" and "device_id");

[0036] Compare the "ID field" of each manufacturer in the feature library. If a matching field is found (such as Bosch's "parking_status"), the device manufacturer is determined;

[0037] If multiple manufacturers are matched at the same time (in extremely special cases), the final decision will be made based on the preset priority (e.g. Bosch takes precedence over Jieshun).

[0038] For details, please refer to Figure 1-Figure 3 , the protocol fingerprint feature library contains:

[0039] - Bosch BIS protocol identification field `parking_status`;

[0040] - The Jieshun JOS protocol identification field `jos_version`; - The Hikvision protocol identification field `hik_car_info`.

[0041] In this embodiment: 1. The "translation manual" mechanism of the mapping rule: Each manufacturer corresponds to a "translation manual" that records the conversion rules from the original fields to the standard fields:

[0042] The field name "license_plate" (license plate number) of Jieshun is the same as that of the standard model and can be directly used;

[0043] The "cap_time" (capture time) of Jieshun needs to be translated into the standard "capture_time";

[0044] The time format such as "2025 / 06 / 20 14.30.22" needs to be converted into the standard format of "2025-06-20T14:30:22Z" according to the rules.

[0045] Rule update: When the manufacturer's agreement changes, the gateway can download the new "translation manual" in real time and take effect without restarting.

[0046] 2. Specific execution of field conversion: Taking time conversion as an example, the process is similar to "language translation":

[0047] Find the corresponding time format rule according to the manufacturer type (such as the "year-month-day hour-minute-second" format of Jieshun);

[0048] Translate the original time string into a unified standard time format according to the rules to ensure that the time data formats of all manufacturers are consistent.

[0049] For details, please refer to Figure 1-Figure 3 , and the fault tolerance mechanism includes:

[0050] - Store data locally for ≥72 hours when the network is disconnected;

[0051] - Dynamically update the rule library when the protocol changes;

[0052] - Enable AI semantic completion for abnormal fields.

[0053] In this embodiment: 1. Definition of the standard data "template": Develop a unified JSON data template that specifies the mandatory fields (such as license plate number, capture time, manufacturer type) and optional fields (such as vehicle color, parking status):

[0054] The license plate number should conform to the domestic license plate format (such as "粤B12345");

[0055] The time should be unified into the international standard format (such as "2025-06-20T14:30:22Z");

[0056] The parking status is represented by text ("entry" "exit") instead of numbers (1 / 0).

[0057] 2. Data verification and conversion: The gateway compares the converted data with the standard template:

[0058] If a field is missing (e.g. a manufacturer did not transmit the vehicle color), fill it with a default value or mark it as "unknown";

[0059] If the format is incorrect (such as a garbled time string), record the error and try to fix it locally to ensure that the data uploaded to the cloud fully meets the template requirements.

[0060] For details, please refer to Figure 2 ,-Multi-protocol communication interface (RS485 / TCP / IP / 4G);

[0061] -Edge computing module (including rule engine);

[0062] - Self-healing storage unit (prevents data loss).

[0063] In this embodiment: 1. Off-network data "safe": The gateway has a built-in large-capacity storage module, which automatically turns on the "safe" mode when the network is disconnected:

[0064] Continuously store device data for at least 72 hours, similar to how mobile phone albums automatically save photos;

[0065] After the network is restored, data will be "resumed" in chronological order to ensure that no record is lost.

[0066] 2. Dynamic "self-learning" of the protocol: When the vendor protocol changes suddenly (such as adding a new field):

[0067] The gateway first tries to use "fuzzy matching" to guess the meaning of the newly added field (for example, "car_color" may mean "vehicle color");

[0068] Automatically generate temporary conversion rules and request the cloud to update the formal rules;

[0069] New rules take effect immediately after downloading, without the need for manual code modification.

[0070] 3. "Smart completion" of abnormal fields: When encountering unrecognized fields, the gateway understands their meaning through "semantic analysis":

[0071] For example, the field "car_color" is not defined in the rule base, but is found to be highly correlated with "vehicle color" through semantic analysis;

[0072] Automatically map it to the standard field "vehicle_color" and record the rule for subsequent use.

[0073] 5. Gateway device hardware and interface implementation coordination:

[0074] 1. Multi-protocol "translator" interface: The gateway is equipped with multiple communication interfaces, like a "multi-language translator":

[0075] RS485 interface: connect to Bosch devices and support industrial-grade serial communication;

[0076] TCP / IP network port: connect to Jieshun equipment and transmit data through the network;

[0077] 4G module: When the wired network is interrupted, it automatically switches to the 4G network to transmit data.

[0078] 2. Edge computing "brain": The gateway has a built-in rules engine, which processes data in real time like an "intelligent brain":

[0079] After receiving device data, immediately call the feature library to identify the manufacturer;

[0080] Convert the field format according to the "Translation Manual";

[0081] Verify the legitimacy of data to ensure compliance with unified standards.

[0082] Finally, it should be noted that the above descriptions are merely preferred embodiments of the present invention and are not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art will be able to modify the technical solutions described in the aforementioned embodiments or substitute equivalents for some of the technical features. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention shall be included within the scope of protection of the present invention.

Claims

1. An adaptive compatibility method for multi-source heterogeneous parking systems, characterized in that include: -Identify device vendor types through protocol fingerprint feature library; -Load corresponding field mapping rules according to manufacturer type; -Convert heterogeneous data into a unified JSON Schema standard format.

2. The method according to claim 1, wherein: The protocol fingerprint feature library contains: - Bosch BIS protocol identification field `parking_status`; - The Jieshun JOS protocol identification field `jos_version`; - The Hikvision protocol identification field `hik_car_info`.

3. The method according to claim 1, wherein: Fault tolerance mechanisms include: - Local storage of ≥72 hours of data when disconnected from the Internet; -Dynamic hot update rule base when protocol changes; - Enable AI semantic completion for exception fields.

4. An adaptive compatible gateway device, characterized in that include: -Multi-protocol communication interface (RS485 / TCP / IP / 4G); -Edge computing module (including rule engine); - Self-healing storage unit (prevents data loss).

Images