Alarm event execution method and device, storage medium and electronic device

Abstract

This application discloses a method and apparatus for executing alarm events, a storage medium, and an electronic device. The method includes: determining whether a target vehicle model matching vehicle data exists by using a pre-configured first feature code, wherein the first feature code includes a feature code uniquely configured for each of multiple vehicle models, and the vehicle data includes at least a second feature code of the vehicle; and, if no target vehicle model matching the vehicle data exists, executing an alarm event using the second feature code. This solves the problem in related technologies where vehicle manufacturers' vehicle data platforms lack an effective alarm mechanism, making it impossible to promptly detect and notify relevant personnel to handle vehicle data discarded due to the lack of feature codes configured on the vehicle manufacturer's vehicle data platform.

Description

Technical Field

[0001] This application relates to the field of information technology and data processing technology in the automotive manufacturing industry. Specifically, it relates to a method and apparatus for executing alarm events, a storage medium, and an electronic device. Background Technology

[0002] Currently, with the rapid development of the automotive manufacturing industry, vehicle data processing and flow have become an important part of enterprise information management. In the traditional process, the MES system on the automotive production line is responsible for collecting raw data during the production process, cleaning it through a data warehouse, and then entering it into the vehicle data platform. In this process, the configuration and matching of vehicle model feature codes is a critical step, as it determines whether the data can be correctly classified and applied.

[0003] However, the configuration and matching of vehicle model feature codes in related technologies face the following problems in practical applications: Existing systems (i.e., vehicle manufacturer data platforms) lack dynamic feature code configuration capabilities and cannot adapt to changes in vehicle models in real time, resulting in lagging feature code configuration. If a new vehicle model's feature code is omitted from the vehicle manufacturer's data platform, the vehicle will be incorrectly processed or discarded during data transfer because it cannot match the feature code on the platform, severely affecting the integrity and accuracy of the data. Existing systems also lack effective alarm mechanisms, failing to promptly detect and notify relevant personnel to address data loss issues caused by omitted feature code configurations on the vehicle manufacturer's data platform.

[0004] Regarding the issue that automakers' vehicle data platforms lack effective alarm mechanisms, making it impossible to promptly detect and notify relevant personnel to handle vehicle data that is discarded due to the lack of configured feature codes on the automakers' vehicle data platforms, no effective solution has yet been proposed.

[0005] Therefore, it is necessary to improve the relevant technology to overcome the aforementioned defects. Summary of the Invention

[0006] This application provides an alarm event execution method and apparatus, storage medium and electronic device to at least solve the problem that vehicle data platforms of car manufacturers lack an effective alarm mechanism, making it impossible to promptly detect and notify relevant personnel to handle vehicle data that is discarded due to the lack of a feature code configured on the vehicle data platform.

[0007] According to one aspect of the embodiments of this application, a method for executing an alarm event is provided, comprising: determining whether there is a target vehicle model matching vehicle data by using a pre-configured first feature code, wherein the first feature code includes a feature code uniquely configured for each of a variety of vehicle models, and the vehicle data includes at least a second feature code of the vehicle; and executing an alarm event by using the second feature code if no target vehicle model matching the vehicle data exists.

[0008] In an exemplary embodiment, determining whether a target vehicle model matching the vehicle data exists using a pre-configured first feature code includes: locating a first field of the vehicle data, wherein the first field is the corresponding field of the second feature code in the vehicle data; comparing the first field with the first feature code to obtain a comparison result; if the comparison result indicates that the first field matches any feature code in the first feature code, determining that a target vehicle model matching the vehicle data exists; if the comparison result indicates that the first field does not match any feature code in the first feature code, determining that no target vehicle model matching the vehicle data exists.

[0009] In an exemplary embodiment, comparing the first field with the first feature code to obtain a comparison result includes: splitting the first field to obtain M groups of second fields, wherein each group of second fields includes: a first feature code family and a first feature code character corresponding to the first feature code family, where M is a positive integer; and splitting any of the feature codes to obtain N groups of third fields, wherein each group of third fields includes: a second feature code family and a second feature code character corresponding to the second feature code family, where N is a positive integer and N is less than or equal to M; matching the M groups of second fields and the N groups of third fields; if there is an N group of second fields in the M groups of second fields that is completely consistent with the N groups of third fields, determining that the comparison result is that the first field is consistent with any feature code in the first feature code; if there is no N group of second fields in the M groups of second fields that is completely consistent with the N groups of third fields, determining that the comparison result is that the first field is inconsistent with all feature codes in the first feature code.

[0010] In an exemplary embodiment, executing an alarm event using the second feature code includes: determining whether the second feature code matches a third feature code, wherein the third feature code is a universal feature code pre-configured for a general vehicle model, the general vehicle model including: vehicle models other than the multiple vehicle models that are not uniquely configured with feature codes, the multiple vehicle models including the target vehicle model; if the second feature code matches the third feature code, marking the vehicle data as alarm data, and executing the alarm event according to preset rules.

[0011] In an exemplary embodiment, after determining whether the second feature code matches the third feature code, the method further includes: if the second feature code does not match the third feature code, marking the vehicle data as useless data; and isolating and storing the useless data.

[0012] In an exemplary embodiment, executing the alarm event according to a preset rule includes: determining the number of tags that the received vehicle data is marked as alarm data; and executing the alarm event to the target object when the number of tags meets a critical number indicated by the preset rule.

[0013] In an exemplary embodiment, after determining whether there is a target model that matches the vehicle data by using a pre-configured first feature code, the method further includes: if there is a target model that matches the vehicle data, using the target model as the storage type of the vehicle data; and storing the vehicle data using the storage type.

[0014] According to another aspect of the embodiments of this application, an alarm event execution device is provided, comprising: a determination module, configured to determine whether there is a target model that matches vehicle data by means of a pre-configured first feature code, wherein the first feature code includes a feature code uniquely configured for each of a variety of models, and the vehicle data includes at least: a second feature code of the vehicle; and an alarm module, configured to execute an alarm event by means of the second feature code if there is no target model that matches the vehicle data.

[0015] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, and the computer program is configured to execute the above-mentioned alarm event execution method when running.

[0016] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the execution method of the alarm event through the computer program.

[0017] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program, wherein when the computer program is executed by a processor, a method for executing the aforementioned alarm event is provided.

[0018] This application utilizes a pre-configured first feature code to determine whether a target vehicle model matches the vehicle data. The first feature code includes a unique feature code configured for each of multiple vehicle models. The vehicle data includes at least a second feature code. If no target vehicle model matches the vehicle data, an alarm event is triggered using the second feature code. In other words, by performing a matching process between the vehicle data and the target vehicle model, and then determining that no matching target vehicle model exists, an alarm event can be triggered using the second feature code in the vehicle data. Therefore, this technical solution addresses the problem in related technologies where vehicle manufacturers' vehicle data platforms lack an effective alarm mechanism, failing to promptly detect and notify relevant personnel to handle vehicle data discarded due to the lack of a configured feature code (i.e., the first feature code) on the vehicle manufacturer's vehicle data platform, thus achieving the technical effect of timely alarms. Attached Figure Description

[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0021] Figure 1 This is a hardware structure block diagram of a vehicle for an alarm event execution method according to an embodiment of this application;

[0022] Figure 2 This is a flowchart of an alarm event execution method according to an embodiment of this application;

[0023] Figure 3 This is a schematic diagram of the alarm process according to an embodiment of this application;

[0024] Figure 4 This is a schematic diagram illustrating the feature code definition according to an embodiment of this application;

[0025] Figure 5 This is a structural block diagram of an alarm event execution device according to an embodiment of this application. Detailed Implementation

[0026] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0028] The methods and embodiments provided in this application can be executed in a vehicle, computer terminal, or similar computing device. Taking operation in a vehicle as an example, Figure 1 This is a hardware structure block diagram of a vehicle for an alarm event execution method according to an embodiment of this application. For example... Figure 1 As shown, a vehicle may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor (MCU) or a field-programmable gate array (FPGA)) and a memory 104 for storing data are also shown. The vehicle may further include a transmission device 106 for communication functions and an input / output device 108. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the vehicle described above. For example, the vehicle may also include components that are larger than... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0029] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the alarm event execution method in this embodiment. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thus implementing the above-described method. The memory 104 may include high-speed random access memory and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the vehicle via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0030] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the vehicle's communication provider. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module used for wireless communication with the Internet.

[0031] This embodiment provides a method for executing alarm events, which is applied to the aforementioned vehicle or to a vehicle data platform of an automaker associated with the aforementioned vehicle. Figure 2 This is a flowchart of an alarm event execution method according to an embodiment of this application, such as... Figure 2 As shown, the process includes the following steps S202-S204:

[0032] Step S202: Determine whether there is a target vehicle model that matches the vehicle data by using a pre-configured first feature code, wherein the first feature code includes a feature code uniquely configured for each of the multiple vehicle models, and the vehicle data includes at least: the second feature code of the vehicle;

[0033] Step S204: If no target vehicle model matches the vehicle data, an alarm event is executed using the second feature code.

[0034] Through the above steps, a pre-configured first feature code is used to determine whether a target vehicle model matching the vehicle data exists. The first feature code includes a unique feature code configured for each of multiple vehicle models. The vehicle data includes at least a second feature code for the vehicle. If no target vehicle model matching the vehicle data exists, an alarm event is executed using the second feature code. In other words, by performing a matching process between the vehicle data and the target vehicle model, and then determining that no matching target vehicle model exists, an alarm event can be executed using the second feature code in the vehicle data. Therefore, this technical solution solves the problem in related technologies where automakers' vehicle data platforms lack an effective alarm mechanism, making it impossible to promptly detect and notify relevant personnel to handle vehicle data discarded due to the lack of configured feature codes on the automaker's vehicle data platform, thus achieving the technical effect of timely alarms.

[0035] In an exemplary embodiment, determining whether a target vehicle model matching the vehicle data exists using a pre-configured first feature code includes: locating a first field of the vehicle data, wherein the first field is the corresponding field of the second feature code in the vehicle data; comparing the first field with the first feature code to obtain a comparison result; if the comparison result indicates that the first field matches any feature code in the first feature code, determining that a target vehicle model matching the vehicle data exists; if the comparison result indicates that the first field does not match any feature code in the first feature code, determining that no target vehicle model matching the vehicle data exists.

[0036] In this embodiment, the first feature code refers to a specific feature code configured for each vehicle model. These feature codes are defined based on different vehicle attributes, such as vehicle model, configuration, and production year. The first feature code is used to accurately match vehicle data to a specific vehicle model. The second feature code actually refers to the feature information contained in the vehicle data, stored in specific fields of the vehicle data, and is used for comparison with the first feature code.

[0037] Further, the first field is compared with the first feature code to obtain a comparison result, including: splitting the first field to obtain M groups of second fields, wherein each group of second fields includes: a first feature code family and a first feature code character corresponding to the first feature code family, where M is a positive integer; and splitting any of the feature codes to obtain N groups of third fields, wherein each group of third fields includes: a second feature code family and a second feature code character corresponding to the second feature code family, where N is a positive integer and N is less than or equal to M; matching the M groups of second fields and the N groups of third fields; if there is an N group of second fields in the M groups of second fields that is completely consistent with the N groups of third fields, the comparison result is determined to be that the first field is consistent with any feature code in the first feature code; if there is no N group of second fields in the M groups of second fields that is completely consistent with the N groups of third fields, the comparison result is determined to be that the first field is inconsistent with all feature codes in the first feature code.

[0038] It is understandable that a feature code includes a feature code family and the corresponding feature code characters within that family. In one case, such as... Figure 3 As shown, feature code families include "a", "b", etc., and feature code characters include "Fa01", "Fa02", etc. Feature code characters essentially include the symbols corresponding to the feature code families, and can be directly used as feature codes. In another case, such as... Figure 4 As shown, the feature code families include, for example, “Fa”, “Fb”, etc., and the feature code characters include, for example, “01”, “02”, etc. The feature code families and feature code characters are combined to form the feature codes “Fa01”, “Fa02”, etc. It should be noted that the above feature codes are only examples and are not intended to limit the scheme of this application.

[0039] In this embodiment of the application, the first field in the vehicle data can be located using a family of feature codes, for example, such as Figure 3 As shown, for vehicle data 1, the second field in group M within the first field can be located using feature codes a, b, c, and d. Optionally, if the feature codes are based on vehicle configuration definitions, the system will search for the "configuration" field in the data.

[0040] Furthermore, after splitting any feature code to obtain N groups of third fields, the M groups of second fields are matched with the N groups of third fields: First, feature code families are matched. If it is determined that the M first feature code families include N second feature code families, then the N first feature code characters are compared one-to-one with the N second feature code characters. If the N first feature code characters and the N second feature code characters are completely identical, then the comparison result can be determined as the first field, that is, the second feature code matches any of the feature codes. Therefore, the vehicle belongs to the target vehicle model corresponding to any of the feature codes.

[0041] Conversely, if either condition 1 or condition 2 is met, it can be determined that the vehicle does not belong to any of the various vehicle models that have been configured with feature codes. Condition 1: The M first feature code families do not include any of the N second feature code families; Condition 2: The M first feature code families include N second feature code families, but the N first feature code characters and the N second feature code characters are not completely identical.

[0042] For example, such as Figure 3 As shown, the second feature code families of vehicle models A and B are both "b" and "d", while the first feature code families of vehicle identification numbers 001, 002, 003, and 004 all include "a", "b", "c", and "d". Then, we continue to perform a one-to-one comparison between N first feature code characters and N second feature code characters, and the comparison result is: the vehicle with vehicle identification number 001 belongs to vehicle model A, and the vehicle with vehicle identification number 002 belongs to vehicle model B.

[0043] In an exemplary embodiment, executing an alarm event using the second feature code includes: determining whether the second feature code matches a third feature code, wherein the third feature code is a universal feature code pre-configured for a general vehicle model, the general vehicle model including: vehicle models other than the multiple vehicle models that are not uniquely configured with feature codes, the multiple vehicle models including the target vehicle model; if the second feature code matches the third feature code, marking the vehicle data as alarm data, and executing the alarm event according to preset rules.

[0044] Understandably, if it is determined that the second feature code does not match any of the first feature codes, it is necessary to determine whether the second feature code matches the third feature code, that is, to determine whether the vehicle with the second feature code is a vehicle that was missed and was not configured with the feature code corresponding to its vehicle model. For example, such as Figure 3 As shown, the general feature codes are Fa01 and Fc01, then based on Figure 3 According to the data cleanup table in the data warehouse, the second and third feature codes of vehicle VIN 004 match. The vehicle data of vehicle VIN 004 should be marked as alarm data and wait for the alarm event to be executed.

[0045] Furthermore, after determining whether the second feature code matches the third feature code, the method further includes: if the second feature code does not match the third feature code, marking the vehicle data as useless data; and isolating and storing the useless data.

[0046] Optional, such as Figure 3As shown, if the second and third feature codes of vehicle with chassis number 003 do not match, then the vehicle data of vehicle with chassis number 003 should be marked as useless data and wait to be discarded or isolated for storage.

[0047] In some optional embodiments, the alarm event is executed according to a preset rule, including: determining the number of tags that the received vehicle data is marked as alarm data; and executing the alarm event to the target object when the number of tags meets a critical number indicated by the preset rule.

[0048] It is understood that different preset rules can be pre-configured to execute alarm events. For example, it can be set to execute an alarm event to the target object every time a vehicle data is marked as alarm data; in this case, the marking count is 1. For example, multiple alarms can be set, with the marking count set to W, where W is a positive integer not equal to 1. When the number of multiple vehicle data marked as alarm data reaches W, an alarm event is executed to the target object. It should be noted that the preset rules are not limited to rules indicating the number of alarms; they can also be set to trigger alarms to different target objects when the cumulative marking count reaches different levels, etc. This application embodiment does not limit this.

[0049] In an exemplary embodiment, after determining whether a target vehicle model matching the vehicle data exists using a pre-configured first feature code, the method further includes: if a target vehicle model matching the vehicle data exists, using the target vehicle model as the storage type of the vehicle data; and storing the vehicle data using the storage type. That is, after determining the target vehicle model, it can be used as the storage type to store the vehicle data. Optionally, the feature code of the target vehicle model can be used as a storage symbol.

[0050] Obviously, the embodiments described above are only some embodiments of this application, and not all embodiments. To better understand the above method, the following description, in conjunction with embodiments, illustrates the process, but is not intended to limit the technical solutions of the embodiments of this application. Specifically:

[0051] In related technologies, there is a problem that car manufacturers' vehicle data platforms lack effective alarm mechanisms, making it impossible to promptly detect and notify relevant personnel to handle vehicle data that is discarded because it has not been configured with feature codes on the car manufacturers' vehicle data platforms.

[0052] To address the above problems, the embodiments of this application propose the following technical solutions:

[0053] 1) Vehicle model feature code configuration.

[0054] The vehicle data platform of the automaker supports configuring corresponding feature codes (equivalent to the first feature code in the above embodiment) according to different vehicle models. These feature codes are an important basis for vehicle data matching and verification. The system provides a user-friendly interface, allowing administrators to easily configure and update vehicle model feature codes, ensuring rapid adaptation when new models are launched.

[0055] 2) Automatic matching mechanism.

[0056] Once the vehicle manufacturer's vehicle data platform receives the cleaned data (i.e., vehicle data) from the data warehouse, the system automatically matches the vehicle data to the corresponding vehicle model item (equivalent to the target vehicle model in the above embodiment) based on pre-configured feature codes. This process is implemented through efficient algorithms, enabling fast and accurate data matching and improving data processing efficiency.

[0057] 3) Handling missing feature codes.

[0058] To address the issue of missing vehicle model feature codes, this application embodiment introduces a missing feature code alarm function. The system uses globally comprehensive feature codes (equivalent to the third feature code in the above embodiment) as the judgment criterion, periodically or in real-time checking the integrity of the feature code database. Once a missing feature code is detected, the system immediately triggers an alarm mechanism, notifying relevant personnel (equivalent to the target object) via email, SMS, or system messages, prompting them to conduct manual review and processing (i.e., executing the alarm event).

[0059] 4) Alarm function design.

[0060] Alarm triggering conditions: Set reasonable alarm triggering conditions, such as no feature code being configured within a certain period after a new model is launched, or omissions after the feature code library is updated.

[0061] Alarm notification methods: Provides multiple alarm notification methods to ensure that relevant personnel can receive alarm information in a timely manner.

[0062] Alarm handling process: The alarm handling process is clearly defined, including steps such as alarm confirmation, signature code configuration, and data re-matching, to ensure that problems are resolved in a timely manner.

[0063] More specifically, the embodiments of this application implement the above technical solution through the following steps:

[0064] Step 1: Design the data flow process.

[0065] 1) Data collection: The MES (Manufacturing Execution System) of the car manufacturer's production line serves as the data source, pushing raw data, including basic vehicle information and production status, to the data warehouse in real time or periodically.

[0066] 2) Data cleaning: After receiving data, the data warehouse performs data cleaning steps, including deduplication, formatting, and outlier handling, to ensure data consistency and accuracy.

[0067] 3) Data transmission: The cleaned data (i.e., the vehicle data in the above embodiments) is automatically transmitted to the car manufacturer's vehicle data platform through a secure transmission protocol (such as HTTPS) to provide a basis for subsequent analysis.

[0068] Step 2: Vehicle model feature code configuration.

[0069] 1) Feature code definition: Define one or more unique or composite feature codes (i.e. the first feature code mentioned above) for each vehicle model. The feature code should accurately reflect the key attributes of the vehicle model, such as vehicle model, year, configuration, etc.

[0070] 2) Configuration Interface: Design a user-friendly interface on the vehicle data platform of the car manufacturer, allowing administrators to easily configure or modify the vehicle model feature code (i.e., the first feature code mentioned above) through a graphical interface.

[0071] 3) Verification mechanism: After configuration, the system automatically verifies the uniqueness and validity of the feature code to ensure the accuracy of the subsequent matching process.

[0072] 4) Feature definition: such as Figure 4 As shown, key feature codes are extracted and defined to form a feature code library.

[0073] Step 3: Automatic matching mechanism.

[0074] 1) Data reception: The vehicle data platform receives cleaned data from the data warehouse.

[0075] 2) Matching algorithm: Using the preset vehicle model feature code, the algorithm automatically compares the corresponding fields of each vehicle data (equivalent to the first field in the above embodiment) to achieve accurate matching between the vehicle and the vehicle model item.

[0076] 3) Result storage: Successfully matched data will be stored by vehicle type for easy subsequent querying and analysis.

[0077] Step 4: No signature processing configured.

[0078] 1) Detection mechanism: The system periodically checks newly received data for records that fail to match any feature codes.

[0079] 2) Global Feature Code Comparison: For data that cannot be directly matched, the system attempts to use global feature codes (such as general vehicle codes, which are equivalent to the third feature codes in the above embodiments) for secondary matching in order to capture possible missing configurations.

[0080] 3) Marking and Isolation: Data that fails to match in any of the above methods will be marked as "useless data" and isolated for storage; data that matches the global feature code but not the vehicle model feature code will be marked as "alarm" or "alarm data" and await further processing.

[0081] 4) Automatic matching algorithm:

[0082] Define the bicycle feature codes Fa and Fb, and the general feature codes Fc = Fc01 and Fd = Fd01;

[0083] Define vehicle type A as Fa = Fa01, Fb = Fb01, and define vehicle type B as Fa = Fa02, Fb = Fb02;

[0084] Matching and Alarm Correspondence Formula:

[0085] Vehicle 1 (Fa = Fa01 and Fb = Fb01), Vehicle 1 = Vehicle type A;

[0086] Vehicle 2 (Fa = Fa02 and Fb = Fb02), Vehicle 2 = Vehicle type B;

[0087] Vehicle 3 (Fa = Fa03 and Fb = Fb03), Vehicle 3 = Unmatched vehicle model → Vehicle 3 (Fc = Fc01 and Fd = Fd01), Vehicle 3 = Alarm;

[0088] Vehicle 4 (Fa = Fa04 and Fb = Fb04), Vehicle 3 = Unmatched vehicle type → Vehicle 3 (Fc = Fc02 and Fd = Fd02), Vehicle 4 = Discarded;

[0089] Step 5: Alarms and manual review.

[0090] 1) Alarm Trigger: When the system detects a large number or continuous unmatched data, the alarm function is automatically triggered to remind the administrator through system notification.

[0091] 2) Manual review process: After receiving the alarm, the administrator logs into the system to view the details of the unmatched data, determines whether it is necessary to add or adjust the feature code configuration based on the actual information of the vehicle, and performs the corresponding operation.

[0092] 3) Audit Feedback: Audit results (including adding new feature codes, modifying feature codes, or confirming that the data is correct) will be recorded by the system for subsequent auditing and improvement.

[0093] Through practical application at a major automaker, the above-mentioned technical solution has significantly improved the accuracy and efficiency of vehicle data flow. Specifically, the data matching accuracy rate has increased to over 99.9%, effectively reducing data errors and loss caused by missing signature codes; data processing time has been shortened by approximately 30%, improving the overall operating efficiency of the production line; and the alarm function has promptly detected and resolved multiple instances of missing signature codes, avoiding potential production risks and economic losses.

[0094] In summary, the embodiments of this application have significant technical advantages and application value in the field of vehicle data flow and verification, and can bring significant social, economic and technical benefits to enterprises.

[0095] More specifically, this application embodiment reduces economic losses caused by inaccurate data by minimizing data errors and omissions; simultaneously, it reduces manual intervention costs and improves the accuracy and reliability of data in the vehicle data platform by effectively eliminating invalid data through precise matching of feature codes. By dynamically adjusting the feature code configuration, it can quickly adapt to the needs of new vehicle models, reducing the risk of data omissions and enhancing system flexibility. Furthermore, based on this application embodiment, it can also achieve process-oriented and standardized vehicle data management, improving enterprise management levels.

[0096] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods of the various embodiments of this application.

[0097] This embodiment also provides an alarm event execution device for implementing the above embodiments and preferred embodiments; details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0098] Figure 5 This is a structural block diagram of an alarm event execution device according to an embodiment of this application. The device includes:

[0099] The determining module 52 is used to determine whether there is a target model that matches the vehicle data by using a pre-configured first feature code, wherein the first feature code includes a feature code uniquely configured for each of the multiple models, and the vehicle data includes at least: the second feature code of the vehicle;

[0100] The alarm module 54 is used to execute an alarm event using the second feature code when there is no target model that matches the vehicle data.

[0101] The aforementioned device determines whether a target vehicle model matching the vehicle data exists using a pre-configured first feature code. This first feature code includes a unique feature code configured for each of multiple vehicle models. The vehicle data includes at least a second feature code. If no target vehicle model matching the vehicle data exists, an alarm event is triggered using the second feature code. In other words, by performing a matching process between the vehicle data and the target vehicle model, and then determining that no matching target vehicle model exists, an alarm event can be triggered using the second feature code in the vehicle data. Therefore, this technical solution solves the problem in related technologies where automakers' vehicle data platforms lack an effective alarm mechanism, making it impossible to promptly detect and notify relevant personnel to handle vehicle data discarded due to the lack of a configured feature code on the automaker's vehicle data platform. This achieves the technical effect of timely alarms.

[0102] In an exemplary embodiment, the determining module 52 is further configured to: locate a first field of the vehicle data, wherein the first field is the corresponding field of the second feature code in the vehicle data; compare the first field with the first feature code to obtain a comparison result; if the comparison result indicates that the first field is consistent with any feature code in the first feature code, determine that there is a target model that matches the vehicle data of the vehicle; if the comparison result indicates that the first field is inconsistent with all feature codes in the first feature code, determine that there is no target model that matches the vehicle data of the vehicle.

[0103] In an exemplary embodiment, the determining module 52 is further configured to: split the first field to obtain M groups of second fields, wherein each group of second fields includes: a first feature code family and a first feature code character corresponding to the first feature code family, and M is a positive integer; and split any of the feature codes to obtain N groups of third fields, wherein each group of third fields includes: a second feature code family and a second feature code character corresponding to the second feature code family, N is a positive integer and N is less than or equal to M; match the M groups of second fields and the N groups of third fields; if there is an N group of second fields in the M groups of second fields that is completely consistent with the N groups of third fields, determine that the comparison result is that the first field is consistent with any feature code in the first feature code; if there is no N group of second fields in the M groups of second fields that is completely consistent with the N groups of third fields, determine that the comparison result is that the first field is inconsistent with all feature codes in the first feature code.

[0104] In an exemplary embodiment, the alarm module 54 is further configured to: determine whether the second feature code matches the third feature code, wherein the third feature code is a universal feature code pre-configured for a universal vehicle model, the universal vehicle model including: vehicle models other than the multiple vehicle models that are not uniquely configured with feature codes, the multiple vehicle models including the target vehicle model; if the second feature code matches the third feature code, mark the vehicle data as alarm data, and execute the alarm event according to preset rules.

[0105] In an exemplary embodiment, the alarm module 54 is further configured to: mark the vehicle data as useless data if the second feature code does not match the third feature code; and isolate and store the useless data.

[0106] In an exemplary embodiment, the alarm module 54 is further configured to: determine the number of flags for the received vehicle data to be marked as alarm data; and, if the number of flags meets a critical number indicated by the preset rule, execute the alarm event on the target object.

[0107] In an exemplary embodiment, the alarm module 54 is further configured to: if a target vehicle model matching the vehicle data exists, use the target vehicle model as the storage type of the vehicle data; and store the vehicle data using the storage type.

[0108] Embodiments of this application also provide a computer-readable storage medium storing a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when run.

[0109] Optionally, in this embodiment, the storage medium may be configured to store a computer program for performing the following steps:

[0110] S1, determine whether there is a target model that matches the vehicle data by using a pre-configured first feature code, wherein the first feature code includes a feature code uniquely configured for each of the multiple models, and the vehicle data includes at least: the second feature code of the vehicle;

[0111] S2, if no target vehicle model matches the vehicle data, an alarm event is executed using the second feature code.

[0112] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard disk, magnetic disk, or optical disk.

[0113] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0114] Embodiments of this application also provide a computer program product, including a computer program, wherein the computer program, when executed by a processor, performs the steps in any of the above method embodiments.

[0115] Embodiments of this application also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0116] Optionally, in this embodiment, the processor can be configured to perform the following steps via a computer program:

[0117] S1, determine whether there is a target model that matches the vehicle data by using a pre-configured first feature code, wherein the first feature code includes a feature code uniquely configured for each of the multiple models, and the vehicle data includes at least: the second feature code of the vehicle;

[0118] S2, if no target vehicle model matches the vehicle data, an alarm event is executed using the second feature code.

[0119] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0120] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0121] Obviously, those skilled in the art should understand that the modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented here, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this application is not limited to any particular hardware and software combination.

[0122] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method of executing an alarm event, characterized by, include: The existence of a target vehicle model that matches the vehicle data is determined by a pre-configured first feature code, wherein the first feature code includes a feature code uniquely configured for each of the multiple vehicle models, and the vehicle data includes at least: the second feature code of the vehicle. If no target vehicle model matches the vehicle data, an alarm event is triggered using the second feature code.

2. The method of claim 1, wherein, Determining whether a target vehicle model matching the vehicle's data exists using a pre-configured first feature code includes: Locate the first field of the vehicle data, wherein the first field is the corresponding field of the second feature code in the vehicle data; The first field is compared with the first feature code to obtain the comparison result; If the comparison result indicates that the first field matches any of the first feature codes, it is determined that there is a target model that matches the vehicle data of the vehicle. If the comparison result indicates that the first field is inconsistent with all the feature codes in the first feature code, it is determined that there is no target model that matches the vehicle data of the vehicle.

3. The method of claim 2, wherein, The first field is compared with the first feature code to obtain the comparison result, including: The first field is split to obtain M groups of second fields, wherein each group of second fields includes: a first feature code family and a first feature code character corresponding to the first feature code family, and M is a positive integer; and any feature code is split to obtain N groups of third fields, wherein each group of third fields includes: a second feature code family and a second feature code character corresponding to the second feature code family, and N is a positive integer and N is less than or equal to M; Match the second field of group M and the third field of group N; If there is an Nth group of second fields in the Mth group that is completely consistent with the Nth group of third fields, the comparison result is determined to be that the first field is consistent with any feature code in the first feature code. If there is no second field in the M group that is completely identical to the third field in the N group, the comparison result is determined to be that the first field is inconsistent with all the feature codes in the first feature code.

4. The method of claim 1, wherein, Executing an alarm event via the second feature code includes: Determine whether the second feature code matches the third feature code, wherein the third feature code is a universal feature code pre-configured for a general vehicle model, the general vehicle model includes: vehicle models other than the multiple vehicle models that have not been uniquely configured with a feature code, the multiple vehicle models include the target vehicle model; If the second feature code matches the third feature code, the vehicle data is marked as alarm data, and the alarm event is executed according to preset rules.

5. The method according to claim 4, characterized in that, After determining whether the second feature code matches the third feature code, the method further includes: If the second feature code does not match the third feature code, the vehicle data will be marked as useless data. The useless data is isolated and stored.

6. The method according to claim 4, characterized in that, The alarm event is executed according to preset rules, including: Determine the number of tags that mark the received vehicle data as alarm data; If the number of markers meets the critical number indicated by the preset rule, the alarm event is executed on the target object.

7. The method according to claim 6, characterized in that, After determining whether a target vehicle model matching the vehicle data exists by using a pre-configured first feature code, the method further includes: If a target vehicle model that matches the vehicle data exists, the target vehicle model will be used as the storage type for the vehicle data. The vehicle data is stored using the aforementioned storage type.

8. An alarm event execution system, characterized in that, include: The determination module is used to determine whether there is a target model that matches the vehicle data by using a pre-configured first feature code, wherein the first feature code includes a feature code uniquely configured for each of the multiple models, and the vehicle data includes at least: the second feature code of the vehicle; The alarm module is used to execute an alarm event using the second feature code when no target vehicle model matching the vehicle data exists.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a stored program, wherein the program, when executed, performs the method of any one of claims 1 to 7.

10. An electronic device comprising a memory and a processor, characterized in that, The memory stores a computer program, and the processor is configured to execute the method of any one of claims 1 to 7 through the computer program.

Images