Packet monitoring updating method and device, equipment and storage medium

Abstract

The application discloses a message monitoring updating method and device, equipment and a storage medium, and relates to the technical field of vehicle communication. The method comprises the following steps: acquiring message information, sending an instruction to a controller to enable the controller to load a controller boot program and execute the controller boot program, obtaining equipment information, monitoring according to the equipment information, obtaining a working mode, updating and processing the message information according to a routing strategy based on the working mode, and obtaining updated message. The vehicle-mounted gateway is dynamically updated, the message routing and equipment monitoring are optimized, the communication efficiency is improved, and the stability and flexibility of the vehicle-mounted gateway system are enhanced.

Description

Technical Field

[0001] This invention relates to the field of vehicle communication technology, and in particular to a message monitoring and updating method, apparatus, device, and storage medium. Background Technology

[0002] With the development of automotive electronics and intelligence, in-vehicle network systems are becoming increasingly complex. The number of electronic control units (ECUs) within a vehicle is constantly increasing, requiring efficient communication networks for data exchange and collaborative operation. The in-vehicle gateway, acting as a router between various buses within the vehicle, plays a crucial role in communication between different domain controllers. In-vehicle communication networks typically consist of communication nodes such as CAN (Controller Area Network), Ethernet, and LIN (Serial Communication Network), which together form the vehicle's neural network.

[0003] Currently, message information is read through software-based message routing, enabling routing of messages between nodes using the same protocol. Signal routing between different buses requires adding specific signal routing code to the software. This function-based gateway design allows different domain controllers within the vehicle to communicate and exchange data.

[0004] However, each time the routing service is updated, developers need to update the entire controller software using a compiler, a complex and cumbersome process. Traditional gateways typically limit their signal routing functionality to simple signal filling. For scenarios requiring more complex operations such as signal calculation and offsetting, developers need to redevelop the signal operation functions. Furthermore, the function-based gateway design necessitates the intervention of development tools for each update, increasing continuous investment in these tools. Each update involves updating the entire controller software, which not only increases development costs but also amplifies software risks, potentially impacting system stability and security. Therefore, there is an urgent need for a service-oriented method for reading message information from vehicle gateways to reduce the complexity of the update process and mitigate the risks involved. Summary of the Invention

[0005] The main objective of this application is to provide a message monitoring and update method, apparatus, device, and storage medium, aiming to solve the technical problem of how to reduce the update process and thus improve communication efficiency.

[0006] To achieve the above objectives, this application proposes a message monitoring and update method, which is applied to an in-vehicle gateway system. The in-vehicle gateway system includes a controller and a service configuration device. The controller includes a controller bootloader and a routing policy. The method includes:

[0007] Obtain message information;

[0008] A command is sent to the controller to cause the controller to load and execute the controller boot program to obtain device information;

[0009] The operating mode is determined by monitoring the equipment information.

[0010] Based on the described working mode, the message information is updated according to the routing policy to obtain the updated message.

[0011] In one embodiment, the step of sending a command to the controller to cause the controller to load and execute the controller bootstrap to obtain device information includes:

[0012] An initialization command is sent to the controller to trigger the controller to power on and enter the initialization phase;

[0013] Once the controller is detected to have entered the initialization phase, a control command is sent to cause the controller to execute the controller boot program.

[0014] Identify the signals from the controller boot program to obtain device information.

[0015] In one embodiment, the step of identifying the signal of the controller bootloader and obtaining device information includes:

[0016] After the controller executes the controller bootstrap, it enters listening mode;

[0017] The controller bootloader identifies signals to monitor and identify device status and communication requests, thereby obtaining identification signals;

[0018] Based on the identification signal, device information is obtained by parsing it. The device information includes device identifier, version information, network address, and functional status.

[0019] In one embodiment, the step of monitoring based on the device information to obtain the operating mode includes:

[0020] The device information is monitored and analyzed to obtain processed device information;

[0021] The processed equipment information is then processed to obtain monitoring results;

[0022] The monitoring results are analyzed according to preset conditions to determine the working mode.

[0023] In one embodiment, the step of analyzing the monitoring results according to preset conditions to determine the working mode includes:

[0024] When the monitoring results indicate that the service configuration device has a connection request, the working mode is determined to be service update mode, the routing table data of the routing policy is updated and saved;

[0025] When the monitoring result indicates that there is no connection request for the service configuration device, the working mode is determined to be the normal working mode, and the routing table data of the stored routing policy is read and applied.

[0026] In one embodiment, the step of updating the packet information according to the routing policy based on the working mode to obtain the updated packet includes:

[0027] Based on the operating mode, determine the routing strategy for the message information;

[0028] Based on the routing policy, the packet parameters are adjusted and updated according to the packet information to generate the updated packet.

[0029] In one embodiment, after the step of updating the packet information according to the routing policy based on the working mode to obtain the updated packet, the process includes:

[0030] When the updated message indicates that the device performance indicators are abnormal, the fault diagnosis mechanism is executed.

[0031] Adjust message routing policies or service packet configurations to optimize network communication and system response.

[0032] Furthermore, to achieve the above objectives, this application also proposes a message monitoring and updating device, which includes:

[0033] The acquisition module is used to acquire message information;

[0034] The acquisition module is also used to send instructions to the controller so that the controller loads and executes the controller bootloader to obtain device information;

[0035] The monitoring module is used to monitor the equipment information and determine the operating mode.

[0036] The execution module is used to update the message information according to the routing policy based on the working mode to obtain the updated message.

[0037] In addition, to achieve the above objectives, this application also proposes a message monitoring and updating device, the device comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, the computer program being configured to implement the steps of the message monitoring and updating method as described above.

[0038] In addition, to achieve the above objectives, this application also proposes a storage medium, which is a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, it implements the steps of the message monitoring and update method described above.

[0039] In addition, to achieve the above objectives, this application also provides a computer program product, which includes a computer program that, when executed by a processor, implements the steps of the message monitoring and update method described above.

[0040] This application obtains message information, sends instructions to the controller, causing the controller to load and execute the controller bootstrap program to obtain device information, monitors the device based on the device information to determine the operating mode, and updates the message information according to the routing policy based on the operating mode to obtain the updated message. By dynamically updating the vehicle gateway, message routing and device monitoring are optimized, communication efficiency is improved, and the stability and flexibility of the vehicle gateway system are enhanced. Attached Figure Description

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

[0042] Figure 1 This is a flowchart illustrating the first embodiment of the message monitoring and updating method of this application;

[0043] Figure 2 This is a structural block diagram of the vehicle-mounted gateway system of this application;

[0044] Figure 3 This is a schematic diagram of the configuration interface for the first embodiment of the message monitoring and update method of this application;

[0045] Figure 4 This is a routing table template diagram of the first embodiment of the message monitoring and update method of this application;

[0046] Figure 5 This is a service editing interface diagram of the first embodiment of the message monitoring and update method of this application;

[0047] Figure 6 This is a flowchart illustrating the second embodiment of the message monitoring and updating method of this application;

[0048] Figure 7 This is a schematic diagram of the module structure of the message monitoring and updating device according to an embodiment of this application;

[0049] Figure 8This is a schematic diagram of the device structure of the hardware operating environment involved in the message monitoring and update method in this application embodiment.

[0050] The purpose, features, and advantages of this application will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0051] It should be understood that the specific embodiments described herein are merely illustrative of the technical solutions of this application and are not intended to limit this application.

[0052] To better understand the technical solution of this application, a detailed description will be provided below in conjunction with the accompanying drawings and specific implementation methods.

[0053] The main solution of this application embodiment is: by obtaining message information, sending instructions to the controller, so that the controller loads and executes the controller bootstrap program to obtain device information, monitoring based on the device information to obtain the working mode, and updating the message information according to the routing policy based on the working mode to obtain the updated message.

[0054] Currently, message routing is achieved through message routing functionality within the software, enabling routing of messages from nodes using the same protocol. Signal routing between different buses requires adding specific signal routing code to the software. This function-based gateway design allows different domain controllers in a vehicle to communicate and exchange data. However, each time the routing service is updated, developers need to update the entire controller software using a compiler, a complex and cumbersome process. Traditional gateway signal routing functionality is typically limited to simple signal filling. For scenarios requiring more complex operations such as signal calculation and offsetting, developers need to redevelop the signal operation functions. Furthermore, the function-based gateway design necessitates the intervention of development tools with each update, increasing continuous investment in development tools. Each update involves updating the entire controller software, which not only increases development costs but also amplifies software risks, potentially impacting system stability and security.

[0055] Based on this, embodiments of this application provide a message monitoring and update method, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of the message monitoring and updating method of this application.

[0056] In this embodiment, the message monitoring and update method is applied to the vehicle gateway system, referring to... Figure 2 , Figure 2This is a structural block diagram of an in-vehicle gateway system. The in-vehicle gateway system includes a controller 101 and a service configuration device 102. The controller 101 includes a controller boot program area 201 and a routing policy area 202. The controller boot program area 201 is used to update the controller runtime program, and the routing policy area 202 is used to update the routing table service data and store the routing information table. The method includes steps S10 to S40:

[0057] Step S10: Obtain message information.

[0058] It should be noted that the system first receives message information from different electronic control units (ECUs) through various communication interfaces. These messages contain vehicle status, control commands, and other important data. Subsequently, the system parses and preprocesses these messages to ensure the integrity and accuracy of the information.

[0059] Step S20: Send a command to the controller so that the controller loads and executes the controller boot program to obtain device information.

[0060] It's important to note that sending commands to the controller is a crucial operation in the vehicle gateway system, triggering the entire communication and information processing flow. Once the command is sent and the controller receives the signal, it loads and executes its built-in controller bootloader. This bootloader is the core of system initialization and configuration, responsible for starting system services, checking system integrity, and loading the necessary runtime environment. During execution, the controller bootloader performs a series of self-checks and configuration steps to ensure the system is in optimal startup condition. After completing the controller bootloader, it collects device information from various ECUs within the vehicle. This information may include critical data such as the ECU model, firmware version, current operating status, and their location on the network.

[0061] Furthermore, an initialization command is sent to the controller to trigger its power-on and initiate the initialization phase. Sending the initialization command to the controller is the first and crucial step in starting the vehicle gateway system, as it triggers the controller's power-on process and guides the system into the initialization phase. During this phase, the controller executes a series of predefined startup procedures, including hardware checks, memory allocation, and system service loading, ensuring all components are working together and ready. During initialization, the controller also performs self-diagnostics, verifying the functionality of critical hardware and software components and detecting any potential configuration problems or malfunctions. This self-diagnostics includes not only checks of internal components but may also involve assessing the status of connected external devices and the network. In addition, sending the initialization command activates the system's security mechanisms, ensuring that necessary security standards are met during system startup and operation. This includes the initialization of encrypted communication, access control settings, and preventative measures against any security vulnerabilities.

[0062] Furthermore, once the controller enters the initialization phase, a control command is sent to instruct the controller to execute the controller bootloader. Once the controller completes execution and enters normal operating mode, the vehicle gateway system begins performing its core functions, such as message routing, signal processing, and device monitoring.

[0063] Furthermore, the system identifies signals from the controller bootloader and acquires device information. Specifically, after the controller executes the controller bootloader, it enters listening mode. After the controller executes the controller bootloader and successfully initializes, the system automatically switches to listening mode. This stage is crucial for ensuring the smooth operation of the vehicle network and accurate device management. In listening mode, the controller continuously monitors network traffic, identifying and responding to specific signals from the controller bootloader. These signals may include diagnostic requests, device status updates, or communication needs.

[0064] The system identifies signals from the controller bootloader to monitor and recognize device status and communication requests, thus generating identification signals. Through real-time monitoring of these signals, the system can quickly identify the current status of each device in the network and any communication requests, thereby obtaining identification signals. These signals not only reflect the online status of the devices but may also indicate inter-device interaction needs or potential configuration problems.

[0065] Based on the identified signals, the system analyzes them to obtain device information, including device identifier, version information, network address, and functional status. Following the identification of the signals, the system further performs a parsing operation, involving in-depth analysis of the signal content to extract valuable device information. The parsed device information is extremely detailed, including the device identifier, software or hardware version information, its address in the network, and its respective functional status. This information is crucial for understanding the architecture and dynamics of the entire vehicular network.

[0066] Step S30: Monitor the equipment information to obtain the working mode.

[0067] It should be noted that the vehicle gateway system monitors device information after power-on to determine its operating mode. When the ECU powers on, it first enters the controller bootloader area and remains there for 20 milliseconds, during which time the ECU listens for information from the bus devices. If the ECU does not receive a command from the bootloader area within this time, it will operate in normal mode. Conversely, if the ECU receives a command from the controller bootloader area within the preset time, it will enter service update mode. This means the ECU will remain in the controller bootloader area, ready to receive update operations, such as updating routing data or the bootloader itself.

[0068] In normal operating mode, the ECU reads information from the routing table during startup and performs error detection. Once initialization is complete, the ECU periodically invokes the lower-level routing policy to process received messages. Messages may include signals from different vehicle buses, such as CAN, LIN, or Ethernet. Through message mirroring, received messages are copied and sent to the lower-level routing policy for processing. The policy determines the message type—whether it is a routed message, a service message, or an invalid message—based on the routing table information in memory, and takes appropriate actions, such as routing valid messages to the correct bus or performing signal processing.

[0069] When the routing table or ECU firmware needs to be updated, the service configuration device can enter service update mode by connecting to the ECU. In this mode, the user can edit the service package and update the routing information through the service configuration device, and then download the new service package to the routing information table via a bootloader. This method simplifies the update process and reduces the risks associated with updating the entire controller software.

[0070] Step S40: Update the message information according to the routing policy based on the working mode to obtain the updated message.

[0071] It should be noted that updating message information according to different operating modes is an important function. When the ECU is in normal operating mode, its main task is to process the received messages according to the routing strategy. This process includes message routing, message identifier modification, message period modification, and data field length modification, among other aspects. For signal processing, the system supports operations such as signal offset, linear calculation, substitution, logical AND, and OR operations to meet the needs of different application scenarios.

[0072] Furthermore, based on the working mode, a routing strategy for message information is determined. Based on the routing strategy, message parameters are adjusted according to the message information to update and generate updated messages. When it is necessary to update the routing information table or add new services, the system switches to service update mode. In this mode, the service configuration device can connect to the ECU. By updating the data in the routing information table, the service configuration device can import routing tables, create new service packages, edit service packages, export service packages, and distribute service packages, making service package management more convenient. A service package includes message services and signal services, and each service package is independent and can be updated separately without affecting other services. In this embodiment, the service configuration device is a host computer, such as... Figure 3 The configuration interface shown is divided into eight main areas: Area 1 is the toolbar, Area 2 is user information, Area 3 is the routing packet data display area, Area 4 is the advanced settings area, Area 5 is the connection settings area, Area 6 is the start button distribution area, Area 7 is the print output area, and Area 8 is the host computer status bar. Area 1 includes the following functions: New, Data Import, Data Export, Reset, Download Template, Device Detection, Device Connection, Device Disconnection, Search, Filter, Delete Conditions, Select All, Invert Selection, Generate Executable Program, Help, and Suggestions. New opens a new window; Data Import includes importing the routing table and reading service packets. The routing table is a table containing only routing services, while the service packet is in XML format and includes both routing and signal services; Data Export exports the service packet to the local hard drive for future editing; the Reset function restores edited service data; and the Download Template function saves a template from the host computer. Figure 4 The diagram shows a routing table template. Users can edit routing data in this template and import it directly into the host computer using the data import function. The device detection, device connection, and device disconnection functions are used by the host computer to establish communication connections with the corresponding gateway slave devices. The search, filter, delete condition, select all, and deselect functions are for performing routine operations on the service data of Region 3. The executable program generation function is used by the host computer to convert service data into hexadecimal data for use by the service delivery function.

[0073] Area 2 is the user information area, displaying current user information and hardware environment. When the device detection function in Area 1 is enabled, Area 2 displays the hardware environment currently available for connecting to the lower-level device.

[0074] Zone 3 is the routing packet data display area. When the data import function is enabled in Zone 1 and the table file shown in the figure is selected, the host computer's background algorithm automatically parses the routing table file and displays it in Zone 3. Alternatively, right-clicking in Zone 3 will bring up a pop-up window... Figure 5 The diagram shows the service editing interface. The service editing interface is divided into three functional areas: functional area 1 is the message routing editing area, functional area 2 is the signal service editing interface, and functional area 3 is the button area.

[0075] Area 4 is the advanced settings area, where you can configure various advanced functions, including: key algorithm import, executable program format, data stream file save location, lower-level machine routing table data storage location, and channel mapping. The channel mapping function maps virtual channels to actual channels on the vehicle gateway system. If you are directly creating new routing packet data, you must first configure channel mapping.

[0076] Zone 5 is for connection settings, including: ECU selection, device transmission channel settings, device baud rate settings, service delivery process settings, and host computer identity settings.

[0077] Area 6 is the dedicated area for the start / stop menu, area 7 is the print output area, and area 8 is the status bar. The status display in area 8 is related to the settings in area 1.

[0078] Once the update is complete, the ECU returns to normal operating mode, at which point the system will process message information according to the latest routing policy. Specifically, the ECU first checks the data in the routing table information area to ensure that all valid routing services are loaded into memory. Subsequently, whenever a new message is received, the system uses the message mirroring function to send the message to the lower-level routing policy for processing. The routing policy filters the received messages based on the routing information table in memory. If a message requires routing, it is copied to a designated memory area, processed as needed, and then packetized and sent. When the updated message indicates abnormal device performance indicators, a fault diagnosis mechanism is executed to adjust the message routing policy or service packet configuration to optimize network communication and system response. In this way, the updated message can be forwarded according to the latest routing rules. The specific forwarding process is as follows: first, click "Download Template" in area 1 to download the template; second, edit the routing table data in the table and then import the routing table data table into the upper-level computer. After the import is complete, the successfully imported routing data is displayed in area 3. Optionally, create new service package data. After the service package data is created, the successfully created routing data will also be displayed in Zone 3. After the service package data is added, channel mapping is performed to associate the virtual channel with the actual channel of the lower-level machine. Third step: Edit service data and filter invalid service packet data. Fourth step: Generate a lower-level machine executable program from the service package data. Fifth step: Scan devices. The upper-level machine scans for connected devices. After the device scan is complete, the scanned devices will be displayed in Zone 2. Sixth step: In the connection settings in Zone 5, select the lower-level ECU from the drop-down menu and select the device channel to connect to the connected lower-level ECU. Seventh step: Click the start button in Zone 6 to start the service delivery process. Eighth step: After the service delivery is complete, export the current service package data to the local machine or server for future use, thus ensuring the efficiency and flexibility of the vehicle communication network.

[0079] This embodiment provides a message monitoring and update method. By acquiring message information and sending instructions to the controller, the controller loads and executes a controller bootloader to obtain device information. Based on this device information, monitoring is performed to determine the operating mode. The message information is then updated according to the operating mode and a routing policy to obtain the updated message. By dynamically updating the vehicle gateway, message routing and device monitoring are optimized, communication efficiency is improved, and the stability and flexibility of the vehicle gateway system are enhanced.

[0080] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in Embodiment 1 above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 6 The message monitoring and update method step S30 further includes steps S301~S302:

[0081] Step S301: Monitor and parse the device information to obtain the processed device information.

[0082] It should be noted that during this process, the system actively monitors ECUs in the network and collects key data, such as operating parameters, error codes, and performance indicators, through advanced diagnostic tools and communication protocols. The system not only collects data but also uses built-in algorithms and models to parse this raw device information. The parsing process involves data cleaning, format conversion, and semantic understanding to ensure the accuracy and usability of the information.

[0083] The processed device information provides the system with powerful insights, enabling it to make more informed decisions. For example, if the system detects a performance degradation or potential failure risk in an ECU, it can issue an early warning and take preventative measures, such as rerouting messages, adjusting resource allocation, or scheduling maintenance. The processed device information is richer and more structured, including but not limited to the ECU's health status, software version, hardware specifications, real-time performance data, and possible fault predictions.

[0084] Furthermore, the processed equipment information can be used to optimize vehicle energy management, improve ride comfort, and enhance driving safety. The system can dynamically adjust vehicle operating strategies based on the actual operating status of the ECU, such as adjusting engine control, transmission logic, or suspension system settings, to adapt to different driving conditions and passenger needs.

[0085] Step S302: Process the processed equipment information to obtain the monitoring results.

[0086] It's important to note that the monitoring results are obtained by comprehensively considering multiple dimensions, including ECU response time, error rate, data processing capabilities, and communication efficiency. The system evaluates the operating parameters of each ECU, such as CPU load, memory usage, and I / O performance, to determine if they are operating within normal ranges. Furthermore, the system monitors network communication quality, including message transmission latency, packet loss rate, and collision rate, to assess network stability and reliability. Using these monitoring results, the vehicle gateway system can perform a range of automated tasks, such as dynamically adjusting message routing paths, optimizing data transmission priorities, reallocating system resources, or triggering remote diagnostics and repair procedures. For example, if a particular ECU is detected to be frequently experiencing errors or response delays, the system can automatically route its messages to an alternative path to avoid impacting normal vehicle operation.

[0087] Step S303: Analyze the monitoring results according to preset conditions to determine the working mode.

[0088] It should be noted that this analysis process involves real-time processing and evaluation of a large amount of collected data to identify various patterns and trends in vehicle networks.

[0089] The system's built-in analysis engine comprehensively evaluates monitoring results based on a series of preset conditions, such as vehicle speed, engine status, battery level, and network traffic. These preset conditions are designed as trigger points; when monitoring results meet or exceed these conditions, the system automatically adjusts its operating mode to optimize resource allocation, improve communication efficiency, and ensure task priority and response time. For example, if the system detects that the vehicle is traveling at high speed, it may automatically switch to a mode that prioritizes critical safety information, ensuring communication priority for the braking system, stability control, and collision prevention system. Conversely, if the vehicle is stationary, the system may enter an energy-saving mode, reducing unnecessary communication to extend the vehicle's battery life.

[0090] Furthermore, when monitoring results indicate a connection request from the service configuration device, the operating mode is set to service update mode. The routing table data of the routing policy is updated and saved. When the monitoring results of the vehicle gateway system indicate that the service configuration device (such as a host computer or diagnostic tool) has initiated a connection request, the system intelligently switches the operating mode to service update mode. This mode is specifically designed for system upgrades, maintenance, and configuration changes, ensuring that the vehicle network can adapt to the latest service requirements and technical standards. In service update mode, the system receives update instructions from the service configuration device. These instructions may include new routing rules, optimized signal processing algorithms, or software patches. The system updates the routing table data in the routing policy according to these instructions to reflect the latest configuration and communication requirements of devices in the network. The updated routing table data is verified and saved to ensure that the latest routing settings are maintained even after a system restart.

[0091] Furthermore, when monitoring results indicate that no connection request is found from the service configuration device, the operating mode is determined to be the normal operating mode, and the routing table data storing the routing policy is read and applied. When the monitoring results of the vehicle gateway system do not detect a connection request from the service configuration device (such as a host computer or diagnostic tool), the system will automatically determine and maintain the normal operating mode. In this mode, the system focuses on performing routine communication tasks, including message routing, signal processing, and device status monitoring, ensuring the efficient and stable operation of the vehicle network. In the normal operating mode, the system reads pre-configured and stored routing policy information, which defines the flow path of data within the vehicle's internal network. The system will apply this routing table data to guide data packets to be transmitted between different electronic control units (ECUs) according to predetermined routing rules, thereby realizing the vehicle's control functions and information exchange.

[0092] In addition, the system continuously monitors network status and device performance to respond in real time to any emergencies or potential communication problems. For example, if an ECU experiences communication delays or malfunctions, the system will dynamically reroute based on alternative paths in the routing table data to ensure uninterrupted transmission of critical information. Furthermore, the system can automatically adjust to diagnostic or repair mode based on anomalies detected in the monitoring results, such as performance degradation of an ECU or increased network latency, to ensure that problems are identified and resolved promptly.

[0093] This embodiment monitors and parses device information to obtain processed device information. Based on this processed information, further processing is performed to obtain monitoring results. These results are then analyzed according to preset conditions to determine the operating mode. Through in-depth analysis of device information and intelligent decision-making, the vehicle gateway system can achieve refined management of the vehicle network, providing drivers and passengers with a safer, more comfortable, and more efficient driving experience.

[0094] This application also provides a message monitoring and updating device; please refer to... Figure 7 The device includes:

[0095] Module 10 is used to acquire message information.

[0096] The acquisition module 10 is also used to send instructions to the controller so that the controller loads and executes the controller bootloader to obtain device information.

[0097] The monitoring module 20 is used to monitor the equipment information and obtain the working mode.

[0098] The execution module 30 is used to update the message information according to the routing policy based on the working mode to obtain the updated message.

[0099] The message monitoring and update apparatus provided in this application, employing the message monitoring and update method in the above embodiments, can solve the technical problem of how to reduce the update process and thus improve communication efficiency. Compared with the prior art, the beneficial effects of the message monitoring and update apparatus provided in this application are the same as those of the message monitoring and update method provided in the above embodiments, and other technical features in the message monitoring and update apparatus are the same as those disclosed in the methods of the above embodiments, and will not be repeated here.

[0100] In one embodiment, the acquisition module 10 is further configured to send an initialization command to the controller to trigger the controller to power on and enter the initialization phase; after detecting that the controller has entered the initialization phase, send a control command to cause the controller to execute the controller boot program; identify the signals of the controller boot program and acquire device information.

[0101] In one embodiment, the acquisition module 10 is further configured to enter a listening mode after the controller executes the controller bootstrap; identify the signals of the controller bootstrap to monitor and identify the device status and communication requests, and obtain identification signals; and parse the identification signals to obtain device information, including device identifier, version information, network address and functional status.

[0102] In one embodiment, the acquisition module 10 is further configured to monitor and parse device information to obtain processed device information; process the processed device information to obtain monitoring results; and analyze the monitoring results according to preset conditions to determine the working mode.

[0103] In one embodiment, the acquisition module 10 is further configured to determine the working mode as service update mode, update the routing table data of the routing policy and save it when the monitoring result indicates that the service configuration device has a connection request; and to determine the working mode as normal working mode when the monitoring result indicates that the service configuration device does not have a connection request, and read and apply the routing table data of the stored routing policy.

[0104] In one embodiment, the acquisition module 10 is further configured to determine the routing strategy for the message information based on the working mode; and to update the message parameters according to the message information based on the routing strategy to generate the updated message.

[0105] In one embodiment, the execution module 30 is further configured to execute a fault diagnosis mechanism when the updated message indicates that the device performance indicators are abnormal; and adjust the message routing policy or service packet configuration to optimize network communication and system response.

[0106] This application provides a message monitoring and updating device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the message monitoring and updating method in the first embodiment described above.

[0107] The following is for reference. Figure 8 The diagram illustrates a structural schematic suitable for implementing the message monitoring and update device in the embodiments of this application. The message monitoring and update device in the embodiments of this application may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Description), PMPs (Portable Media Players), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 8 The message monitoring and update device shown is merely an example and should not impose any limitations on the functionality and scope of use of the embodiments of this application.

[0108] like Figure 8 As shown, the message monitoring and update device may include a processing unit 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1002 or a program loaded from a storage device 1003 into a random access memory (RAM) 1004. The RAM 1004 also stores various programs and data required for the operation of the message monitoring and update device. The processing unit 1001, ROM 1002, and RAM 1004 are interconnected via a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Typically, the following systems can be connected to I / O interface 1006: input devices 1007 including, for example, touchscreens, touchpads, keyboards, mice, image sensors, microphones, accelerometers, gyroscopes, etc.; output devices 1008 including, for example, liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices 1003 including, for example, magnetic tapes, hard disks, etc.; and communication devices 1009. Communication device 1009 allows the message monitoring and updating device to communicate wirelessly or wiredly with other devices to exchange data. Although a message monitoring and updating device with various systems is shown in the figure, it should be understood that it is not required to implement or possess all the systems shown. More or fewer systems can be implemented alternatively.

[0109] Specifically, according to the embodiments disclosed in this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments disclosed in this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication device, or installed from storage device 1003, or installed from ROM 1002. When the computer program is executed by processing device 1001, it performs the functions defined in the methods of the embodiments disclosed in this application.

[0110] The message monitoring and update device provided in this application, employing the message monitoring and update method in the above embodiments, can solve the technical problem of how to reduce the update process and thus improve communication efficiency. Compared with the prior art, the beneficial effects of the message monitoring and update device provided in this application are the same as those of the message monitoring and update method provided in the above embodiments, and other technical features in this message monitoring and update device are the same as those disclosed in the method of the previous embodiment, and will not be repeated here.

[0111] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any suitable manner in one or more embodiments or examples.

[0112] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0113] This application provides a computer-readable storage medium having computer-readable program instructions (i.e., a computer program) stored thereon, which are used to execute the message monitoring and update method in the above embodiments.

[0114] The computer-readable storage medium provided in this application may be, for example, a USB flash drive, but is not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, system, or device. The program code contained on the computer-readable storage medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination thereof.

[0115] The aforementioned computer-readable storage medium may be included in the message monitoring and update device; or it may exist independently and not be assembled into the message monitoring and update device.

[0116] The aforementioned computer-readable storage medium carries one or more programs that, when executed by the message monitoring and update device, enable the message monitoring and update device to write computer program code for performing the operations of this application in one or more programming languages ​​or a combination thereof. These programming languages ​​include object-oriented programming languages—such as Java, Smalltalk, and C++—and conventional procedural programming languages—such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a standalone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving remote computers, the remote computer can be connected to the user's computer via any type of network—including a local area network (LAN) or a wide area network (WAN)—or can be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0117] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0118] The modules described in the embodiments of this application can be implemented in software or hardware. The names of the modules do not necessarily limit the functionality of the unit itself.

[0119] The readable storage medium provided in this application is a computer-readable storage medium that stores computer-readable program instructions (i.e., a computer program) for executing the above-described message monitoring and update method, thereby solving the technical problem of how to reduce the update process and improve communication efficiency. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided in this application are the same as those of the message monitoring and update method provided in the above embodiments, and will not be repeated here.

[0120] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the message monitoring and update method described above.

[0121] The computer program product provided in this application solves the technical problem of how to reduce the update process and thus improve communication efficiency. Compared with the prior art, the beneficial effects of the computer program product provided in this application are the same as those of the message monitoring and update method provided in the above embodiments, and will not be repeated here.

[0122] The above description is only a part of the embodiments of this application and does not limit the patent scope of this application. All equivalent structural transformations made under the technical concept of this application and using the contents of the specification and drawings of this application, or direct / indirect applications in other related technical fields, are included in the patent protection scope of this application.

Claims

1. A message monitoring and updating method, characterized in that, The method is applied to an in-vehicle gateway system, the in-vehicle gateway system including a controller and a service configuration device, the controller including a controller bootloader and a routing policy, the method including: Obtain message information; A command is sent to the controller to cause the controller to load and execute the controller boot program to obtain device information; The operating mode is determined by monitoring the equipment information. Based on the working mode, the message information is updated according to the routing policy to obtain the updated message; The step of monitoring based on the device information to obtain the working mode includes: The device information is monitored and analyzed to obtain processed device information; The processed equipment information is then processed to obtain monitoring results; The monitoring results are analyzed according to preset conditions to determine the working mode; The step of sending a command to the controller to cause the controller to load and execute the controller bootloader to obtain device information includes: An initialization command is sent to the controller to trigger the controller to power on and enter the initialization phase; Once the controller is detected to have entered the initialization phase, a control command is sent to cause the controller to execute the controller boot program. Identify signals from the controller bootloader to obtain device information; the step of identifying signals from the controller bootloader to obtain device information includes: After the controller executes the controller bootstrap, it enters listening mode; The controller bootloader identifies signals to monitor and identify device status and communication requests, thereby obtaining identification signals; Based on the identification signal, device information is obtained by parsing, including device identifier, version information, network address, and functional status; The step of analyzing the monitoring results according to preset conditions to determine the working mode includes: When the monitoring results indicate that the service configuration device has a connection request, the working mode is determined to be service update mode, the routing table data of the routing policy is updated and saved; When the monitoring result indicates that there is no connection request for the service configuration device, the working mode is determined to be the normal working mode, and the routing table data of the stored routing policy is read and applied.

2. The method as described in claim 1, characterized in that, The step of updating the message information according to the routing policy based on the working mode to obtain the updated message includes: Based on the operating mode, determine the routing strategy for the message information; Based on the routing policy, the packet parameters are adjusted and updated according to the packet information to generate the updated packet.

3. The method as described in claim 1, characterized in that, After the step of updating the message information according to the routing policy based on the working mode to obtain the updated message, the following steps are included: When the updated message indicates that the device performance indicators are abnormal, the fault diagnosis mechanism is executed. Adjust message routing policies or service packet configurations to optimize network communication and system response.

4. A message monitoring and updating device, characterized in that, The device is applied to an in-vehicle gateway system, the in-vehicle gateway system including a controller and service configuration device, the controller including a controller bootloader and routing policies, and the device including: The acquisition module is used to acquire message information; The acquisition module is also used to send instructions to the controller so that the controller loads and executes the controller bootloader to obtain device information; The acquisition module is also used to send an initialization command to the controller so that the controller is powered on and enters the initialization phase; Once the controller is detected to have entered the initialization phase, a control command is sent to cause the controller to execute the controller boot program. The acquisition module is also used to enter listening mode after the controller executes the controller bootstrap; The controller bootloader identifies signals to monitor and identify device status and communication requests, thereby obtaining identification signals; Based on the identification signal, device information is obtained by parsing, including device identifier, version information, network address, and functional status; The monitoring module is used to monitor the equipment information and determine the operating mode. The monitoring module is also used to monitor and parse the device information to obtain processed device information; The processed equipment information is then processed to obtain monitoring results; The monitoring results are analyzed according to preset conditions to determine the working mode; The monitoring module is also used to determine the working mode as service update mode, update the routing table data of the routing policy and save it when the monitoring results indicate that there is a connection request for the service configuration device; When the monitoring result indicates that there is no connection request for the service configuration device, the working mode is determined to be the normal working mode, and the routing table data of the stored routing policy is read and applied; The execution module is used to update the message information according to the routing policy based on the working mode to obtain the updated message.

5. A message monitoring and update device, characterized in that, The device includes: a memory, a processor, and a message monitoring and update program stored in the memory and executable on the processor, the message monitoring and update program being configured to implement the steps of the message monitoring and update method as described in any one of claims 1 to 3.

6. A medium, characterized in that, The medium stores a message monitoring and update program, which, when executed by a processor, implements the steps of the message monitoring and update method as described in any one of claims 1 to 3.

Images