TBOX integrated vehicle-mounted anomaly detection early warning method and system

Abstract

The invention discloses a TBOX integrated vehicle-mounted anomaly detection early warning method and system, and relates to the technical field of anomaly detection, and the method comprises the steps: obtaining an integrated data packet of TBOX integration; identifying a vehicle-mounted component associated with the TBOX by analyzing the integrated data packet, and determining a component relationship; topological connection is carried out according to the component relation to obtain a vehicle-mounted component topological structure, integration anomaly detection is carried out on the integrated data packet according to the vehicle-mounted component topological structure, an integration anomaly detection result is obtained, and the integration anomaly detection result comprises abnormal vehicle-mounted components which detect and identify integration anomaly; and generating an integrated early warning signal according to the integrated anomaly detection result, and updating the integrated data packet to obtain an integrated updated data packet. The technical problems that in the prior art, vehicle-mounted assembly integration is complex, and anomaly detection is incomplete are solved, and the technical effect of improving the accuracy of vehicle-mounted system integration anomaly detection is achieved.

Description

Technical Field

[0001] The present invention relates to the technical field of anomaly detection, and particularly to an in-vehicle anomaly detection and warning method and system integrated with TBOX. Background Art

[0002] With the rapid development of intelligent vehicle technology and vehicle networking systems, as the core device for in-vehicle communication and control, TBOX plays an increasingly important role in aspects such as vehicle data management, remote control, and fault diagnosis. To meet the increasingly complex functional requirements, TBOX integrates a large number of in-vehicle electronic components, such as sensors, actuators, and communication modules, forming a highly integrated system structure. However, with the complexity of the in-vehicle system structure, the dependency relationships and data interaction frequencies between components have increased significantly, and TBOX faces problems such as poor component compatibility, difficult adaptation, and difficulty in timely identifying abnormal states during the integration process.

[0003] Most traditional in-vehicle anomaly detection methods rely on single-point monitoring or fixed-rule judgment, making it difficult to achieve comprehensive monitoring of the entire integrated system. There are defects such as low detection accuracy, lag in anomaly response, and lack of systematic warning capabilities, and it is difficult to meet the high requirements of modern intelligent vehicles for stability, safety, and real-time performance. Summary of the Invention

[0004] This application provides an in-vehicle anomaly detection and warning method and system integrated with TBOX, which is used to solve the technical problems of complex integration of in-vehicle components and incomplete anomaly detection in the prior art.

[0005] In view of the above problems, this application provides an in-vehicle anomaly detection and warning method and system integrated with TBOX.

[0006] In the first aspect of this application, an in-vehicle anomaly detection and warning method integrated with TBOX is provided. The method includes: Obtain an integrated data packet integrated with TBOX; identify in-vehicle components associated with the TBOX by parsing the integrated data packet, and determine the component relationships; perform topological connection according to the component relationships to obtain an in-vehicle component topological structure, and perform integrated anomaly detection on the integrated data packet according to the in-vehicle component topological structure to obtain an integrated anomaly detection result, where the integrated anomaly detection result includes abnormal in-vehicle components with detection identifiers of integrated anomalies; generate an integrated warning signal according to the integrated anomaly detection result, and update the integrated data packet to obtain an integrated updated data packet.

[0007] In the second aspect of this application, an in-vehicle anomaly detection and warning system integrated with TBOX is provided. The system includes: A data packet acquisition module for acquiring an integrated data packet integrated by the TBOX; a component relationship determination module for identifying vehicle-mounted components associated with the TBOX by parsing the integrated data packet and determining the component relationship; an integrated anomaly detection module for performing topological connection according to the component relationship to obtain a vehicle-mounted component topological structure, and performing integrated anomaly detection on the integrated data packet according to the vehicle-mounted component topological structure to obtain an integrated anomaly detection result, where the integrated anomaly detection result includes abnormal vehicle-mounted components that detect and identify integration anomalies; a warning signal generation module for generating an integrated warning signal according to the integrated anomaly detection result and updating the integrated data packet to obtain an integrated updated data packet.

[0008] One or more technical solutions provided in this application have at least the following technical effects or advantages: This application acquires an integrated data packet integrated by the TBOX; identifies vehicle-mounted components associated with the TBOX by parsing the integrated data packet and determines the component relationship; performs topological connection according to the component relationship to obtain a vehicle-mounted component topological structure, performs integrated anomaly detection on the integrated data packet according to the vehicle-mounted component topological structure to obtain an integrated anomaly detection result, where the integrated anomaly detection result includes abnormal vehicle-mounted components that detect and identify integration anomalies; generates an integrated warning signal according to the integrated anomaly detection result and updates the integrated data packet to obtain an integrated updated data packet. The present invention solves the technical problems of complex integration of vehicle-mounted components and incomplete anomaly detection in the prior art, and achieves the technical effect of improving the accuracy of integrated anomaly detection of vehicle-mounted systems by constructing a vehicle-mounted component topological structure and performing hierarchical integrated anomaly detection and data packet update based on the topological structure. Description of the Drawings

[0009] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention, and those of ordinary skill in the art can also obtain other drawings without creative efforts based on these drawings.

[0010] Figure 1 It is a schematic flowchart of a vehicle-mounted anomaly detection and warning method integrated by the TBOX provided in an embodiment of this application; Figure 2 It is a schematic structural diagram of a vehicle-mounted anomaly detection and warning system integrated by the TBOX provided in an embodiment of this application.

[0011] Description of the reference numerals: data packet acquisition module 11, component relationship determination module 12, integrated anomaly detection module 13, warning signal generation module 14. Detailed Embodiments

[0012] The present application provides a vehicle abnormal detection and warning method and system integrated with TBOX, aiming to solve the technical problems of complex integration of vehicle components and incomplete abnormal detection in the prior art. By constructing a vehicle component topology structure and performing hierarchical integration of abnormal detection and data packet update based on the topology structure, the technical effect of improving the accuracy of abnormal detection in vehicle system integration is achieved.

[0013] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present application without creative efforts shall fall within the protection scope of the present application.

[0014] It should be noted that any variations of the terms "including" and "having" are intended to cover non-exclusive inclusion. For example, a process, method, system, product or server that includes a series of steps or units does not necessarily have to be limited to those steps or units clearly listed, but may include other steps or modules that are not clearly listed or are inherent to these processes, methods, products or devices.

[0015] Embodiment 1, as Figure 1 shown, the present application provides a vehicle abnormal detection and warning method integrated with TBOX, and the method includes: Step S100: Obtain an integrated data packet integrated with TBOX.

[0016] In the embodiment of the present application, obtaining the integrated data packet integrated with TBOX is the starting step of the entire abnormal detection process, and its core lies in comprehensively collecting and structuring all the vehicle component data currently interacting with TBOX in the vehicle. First, TBOX establishes a physical connection with the in-vehicle communication network (such as CAN bus, LIN bus or Ethernet), and uses the bus listening mechanism to capture all incoming data messages in real time. Subsequently, a multi-protocol parsing module is called, and corresponding parsing methods are used for message decoding according to the communication protocol type. For example, the DBC file is used to parse the CAN frame structure, and key fields such as component identification, operating parameters, status information, and diagnostic codes are extracted from the messages. The parsed multi-source data is uniformly aligned through the timestamp synchronization mechanism, and further, redundant fields and conflicting parameters are removed through the data fusion algorithm to ensure the consistency and accuracy of the data. Finally, all the component information after parsing and fusion processing is encapsulated into an integrated data packet with a unified format and complete fields.

[0017] Step S200: Identify the vehicle components associated with the TBOX by parsing the integrated data packet, and determine the component relationship.

[0018] In the embodiments of the present application, by parsing the integrated data packet integrated by the TBOX, vehicle-mounted components associated with the TBOX are identified, and the component relationships among the components are determined. Specifically, first, a hash matching method is used to extract the component identification fields in the integrated data packet, including Component ID, communication address, and function label, and these fields are quickly compared with the component registry maintained inside the TBOX to identify the vehicle-mounted components that currently have data interaction or integrated configuration with the TBOX, and a complete component list is generated. Secondly, using the path mapping method, the source address and destination address information recorded in the data packet is parsed, and combined with the interface binding information of the TBOX, it is judged whether there is a data exchange path between the components, and the communication transmission relationship between the components is established.

[0019] Subsequently, the initialization configuration fields in the data packet are parsed, such as the dependent component number, configuration priority, and function reference relationship. Using the configuration dependency modeling method, the loading order and function collaboration path of each component during the vehicle power-on preparation stage are constructed, and the function dependency relationship in the non-operating state during the function preparation stage between the components is identified. Finally, for the operation process logs, status feedback sequences, and function call records included in the integrated data packet, the call chain tracing method is used to reconstruct the time series, and the control trigger and data feedback paths formed by each component during the vehicle operation process are analyzed, so as to clarify the function dependency relationship in the operating state between the components.

[0020] Through the above four steps, the vehicle-mounted components associated with the TBOX are comprehensively identified, and based on information such as communication paths, initialization configurations, and dynamic calls, the component relationships among the components are determined.

[0021] Furthermore, the method provided by the application embodiments further includes: Identifying vehicle-mounted components associated with the TBOX by parsing the integrated data packet, and determining the component relationships; wherein, the component relationships include communication transmission relationships, function dependency relationships in the non-operating state, and function dependency relationships in the operating state.

[0022] In the embodiments of the present application, in order to identify the vehicle-mounted components associated with the TBOX and further determine the structural relationships between the components, first, the integrated data packet is deeply parsed. This process uses the component identification extraction method. By analyzing the communication messages, configuration entries, and component registration information included in the data packet, all vehicle-mounted component identifications that have interaction records with the TBOX are extracted, including the network address of each component (such as CAN ID, LIN address), module type (such as ECU, sensor, actuator), and the subsystem to which it belongs. Through this extraction process, a component set involved by the TBOX in the current system is initially constructed.

[0023] After identifying the components, a multi-level relationship parsing method is further adopted to determine the specific association relationships between each component and the TBOX. The determined component relationships include three key types. First is the communication transmission relationship. By parsing fields such as the bus type, communication channel, and message frame structure recorded in the data packet, it is judged whether each component has a physical connection with the TBOX and can perform data interaction through communication protocols such as CAN, LIN, Ethernet, etc. This relationship reflects the data transmission path between the TBOX and the component. Second is the functional dependency relationship in the non-operating state. By analyzing the system startup configuration table and module initialization process, it is judged whether some components need to rely on the startup signal of the TBOX or the system initialization result to complete loading or wake-up, such as the power-on sequence control and basic configuration loading during the startup phase. This type of relationship reflects the functional coupling logic in the cold startup phase of the system. Finally is the functional dependency relationship in the operating state. By analyzing the real-time scheduling table, status synchronization fields, and functional call paths between components, it is identified which components need to rely on the data support, control commands, or parameter feedback provided by the TBOX in real time during the system operation, such as powertrain control, environmental perception linkage, and status write-back. This type of relationship reflects the real-time collaboration and control coupling during dynamic operation.

[0024] Through the above parsing process, the component relationships between the TBOX and in-vehicle components are comprehensively constructed. The component relationships include communication transmission relationships, functional dependency relationships in the non-operating state, and functional dependency relationships in the operating state.

[0025] Step S300: Perform topological connection according to the component relationships to obtain the in-vehicle component topological structure, and perform integrated anomaly detection on the integrated data packet according to the in-vehicle component topological structure to obtain the integrated anomaly detection result, where the integrated anomaly detection result includes the abnormal in-vehicle components that identify the integrated anomalies.

[0026] In the embodiment of the present application, after completing the identification of the TBOX-associated in-vehicle components and their component relationships, based on the parsed communication paths and functional dependency relationships, each component is topologically connected according to the graph modeling method. Each in-vehicle component is abstracted as a node, and the nodes are connected by directed edges. The direction of the edges represents the data flow or functional call direction between the components. During the construction process, first connect all the components that have direct communication or functional dependency with the TBOX to form the first-level in-vehicle component topological structure, which is used to represent the set of components directly managed or controlled by the TBOX; subsequently, continue to expand other components that are dependent on or connected by these first-level components to form the second-level in-vehicle component topological structure, which is used to represent the indirectly associated component relationships. Through the above connection process, a complete in-vehicle component topological structure is generated, reflecting the structural hierarchy and dependency path of the TBOX and all in-vehicle components during the integration process.

[0027] Based on the topological structure, anomaly detection is respectively performed on the integrated data corresponding to the primary and secondary components. The detection content includes, but is not limited to, indicators such as communication status, protocol matching degree, interface compatibility, and functional dependency integrity. The key point of the detection for the primary component lies in whether it can directly complete the normal integration with the TBOX, while the secondary component focuses on whether its dependency path is stable and whether it is affected by the anomaly of the primary component. During the detection process, if it is found that a component does not meet the integration requirements, such as communication anomalies, configuration conflicts, or function interruptions, it is determined as an integration anomaly.

[0028] Finally, the detection results of the primary and secondary topological structures are combined and output as the integrated anomaly detection results. All detected abnormal vehicle-mounted components are clearly identified in this result, including their anomaly types and the topological levels where they are located.

[0029] Furthermore, in the method provided by the application embodiment, when performing integrated anomaly detection on the integrated data packet according to the vehicle-mounted component topological structure, it further includes: Decompose the vehicle-mounted component topological structure to output a primary vehicle-mounted component topological structure and a secondary vehicle-mounted component topological structure, where the primary vehicle-mounted component topological structure is the vehicle-mounted component directly associated with the TBOX, and the secondary vehicle-mounted component topological structure is the vehicle-mounted component indirectly associated with the TBOX; perform integrated anomaly detection on the integrated data packet according to the primary vehicle-mounted component topological structure and the secondary vehicle-mounted component topological structure to obtain a primary integrated anomaly detection result and a secondary integrated anomaly detection result; output the primary integrated anomaly detection result and the secondary integrated anomaly detection result as the integrated anomaly detection result.

[0030] In the embodiment of the present application, first, the vehicle-mounted component topological structure is decomposed into a primary vehicle-mounted component topological structure and a secondary vehicle-mounted component topological structure. The topological decomposition adopts the breadth-first search (BFS) method, starting from the TBOX as the root node for traversal, and hierarchical classification is carried out according to the connection depth between the components and the TBOX: all vehicle-mounted components directly establishing a communication connection with the TBOX through physical communication interfaces (such as CAN, LIN, or Ethernet) are identified as primary components, constituting the primary vehicle-mounted component topological structure; while the components indirectly associated with the TBOX through the primary components are classified as secondary components, constituting the secondary vehicle-mounted component topological structure.

[0031] After obtaining the first-level and second-level topological structures, anomaly detection is performed on the components at each level. For the first-level components, a protocol compatibility verification method is adopted to extract the communication protocol types, interface electrical parameters, function configuration items, etc. contained in the integrated data packet, and compare them with the preset standard requirements of the TBOX to identify whether there are problems such as protocol mismatch, interface incompatibility, or function loading failure, and generate the first-level integrated anomaly detection results. For the second-level components, a dependency chain consistency check method is used to analyze whether the dependency paths on the first-level components are complete, whether the state transfer is stable, and whether there are interruptions in the response link, identify potential anomaly risks, and form the second-level integrated anomaly detection results.

[0032] Finally, the first-level and second-level detection results are merged to output the integrated anomaly detection results. This result not only includes the list of in-vehicle components detected as anomalies, but also identifies the topological level, anomaly type, and corresponding key parameters of each abnormal component.

[0033] Furthermore, in the method provided by the application embodiment, when performing integrated anomaly detection on the integrated data packet according to the first-level in-vehicle component topological structure and the second-level in-vehicle component topological structure, it further includes: Separate the integrated data packet to output a first-level integrated data packet and a second-level integrated data packet; while performing integrated anomaly detection on the first-level in-vehicle component topological structure according to the first-level integrated data packet, perform parallel integrated anomaly detection on the second-level in-vehicle component topological structure according to the second-level integrated data packet to obtain the first-level integrated anomaly detection result and the second-level integrated anomaly detection result.

[0034] In the embodiment of the present application, the integrated data packet is first structurally separated. A method based on component index matching is adopted, and using the identification information of the first-level and second-level components in the previously constructed in-vehicle component topological structure, various fields (such as Component ID, function module identification, communication parameters) in the original integrated data packet are screened and classified. All data segments belonging to the first-level in-vehicle components are extracted and assembled into a first-level integrated data packet; the data segments belonging to the second-level in-vehicle components are extracted and assembled into a second-level integrated data packet.

[0035] After obtaining the separated first-level integrated data packet, an anomaly detection is performed on its content using the protocol adaptation verification method. Specifically, the data fields corresponding to each first-level component are extracted, such as communication protocol version, message format, interface parameters, function status flags, etc., and compared one by one with the integration standard of the TBOX. During the detection process, if the parameters of the component meet the communication requirements but the function configuration is not yet complete, it is allowed to enter the partial integration state, that is, a communication link is initially established but the complete function process is not yet activated, so as to ensure the continuity of the detection and the flexible integration ability of the system. If serious protocol conflicts, interface incompatibilities and other problems are detected, the component is marked as abnormal and recorded in the first-level integrated anomaly detection result.

[0036] At the same time, during the process of processing the first-level data, a parallel detection of the second-level integrated data packet is performed using the dependency path verification method. This method determines whether the first-level components it depends on have completed partial or all integrations based on the upstream dependency relationship of the second-level components in the topological structure; if the dependency chain is complete, continue to detect the operating state, configuration consistency and communication stability of the second-level components; if a path interruption, abnormal dependent component or status synchronization failure is found, the second-level component is marked as abnormal and recorded in the second-level integrated anomaly detection result. This method can effectively identify chain failures caused by upstream anomalies and ensure the accuracy of anomaly location.

[0037] Finally, the first-level and second-level integrated anomaly detection results are output respectively.

[0038] Furthermore, in the method provided by the application embodiment, when performing integrated anomaly detection on the integrated data packet according to the first-level vehicle-mounted component topological structure and the second-level vehicle-mounted component topological structure, it further includes: Separate the integrated data packet to output a first-level integrated data packet and a second-level integrated data packet; after performing integrated anomaly detection on the first-level vehicle-mounted component topological structure according to the first-level integrated data packet, determine whether the first-level integrated anomaly detection result includes abnormal vehicle-mounted components. If not, perform the first-level integration by the TBOX according to the first-level vehicle-mounted component topological structure; then perform integrated anomaly detection on the second-level vehicle-mounted component topological structure according to the second-level integrated data packet, output the second-level integrated anomaly detection result, and output the second-level integrated anomaly detection result as the integrated anomaly detection result.

[0039] In the embodiment of the present application, first, a separation operation is performed on the integrated data packet, and a component ID mapping and matching method is used for processing. Specifically, the component identification fields (such as ComponentID) of all data records are extracted from the integrated data packet, and are compared one by one with the list of primary and secondary components divided by the previous topology structure. The data belonging to the primary components is divided into primary integrated data packets, and the data belonging to the secondary components is divided into secondary integrated data packets. This process ensures that each type of data strictly corresponds to its corresponding topological level, facilitating subsequent hierarchical anomaly detection.

[0040] Then, based on the primary integrated data packet, an integrated anomaly detection is performed on the primary vehicle-mounted component topology structure. Using the communication protocol and function configuration consistency verification method, the adaptation degree of each primary component to the TBOX in terms of communication protocol, electrical interface, function configuration, etc. is analyzed item by item. After the detection is completed, a primary integrated anomaly detection result is formed to identify which primary components have abnormal conditions that do not meet the integration conditions.

[0041] Subsequently, it enters the critical judgment stage, and an anomaly result determination method is used to analyze the primary integrated anomaly detection result. If the detection result includes abnormal vehicle-mounted components, that is, there are problems such as protocol incompatibility and function configuration failure, then the original integrated data packet is processed according to this anomaly result, and a target field correction and parameter adjustment method is used for local update to generate a primary integrated update data packet. The update content includes setting the abnormal fields to null, rolling back the configuration, adjusting communication parameters, etc. Subsequently, the primary integration operation of the TBOX is re-executed according to the updated data packet, that is, on the premise of fixing the configuration conflict, effective communication and function loading between the TBOX and the primary components are achieved. If the primary anomaly detection result does not include abnormal vehicle-mounted components, there is no need to update the data packet, and the primary integration operation is directly performed according to the original primary topology structure and data content to establish communication and integrate functions of the primary components.

[0042] While the primary detection is completed, a parallel detection is performed on the secondary integrated data packet. Using the dependency chain consistency analysis method, it is checked whether the dependency path of the secondary components on the primary components is complete, and whether their function responses and status feedback match the upstream components. If there are problems such as dependency breakage, abnormal response, or path conflict, the component is recorded as abnormal, and a secondary integrated anomaly detection result is formed.

[0043] Finally, the result obtained from the secondary detection process is output as the integrated anomaly detection result of this round of detection, and the content includes all secondary vehicle-mounted components that failed to be successfully integrated, the reasons for the anomalies, and their location paths.

[0044] Furthermore, in the method provided by the application embodiment, determining whether the primary integrated anomaly detection result includes abnormal vehicle-mounted components further includes: If so, perform a first-level update on the integrated data packet according to the first-level integrated anomaly detection result, output a first-level integrated update data packet, and perform the first-level integration on the TBOX according to the first-level integrated update data packet.

[0045] In the embodiment of the present application, when the first-level integrated anomaly detection result contains abnormal vehicle-mounted components, it indicates that there are parameter configuration problems in the original integrated data packet that affect the integration process. At this time, the data packet needs to be updated. First, an abnormal field identification method is used to extract the identification information of each abnormal component and its associated abnormal fields from the anomaly detection result, including communication protocol type, interface parameters, voltage level, function initialization configuration, etc. Through these fields, the corresponding data area is located in the original integrated data packet. Subsequently, the abnormal fields are updated using parameter correction and function masking methods. For example, an incompatible communication protocol is replaced with a standard protocol supported by the TBOX, the port parameters are adjusted to meet the electrical interface specifications, or the currently unavailable function configuration items are masked. After the correction is completed, the updated data content is repackaged and output as a first-level integrated update data packet. This data packet eliminates the abnormal content that affects the integration stability while retaining the original valid information.

[0046] After the data update is completed, based on this first-level integrated update data packet, the integration operations are sequentially performed according to the first-level vehicle-mounted component topology. This process uses a step-by-step loading and communication confirmation method to establish a communication connection for each component, load the updated function parameters, perform configuration initialization, and complete the handshake confirmation at the protocol layer. Through this process, stable data interaction and function integration are achieved between the TBOX and each first-level vehicle-mounted component, avoiding integration failures caused by the original abnormal configuration. Finally, the effective integration of the first-level vehicle-mounted components is completed.

[0047] Further, in the method provided by the application embodiment, after the second-level integrated anomaly detection result is output, it further includes: Determine whether the second-level integrated anomaly detection result includes abnormal vehicle-mounted components; if not, the integrated anomaly detection result is returned as empty; if so, perform a second-level update on the integrated data packet according to the second-level integrated anomaly detection result, output a second-level integrated update data packet, and perform the second-level integration on the TBOX according to the second-level integrated update data packet.

[0048] In the embodiment of the present application, after outputting the secondary integration anomaly detection result, in order to determine whether to continue executing the integration operation of the TBOX for the secondary vehicle-mounted components, an anomaly result judgment method is first used to process the detection result. This method traverses the status fields of each component in the anomaly detection result to determine whether there are vehicle-mounted components marked as anomalies, such as interrupted dependency paths, incorrect configuration parameters, or abnormal communication status. If the judgment result is that there are no abnormal vehicle-mounted components, it means that all current secondary components meet the TBOX integration conditions. At this time, the integration anomaly detection result is returned as empty, indicating that there is no integration anomaly in the system, and the process can end directly.

[0049] If the judgment result is that there are abnormal vehicle-mounted components, it means that some secondary components do not yet meet the integration conditions, and the original integration data packet needs to be updated. This process uses an anomaly field correction method. According to the component ID and anomaly type listed in the anomaly detection result, the corresponding fields in the original data packet are located, such as dependency relationship configuration, protocol parameters, function call items, etc., and adjusted, such as correcting the dependency chain path, replacing incompatible protocol fields, or temporarily disabling the faulty module. After the above corrections are completed, the updated content is repackaged and output as a secondary integration update data packet.

[0050] Next, the secondary integration operation of the TBOX is executed based on this update data packet. Using a dependency-oriented hierarchical loading method, communication connections with the TBOX are established one by one according to the dependency order of the secondary vehicle-mounted components in the topological structure, the updated configuration parameters are loaded, and the function initialization is completed. Through this operation, the TBOX can complete the integration process of all secondary components on the basis of the corrected anomaly conditions. Finally, the secondary integration of the TBOX is completed.

[0051] Furthermore, in the method provided by the application embodiment, when performing integration anomaly detection on the integration data packet according to the vehicle-mounted component topological structure, it further includes: According to the integration data packet, the integration feasibility with each node in the vehicle-mounted component topological structure is detected, including the hardware compatibility index, software adaptability index, communication protocol matching index, and functional safety index between the TBOX and each node; when any of the hardware compatibility index, software adaptability index, communication protocol matching index, and functional safety index does not reach the corresponding preset threshold, it is marked as an abnormal vehicle-mounted component with integration anomaly.

[0052] In the embodiments of the present application, to detect the integration feasibility of each node in the topology structure of the TBOX and in-vehicle components, first, detailed parameter information of each component is extracted from the integration data packet and corresponding to each node in the topology structure. This process uses the node parameter mapping method to establish an association between the configuration fields in the integration data packet and each topology node, and constructs the index set required for detection. Specifically, it includes hardware compatibility indicators such as "power supply voltage", "communication interface type", "current capacity", etc.; software adaptability indicators such as "driver version", "firmware version", "operating system compatibility"; communication protocol matching indicators including "communication protocol type (such as CAN 2.0, CAN FD, LIN)", "frame format", "message period", "bandwidth requirement"; and functional safety indicators such as "redundant configuration", "fault detection ability", "safety level", "fault isolation mechanism", etc.

[0053] After the index extraction is completed, the above parameters are determined using the threshold comparison method. The preset threshold refers to the lowest acceptable standard configured for each type of integration index in the TBOX system. For example, the preset threshold for the power supply voltage is 9V–16V, the driver version shall not be lower than two minor versions of the current core version of the TBOX, the communication protocol shall be exactly the same as the standard supported by the TBOX port (such as supporting CAN FD but not supporting CAN 2.0A), the frame period shall not exceed the maximum reception delay allowed by the TBOX (such as 20ms), and the safety level shall meet the system-level requirement of the lowest ASIL-B. Each index is closely related to the software and hardware capabilities and safety policies of the TBOX.

[0054] After comparing the four indicators of each component with these preset thresholds respectively, if any indicator does not reach the corresponding preset threshold, it is considered that the component cannot be reliably integrated with the TBOX in the current integration environment. At this time, the abnormal identification method is used to mark the component as an abnormal in-vehicle component with integration abnormality.

[0055] Step S400: Generate an integration warning signal according to the integration abnormality detection result, and update the integration data packet to obtain an integrated update data packet.

[0056] In the embodiments of the present application, after completing the integrated anomaly detection and obtaining the integrated anomaly detection result, in order to achieve timely response and repair of the abnormal components, an integrated warning signal is first generated. This process adopts a warning generation method based on anomaly type mapping. Specifically, the anomaly types of each identified abnormal vehicle-mounted component (such as communication protocol mismatch, software version incompatibility, hardware interface conflict, or functional safety deficiency) are extracted and matched with a preset risk level mapping table. This mapping table classifies the anomaly types into a prompt level, a warning level, and a severe level according to the system impact degree. Through this mapping method, the abnormal components are associated with their corresponding warning levels, and then a standardized integrated warning signal is constructed, including the abnormal component ID, the description of the abnormal item, the impact path (such as the position in the topological structure), and the recommended handling measures. The generated warning signal can be uploaded by the TBOX system to the host computer or the remote monitoring platform for dynamic warning and integrated strategy adjustment.

[0057] Based on the generation of the warning signal, the current integrated data packet is corrected to ensure that the next integration operation can bypass the abnormal impact. This process adopts a field replacement and anomaly item avoidance method. Specifically, first, according to the identification information of the abnormal component in the integrated anomaly detection result, the data fields related to this component in the integrated data packet are located, such as communication protocol configuration, function initialization parameters, interface allocation table, etc.; then, targeted updates are performed according to the anomaly type. For example, the incompatible protocol field is replaced with the default protocol type, the function initialization flag bit is set to "not enabled", or the path configuration of the component is set to the "to be blocked" state. All adjustment operations are only performed on the fields of the abnormal component to ensure that the overall data structure remains consistent.

[0058] After completing the above corrections, the data repackaging method is used to reorganize the modified content into a structured integrated update data packet. This update data packet is used as the input content to replace the original data for the subsequent TBOX to re-execute the integration process or prepare for function loading. Through the above processing steps, the TBOX realizes a closed-loop control process from anomaly recognition → warning generation → data repair → integration preparation, enhancing the integration stability and response ability in a complex vehicle electronic environment.

[0059] Furthermore, the method provided by the application embodiments further includes: After updating the integrated data packet to obtain the integrated update data packet, the TBOX is updated and integrated according to the integrated update data packet until the integrated anomaly detection result output by the real-time detection returns empty.

[0060] In the embodiments of the present application, after completing the correction of the integrated data packet according to the integrated anomaly detection result and generating an integrated update data packet, the integration process is continuously promoted based on the updated data content until the system state meets the expected compatibility and stability requirements. To this end, an update-driven cyclic integration method is adopted, and the effect of each round of integration operation is dynamically verified through a real-time feedback mechanism.

[0061] First, according to the content of the updated data packet, the integration process of in-vehicle components is re-executed. This process adopts a structure mapping loading method. According to the reserved or corrected field content in the integrated update data packet, the communication protocol, initialization parameters, and function configuration of the components are loaded item by item, and the logical binding and communication link between the TBOX and the components are restored or established. During this process, the integration operation will skip the abnormal modules that have been shielded or are not enabled temporarily, and preferentially integrate the components in a compatible state.

[0062] After the integration is completed, the real-time anomaly detection method is immediately started to quickly verify the current system state. The detection mechanism compares the communication status, protocol consistency, and function feedback of the currently running components by re-parsing them with the compatibility standard of the TBOX, and outputs a new integrated anomaly detection result. If there are still un-repaired or newly emerged abnormal in-vehicle components in the detection result, it means that the data update in this round has not completely solved the integration problem.

[0063] At this time, based on the new detection result, the aforementioned anomaly field positioning and parameter correction method is continued to be used to incrementally correct the integrated data packet again, generate a new integrated update data packet, and repeat the above process. This process forms a dynamic closed loop, that is, "update data packet → execute integration → real-time detection → re-update", and the identification, shielding, or compatibility adjustment of abnormal components are promoted in each round of operation.

[0064] When the real-time detection result of a certain round finally returns empty, that is, no integration anomaly is detected, it means that the TBOX has completed the effective integration of all target components, and the entire process terminates. Through this mechanism, the TBOX can achieve stable and complete integration control in a complex and changeable in-vehicle system environment with the help of real-time feedback and iterative correction capabilities.

[0065] In the embodiments of the present application, in summary, the embodiments of the present application have at least the following technical effects: This application obtains an integrated data packet for TBOX integration; identifies vehicle-mounted components associated with the TBOX by parsing the integrated data packet, and determines component relationships; performs topological connection according to the component relationships to obtain a vehicle-mounted component topological structure, performs integrated anomaly detection on the integrated data packet according to the vehicle-mounted component topological structure, and obtains an integrated anomaly detection result, where the integrated anomaly detection result includes abnormal vehicle-mounted components that detect and identify integration anomalies; generates an integrated warning signal according to the integrated anomaly detection result, and updates the integrated data packet to obtain an integrated updated data packet. The present invention solves the technical problems of complex integration of vehicle-mounted components and incomplete anomaly detection in the prior art, and achieves the technical effect of improving the accuracy of integrated anomaly detection of vehicle-mounted systems by constructing a vehicle-mounted component topological structure and performing hierarchical integrated anomaly detection and data packet update based on the topological structure.

[0066] Embodiment 2, based on the same inventive concept as the vehicle-mounted anomaly detection and warning method for TBOX integration in the foregoing embodiment, as Figure 2 shown, this application provides a vehicle-mounted anomaly detection and warning system for TBOX integration. The system in the embodiment of this application and the method embodiment are based on the same inventive concept. Among them, the system includes:

[0067] A data packet acquisition module 11, configured to acquire an integrated data packet for TBOX integration; a component relationship determination module 12, configured to identify vehicle-mounted components associated with the TBOX by parsing the integrated data packet, and determine component relationships; an integrated anomaly detection module 13, configured to perform topological connection according to the component relationships to obtain a vehicle-mounted component topological structure, perform integrated anomaly detection on the integrated data packet according to the vehicle-mounted component topological structure, and obtain an integrated anomaly detection result, where the integrated anomaly detection result includes abnormal vehicle-mounted components that detect and identify integration anomalies; a warning signal generation module 14, configured to generate an integrated warning signal according to the integrated anomaly detection result, and update the integrated data packet to obtain an integrated updated data packet.

[0068] Further, the system is also used to implement the following functions: Decompose the vehicle-mounted component topological structure, and output a first-level vehicle-mounted component topological structure and a second-level vehicle-mounted component topological structure, where the first-level vehicle-mounted component topological structure is a vehicle-mounted component directly associated with the TBOX, and the second-level vehicle-mounted component topological structure is a vehicle-mounted component indirectly associated with the TBOX; perform integrated anomaly detection on the integrated data packet according to the first-level vehicle-mounted component topological structure and the second-level vehicle-mounted component topological structure, and obtain a first-level integrated anomaly detection result and a second-level integrated anomaly detection result; output the first-level integrated anomaly detection result and the second-level integrated anomaly detection result as the integrated anomaly detection result.

[0069] Further, the system is also used to implement the following functions: Separate the integrated data packet, and output a first-level integrated data packet and a second-level integrated data packet; while performing integrated anomaly detection on the first-level vehicle-mounted component topology structure according to the first-level integrated data packet, perform parallel integrated anomaly detection on the second-level vehicle-mounted component topology structure according to the second-level integrated data packet, and obtain a first-level integrated anomaly detection result and a second-level integrated anomaly detection result.

[0070] Further, the system is also used to implement the following functions: Separate the integrated data packet, and output a first-level integrated data packet and a second-level integrated data packet; after performing integrated anomaly detection on the first-level vehicle-mounted component topology structure according to the first-level integrated data packet, determine whether the first-level integrated anomaly detection result includes an abnormal vehicle-mounted component. If not, execute the TBOX according to the first-level vehicle-mounted component topology structure for first-level integration; then perform integrated anomaly detection on the second-level vehicle-mounted component topology structure according to the second-level integrated data packet, output a second-level integrated anomaly detection result, and output the second-level integrated anomaly detection result as the integrated anomaly detection result.

[0071] Further, the system is also used to implement the following functions: If it includes, perform a first-level update on the integrated data packet according to the first-level integrated anomaly detection result, output a first-level integrated update data packet, and execute the TBOX according to the first-level integrated update data packet for first-level integration.

[0072] Further, the system is also used to implement the following functions: Determine whether the second-level integrated anomaly detection result includes an abnormal vehicle-mounted component; if not, the integrated anomaly detection result returns as empty; if it includes, perform a second-level update on the integrated data packet according to the second-level integrated anomaly detection result, output a second-level integrated update data packet, and execute the TBOX according to the second-level integrated update data packet for second-level integration.

[0073] Further, the system is also used to implement the following functions: Detect the integration feasibility with each node in the vehicle-mounted component topology structure according to the integrated data packet, including the hardware compatibility index, software adaptability index, communication protocol matching index, and functional safety index between the TBOX and each node; when any of the hardware compatibility index, software adaptability index, communication protocol matching index, and functional safety index fails to reach the corresponding preset threshold, identify it as an abnormal vehicle-mounted component with integrated anomalies.

[0074] Further, the system is also used to implement the following functions: After updating the integrated data packet to obtain an integrated updated data packet, perform the TBOX update integration according to the integrated updated data packet until the integrated anomaly detection result returned by real-time detection is empty.

[0075] Further, the system is also used to implement the following functions: Identify vehicle-mounted components associated with the TBOX by parsing the integrated data packet and determine the component relationships; wherein, the component relationships include communication transmission relationships, functional dependency relationships in the non-operating state, and functional dependency relationships in the operating state.

[0076] It should be noted that the above order of the embodiments of the present application is only for description and does not represent the superiority or inferiority of the embodiments. And the above description of specific embodiments of this specification has been made. The processes depicted in the drawings do not necessarily require the specific order and continuous order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0077] The above are only the preferred embodiments of the present application and are not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principle of the present application shall be included within the protection scope of the present application.

[0078] This specification and the drawings are only exemplary descriptions of the present application and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the present application. Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the present application and its equivalent technologies, the present application is intended to include these changes and modifications.

Claims

1. TBOX integrated vehicle-mounted abnormality detection and early warning method, characterized in that: The method comprises: Get the integration data package for TBOX integration; Identifying the vehicle-mounted components associated with the TBOX by parsing the integrated data packet and determining the component relationship; Performing topological connection according to the component relationship to obtain a vehicle-mounted component topology structure, performing integration anomaly detection on the integrated data packet according to the vehicle-mounted component topology structure, and obtaining an integration anomaly detection result, wherein the integration anomaly detection result includes detecting abnormal vehicle-mounted components with integration anomalies; An integrated warning signal is generated according to the integrated anomaly detection result, and the integrated data packet is updated to obtain an integrated update data packet.

2. The TBOX integrated vehicle-mounted abnormality detection and early warning method according to claim 1, characterized in that: Performing integrated anomaly detection on the integrated data packet according to the vehicle-mounted component topology structure, the method comprising: Decomposing the vehicle-mounted component topology structure, and outputting a primary vehicle-mounted component topology structure and a secondary vehicle-mounted component topology structure, wherein the primary vehicle-mounted component topology structure is the vehicle-mounted component directly associated with the TBOX, and the secondary vehicle-mounted component topology structure is the vehicle-mounted component indirectly associated with the TBOX; Performing integrated anomaly detection on the integrated data packet according to the first-level vehicle-mounted component topology structure and the second-level vehicle-mounted component topology structure, and obtaining a first-level integrated anomaly detection result and a second-level integrated anomaly detection result; The first-level integrated anomaly detection result and the second-level integrated anomaly detection result are output as integrated anomaly detection results.

3. The TBOX integrated vehicle-mounted abnormality detection and early warning method according to claim 2, characterized in that: The integrated data packet is subjected to integrated anomaly detection according to the primary vehicle-mounted component topology structure and the secondary vehicle-mounted component topology structure, the method comprising: Separating the integrated data packet and outputting a primary integrated data packet and a secondary integrated data packet; While performing integrated anomaly detection on the first-level vehicle-mounted component topology structure according to the first-level integrated data packet, performing parallel integrated anomaly detection on the second-level vehicle-mounted component topology structure according to the second-level integrated data packet to obtain first-level integrated anomaly detection results and second-level integrated anomaly detection results.

4. The TBOX integrated vehicle-mounted abnormality detection and early warning method according to claim 2, characterized in that: Performing integration anomaly detection on the integrated data packet according to the primary vehicle-mounted component topology structure and the secondary vehicle-mounted component topology structure, the method further comprising: Separating the integrated data packet and outputting a primary integrated data packet and a secondary integrated data packet; After performing integration anomaly detection on the first-level vehicle-mounted component topology structure according to the first-level integration data packet, determining whether the first-level integration anomaly detection result includes an abnormal vehicle-mounted component, and if not, executing the first-level integration of the TBOX according to the first-level vehicle-mounted component topology structure; Then, an integrated anomaly detection is performed on the secondary vehicle-mounted component topology structure according to the secondary integrated data packet, and a secondary integrated anomaly detection result is output, and the secondary integrated anomaly detection result is output as the integrated anomaly detection result.

5. The TBOX integrated vehicle-mounted abnormality detection and early warning method according to claim 4, characterized in that: Determining whether the first-level integrated abnormality detection result includes an abnormal vehicle-mounted component, the method further includes: If included, the integrated data packet is updated at the first level according to the first level integration anomaly detection result, a first level integration update data packet is output, and the TBOX is executed to perform the first level integration according to the first level integration update data packet.

6. The TBOX integrated vehicle-mounted abnormality detection and early warning method according to claim 4, characterized in that: After outputting the secondary integrated anomaly detection result, the method further includes: Determining whether the secondary integrated abnormality detection result includes an abnormal vehicle-mounted component; If not included, the integrated anomaly detection result is returned as null; If included, performing a secondary update on the integrated data packet according to the secondary integration anomaly detection result, outputting a secondary integration update data packet, and executing the secondary integration of the TBOX according to the secondary integration update data packet.

7. The TBOX integrated vehicle-mounted abnormality detection and early warning method according to claim 1, characterized in that: Performing integrated anomaly detection on the integrated data packet according to the vehicle-mounted component topology structure, the method comprising: According to the integrated data packet, detecting the feasibility of integration with each node in the vehicle-mounted component topology, including hardware compatibility indicators, software adaptability indicators, communication protocol matching indicators and functional safety indicators of the TBOX and each node; When any of the hardware compatibility index, software adaptability index, communication protocol matching index and functional safety index does not reach the corresponding preset threshold, it is identified as an abnormal vehicle-mounted component with integration abnormality.

8. The TBOX integrated vehicle-mounted abnormality detection and early warning method according to claim 1, characterized in that: After the integrated data packet is updated to obtain an integrated update data packet, the TBOX is updated and integrated according to the integrated update data packet until the integrated abnormality detection result output by the real-time detection is returned to be empty.

9. The TBOX integrated vehicle-mounted abnormality detection and early warning method according to claim 1, characterized in that: Identifying the vehicle-mounted components associated with the TBOX by parsing the integrated data packet and determining the component relationship; The component relationships include communication transmission relationships, functional dependency relationships in a non-operating state, and functional dependency relationships in an operating state. 10.TBOX integrated vehicle-mounted abnormality detection and warning system, characterized by: The system comprises: The data packet acquisition module is used to acquire the integrated data packet of TBOX; A component relationship determination module, configured to identify the vehicle-mounted components associated with the TBOX by parsing the integrated data packet and determine the component relationship; An integrated anomaly detection module is used to obtain a vehicle-mounted component topology structure by topologically connecting the component relationships, and to perform integrated anomaly detection on the integrated data packet according to the vehicle-mounted component topology structure to obtain an integrated anomaly detection result, wherein the integrated anomaly detection result includes detecting abnormal vehicle-mounted components with integrated anomalies; The warning signal generating module is used to generate an integrated warning signal according to the integrated abnormality detection result, and to update the integrated data packet to obtain an integrated update data packet.

Images