Information monitoring system, vehicle machine and vehicle

Abstract

The utility model discloses an information monitoring system, a vehicle machine and a vehicle. Relates to the technical field of information monitoring, the information monitoring system is connected with a user interface, the information monitoring system comprises a reading module, a classification module, a layout module and a refreshing module, and the reading module is used for reading CAN database files. The classification module is used for classifying and processing the CAN database files and determining the types of the CAN database files. The layout module is used for determining the layout mode of the CAN database file according to the type of the CAN database file and sending the CAN database file and the layout mode of the CAN database file to the refreshing module. And the refreshing module is used for analyzing the CAN database file to obtain the monitoring data, and updating the monitoring data to the user interface based on the layout mode of the CAN database file. According to the invention, the universality of the information monitoring system is enhanced, so that the information monitoring system can adapt to the requirements of business changes.

Description

Technical Field

[0001] This application relates to the field of information monitoring technology, and more specifically, to an information monitoring system, an in-vehicle infotainment system, and a vehicle. Background Technology

[0002] Vehicles typically include a battery management system and an information monitoring system. The information monitoring system collects and processes data from the battery management system in real time and displays it to the user, providing a convenient operating experience. Currently, information monitoring systems are mainly built using the Windows Forms development framework. However, information monitoring systems built using the Windows Forms framework can only read files using one communication protocol and cannot read files using other communication protocols, resulting in limited versatility. Utility Model Content

[0003] This application provides an information monitoring system connected to a user interface. The information monitoring system includes a reading module, a classification module, a layout module, and a refresh module. The classification module is connected to the reading module, the layout module is connected to the classification module, and the refresh module is connected to both the layout module and the user interface. When the information monitoring system is configured for use, the reading module reads a CAN database file and transmits it to the classification module. The classification module classifies the CAN database file, determines its type, and transmits the CAN database file and its type to the layout module. The layout module determines the layout method of the CAN database file based on its type and sends the CAN database file and its layout method to the refresh module. The refresh module parses the CAN database file to obtain monitoring data and updates the monitoring data to the user interface based on the layout method of the CAN database file.

[0004] In some implementations, the information monitoring system is built based on a model-view-view model development pattern and a Windows rendering basic development framework. The reading module includes multiple business interfaces, and at least one of the multiple business interfaces includes a CAN hardware interaction interface.

[0005] In some implementations, the CAN database file includes node data, message data, and signal data. The node data defines the number and names of nodes used by the program to communicate on the CAN bus. The message data describes the messages on the CAN bus, and the signal data defines the physical quantities and states of the messages on the CAN bus. The classification module includes:

[0006] The root node layer is used to receive the CAN database file from the reading module;

[0007] The child node layer, connected to the root node layer, is used to classify and process the CAN database file according to the signal data to determine the type of the CAN database file.

[0008] In some implementations, the signal data includes a status value, and the CAN database file type includes value signals, status signals, and alarm signals. The child node layer is further configured to determine the type of the CAN database file corresponding to the signal data as the value signal when the status value is empty; or,

[0009] The sub-node layer is further configured to, when the state value is a first preset state value, determine the type of the CAN database file corresponding to the signal data as the state signal; or...

[0010] The sub-node layer is also used to determine the type of the CAN database file corresponding to the signal data as the alarm signal when the state value is the second preset state value.

[0011] In some implementations, the CAN database file includes signal data, and the types of the CAN database file include value signal data, status signal data, and alarm signal data. When the type of the CAN database file is value signal data, the layout module is further configured to determine the layout of the CAN database file to display the name, content, and background color of the signal data; or,

[0012] When the type of the CAN database file is the status signal data, the layout module is further configured to obtain the description information and prompt color corresponding to the value description based on the value description of the signal data, and determine the layout mode of the CAN database file to display the description information and the prompt color; or,

[0013] When the type of the CAN database file is the alarm signal data, the layout module is also used to determine the layout of the CAN database file to display the name and background color of the signal data.

[0014] In some implementations, the monitoring data includes the name, content, background color, and descriptive information and prompt color corresponding to the value description of the signal data. When the layout of the CAN database file is determined to display the name, content, and background color of the signal data, the refresh module is further used to display the name, content, and background color of the signal data through the user interface; or,

[0015] When the layout of the CAN database file is determined to display the description information and the prompt color, the refresh module is also used to display the description information and the prompt color through the user interface; or,

[0016] When the layout of the CAN database file is determined to display the name and background color of the signal data, the refresh module is also used to display the name and background color of the signal data through the user interface.

[0017] In some implementations, the CAN database file includes signal data. At the current moment, the refresh module is also used to integrate and encapsulate all monitoring data obtained from parsing all signal data to obtain a signal data model.

[0018] In some implementations, at the next moment, the refresh module is also used to synchronously update the signal data model if the monitoring data changes.

[0019] In some implementations, the information monitoring system further includes a user interface interface for connecting the refresh module and the user interface.

[0020] In some implementations, the CAN database file includes signal data, and the information monitoring system further includes a monitoring module connected to the user interface. The monitoring module is used to monitor whether the value of the signal data remains within a preset data value range, and to send a prompt message if the value of the signal data does not remain within the preset data value range.

[0021] This application also provides a vehicle infotainment system, which includes the information monitoring system described in any of the above embodiments.

[0022] This application also provides a vehicle that includes the information monitoring system of any of the above embodiments; or, the vehicle includes the vehicle-mounted system of any of the above embodiments.

[0023] This application provides an information monitoring system. A classification module categorizes CAN database files read by a reading module to determine the file type. This CAN database file and its type are then transmitted to a layout module. The layout module determines the layout of the CAN database file based on its type and sends the layout and the CAN database file itself to a refresh module. The refresh module can then directly update the monitoring data obtained from parsing the CAN database file to the user interface based on the layout, allowing the user to view and use it. This application eliminates the need to rewrite or compile other programs in the information monitoring system after changing the communication protocol, enhancing its versatility and enabling it to adapt to changing business needs.

[0024] Additional aspects and advantages of this application will be set forth in part in the description which follows, and in part will be obvious from the description, or may be learned by practice of this application. Attached Figure Description

[0025] The above and / or additional aspects and advantages of this application will become apparent and readily understood from the description of the embodiments taken in conjunction with the following drawings, wherein:

[0026] Figure 1 This is a schematic diagram of the structure of an information monitoring system according to some embodiments of this application;

[0027] Figure 2 This is a schematic diagram of the structure of an information monitoring system according to some embodiments of this application;

[0028] Figure 3 This is a schematic diagram of the structure of an information monitoring system according to some embodiments of this application;

[0029] Figure 4 This is a schematic diagram of the structure of an information monitoring system according to some embodiments of this application;

[0030] Figure 5 This is a schematic diagram of the structure of an information monitoring system according to some embodiments of this application;

[0031] Figure 6 This is a schematic diagram of the structure of an information monitoring system according to some embodiments of this application;

[0032] Figure 7 This is a schematic diagram of the structure of an information monitoring system according to some embodiments of this application;

[0033] Figure 8 This is a structural schematic diagram of a vehicle according to some embodiments of this application.

[0034] Explanation of key component symbols:

[0035] 1000 vehicles;

[0036] Car infotainment system 100;

[0037] Information monitoring system 10;

[0038] Read module 11; Service interface 111; CAN hardware interaction interface 1111;

[0039] Classification module 12; Root node layer 121; Child node layer 122; First child node layer 1221; Second child node layer 1222; Third child node layer 1223;

[0040] Layout module 13;

[0041] Refresh module 14;

[0042] User interface 15;

[0043] Monitoring module 16;

[0044] User interface 20;

[0045] Battery Management System 30. Detailed Implementation

[0046] To make the above-mentioned objectives, features, and advantages of this application more apparent and understandable, the specific embodiments of this application are described in detail below with reference to the accompanying drawings. Many specific details are set forth in the following description to provide a thorough understanding of this application. However, this application can be implemented in many other ways different from those described herein, and those skilled in the art can make similar modifications without departing from the spirit of this application. Therefore, this application is not limited to the specific embodiments disclosed below.

[0047] In the description of this application, it should be understood that the terms "center", "length", "upper", "lower", "front", "rear", "vertical", "horizontal", "top", "bottom", "inner", "outer", etc., indicate the orientation or positional relationship based on the orientation or positional relationship shown in the accompanying drawings. They are only for the convenience of describing this application and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application.

[0048] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified.

[0049] In this application, unless otherwise expressly specified and limited, the terms "installation," "connection," "joining," etc., should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral part; they can refer to a mechanical connection or an electrical connection; they can refer to a direct connection or an indirect connection through an intermediate medium; they can refer to the internal communication of two components or the interaction between two components, unless otherwise expressly limited. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.

[0050] In this application, unless otherwise expressly specified and limited, "above" or "below" the second feature can mean that the first feature is in direct contact with the second feature, or that the first feature is in indirect contact with the second feature through an intermediate medium. Furthermore, "above," "on top of," and "over" the second feature can mean that the first feature is directly above or diagonally above the second feature, or simply that the first feature is at a higher horizontal level than the second feature. "Below," "below," and "under" the second feature can mean that the first feature is directly below or diagonally below the second feature, or simply that the first feature is at a lower horizontal level than the second feature.

[0051] A Battery Management System (BMS) is a system used to monitor and manage battery packs. Electric and hybrid vehicles that require power batteries are typically equipped with a BMS. The main function of the BMS is to ensure sufficient safety and good performance of the power battery during vehicle operation and to extend the battery's lifespan. Vehicles also usually have an information monitoring system, which collects and processes data from the BMS in real time and displays it to the user, providing a convenient operating experience. Currently, information monitoring systems are mainly built using the Windows Forms (WF) development framework. While the Windows Forms framework is a Windows development tool from Microsoft, information monitoring systems built using it can only read files using one communication protocol, resulting in limited versatility. How to solve the problem of limited versatility caused by the Windows Forms framework's limitation to reading files using only one communication protocol has become a pressing issue for those skilled in the art. To address these problems, this application provides an information monitoring system (such as...) Figure 1 As shown), vehicle-mounted systems (such as...) Figure 8 (as shown) and vehicles (such as) Figure 8 (As shown).

[0052] Please see Figure 1 and Figure 2 The information monitoring system of this embodiment is connected to a user interface 20. The information monitoring system 10 includes a reading module 11, a classification module 12, a layout module 13, and a refresh module 14. The classification module 12 is connected to the reading module 11, the layout module 13 is connected to the classification module 12, and the refresh module 14 is connected to both the layout module 13 and the user interface 20. When the information monitoring system 10 is configured for use, the reading module 11 reads the CAN database file and transmits it to the classification module 12. The classification module 12 classifies the CAN database file, determines its type, and transmits the CAN database file and its type to the layout module 13. The layout module 13 determines the layout of the CAN database file based on its type and sends it to the refresh module 14. The refresh module 14 parses the CAN database file to obtain monitoring data and updates the monitoring data to the user interface 20 based on the layout of the CAN database file.

[0053] Specifically, please refer to Figure 2 To ensure the normal operation of the vehicle's power battery and extend its lifespan as much as possible, vehicles are typically equipped with a battery management system 30 to control and ensure the normal operation of the power battery, and an information monitoring system 10 to monitor the battery management system 30. The information monitoring system 10 needs to collect data from the battery management system 30 in real time and display it to the user, such as battery pack voltage, current, temperature, battery charging status, and battery health status. This information helps users intuitively understand the current operating status of the battery. Monitoring this data ensures that the battery operates within a safe operating range, preventing potential safety problems such as overcharging, over-discharging, and overheating. The information monitoring system 10 also needs to record and analyze long-term battery pack operating data to predict the power battery's lifespan and performance degradation. In addition, the information monitoring system 10 also has functions such as online monitoring of the power battery status, fault diagnosis, and alarm notification. For example, if an abnormality occurs in the power battery, the host computer can quickly issue an alarm, enabling the user to take timely measures to prevent the problem from escalating. Therefore, the information monitoring system 10 is of great significance for ensuring the safe and efficient operation of the power battery, preventing potential safety risks, and optimizing the use and maintenance strategies of the power battery.

[0054] Currently, the Windows Forms development framework is a relatively outdated framework. For the information monitoring system 10 developed using the Windows Forms development framework, the business code within the information monitoring system 10 (i.e., the code related to monitoring the battery management system) is too tightly coupled with the code of the Windows Forms development framework itself. The information monitoring system 10 built using the Windows Forms development framework can only read files of one communication protocol and cannot read files of other communication protocols. This means that after the communication protocol is changed (for example, the way the information monitoring system 10 obtains communication files is changed from the CAN communication network to another communication network), relevant personnel need to re-modify and recompile the relevant code of the information monitoring system 10 so that the information monitoring system 10 can adapt to the new communication network type. This seriously reduces the versatility of the information monitoring system 10.

[0055] Furthermore, in this application, the CAN database file (also known as the DBC file) is a specific implementation and interpretation of the CAN communication protocol. Therefore, the DBC file generated by extracting corresponding information from the CAN communication protocol can accurately reflect the various types of information data transmitted by the CAN communication network. The information monitoring system 10 provided in this application uses the CAN database file as the carrier of the CAN communication signal decoding algorithm of the program, and abstracts and encapsulates the structure of the DBC file. By loading the DBC file, the reception and transmission of signals can be encoded and decoded using a unified algorithm interface.

[0056] For more details, please refer to Figure 1 The information monitoring system 10 includes a reading module 11, a classification module 12, a layout module 13, and a refresh module 14. These modules are connected sequentially, with the refresh module 14 connected to a user interface 20. The reading module 11 reads the CAN database file and transmits it to the classification module 12. The CAN database file is a text file containing data for communication on the CAN bus. The classification module 12 classifies the CAN database file, determines its type, and transmits the CAN database file and its type to the layout module 13. The layout module 13 determines the layout of the CAN database file based on its type and sends it to the refresh module 14. The refresh module 14 parses the CAN database file, obtains monitoring data, and updates the monitoring data to the user interface 20 based on the layout of the CAN database file. The types and layouts of the CAN database files will be explained in detail below.

[0057] Furthermore, the CAN database file content mainly includes node data, message data, and signal data. Node data defines the number and names of nodes used for communication on the CAN bus. Message data describes messages on the CAN bus, including message ID, name, length, and period. Message data is the basic unit of CAN bus communication and is used to transmit data between devices on the CAN bus. Signal data defines the name, length, position, unit, factor, and range of each signal in the CAN message. Signal data is the data element in the message, used to represent a specific physical quantity or state.

[0058] Understandably, the information monitoring system provided in this application classifies the CAN database files read by the reading module to determine the type of the CAN database files. It then transmits the CAN database files and their types to the layout module. The layout module determines the layout method of the CAN database files based on their types and sends the layout method and the CAN database files to the refresh module. This allows the refresh module to directly update the monitoring data obtained from parsing the CAN database files to the user interface based on the layout method, enabling user viewing. After changing the communication protocol, this application only requires updating the CAN database files corresponding to the communication protocol, without rewriting or compiling other programs in the information monitoring system. This enhances the versatility of the information monitoring system, allowing it to adapt to changing business needs.

[0059] In some implementations, please refer to Figure 3 The information monitoring system is built based on the model-view-view model development mode and the Windows presentation basic development framework. The reading module includes multiple business interfaces 111, and the multiple business interfaces 111 include at least one CAN hardware interaction interface 1111.

[0060] It is understandable that the Model-View-ViewModel development pattern refers to the MVVM (Model-View-ViewModel) development pattern, and the Windows Presentation Foundation (WPF) development framework refers to the WPF (Windows Presentation Foundation) framework. The WPF framework provides powerful data binding, templating, styling, and theme capabilities. It also employs vector graphics and hardware acceleration technology, supporting display devices of various resolutions and better utilizing the system's image processing units to provide high-quality graphics rendering and smooth animation effects. From a design perspective, the WPF framework uses an XML-based declarative programming model, defining the user interface through XAML (Extensible Application Markup Language), and employs the Model-View-ViewModel development pattern. This separates interface design from code logic, improving code maintainability and readability. Furthermore, the WPF framework supports collaborative development by multiple users, such as using Git. Therefore, using the WPF framework to build the information monitoring system 10 in this application can also improve the efficiency of building the information monitoring system 10.

[0061] In some implementations, please refer to Figure 3 The information monitoring system 10 is developed using a combination of Inversion of Control (IoC) and IHost general-purpose host.

[0062] Understandably, the Inversion of Control (IoC) container supports dependency injection and mock object functionality, making testing and debugging more convenient. Developers can easily replace actual objects with mock objects to simulate different scenarios and conditions for testing. Simultaneously, the IoC container provides a unified logging and exception handling mechanism, facilitating rapid problem location and resolution. Furthermore, through the IHost interface, applications within the Windows Presentation Basic Development Framework can better integrate and coordinate various components and services, achieving more efficient resource management and more stable operation. Moreover, the IHost interface offers flexible extensibility, allowing developers to customize and extend application functionality as needed. In this application, multiple business interfaces 111 can all be IHost interfaces.

[0063] In some implementations, please refer to Figure 4The CAN database file includes node data, message data, and signal data. Node data defines the number and names of nodes used for communication on the CAN bus. Message data describes messages on the CAN bus, and signal data defines the physical quantities and states of messages on the CAN bus. The classification module 12 includes a root node layer 121 and a child node layer 122. The root node layer 121 receives the CAN database file from the reading module. The child node layer 122 is connected to the root node layer 121 and is used to classify the CAN database file according to the signal data to determine the type of the CAN database file.

[0064] Specifically, the CAN database file content mainly includes node data, message data, and signal data. Node data defines the number and names of nodes used for communication on the CAN bus. Message data describes messages on the CAN bus, including message ID, name, length, and period. Message data is the basic unit of CAN bus communication and is used to transmit data between devices on the CAN bus. Signal data defines the name, length, position, unit, factor, and range of each signal in the CAN message. Signal data is the data element in the message, used to represent specific physical quantities or states.

[0065] Specifically, the classification module 12 adopts a tree structure to classify CAN database files according to signal data. The root node layer 121 is used to read CAN database files from the reading module 11 and to store the CAN database files. The child node layer 122 is used to process the CAN database files according to the signal data to determine the type of the CAN database files. The classification process will be explained in more detail below.

[0066] In some implementations, please refer to Figure 5 The sub-node layer 122 includes a first sub-node layer 1221, a second sub-node layer 1222, and a third sub-node layer 1223. The first sub-node layer 1221 stores node data for signal data, the second sub-node layer 1222 stores message data for signal data, and the third sub-node layer 1223 stores signal data for signal data. It is also used to classify and process the CAN database file according to the signal data to determine the type of the CAN database file.

[0067] Specifically, the first sub-node layer 1221 is used to store the node data contained in the CAN database file; the second sub-node layer 1222 is used to store the message data contained in the CAN database file; and the third sub-node layer 1223 is used to store the signal data contained in the CAN database file. In the third sub-node layer 1223, this application continues to classify the signal data at the level of signal data, dividing the signal data contained in the CAN database file into value signals, status signals, and alarm signals based on the status values ​​of the signal table. The classification process will be explained in more detail below.

[0068] In some implementations, please refer to Figure 4 The signal data includes status values, and the CAN database file types include value signals, status signals, and alarm signals. The sub-node layer 122 is further configured to determine the type of the CAN database file corresponding to the signal data as a value signal when the status value is empty. Alternatively, the sub-node layer 122 is further configured to determine the type of the CAN database file corresponding to the signal data as a status signal when the status value is a first preset status value. Alternatively, the sub-node layer 122 is further configured to determine the type of the CAN database file corresponding to the signal data as an alarm signal when the status value is a second preset status value.

[0069] Specifically, the signal data contains a status value that represents the data type of the signal data itself. The specific values ​​of the status values ​​can be multiple. By consulting a status value table, the meaning of each status value can be found. The meaning of the status value is the type of the signal data itself, i.e., the type of the CAN database file. When the status value is empty, the child node layer 122 determines the type of the CAN database file corresponding to the signal data as a value signal. When the status value is a first preset status value, the child node layer 122 also determines the type of the CAN database file corresponding to the signal data as a status signal. When the status value is a second preset status value, the child node layer 122 also determines the type of the CAN database file corresponding to the signal data as an alarm signal. Both the first and second preset status values ​​are set by the operator, and the number of both preset status values ​​can be set to one, two, or more.

[0070] In some implementations, please refer to Figure 1The CAN database file includes signal data. The types of CAN database files include value signal data, status signal data, and alarm signal data. When the CAN database file type is value signal data, the layout module 13 is further used to determine the layout of the CAN database file to display the name, content, and background color of the signal data. Alternatively, when the CAN database file type is status signal data, the layout module 13 is further used to obtain the description information and indicator color corresponding to the value description based on the signal data's value description, and determine the layout of the CAN database file to display the description information and indicator color. Alternatively, when the CAN database file type is alarm signal data, the layout module 13 is further used to determine the layout of the CAN database file to display the name and background color of the signal data.

[0071] Specifically, after obtaining the type of the CAN database file, the layout module 13 can determine the layout method of the CAN database file based on its type. The layout method of the CAN database file refers to how the user interface 20 displays the CAN database file. When the CAN database file type is value signal data, the layout module 13 further determines the layout method to display the name, content, and background color of the signal data. When the CAN database file type is status signal data, the layout module 13 further obtains the description information and prompt color corresponding to the value description based on the signal data's value description, and determines the layout method to display the description information and prompt color. When the CAN database file type is alarm signal data, the layout module 13 further determines the layout method to display the name and background color of the signal data.

[0072] In some implementations, please refer to Figure 1 The monitoring data includes the name, content, background color, and corresponding descriptive information and indicator colors of the signal data values. When the CAN database file layout is determined to display the name, content, and background color of the signal data, the refresh module 14 is also used to display the name, content, and background color of the signal data through the user interface. (This is repeated three times in the original text.)

[0073] It is understood that monitoring data refers to the data obtained by the refresh module 14 after parsing the CAN database file. Monitoring data includes the name, content, background color, and corresponding descriptive information and prompt colors of the signal data values. The refresh module 14 refreshes the content displayed on the user interface 20 according to the layout of the CAN database file determined by the layout module 13. When the layout of the CAN database file is determined to display the name, content, and background color of the signal data, the refresh module 14 is also used to display the name, content, and background color of the signal data through the user interface. When the layout of the CAN database file is determined to display descriptive information and prompt colors, the refresh module 14 is also used to display descriptive information and prompt colors through the user interface. When the layout of the CAN database file is determined to display the name and background color of the signal data, the refresh module 14 is also used to display the name and background color of the signal data through the user interface.

[0074] In some implementations, please refer to Figure 1 The refresh module 14 is also used to create new dependency objects, new dependency properties, and new binding sources.

[0075] It is understandable that creating new dependency objects, creating new dependency properties, and creating new binding sources are steps executed at the program level during the process of refreshing the display content of the user interface 20 by the refresh module 14. Among these, the dependency object is the main body using the binding function, the dependency property is the specific attribute on the main body using the binding function, and the binding source is the signal data model associated with the user interface using the binding function. The signal data model will be explained in more detail below.

[0076] In some implementations, please refer to Figure 1 The CAN database file includes signal data. At the current moment, the refresh module 14 is also used to integrate, encapsulate, and parse all the monitoring data obtained from all the signal data to obtain the signal data model.

[0077] Specifically, the construction of the signal data model is based on the classification of signal data. The signal data model is a packaging of the content of the signal data. When users or operators need to extract signal data from the information monitoring system 10, they can directly extract the signal data model from the information monitoring system 10, thereby avoiding the need for users or operators to query all CAN database files in the information monitoring system 10 and reducing the workload of users or operators.

[0078] In some implementations, please refer to Figure 1 In the next moment, the refresh module 14 is also used to synchronously update the signal data model when the monitoring data changes.

[0079] Understandably, when the signal data in the CAN database file changes, the signal data model also needs to be updated synchronously to avoid users or operators retrieving incorrect signal data when retrieving the signal data model from the information monitoring system 10 for querying or using signal data.

[0080] In some implementations, please refer to Figure 6 The information monitoring system 10 also includes a user interface interface 15, which is used to connect the refresh module 14 and the user interface 20.

[0081] Specifically, the refresh module 14 and the user interface 20 also need to be connected through the user interface interface 15. In this application, the user interface interface 15 can use the Notification Property Changed (IPC) interface. The Notification Property Changed interface is an interface used in programming to implement the notification property change function. This application uses the Notification Property Changed interface to implement data-driven updates within the user interface 20. Through the user interface interface 15, this application can separate the user interface 20 from the data processing part (i.e., the information monitoring system 10) to improve the versatility of the information monitoring system 10.

[0082] In some implementations, please refer to Figure 7 The CAN database file includes signal data. The information monitoring system 10 also includes a monitoring module 16, which is connected to the user interface 20. The monitoring module 16 is used to monitor whether the value of the signal data is within the preset data value range, and to send a prompt message if the value of the signal data is not within the preset data value range.

[0083] Specifically, this application also adds a signal data waveform monitoring function for the signal data value. This signal data waveform monitoring function is implemented through monitoring module 16. Monitoring module 16 uses a red auxiliary line to indicate whether the signal value is within a suitable range, based on the upper and lower limits of the signal data. For example, if the signal data value exceeds the range indicated by the red auxiliary line, monitoring module 16 will alert the user or operator by emitting an alarm sound, displaying an alarm light, and providing a voice prompt. Simultaneously, monitoring module 16 also adds two reference axes perpendicular to the time axis to help operators finely analyze the changes in signal data within a time range.

[0084] In summary, this application provides an information monitoring system 10. The classification module 12 classifies the CAN database file read by the reading module 11 to determine its type, and then transmits the CAN database file and its type to the layout module 13. The layout module 13 determines the layout method of the CAN database file based on its type and sends the layout method and the CAN database file to the refresh module 14. This allows the refresh module 14 to directly update the monitoring data obtained from parsing the CAN database file to the user interface based on the layout method, for user viewing. After changing the communication protocol, this application only requires updating the CAN database file corresponding to the communication protocol, without rewriting or compiling other programs in the information monitoring system. This enhances the versatility of the information monitoring system, enabling it to adapt to changing business needs.

[0085] In some implementations, please refer to Figure 8 This application also provides a vehicle infotainment system 100, which includes the information monitoring system 10 in any of the above embodiments.

[0086] In some implementations, please refer to Figure 1 and Figure 8 This application also provides a vehicle 1000, which includes a vehicle-mounted system 100, or an information monitoring system 10 in any of the above embodiments.

[0087] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification. At the same time, other implementation methods can be derived from the above embodiments, so that structural and logical substitutions and changes can be made without departing from the scope of this disclosure.

[0088] The above embodiments merely illustrate several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. An information monitoring system, characterized in that, The information monitoring system is connected to a user interface, and the information monitoring system includes: Read module; A classification module is connected to the reading module; A layout module is connected to the classification module; The refresh module is connected to the layout module and the user interface; When the information monitoring system is configured for use, the reading module reads the CAN database file and transmits it to the classification module. The classification module classifies the CAN database file, determines its type, and transmits the CAN database file and its type to the layout module. The layout module determines the layout of the CAN database file based on its type and sends it to the refresh module. The refresh module parses the CAN database file to obtain monitoring data and updates the monitoring data to the user interface based on the layout of the CAN database file.

2. The information monitoring system according to claim 1, characterized in that, The information monitoring system is built based on the model-view-view model development pattern and the Windows presentation basic development framework. The reading module includes multiple business interfaces, and at least one of the multiple business interfaces includes a CAN hardware interaction interface.

3. The information monitoring system according to claim 1, characterized in that, The CAN database file includes node data, message data, and signal data. The node data is used to define the number and name of nodes that the program communicates on the CAN bus. The message data describes the messages on the CAN bus. The signal data is used to define the physical quantities and states of the messages on the CAN bus. The classification module includes: The root node layer is used to receive the CAN database file from the reading module; The child node layer, connected to the root node layer, is used to classify and process the CAN database file according to the signal data to determine the type of the CAN database file.

4. The information monitoring system according to claim 3, characterized in that, The signal data includes status values, and the CAN database file types include value signals, status signals, and alarm signals. The child node layer is further configured to determine the type of the CAN database file corresponding to the signal data as the value signal when the status value is empty; or... The sub-node layer is further configured to, when the state value is a first preset state value, determine the type of the CAN database file corresponding to the signal data as the state signal; or... The sub-node layer is also used to determine the type of the CAN database file corresponding to the signal data as the alarm signal when the state value is the second preset state value.

5. The information monitoring system according to claim 1, characterized in that, The CAN database file includes signal data, and the types of the CAN database file include value signal data, status signal data, and alarm signal data. When the type of the CAN database file is value signal data, the layout module is further used to determine the layout of the CAN database file to display the name, content, and background color of the signal data; or... When the type of the CAN database file is the status signal data, the layout module is further configured to obtain the description information and prompt color corresponding to the value description based on the value description of the signal data, and determine the layout mode of the CAN database file to display the description information and the prompt color; or, When the type of the CAN database file is the alarm signal data, the layout module is also used to determine the layout of the CAN database file to display the name and background color of the signal data.

6. The information monitoring system according to claim 5, characterized in that, The monitoring data includes the name, content, background color, and descriptive information and prompt color corresponding to the value description of the signal data. When the layout of the CAN database file is determined to display the name, content, and background color of the signal data, the refresh module is also used to display the name, content, and background color of the signal data through the user interface; or... When the layout of the CAN database file is determined to display the description information and the prompt color, the refresh module is also used to display the description information and the prompt color through the user interface; or, When the layout of the CAN database file is determined to display the name and background color of the signal data, the refresh module is also used to display the name and background color of the signal data through the user interface.

7. The information monitoring system according to claim 1, characterized in that, The CAN database file includes signal data. At the current moment, the refresh module is also used to integrate, encapsulate, and parse all the monitoring data obtained from all the signal data to obtain a signal data model.

8. The information monitoring system according to claim 7, characterized in that, In the next moment, the refresh module is also used to synchronously update the signal data model when the monitoring data changes.

9. The information monitoring system according to claim 1, characterized in that, The information monitoring system also includes a user interface interface, which is used to connect the refresh module and the user interface.

10. The information monitoring system according to claim 1, characterized in that, The CAN database file includes signal data, and the information monitoring system also includes a monitoring module connected to the user interface. The monitoring module is used to monitor whether the value of the signal data remains within a preset data value range, and to send a prompt message if the value of the signal data does not remain within the preset data value range.

11. A vehicle infotainment system, characterized in that, include: The information monitoring system according to any one of claims 1-10.

12. A vehicle, characterized in that, include: The information monitoring system according to any one of claims 1-10; or, The vehicle infotainment system as described in claim 11.

Images