Vehicle control process monitoring method, device, electronic equipment and storage medium
By generating and updating vehicle control data monitoring tables, key node information during the interaction between the vehicle and the TSP is recorded in detail, which solves the problem of imprecise monitoring of the vehicle control process and improves the efficiency of troubleshooting and the stability of the vehicle control system.
Patent Information
- Application Number
- CN202411269058.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-11
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2044-09-11
AI Technical Summary
In existing technologies, the vehicle control process is not monitored precisely enough during the interaction between the vehicle and the vehicle-to-everything (TSP) content service provider. This makes it impossible to know in advance whether the vehicle control is operating healthily and stably, which affects the user experience and makes troubleshooting difficult.
By generating a vehicle control data monitoring table, global and key node information in the vehicle control process is recorded, and data is updated at key nodes. Finally, the data is saved to the database to monitor the vehicle control process in detail and obtain the execution results and key node status.
It enables detailed monitoring of the vehicle control process, improves troubleshooting efficiency, reduces problem investigation time and cost, enhances the fault tolerance and real-time performance of vehicle control applications, and ensures the stability of the vehicle control system.
Smart Images

Figure CN118796612B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of intelligent vehicle technology, and in particular to a vehicle control process monitoring method, device, electronic equipment and storage medium. Background Art
[0002] Telematics Service Provider (TSP) refers to a service provider that provides intelligent automotive services based on the Internet and communication networks. It is an indispensable part of the automotive networking system, mainly involving functions such as vehicle safety, vehicle monitoring, navigation, communication, infotainment, and driving behavior analysis. TSP plays an important role as a bridge between vehicles and the Internet world. It can realize functions such as vehicle status monitoring, remote monitoring, early warning, and command through information exchange between vehicle-mounted devices and the Internet. At the same time, TSP can also provide car owners with functions such as intelligent navigation, entertainment, and online updates, allowing drivers to have a more convenient and comfortable driving experience.
[0003] There are many systems involved in the interaction between TSP and vehicle. If any of them fails, users will not be able to use the vehicle control. At the same time, since there are many systems involved in the interaction between TSP and vehicle, any of them fails, users will not be able to use the vehicle control. Furthermore, technicians have no way of knowing in advance whether the vehicle control is running healthily and stably. Summary of the invention
[0004] In view of this, the embodiments of the present application provide a vehicle control process monitoring method, device, electronic device and storage medium to solve the problem that vehicle process monitoring is not precise enough and early warning is delayed in the prior art.
[0005] According to a first aspect of an embodiment of the present application, a vehicle control process monitoring method is provided. The method is executed by a vehicle control process monitoring device, and includes:
[0006] In response to receiving the target vehicle control request, the vehicle control process monitoring device generates a vehicle control data monitoring table of the target vehicle control request, and writes the first global vehicle control information and the first key node vehicle control information into the vehicle control data monitoring table;
[0007] When the Internet of Vehicles content service provider platform TSP sequentially executes the target vehicle control process corresponding to the target vehicle control request, in response to determining that the TSP executes to a key node in the target vehicle control process, writing the second global vehicle control information and the second key node vehicle control information in the vehicle control data monitoring table;
[0008] In response to determining that the TSP completes execution of the target vehicle control process, writing the third global vehicle control information into the vehicle control data monitoring table to complete the vehicle control data monitoring table of the target vehicle control request;
[0009] The completed vehicle control data monitoring table is saved in the database, and the vehicle control process is monitored using the vehicle control data monitoring table.
[0010] According to a second aspect of an embodiment of the present application, a vehicle control process monitoring device is provided, comprising:
[0011] A generating module, configured to generate a vehicle control data monitoring table of the target vehicle control request in response to receiving the target vehicle control request;
[0012] A writing module is configured to write first global vehicle control information and first key node vehicle control information into the vehicle control data monitoring table;
[0013] The writing module is further configured to write the second global vehicle control information and the second key node vehicle control information in the vehicle control data monitoring table in response to determining that the TSP executes to a key node in the target vehicle control process when the vehicle network content service providing platform TSP sequentially executes the target vehicle control process corresponding to the target vehicle control request;
[0014] The writing module is further configured to write the third global vehicle control information into the vehicle control data monitoring table in response to determining that the TSP completes execution of the target vehicle control process, thereby completing the vehicle control data monitoring table requested by the target vehicle control;
[0015] The monitoring module is configured to save the completed vehicle control data monitoring table in a database and use the vehicle control data monitoring table to monitor the vehicle control process.
[0016] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the above method when executing the computer program.
[0017] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, which stores a computer program, and when the computer program is executed by a processor, the steps of the above method are implemented.
[0018] Compared with the prior art, the embodiments of the present application have the following beneficial effects: the embodiments of the present application extract key nodes from the process of TSP executing vehicle control, generate a vehicle control data monitoring table when receiving a target vehicle control request, first write the first global vehicle control information and the first key node vehicle control information, and then when TSP executes to the key node in the vehicle control process, write the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table, further after TSP completes the execution of the target vehicle control process, write the third global vehicle control information into the vehicle control data monitoring table, complete the vehicle control data monitoring table of the target vehicle control request, and finally save the completed vehicle control data monitoring table in the database to use the vehicle control data monitoring table to monitor the vehicle control process, thereby realizing detailed monitoring of the vehicle control process, being able to monitor and obtain the execution results of the vehicle control request, and also obtaining the execution status information of the key nodes in the execution process, thereby greatly improving the monitoring information flow, and providing strong data support for subsequent troubleshooting and vehicle control data analysis.
[0019] Furthermore, the technical solution of the embodiment of the present application can provide rich vehicle control process monitoring data, reducing the time and cost of technical personnel in troubleshooting problems; by analyzing the data in the vehicle control data monitoring table, it is possible to perceive in advance whether the vehicle control will affect the user experience, such as time and failure rate, thereby improving the fault tolerance of the vehicle control application; by analyzing the data in the vehicle control data monitoring table in advance, the problem can be quickly solved when the user reports a problem, thereby improving the real-time nature of the vehicle control application fault handling and at the same time improving the stability of the vehicle control system. BRIEF DESCRIPTION OF THE DRAWINGS
[0020] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.
[0021] Figure 1 It is a scenario diagram of an application scenario of an embodiment of the present application.
[0022] Figure 2 It is a flow chart of a vehicle control process monitoring method provided in an embodiment of the present application.
[0023] Figure 3 It is a flowchart of a method provided in an embodiment of the present application for writing second global vehicle control information and second key node vehicle control information in a vehicle control data monitoring table in response to determining that TSP is executed to a key node in a target vehicle control process.
[0024] Figure 4It is a flowchart diagram of another method provided by an embodiment of the present application for writing second global vehicle control information and second key node vehicle control information in a vehicle control data monitoring table in response to determining that TSP is executed to a key node in a target vehicle control process.
[0025] Figure 5 It is a flowchart of a method for printing a vehicle control log of a target key node when a target vehicle control process is executed to the target key node by a TSP device where the target key node is located provided in an embodiment of the present application.
[0026] Figure 6 It is a flowchart diagram of a method for screening and obtaining vehicle control logs of key nodes when TSP is executed to a key node in a target vehicle control process, provided in an embodiment of the present application.
[0027] Figure 7 It is an interaction diagram of the vehicle control process execution method provided in an embodiment of the present application.
[0028] Figure 8 It is a flow chart of a method for parsing data in a vehicle control log provided in an embodiment of the present application, and writing the vehicle control data obtained by the parsing into a vehicle control data monitoring table as second global vehicle control information and second key node vehicle control information.
[0029] Fig. 9 It is a flow chart of a method in which the vehicle control process monitoring device provided in an embodiment of the present application obtains the second global vehicle control information and the second key node vehicle control information in the vehicle control process message topic of Kafka and writes them into the vehicle control data monitoring table.
[0030] Fig.10 It is a flowchart diagram of a method for writing third global vehicle control information into a vehicle control data monitoring table in response to determining that the TSP completes execution of a target vehicle control process, provided in an embodiment of the present application.
[0031] Fig.11 It is a flowchart of the method for collecting, parsing, storing and displaying system logs provided in an embodiment of the present application.
[0032] Fig.12 It is a flow chart of a method for monitoring a vehicle control process using a vehicle control data monitoring table provided in an embodiment of the present application.
[0033] Fig.13 It is a schematic diagram of the vehicle control process monitoring graphical display interface provided in an embodiment of the present application.
[0034] Fig.14 It is a schematic diagram of the monitoring interface of the vehicle control process monitoring device provided in an embodiment of the present application.
[0035] Fig.15It is a schematic diagram of a vehicle control process monitoring device provided in an embodiment of the present application.
[0036] Fig.16 It is a schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0037] In the following description, specific details such as specific system structures, technologies, etc. are provided for the purpose of illustration rather than limitation, so as to provide a thorough understanding of the embodiments of the present application. However, it should be clear to those skilled in the art that the present application may also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to prevent unnecessary details from obstructing the description of the present application.
[0038] A vehicle control process monitoring method and device according to an embodiment of the present application will be described in detail below with reference to the accompanying drawings.
[0039] In related technologies, vehicle OEMs usually provide a car owner application (Application, APP), which can control the vehicle, realize vehicle status monitoring and early warning functions. The TSP in the cloud platform provides capability support for the car owner APP, so the position of TSP in the Internet of Vehicles is very core.
[0040] As mentioned above, since there are many systems involved in the interaction between TSP and vehicles, any problem in any link will cause users to be unable to use the vehicle control. At the same time, technicians have no way of knowing in advance whether the vehicle control is running healthily and stably.
[0041] Figure 1 Schematic diagram of the application scenario of the embodiment of the present application. Figure 1 As shown in the figure, TSP can be divided into three parts: vehicle side, cloud side and EMQ. The vehicle side includes TBOX, the cloud side includes APP, APP background service, vehicle equipment service, Kafka and equipment gateway, and EMQ is the bridge for interaction between the vehicle side and the cloud side.
[0042] The traditional vehicle control process is that the APP sends a vehicle control command to the APP background service. After the APP background service receives the vehicle control command, it calls the device center to send a vehicle control request to the vehicle device service, and the vehicle device service sends the request to the Kafka message center. Furthermore, the vehicle device service center also returns the task identification document (id) to the APP background service, and the APP background service further returns the task id to the APP.
[0043] The device gateway subscribes to the vehicle control request message in Kafka, obtains the request after receiving the vehicle control request in Kafka, encapsulates the vehicle control request protocol, and then sends the encapsulated protocol to EMQ. TBOX subscribes to the vehicle control request message in EMQ, obtains the vehicle control request protocol after EMQ receives the encapsulated protocol, and executes the vehicle control request after parsing the vehicle control instruction. After executing the vehicle control request, TBOX sends the vehicle control request task execution result to EMQ. The device gateway subscribes to the vehicle control request result message in EMQ, obtains the vehicle control execution result after EMQ receives the vehicle control request task execution result sent by TBOX, and sends the vehicle control execution result to the Kafka message center.
[0044] The APP backend service subscribes to the vehicle control execution result message in Kafka. After Kafka receives the vehicle control execution result sent by the device gateway, it obtains and stores the vehicle control execution result locally. At the same time, after receiving the task id, the APP can use the task id to periodically obtain the vehicle control execution result from the APP backend service, and after the APP backend service receives the vehicle control execution result from Kafka, it obtains and displays the vehicle control execution result from the APP backend service.
[0045] The above-mentioned vehicle control process monitoring in the related technology can obtain information such as the issued instructions, execution status, issuance time, user mobile phone number, vehicle identification number (VIN), and execution results. In other words, the related technology can easily know the results of each vehicle control instruction operated by the user, such as whether the execution of this vehicle control is successful or failed, and can also instantly obtain the total time spent on executing the vehicle control instruction. However, the vehicle control process monitoring method in the related technology cannot know in detail which link or key node has problems, and statistically analyze which vehicles may have problems in which links, whether these problems are hardware, network, or software problems, etc.
[0046] In other words, the related technology lacks a monitoring solution for the vehicle control process of the TSP platform of the Internet of Vehicles, and usually simply records the operation records of the vehicle control. Using the existing TSP monitoring method, technicians cannot know in advance whether the user can use the vehicle control command normally, and can only wait for user feedback, but when the user feedbacks, the problem may be quite serious.
[0047] Furthermore, too many systems are involved in the interaction between TSP and vehicles; users operate vehicle control many times, and technicians do not know which time or period the vehicle control has a problem, and cannot quickly locate the problem. Moreover, because there are too many systems involved, many systems or components are still executed asynchronously, and it is impossible to connect the logs generated by a specific request in each system.
[0048] Furthermore, the vehicle control process monitoring solution in the related technology cannot dynamically check the time consumption of vehicle remote control. For example, if there are many people using the owner application (Application, APP) in a certain period of time, the TSP is under great pressure, causing the remote control to take a long time in a certain period of time, affecting the user experience.
[0049] In addition, when vehicle control cannot be executed normally, the vehicle control process monitoring solution in the related technology cannot quickly and accurately locate whether there is an abnormality in the vehicle-side communication module (TBOX) or in a service process in the cloud.
[0050] In view of this, an embodiment of the present application provides a vehicle control process monitoring method, which extracts key nodes from the process of TSP executing vehicle control, generates a vehicle control data monitoring table when receiving a target vehicle control request, first writes the first global vehicle control information and the first key node vehicle control information, and then when the TSP executes to the key node in the vehicle control process, writes the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table, and further writes the third global vehicle control information into the vehicle control data monitoring table after the TSP completes the execution of the target vehicle control process, completing the vehicle control data monitoring table of the target vehicle control request, and finally saves the completed vehicle control data monitoring table in a database to use the vehicle control data monitoring table to monitor the vehicle control process, thereby realizing detailed monitoring of the vehicle control process, which can not only monitor and obtain the execution results of the vehicle control request, but also obtain the execution status information of the key nodes in the execution process, thereby greatly improving the monitoring information flow, and providing strong data support for subsequent troubleshooting and vehicle control data analysis.
[0051] Figure 2 FIG. 1 is a flow chart of a vehicle control process monitoring method provided by an embodiment of the present application. Figure 2 As shown, the method comprises the following steps:
[0052] In step S201 , in response to receiving a target vehicle control request, the vehicle control process monitoring device generates a vehicle control data monitoring table of the target vehicle control request, and writes first global vehicle control information and first key node vehicle control information into the vehicle control data monitoring table.
[0053] In step S202, when the Internet of Vehicles content service provider platform TSP sequentially executes the target vehicle control process corresponding to the target vehicle control request, in response to determining that TSP executes to the key node in the target vehicle control process, the second global vehicle control information and the second key node vehicle control information are written into the vehicle control data monitoring table.
[0054] In step S203 , in response to determining that the TSP completes execution of the target vehicle control process, the third global vehicle control information is written into the vehicle control data monitoring table to complete the vehicle control data monitoring table requested by the target vehicle control.
[0055] In step S204, the completed vehicle control data monitoring table is saved in a database, and the vehicle control process is monitored using the vehicle control data monitoring table.
[0056] In an embodiment of the present application, the vehicle control process monitoring method can be executed by a vehicle control process monitoring device. The vehicle control process monitoring device can be a terminal device, a server, or a distributed device. The vehicle control process monitoring device can be configured with a log collection tool, a log data collection tool, and a log parsing tool, and the vehicle control process monitoring device can also communicate with the TSP to encapsulate the parsed log elements into entity classes and send them to Kafka, and consume the vehicle control process messages in Kafka as a message sender group.
[0057] In an embodiment of the present application, the vehicle control process monitoring device can generate a vehicle control data monitoring table for the target vehicle control request after receiving the target vehicle control request, and write the first global vehicle control information and the first key node vehicle control information into the vehicle control data monitoring table. Among them, the target vehicle control request is a vehicle control request sent by the APP to the APP background service, and the vehicle control process monitoring device is used to monitor the vehicle control process, so it can also receive the vehicle control request sent by the APP. After receiving the target vehicle control request, the vehicle control process monitoring device can generate a vehicle control data monitoring table corresponding to this vehicle control request. It should be noted that the contents of each table item in the newly created vehicle control data monitoring table are blank, and relevant information needs to be obtained and written in different ways later.
[0058] In an embodiment of the present application, after generating a vehicle control data monitoring table for a target vehicle control request, the vehicle control process monitoring device may first obtain the first global vehicle control information and the first key node vehicle control information, and write the first global vehicle control information and the first key node vehicle control information into the vehicle control data monitoring table.
[0059] In an embodiment of the present application, the vehicle control process monitoring device can collect the logs of each key node in the vehicle control process when the TSP sequentially executes the target vehicle control process corresponding to the target vehicle control request, filter out the vehicle control log from the log, and then parse the vehicle control log to obtain vehicle control information, and then write the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table.
[0060] In an embodiment of the present application, the vehicle control process monitoring device can also obtain the third global vehicle control information after the TSP completes the execution of the target vehicle control process, and write the third global vehicle control information into the vehicle control data monitoring table, thereby completing the vehicle control data monitoring table of the target vehicle control request.
[0061] Finally, the vehicle control process monitoring device saves the completed vehicle control data monitoring table in a database so that the user can use the vehicle control data monitoring table to monitor the vehicle control process.
[0062] According to the technical solution provided in the embodiment of the present application, by extracting key nodes from the process of TSP executing vehicle control, a vehicle control data monitoring table is generated when a target vehicle control request is received, and first the first global vehicle control information and the first key node vehicle control information are written therein. Then, when TSP executes to a key node in the vehicle control process, the second global vehicle control information and the second key node vehicle control information are written therein. Further, after TSP completes the execution of the target vehicle control process, the third global vehicle control information is written therein to complete the vehicle control data monitoring table of the target vehicle control request. Finally, the completed vehicle control data monitoring table is saved in a database so as to use the vehicle control data monitoring table to monitor the vehicle control process, thereby achieving detailed monitoring of the vehicle control process. Not only can the execution results of the vehicle control request be monitored, but also the execution status information of the key nodes in the execution process can be obtained, thereby greatly improving the monitoring information flow and providing strong data support for subsequent troubleshooting and vehicle control data analysis.
[0063] In an embodiment of the present application, writing the first global vehicle control information and the first key node vehicle control information into the vehicle control data monitoring table may be by obtaining user identification information, vehicle identification information and key node identification; obtaining vehicle control command information corresponding to a target vehicle control request; writing the user identification information, vehicle identification information and vehicle control command information corresponding to the target vehicle control request as the first global vehicle control information into the vehicle control data monitoring table, and writing the key node identification as the first key node vehicle control information into the vehicle control data monitoring table.
[0064] That is, the first global vehicle control information may include user identification information, vehicle identification information, and vehicle control instruction information corresponding to the target vehicle control request, wherein the user identification information, vehicle identification information, and vehicle control instruction information corresponding to the target vehicle control request may be obtained from the target vehicle control request. The first key node vehicle control information may include a key node identifier, which may be predefined and recorded as a default item in the vehicle control data monitoring table.
[0065] Figure 3 1 is a flow chart of a method for writing second global vehicle control information and second key node vehicle control information into a vehicle control data monitoring table in response to determining that TSP is executed to a key node in a target vehicle control process provided by an embodiment of the present application. Figure 3 As shown, the method comprises the following steps:
[0066] In step S301, logs are collected and filtered from TSP devices where each key node is located. When TSP is executed to a key node in a target vehicle control process, the vehicle control log of the key node is filtered.
[0067] In step S302, the data in the vehicle control log is parsed, and the vehicle control data obtained by the parsing is written into the vehicle control data monitoring table as the second global vehicle control information and the second key node vehicle control information.
[0068] In the embodiment of the present application, the second global vehicle control information and the second key node vehicle control information can be obtained by the vehicle control process monitoring device collecting the logs of each key node in the vehicle control process, filtering out the vehicle control logs and parsing the vehicle control logs. In other words, the vehicle control process monitoring device can collect and filter logs from the TSP device where each key node is located, and when the TSP executes to the key node in the target vehicle control process, the vehicle control log of the key node is filtered out. Furthermore, the vehicle control process monitoring device can also parse the data in the vehicle control log, and write the parsed vehicle control data as the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table.
[0069] In the embodiment of the present application, the key nodes in the target vehicle control process include the command initialization process node, the SMS wake-up process node, the vehicle communication module TBOX login process node, the command sending to EMQ process node, the TBOX response acquisition process node, the TBOX response processing process node and the execution result feedback process node.
[0070] Among them, the command initialization process node means that after the APP background service receives the vehicle control request from the APP, it will immediately perform a legal check on the vehicle control request parameters, vehicle control authority check, vehicle status check, etc. After the check is completed, the vehicle control request parameters are packaged into vehicle control instructions and packaged into instructions that TBOX can recognize; only then does it indicate that the command has been initialized.
[0071] The SMS wake-up process node refers to sending SMS mainly when the TBOX loaded on the vehicle is in sleep mode (TBOX and EMQ in sleep mode are in disconnected mode, that is, they cannot receive vehicle control commands sent from the cloud). The cloud needs to send SMS to TBOX through China Telecom, China Mobile, or China Unicom. After receiving the SMS, TBOX will actively initiate a connection to EMQ.
[0072] The TBOX login process node means that after TBOX receives the SMS sent by the cloud, it actively connects to EMQ, and then actively initiates a login request through EMQ. After the cloud receives the login request and verifies the legitimacy of the login request, the cloud changes the status of TBOX from offline to online.
[0073] Sending commands to the EMQ process node means that the vehicle control command is successfully sent to EMQ after being transmitted through various systems in the cloud, and EMQ replies to the cloud that the vehicle control command has been received.
[0074] The process node of obtaining TBOX response means that after TBOX receives the vehicle control command from EMQ, it converts the vehicle control command into a command that can be executed by the vehicle and sends it to the vehicle for execution. After the vehicle executes the command, it sends the vehicle control execution result to EMQ.
[0075] The TBOX response process node means that after TBOX responds to the cloud vehicle control result, the cloud needs to parse, store, and process the result data in related business logic.
[0076] The feedback execution result process node refers to pushing the vehicle control result message to the APP, or the APP actively calls the vehicle control interface to obtain the vehicle control result.
[0077] Figure 4 1 is a flow chart of another method provided by an embodiment of the present application for writing second global vehicle control information and second key node vehicle control information into a vehicle control data monitoring table in response to determining that TSP is executed to a key node in a target vehicle control process. Figure 4 As shown, the method comprises the following steps:
[0078] In step S401 , in response to determining that the TSP is executed to the command initialization process node, a vehicle control request identifier of a target vehicle control request and a time of issuing a vehicle control instruction corresponding to the target vehicle control request are obtained.
[0079] In step S402, the vehicle control request identifier and the issuing time are written into the vehicle control data monitoring table as the second global vehicle control information.
[0080] In step S403, the vehicle control request identifier is written into the vehicle control data monitoring table as at least part of the second key node vehicle control information.
[0081] In an embodiment of the present application, the second global vehicle control information may be the vehicle control request identifier of the target vehicle control request and the issuing time of the vehicle control instruction corresponding to the target vehicle control request. Furthermore, the vehicle control request identifier of the target vehicle control request may also be part of the second key node vehicle control information. That is to say, in the vehicle control data monitoring table, the vehicle control request identifier of the target vehicle control request may be recorded in the table header as global information, and further, the vehicle control request identifier of the target vehicle control request may be recorded in the list for recording the vehicle control information of each key node. Among them, the vehicle control request identifier of the target vehicle control request and the issuing time of the vehicle control instruction corresponding to the target vehicle control request are both generated by the command initialization process node.
[0082] That is to say, when TSP executes to the command initialization process node, the command initialization log has been generated and printed, and the command initialization log includes the vehicle control request identifier of the target vehicle control request and the vehicle control instruction issuance time corresponding to the target vehicle control request. Therefore, the vehicle control process monitoring device can obtain the vehicle control request identifier of the target vehicle control request and the issuance time of the vehicle control instruction corresponding to the target vehicle control request. Then, the vehicle control request identifier and the issuance time are written into the vehicle control data monitoring table as the second global vehicle control information, and the vehicle control request identifier is written into the vehicle control data monitoring table as at least part of the second key node vehicle control information.
[0083] In an embodiment of the present application, when the target vehicle control process is executed to the target key node, the TSP device where the target key node is located prints the vehicle control log of the target key node for collection by the vehicle control process monitoring device. The target key node is any key node in the target vehicle control process.
[0084] Figure 5 It is a flow chart of a method for printing a vehicle control log of a target key node when the target vehicle control process is executed to the target key node by the TSP device at the target key node provided in the embodiment of the present application. Figure 5 As shown, the method comprises the following steps:
[0085] In step S501 , in response to determining that the vehicle control application background service device in the TSP completes encapsulation of the vehicle control instruction corresponding to the target vehicle control request, the vehicle control application background service device prints a command initialization log.
[0086] In step S502 , in response to determining that the vehicle service device in the TSP receives the SMS sending result returned by the operator, the vehicle service device prints a SMS sending wake-up log.
[0087] In step S503 , in response to determining that the vehicle service device in the TSP receives the TBOX login request sent by the TBOX via the EMQ, the device gateway and the message middleware Kafka, the vehicle service device prints the TBOX login log.
[0088] In step S504 , in response to determining that the device gateway in the TSP has received the successfully received target vehicle control request message sent by the EMQ, the device gateway prints a sending command to the EMQ log.
[0089] In step S505 , in response to determining that the device gateway in the TSP receives the vehicle control instruction execution result sent by the TBOX via the EMQ, the device gateway prints the TBOX response log.
[0090] In step S506 , in response to determining that the vehicle control application background service device in the TSP receives the vehicle control instruction execution result from Kafka, the vehicle control application background service prints and processes the TBOX log.
[0091] In step S507 , in response to determining that the vehicle control application background service device in the TSP completes the business processing based on the TBOX response result, the vehicle control application background service prints a feedback execution result log.
[0092] In the embodiment of the present application, when the target key node is located in the TSP device, when the target vehicle control process is executed to the target key node, the vehicle control log of the target key node can be printed. When the vehicle control application background service device in the TSP completes the encapsulation of the vehicle control instruction corresponding to the target vehicle control request, the vehicle control application background service device prints the command initialization log. And, when the vehicle service device in the TSP receives the result of sending SMS returned by the operator, the vehicle service device prints the SMS wake-up log. And, when the vehicle service device in the TSP receives the TBOX login request sent by TBOX via EMQ, the device gateway and the message middleware Kafka, the vehicle service device prints the TBOX login log. And, when the device gateway in the TSP receives the target vehicle control request message sent by EMQ, the device gateway prints the send command to the EMQ log. And, when the device gateway in the TSP receives the vehicle control instruction execution result sent by TBOX via EMQ, the device gateway prints the TBOX response log. And, when the vehicle control application background service device in the TSP receives the vehicle control instruction execution result from Kafka, the vehicle control application background service prints the processing TBOX log. And, when the vehicle control application background service device in the TSP completes the business processing based on the TBOX response result, the vehicle control application background service prints a feedback execution result log.
[0093] If TBOX is not in sleep mode, the process of sending SMS to wake up the vehicle control system can be skipped, and there is no need to print the SMS wake-up log. On the other hand, if TBOX is in logged-in mode, the process of sending TBOX login request to the vehicle control system via EMQ, device gateway and message middleware Kafka can be skipped, and there is no need to print the TBOX login log.
[0094] Figure 6 1 is a flow chart of a method for filtering and obtaining a vehicle control log of a key node when TSP is executed to a key node in a target vehicle control process provided by an embodiment of the present application. Figure 7 As shown, the method comprises the following steps:
[0095] In step S601 , the vehicle control process monitoring device collects all logs of key nodes when the TSP executes the target vehicle control process.
[0096] In step S602 , after the TSP is executed to the key node in the target vehicle control process and the vehicle control log of the key node is printed, the vehicle control process monitoring device collects the vehicle control log of the key node.
[0097] In step S603, the vehicle control process monitoring device parses all the collected logs, and in response to determining that the logs include a vehicle control log identifier, the vehicle control logs of key nodes are screened.
[0098] In the embodiment of the present application, when the TSP executes the target vehicle control process, the vehicle control process monitoring device can continuously collect all logs of key nodes and parse all collected logs. Furthermore, after the TSP executes to the key node in the target vehicle control process and completes the printing of the vehicle control log of the key node, the vehicle control process monitoring device will collect the vehicle control log of the key node. At this time, the vehicle control process monitoring device can determine that the log contains a vehicle control log identifier by parsing the log, and can determine that the log is a vehicle control log.
[0099] Figure 7 is an interactive diagram of the vehicle control process execution method provided in the embodiment of the present application. Figure 7 As shown, the APP can send a vehicle control request to the APP background service, and the APP background service encapsulates the vehicle control command and returns the result to the APP for execution. Furthermore, the APP background service can also send a vehicle control command to the vehicle device service. After receiving the vehicle control command, the vehicle control device service can send a text message wake-up request to the operator. The operator returns the result of sending the text message. The APP background service receives the result returned by the text message and records the text message result log.
[0100] On the other hand, the operator sends a text message to TBOX, which parses the text message and completes the wake-up, and then sends a login request to EMQ. EMQ pushes the login request to the device gateway, which sends the login request to the vehicle device service via Kafka and related intermediate services.
[0101] After receiving the login request, the vehicle device service processes the login request and prints the TBOX login log, and changes the vehicle status to logged in. Subsequently, the vehicle service device sends the vehicle control command to Kafka, and Kafka pushes the vehicle control command to the device gateway. The device gateway further sends the vehicle control command to EMQ, and EMQ sends the vehicle control command to TBOX and returns the result to the device gateway. After receiving the return result, the device gateway prints the sending command to the EMQ log.
[0102] TBOX executes the received vehicle control command and sends the execution result to EMQ. EMQ pushes the received execution result to the device gateway. The device gateway prints the TBOX response log after receiving the execution result. The device gateway further sends the execution result to Kafka, which is pushed to the APP background service by Kafka. The APP background service processes the TBOX response result and prints the processing TBOX log. Furthermore, the APP post-processing service changes the vehicle control command execution result, pushes messages, and prints the feedback execution result log. The APP obtains the vehicle control result from the APP background service, or the APP background service feeds back the response result to the APP.
[0103] In one example, the APP can call the vehicle control interface provided by the APP background service, such as: / v0 / public / vehicle-remote-control / send-vehicle-control-command. Furthermore, the window opening command can also be passed in, such as CommandType=WINDOW, command=ON, vin=XX.
[0104] After receiving the APP request, the APP background service uses the function UUID.randomUUID().toString() to generate the vehicle control request identifier (requestId) corresponding to the target vehicle control request, then performs parameter verification, encapsulates the vehicle control request identifier requestId and the remote control command, and finally prints the command initialization log.
[0105] The APP background service calls the vehicle device service to send the vehicle control interface, such as / v0 / public / vehicles / remote-instructions, and passes in the remote control instructions for controlling the vehicle and the vehicle control request identifier requestId. The vehicle device service calls the operator interface to send a text message to the Subscriber Identity Module (SIM) card in the TBOX installed in the vehicle, passing in the vehicle control request identifier requestId and the instruction to wake up the TBOX.
[0106] The vehicle equipment service prints the result log of sending SMS and waits for the TBOX login request. After receiving the SMS, TBOX wakes up, then logs in to the cloud through the vehicle-cloud protocol, and passes in the basic vehicle information and the vehicle control request identifier requestId. After receiving the TBOX login request, the vehicle equipment service prints the TBOX login log, verifies the basic vehicle information, and changes the vehicle status to online. The vehicle equipment service sends the vehicle control command and the vehicle control request identifier requestId to Kafka. The device gateway receives the vehicle control command and the vehicle control request identifier requestId from Kafka to verify the validity of the vehicle control command. The device gateway sends the vehicle control command to EMQ. After receiving the vehicle control command, EMQ returns it to the device gateway to indicate that it has been successfully received.
[0107] The device gateway prints the result log of the vehicle control command sent to EMQ. After receiving the vehicle control command from EMQ, TBOX verifies the legitimacy of the command and then sends it to the vehicle to execute the vehicle control command. TBOX sends the vehicle control command execution result (carrying the vehicle control request identifier requestId) to EMQ. After receiving the TBOX command execution result from EMQ, the device gateway parses it according to the vehicle-cloud protocol to obtain the execution result content and the vehicle control request identifier requestId. And print the TBOX response log. The device gateway sends the command execution result and the vehicle control request identifier requestId to Kafka. The APP background service obtains the command execution result and the vehicle control request identifier requestId from Kafka, and prints and processes the TBOX response log. After receiving the TBOX response result, the APP background service performs business processing, such as pushing messages to the APP and modifying the vehicle control command execution result status, and printing the feedback APP execution result log.
[0108] Figure 8 1 is a flow chart of a method for parsing data in a vehicle control log provided by an embodiment of the present application, and writing the vehicle control data obtained by the parsing into a vehicle control data monitoring table as second global vehicle control information and second key node vehicle control information. Figure 8 As shown, the method comprises the following steps:
[0109] In step S801, all logs collected by the vehicle control process monitoring device are written into a log file using a log framework.
[0110] In step S802, a log data collection tool is used to send all data in the log file to a log parsing tool.
[0111] In step S803 , when the log parsing tool determines that the target log includes the vehicle control log identifier, the target log is determined to be the vehicle control log.
[0112] In step S804, the log parsing tool uses preset parsing rules to segment the data in the vehicle control log to obtain parsed vehicle control log elements.
[0113] The parsed vehicle control log elements include the second global vehicle control information and the second key node vehicle control information.
[0114] In step S805, the parsed vehicle control log elements are repackaged into entity classes, and the entity classes are sent to the vehicle control process message topic of Kafka in the TSP.
[0115] In step S806, the vehicle control process monitoring device obtains the second global vehicle control information and the second key node vehicle control information from the vehicle control process message topic of Kafka, and writes them into the vehicle control data monitoring table.
[0116] In an embodiment of the present application, when parsing the logs collected by the vehicle control process monitoring device, the log framework can be used to first write all the logs collected by the vehicle control process monitoring device into a log file. In one example, the log framework can be slf4j, for example. Next, a log data collection tool can be used to send all the data in the log file to a log parsing tool. In one example, the log data collection tool can be filebeat, for example, and the log parsing tool can be logStash, for example.
[0117] In the embodiment of the present application, the log parsing tool parses the logs one by one, and uses the preset parsing rules to segment the data in the vehicle control log to obtain the parsed vehicle control log elements, which may include the second global vehicle control information and the second key node vehicle control information. The parsed vehicle control log elements can then be repackaged into entity classes, and the entity classes are sent to the vehicle control process message topic of Kafka in the TSP.
[0118] The vehicle control process monitoring device can subscribe to the vehicle control process messages in Kafka, and then update the vehicle control process message topic of Kafka. For example, when the entity class encapsulated by the new vehicle control log element is received and stored, the second global vehicle control information and the second key node vehicle control information are obtained from the vehicle control process message topic and written into the vehicle control data monitoring table.
[0119] In other words, the log framework slf4j can be used to output the log to a file, and the log data collection tool filebeat can be used to obtain the log content from the file and send it to the log parsing tool logStash. The log parsing tool logstash parses the logs one by one and determines whether the logs are related to the vehicle control process. If so, they are sent to the vehicle control process message topic (topic) corresponding to Kafak. Furthermore, all parsed system logs can be stored in the database ES, and then the visualization platform kibana can be used to display the logs of all request systems. The vehicle control process monitoring service can obtain the corresponding vehicle control data for each key node from the vehicle control process message topic corresponding to Kafka. The vehicle control process monitoring service can also be stored in databases such as mysql and mongodb.
[0120] In the embodiment of the present application, the log format corresponding to each key node may be, for example:
[0121] Command initialization:
[0122] log.info("CONTROLLOG#INITIALIZE#{}#{}#{}#{}#{}#{}" ,phone,pdid,commandType,command,result,reason);
[0123] Send SMS to wake up:
[0124] log.info("CONTROLLOG#WAKEUP#{}#{}#{}#{}#{}",pdid, commandType, command, result, reason);
[0125] TBOX login:
[0126] log.info("CONTROLLOG#LOGIN#{}#{}#{}#{}#{}", pdid,commandType,command,result,reason);
[0127] Command to send EMQ:
[0128] log.info("CONTROLLOG#SENDEMQ#{}#{}#{}#{}#{}",pdid,commandType,command,result,reason);
[0129] Get TBOX response:
[0130] log.info("CONTROLLOG#GETTBOX#{}#{}#{}#{}#{}",pdid,commandType,command,result,reason);
[0131] Processing TBOX response:
[0132] log.info("CONTROLLOG#HANDTBOX#{}#{}#{}#{}#{}",pdid,commandType,command,result,reason);
[0133] Feedback APP execution results:
[0134] log.info("CONTROLLOG#SENDAPPMSG#{}#{}#{}#{}#{}",pdid,commandType,command,result,reason).
[0135] Among them, CONTROLLOG is the vehicle control log identifier, INITIALIZE indicates that the node type is a command initialization process node, WAKEUP indicates that the node type is a process node for sending a text message to wake up, LOGIN indicates that the node type is a TBOX login process node, SENDEMQ indicates that the node type is a command sending EMQ process node, GETTBOX indicates that the node type is a process node for obtaining a TBOX response, HANDTBOX indicates that the node type is a process node for processing a TBOX response, and SENDAPPMSG indicates that the node type is a process node for feedback the execution result of the APP.
[0136] Furthermore, pdid is the device number; commandType is the command type, such as LOCK (lock); command is the instruction action, such as ON represents unlocking and OFF represents locking; result represents the execution result of the key node, and the execution result can be success or failure; reason represents the reason for failure.
[0137] When outputting the log to a file through the log framework slf4j, the log can be constructed into text and written into the log file through the log framework slf4j. For example, through "#CONTROLLOG#INITIALIZE#LOCK#ON#success#success", and then merge the vehicle control request identifier requestId in this log, #CONTROLLOG#INITIALIZE#LOCK#ON#success# success#ba462c3043044a82940f5a38b23677f6.
[0138] Then, use the log data collection tool filebeat to collect the log file data and send it to the log parsing tool logStash channel. The log parsing tool logStash receives the log: #CONTROLLOG#SKEV2024XX#INITIALIZE#LOCK#ON#success#successba462c3043044a82940f5a38b23677f6, and judges whether the log text starts with: #CONTROLLOG. If this log is a key log of the vehicle control process, it means that it needs to be parsed and the parsing result is sent to Kafka. Using Figure 8In the illustrated embodiment, the preset parsing rules in step 804 are segmented according to #, and after segmentation, they are stored in order and stored in a data structure array, CONTROLLOG, SKEV2024XX, INITIALIZE, LOCK, ON, success, success; the first element in the array: CONTROLLOG, the second element: SKEV2024XX, the third element: INITIALIZE, the fourth element: LOCK, the fifth element: ON, the sixth element: success; the seventh element: success; the eighth element: ba462c3043044a82940f5a38b23677f6.
[0139] Encapsulate the parsed elements into the corresponding entity class, convert them into the lightweight data exchange format json, and send them to the corresponding Kafka message middleware. In an example, the above eight elements and the vehicle control request identifier requestId, the current system time, can be encapsulated into a lightweight data exchange format json, for example {" "type":"CONTROLLOG","pdid":"SKEV2024XX","node":"INITIALIZE","commandType":"LOCK","command":"ON","result":"success","reason":"Success","requestId":"ba462c3043044a82940f5a38b23677f6","time":"2024-06-15 09:32:21:100"}; or {"phone":"135680XX","type":"CONTROLLOG","pdid":"SKEV2024XX","node":"INITIALIZE","commandType":"LOCK","command":"ON","result":"success","reason":"Success","requestId":"ba462c3043044a82940f5a38b23677f6","time":"2024-06-15 09:32:21:100"}. Then send the encapsulated json message to topic="VehicleControlProcessTopic" in Kafka.
[0140] The message group consumption defined in the vehicle control process service corresponds to the topic VehicleControlProcessTopic in Kafka for vehicle control process messages.
[0141] Fig. 9 This is a flow chart of a method provided by the vehicle control process monitoring device of the present application embodiment to obtain the second global vehicle control information and the second key node vehicle control information from the vehicle control process message topic of Kafka and write them into the vehicle control data monitoring table. Fig. 9 As shown, the method comprises the following steps:
[0142] In step S901 , the vehicle control process monitoring device obtains the vehicle control process message of the target vehicle control request from Kafka.
[0143] In step S902, in response to determining that the vehicle control process message is at a command initialization process node, first global vehicle control information, second global vehicle control information, first key node vehicle control information and at least part of the second key node vehicle control information are written into a vehicle control data monitoring table.
[0144] Among them, at least part of the second key node vehicle control information includes a vehicle control request identifier of the target vehicle control request.
[0145] In step S903, in response to determining that the vehicle control process message is not at the command initialization process node, the remaining second key node vehicle control information of the executed key nodes is written into the vehicle control data monitoring table.
[0146] In step S904 , in response to determining that the vehicle control process message is at the last node of the vehicle control process, the third global vehicle control information is written into the vehicle control data monitoring table.
[0147] In the embodiment of the present application, the vehicle control process monitoring device obtains the second global vehicle control information and the second key node vehicle control information in the vehicle control process message topic of Kafka, and when writing into the vehicle control data monitoring table, the vehicle control monitoring device can first subscribe to the vehicle control process message in Kafka. In this way, when the vehicle control process message in Kafka is updated, for example, an entity class composed of information elements in the key node log corresponding to the target vehicle control request is written into the vehicle control process message topic in Kafka, the vehicle control process monitoring device can obtain the written entity class and extract the information that needs to be written into the vehicle control monitoring data table.
[0148] Furthermore, when extracting information, the vehicle control process monitoring device can first determine whether the vehicle control process message is in the command initialization process node. If so, it indicates that the vehicle control process has just started to execute and the log of the key node has not yet been printed. At this time, only the first global vehicle control information, the second global vehicle control information, the first key node vehicle control information and at least part of the second key node vehicle control information can be written into the vehicle control data monitoring table. At the same time, the execution status of the key nodes that have not yet been executed can also be set to pending execution.
[0149] On the contrary, if it is determined that the vehicle control process message is not in the command initialization process node, the vehicle control information of the remaining second key node of the executed key node can be written into the vehicle control data monitoring table. In addition, for the key nodes that have been written with vehicle control information, their execution status can also be changed from pending execution to successful execution or failed execution. For the key nodes that failed to execute, the failure reason can be written in the list corresponding to the key node in the vehicle control data monitoring table, or the system log link can be written, or both the failure reason and the system log link can be written.
[0150] In the embodiment of the present application, when extracting information, the vehicle control process monitoring device can also determine whether the vehicle control process message is at the last node of the vehicle control process, that is, the node for printing and feedback execution results. If so, the current system time can be obtained, and the overall time consumption of the target vehicle control request can be calculated, and then the overall time consumption can be written into the vehicle control data monitoring table as the third global vehicle control information. Otherwise, only the vehicle control information of the key nodes updated by this message can be saved.
[0151] That is to say, when the message group obtains the message, it can filter the result and assemble the parameters to store in the database. On the one hand, after obtaining the message and parsing it, it can be determined whether the node in the message is a command initialization (INITIALIZE) process node. If it is the first step, the mobile phone number, device number pdid, command type commandType, command action command, vehicle control request identifier requestId and time time in the message are stored in the vehicle control process monitoring table tsp_vehicle_control_monitor, and the execution result is set to the executing state. The time consumption is temporarily not filled in, and the data is updated after the execution is completed. The second step is to store the vehicle control request identifier requestId, process monitoring node type, execution time point, reason reason, result result, and system kibna address in the vehicle control process monitoring table detail table tsp_vehicle_control_monitor_detail. If not, only the vehicle control request identifier requestId, process monitoring node type, execution time point, reason reason, and result result need to be stored in the tsp_vehicle_control_monitor_detail table.
[0152] On the other hand, after obtaining and parsing the message, it can be determined whether the message is the last node of the vehicle control process, that is, whether node is equal to SENDAPPMSG. If so, first obtain the time corresponding to the start of the vehicle control instruction from tsp_vehicle_control_monitor according to the vehicle control request identifier requestId, and subtract the current message time to obtain the costTime vehicle control time. Then determine whether the current SENDAPPMSG is successful. If successful, update the execution result and time in the tsp_vehicle_control_monitor table. Finally, store the vehicle control request identifier requestId, process monitoring node type, execution time point, reason reason, result result, system kibna address in the tsp_vehicle_control_monitor_detail table.
[0153] If not, the vehicle control request identifier requestId, process monitoring node type, execution time point, reason reason, result result, and system kibna address are stored in the tsp_vehicle_control_monitor_detail table.
[0154] Fig.10 1 is a flow chart of a method for writing third global vehicle control information into a vehicle control data monitoring table in response to determining that the TSP completes the execution of the target vehicle control process provided by an embodiment of the present application. Fig.10 As shown, the method comprises the following steps:
[0155] In step S1001 , in response to determining that the TSP completes the execution of the target vehicle control process, the total execution time of the target vehicle control process is obtained.
[0156] In step S1002 , the total execution time is written into the vehicle control data monitoring table as the third global vehicle control information.
[0157] In the embodiment of the present application, the third global vehicle control message may be the total execution time of the target vehicle control process. Therefore, in response to determining that the TSP completes the execution of the target vehicle control process, writing the third global vehicle control information in the vehicle control data monitoring table may be, when determining that the TSP completes the execution of the target vehicle control process, obtaining the total execution time of the target vehicle control process, and then writing the total execution time as the third global vehicle control information into the vehicle control data monitoring table.
[0158] Fig.11 1 is a flow chart of a method for collecting, parsing, storing and displaying system logs provided in an embodiment of the present application. Fig.11As shown in the figure, the system logs can be collected from each service through the log collection framework and converted into log files by filebeat. The log files can be transferred to logstash, parsed in logstash and stored in the database (ES) and Kafka respectively. The log data in ES can be displayed through the visualization platform kibana. The log data in Kafka can be subscribed by the vehicle control process monitoring service, and the vehicle control process monitoring service generates a vehicle control process monitoring table based on the log data, and further stores the vehicle control process monitoring table in a database such as mysql.
[0159] Table 1 is a vehicle control process monitoring table provided in an embodiment of the present application. As shown in Table 1, the vehicle control process monitoring table includes a main table and a key node table. Among them, the main table includes user identification, vehicle identification, vehicle control instructions, time for issuing vehicle control instructions, execution results, total time and vehicle control request identification requestId fields, and each key node table includes vehicle control request identification requestId, key node identification, execution status, failure reason, execution time period and system log link field. Table 1 gives exemplary information of each field, where the execution status success indicates successful execution.
[0160] Table 1 Vehicle control process monitoring table
[0161] That is to say, in the embodiment of the present application, the second key node vehicle control information at least includes the vehicle control request identifier, execution status and execution time of the target vehicle control request. Among them, the execution status includes execution success, execution failure and execution. In response to the execution status being execution failure, the second key node vehicle control information also includes at least one of the failure reason and the system log link.
[0162] Fig.12 FIG. 1 is a flow chart of a method for monitoring a vehicle control process using a vehicle control data monitoring table provided in an embodiment of the present application. Fig.12 As shown, the method comprises the following steps:
[0163] In step S1201, a vehicle control data monitoring table corresponding to the target vehicle control request is obtained, and a reason for failure to execute the target vehicle control request is determined based on the vehicle control data monitoring table.
[0164] In step S1202, a vehicle control data monitoring table set corresponding to the target type vehicle control request of the target vehicle is obtained, and a vehicle control process warning strategy or a vehicle control process optimization strategy is determined based on the vehicle control data monitoring table set.
[0165] In the embodiment of the present application, monitoring the vehicle control process using the vehicle control data monitoring table may be to obtain the vehicle control data monitoring table corresponding to the target vehicle control request, and determine the reason for the failure to execute the target vehicle control request based on the vehicle control data monitoring table.
[0166] Among them, the front end of the vehicle control process monitoring device can call the interface v0 / vehicle / control / monitor provided by the TSP cloud, and pass in the command, execution status, time period, user ID, and VIN code. After receiving the request, the TSP cloud determines whether the VIN has a value. If there is a value, it queries the device number pdid corresponding to the vehicle based on vin, and then returns the command, execution status, time period, and user ID to the front end from the tsp_vehicle_control_monitor table and displays it on the page.
[0167] In one example, the vehicle control data monitoring table can be directly graphically displayed on the user interface of the vehicle control process monitoring device, so that the user can monitor the execution process of the vehicle control process in real time.
[0168] Fig.13 Schematic diagram of the vehicle control process monitoring graphical display interface provided by the embodiment of the present application. Fig.13 As shown in the upper middle figure, the total execution time costTime of the vehicle control process of this vehicle control request is 1.2 seconds. The requeid of this vehicle control request and the execution time of each key node are displayed in this interface, and all key nodes of this vehicle control process are successfully executed.
[0169] On the other hand, Fig.13 As shown in the figure below, the total execution time of the vehicle control process of this vehicle control request is 1 second, but the key node processing TBOX response execution failed, so the execution status of the subsequent node feedback APP execution result is not executed. Furthermore, the requeid of this vehicle control request and the execution time of the key nodes that have been successfully executed are displayed in this interface, and the failure reasons and system log links of the key nodes that failed to execute are also displayed in the interface.
[0170] In an embodiment of the present application, the vehicle control process can also be monitored using a vehicle control data monitoring table by obtaining a set of vehicle control data monitoring tables corresponding to a target type vehicle control request of the target vehicle, and determining a vehicle control process warning strategy or a vehicle control process optimization strategy based on the set of vehicle control data monitoring tables.
[0171] In other words, it is also possible to monitor the total number of remote controls and the failure distribution and time consumption distribution of key task node types for all users in different time periods. For example, the total number of remote controls and the failure rate of key task node types can be counted. In an example, the front end can call the interface v0 / vehicle / control / fail / count provided by the TSP cloud and pass in the time period selected by the user, such as the start time and the end time. After receiving the front-end request, the TSP cloud queries the vehicle control records of failed execution from tsp_vehicle_control_monitor to obtain the total number of remote control failures. If there is a failure, query which node failed from tsp_vehicle_control_monitor_detail, and then group and sum according to the key node type to obtain the failure rate of each key node of the remote control. For example, the total number of failures is 100, of which 10 times failed to process the key task node type of HANDTBOX (processing TBOX response), accounting for 10 / 100=10%.
[0172] For example, the time consumption of remote control can be counted separately. In one example, the front end can call the interface v0 / vehicle / control / time / count provided by the TSP cloud, and pass in the time period selected by the user, such as the start time and the end time. After receiving the front-end request, the TSP cloud filters out the records of successful vehicle control from tsp_vehicle_control_monitor, and then groups them according to the vehicle control type (for example, car locks are one type, and car windows are another type, and each type has a different time consumption distribution). Each type of data is sorted by time using the bubble sort algorithm and stored in the container collection as costTime. Next, statistics are performed according to the preset interval time, such as 100 milliseconds, 0-100, 100-200,…, 1000-1100,…, for example, 0-100 is traversed from costTime in order from 0-100; for 100-200,… is similar. TSP returns the results to the front-end. For example, the vehicle control type LOCK (car lock) 0-100 accounts for 0%, 600-700 accounts for 10%, 800-900 accounts for 50%, 900-1000 accounts for 30%, 1000-1100 accounts for 9%, and 1100-1200 accounts for 1%. From the data, we can clearly understand the time consumption and proportion of the entire remote control, thereby helping vehicle control application suppliers to better understand their entire system and whether the performance affects user use. Results can be predicted in advance from data analysis instead of waiting for user feedback to discover and troubleshoot problems.
[0173] Fig.14 Schematic diagram of the monitoring interface of the vehicle control process monitoring device provided in the embodiment of the present application. Fig.14As shown, in the monitoring interface of the vehicle control process monitoring device, the user can query the vehicle control process execution information by entering one or more of the issued instructions, execution status, issued time, user identification (user mobile phone number) and vehicle VIN code. The queried information is displayed in the format of user mobile phone number, issued instructions, VIN, execution status, execution result, and issued time. Among them, the issued instruction refers to the vehicle control instruction issued by the user through the owner APP, such as CHARGE:ON, where CHARGE indicates the type of charging vehicle control instruction and ON means on. The execution status indicates the final execution result of the vehicle control instruction, for example FINISHED=success, ABNORMAL=failure. The execution result indicates the description of the reason for the failure of the execution result. The issuing time is the time when the user clicks on the vehicle control instruction in the owner APP.
[0174] That is to say, when the tester or the car owner APP user fails to use the vehicle control, and therefore needs a technician to check, the technician can enter the vehicle VIN through the vehicle control data monitoring interface to query the results of each vehicle control request operated by the current tester or the car owner APP user; then Fig.13 The vehicle control execution failure flow chart shown in the figure below clearly shows which key link failed, the reason for failure, time consumption and other information. If the reason for the vehicle control failure cannot be determined at this time, the technician can directly click the system log button link below to jump to the visualization platform kibana log, and pass in the vehicle control request identifier requestId to query the start time and end time of the log. This method can improve the efficiency of finding and locating problems several times.
[0175] By adopting the technical solution of the embodiment of the present application, it is possible to implement process monitoring of each vehicle control on the TSP platform, and mark the status of each key node passed by the vehicle control. Parse according to specific parsing log data rules and store in a database (with a component for storing data). The vehicle control process monitoring page of the TSP management platform displays the execution status of each vehicle and different types of remote control at different key nodes; the time taken to complete the vehicle control execution; and the request number of the system log. It is possible to monitor all users in different time periods, various remote control failure rates, time distribution, and distribution of remote control failures at different key nodes.
[0176] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present application, which will not be described one by one here.
[0177] The following is an embodiment of the device of the present application, which can be used to execute the embodiment of the method of the present application. For details not disclosed in the embodiment of the device of the present application, please refer to the embodiment of the method of the present application.
[0178] Fig.15Schematic diagram of a vehicle control process monitoring device provided in an embodiment of the present application. Fig.15 As shown, the device comprises:
[0179] The generating module 1501 is configured to generate a vehicle control data monitoring table of the target vehicle control request in response to receiving the target vehicle control request.
[0180] The writing module 1502 is configured to write the first global vehicle control information and the first key node vehicle control information into the vehicle control data monitoring table.
[0181] The writing module 1502 is also configured to write the second global vehicle control information and the second key node vehicle control information in the vehicle control data monitoring table in response to determining that the TSP executes the target vehicle control process corresponding to the target vehicle control request in sequence.
[0182] The writing module 1502 is further configured to write the third global vehicle control information into the vehicle control data monitoring table in response to determining that the TSP completes execution of the target vehicle control process, thereby completing the vehicle control data monitoring table requested by the target vehicle control.
[0183] The monitoring module 1503 is configured to save the completed vehicle control data monitoring table in a database, and use the vehicle control data monitoring table to monitor the vehicle control process.
[0184] According to the technical solution provided in the embodiment of the present application, by extracting key nodes from the process of TSP executing vehicle control, a vehicle control data monitoring table is generated when a target vehicle control request is received, and first the first global vehicle control information and the first key node vehicle control information are written therein. Then, when TSP executes to a key node in the vehicle control process, the second global vehicle control information and the second key node vehicle control information are written therein. Further, after TSP completes the execution of the target vehicle control process, the third global vehicle control information is written therein to complete the vehicle control data monitoring table of the target vehicle control request. Finally, the completed vehicle control data monitoring table is saved in a database so as to use the vehicle control data monitoring table to monitor the vehicle control process, thereby achieving detailed monitoring of the vehicle control process. Not only can the execution results of the vehicle control request be monitored, but also the execution status information of the key nodes in the execution process can be obtained, thereby greatly improving the monitoring information flow and providing strong data support for subsequent troubleshooting and vehicle control data analysis.
[0185] In an embodiment of the present application, the first global vehicle control information and the first key node vehicle control information are written into the vehicle control data monitoring table, including: obtaining user identification information, vehicle identification information and key node identification; obtaining vehicle control command information corresponding to the target vehicle control request; writing the user identification information, vehicle identification information and the vehicle control command information corresponding to the target vehicle control request as the first global vehicle control information into the vehicle control data monitoring table, and writing the key node identification as the first key node vehicle control information into the vehicle control data monitoring table.
[0186] In an embodiment of the present application, in response to determining that TSP is executed to a key node in the target vehicle control process, second global vehicle control information and second key node vehicle control information are written into the vehicle control data monitoring table, including: collecting and filtering logs from TSP devices where each key node is located, and when TSP is executed to a key node in the target vehicle control process, filtering the vehicle control logs of the key nodes; parsing the data in the vehicle control logs, and writing the parsed vehicle control data as the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table.
[0187] In an embodiment of the present application, the key nodes in the target vehicle control process include: command initialization process node, SMS wake-up process node, vehicle communication module TBOX login process node, command sending to cloud native message server and stream processing database EMQ process node, TBOX response acquisition process node, TBOX response processing process node and execution result feedback process node.
[0188] In an embodiment of the present application, in response to determining that TSP executes to a key node in the target vehicle control process, second global vehicle control information and second key node vehicle control information are written into the vehicle control data monitoring table, including: in response to determining that TSP executes to a command initialization process node, obtaining a vehicle control request identifier of the target vehicle control request, and a issuance time of a vehicle control instruction corresponding to the target vehicle control request; writing the vehicle control request identifier and the issuance time as the second global vehicle control information into the vehicle control data monitoring table; and writing the vehicle control request identifier into the vehicle control data monitoring table as at least part of the second key node vehicle control information.
[0189] In an embodiment of the present application, when the target vehicle control process is executed to the target key node, the TSP device where the target key node is located prints the vehicle control log of the target key node for collection by the vehicle control process monitoring device, and the target key node is any key node in the target vehicle control process; wherein, when the target vehicle control process is executed to the target key node, the TSP device where the target key node is located prints the vehicle control log of the target key node, including: in response to determining that the vehicle control application background service device in the TSP completes the encapsulation of the vehicle control instruction corresponding to the target vehicle control request, the vehicle control application background service device prints the command initialization log; in response to determining that the vehicle service device in the TSP receives the SMS sending result returned by the operator, the vehicle service device prints the SMS sending wake-up log; in response to determining that the vehicle service device in the TSP receives the TB OX sends a TBOX login request via EMQ, the device gateway and the message middleware Kafka, and the vehicle service device prints the TBOX login log; in response to determining that the device gateway in the TSP receives the successful reception of the target vehicle control request message sent by EMQ, the device gateway prints the send command to the EMQ log; in response to determining that the device gateway in the TSP receives the vehicle control instruction execution result sent by TBOX via EMQ, the device gateway prints the TBOX response log; in response to determining that the vehicle control application background service device in the TSP receives the vehicle control instruction execution result from Kafka, the vehicle control application background service prints the processing TBOX log; in response to determining that the vehicle control application background service device in the TSP completes the business processing based on the TBOX response result, the vehicle control application background service prints the feedback execution result log.
[0190] In an embodiment of the present application, when the TSP executes to a key node in the target vehicle control process, the vehicle control log of the key node is screened and obtained, including: when the TSP executes the target vehicle control process, the vehicle control process monitoring device collects all logs of the key node; after the TSP executes to the key node in the target vehicle control process and completes the printing of the vehicle control log of the key node, the vehicle control process monitoring device collects the vehicle control log of the key node; the vehicle control process monitoring device parses all the collected logs, and in response to the analysis determining that the log includes a vehicle control log identifier, the vehicle control log of the key node is screened and obtained.
[0191] In an embodiment of the present application, data in a vehicle control log is parsed, and the vehicle control data obtained by the parsing is written into a vehicle control data monitoring table as second global vehicle control information and second key node vehicle control information, including: using a log framework to write all logs collected by a vehicle control process monitoring device into a log file; using a log data collection tool to send all data in the log file to a log parsing tool; when the log parsing tool determines that the target log includes a vehicle control log identifier in the target log, the log parsing tool determines that the target log is a vehicle control log; the log parsing tool uses preset parsing rules to segment the data in the vehicle control log to obtain parsed vehicle control log elements, and the parsed vehicle control log elements include the second global vehicle control information and the second key node vehicle control information; the parsed vehicle control log elements are repackaged into an entity class, and the entity class is sent to the vehicle control process message topic of Kafka in the TSP; the vehicle control process monitoring device obtains the second global vehicle control information and the second key node vehicle control information in the vehicle control process message topic of Kafka, and writes them into the vehicle control data monitoring table.
[0192] In an embodiment of the present application, the vehicle control process monitoring device obtains the second global vehicle control information and the second key node vehicle control information in the vehicle control process message topic of Kafka, and writes them into the vehicle control data monitoring table, including: the vehicle control process monitoring device obtains the vehicle control process message of the target vehicle control request from Kafka; in response to determining that the vehicle control process message is at the command initialization process node, the first global vehicle control information, the second global vehicle control information, the first key node vehicle control information and at least part of the second key node vehicle control information are written into the vehicle control data monitoring table, at least part of the second key node vehicle control information includes the vehicle control request identifier of the target vehicle control request; in response to determining that the vehicle control process message is not at the command initialization process node, the remaining part of the second key node vehicle control information of the executed key node is written into the vehicle control data monitoring table; in response to determining that the vehicle control process message is at the last node of the vehicle control process, the third global vehicle control information is written into the vehicle control data monitoring table.
[0193] In an embodiment of the present application, in response to determining that the TSP completes the execution of the target vehicle control process, the third global vehicle control information is written into the vehicle control data monitoring table, including: in response to determining that the TSP completes the execution of the target vehicle control process, obtaining the total execution time of the target vehicle control process; and writing the total execution time as the third global vehicle control information into the vehicle control data monitoring table.
[0194] In an embodiment of the present application, the vehicle control information of the second key node includes at least the vehicle control request identifier, execution status and execution time of the target vehicle control request; the execution status includes execution success, execution failure and execution in progress; in response to the execution status being execution failure, the vehicle control information of the second key node also includes at least one of the failure cause and the system log link.
[0195] In an embodiment of the present application, a vehicle control process is monitored using a vehicle control data monitoring table, including: obtaining a vehicle control data monitoring table corresponding to a target vehicle control request, and determining a cause of failure to execute the target vehicle control request based on the vehicle control data monitoring table; or obtaining a set of vehicle control data monitoring tables corresponding to a target type vehicle control request of a target vehicle, and determining a vehicle control process early warning strategy or a vehicle control process optimization strategy based on the set of vehicle control data monitoring tables.
[0196] It should be understood that the size of the serial numbers of the steps in the above embodiments does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.
[0197] Fig.16 Schematic diagram of an electronic device provided in an embodiment of the present application. Fig.16 As shown, the electronic device 16 of this embodiment includes: a processor 1601, a memory 1602, and a computer program 1603 stored in the memory 1602 and executable on the processor 1601. When the processor 1601 executes the computer program 1603, the steps in the above-mentioned method embodiments are implemented. Alternatively, when the processor 1601 executes the computer program 1603, the functions of the modules / units in the above-mentioned device embodiments are implemented.
[0198] The electronic device 16 may be a desktop computer, a notebook, a PDA, a cloud server, or other electronic device. The electronic device 16 may include, but is not limited to, a processor 1601 and a memory 1602. Those skilled in the art will appreciate that Fig.16 The electronic device 16 is merely an example and does not limit the electronic device 16 , and may include more or less components than those shown in the figure, or different components.
[0199] The processor 1601 may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field-programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
[0200] The memory 1602 may be an internal storage unit of the electronic device 16, for example, a hard disk or memory of the electronic device 16. The memory 1602 may also be an external storage device of the electronic device 16, for example, a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card (FlashCard), etc. equipped on the electronic device 16. The memory 1602 may also include both an internal storage unit of the electronic device 16 and an external storage device. The memory 1602 is used to store computer programs and other programs and data required by the electronic device.
[0201] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of software functional units.
[0202] If the integrated module / unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present application implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium, and the computer program can implement the steps of the above-mentioned various method embodiments when executed by the processor. The computer program may include computer program code, which may be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device capable of carrying computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electric carrier signal, telecommunication signal and software distribution medium, etc.
[0203] The above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present application, and should all be included in the protection scope of the present application.
Claims
1. A vehicle control process monitoring method, characterized in that: The method is performed by a vehicle control process monitoring device, and includes: In response to receiving a target vehicle control request, the vehicle control process monitoring device generates a vehicle control data monitoring table of the target vehicle control request, and writes first global vehicle control information and first key node vehicle control information into the vehicle control data monitoring table, wherein the first global vehicle control information includes user identification information, vehicle identification information and vehicle control instruction information corresponding to the target vehicle control request, and the first key node vehicle control information includes a predefined key node identification; When the Internet of Vehicles content service provider platform TSP sequentially executes the target vehicle control process corresponding to the target vehicle control request, in response to determining that the TSP executes to a key node in the target vehicle control process, second global vehicle control information and second key node vehicle control information are written into the vehicle control data monitoring table, wherein the second global vehicle control information is a vehicle control request identifier of the target vehicle control request and a time when the vehicle control instruction corresponding to the target vehicle control request is issued, and at least part of the second key node vehicle control information includes the vehicle control request identifier of the target vehicle control request; In response to determining that the TSP completes the execution of the target vehicle control process, third global vehicle control information is written into the vehicle control data monitoring table to complete the vehicle control data monitoring table of the target vehicle control request, wherein the third global vehicle control information is the overall time consumed to execute the target vehicle control request; The completed vehicle control data monitoring table is saved in a database, and the vehicle control process is monitored using the vehicle control data monitoring table.
2. The method according to claim 1, characterized in that Writing the first global vehicle control information and the first key node vehicle control information into the vehicle control data monitoring table includes: Obtain user identification information, vehicle identification information and key node identification; Obtain vehicle control command information corresponding to the target vehicle control request; The user identification information, vehicle identification information and vehicle control instruction information corresponding to the target vehicle control request are written into the vehicle control data monitoring table as the first global vehicle control information, and the key node identification is written into the vehicle control data monitoring table as the first key node vehicle control information.
3. The method according to claim 1, characterized in that In response to determining that the TSP is executed to a key node in the target vehicle control process, writing second global vehicle control information and second key node vehicle control information into the vehicle control data monitoring table includes: Collect and filter logs from TSP devices at each key node, and filter the vehicle control logs of the key node when TSP is executed to the key node in the target vehicle control process; The data in the vehicle control log is parsed, and the vehicle control data obtained by the parsing is written into the vehicle control data monitoring table as the second global vehicle control information and the second key node vehicle control information.
4. The method according to claim 3, characterized in that The key nodes in the target vehicle control process include: Command initialization process node, SMS wake-up process node, vehicle communication module TBOX login process node, send command to cloud native message server and stream processing database EMQ process node, obtain TBOX response process node, process TBOX response process node and feedback execution result process node.
5. The method according to claim 4, characterized in that In response to determining that the TSP is executed to a key node in the target vehicle control process, writing second global vehicle control information and second key node vehicle control information into the vehicle control data monitoring table includes: In response to determining that the TSP is executed to the command initialization process node, a vehicle control request identifier of a target vehicle control request and a time when a vehicle control instruction corresponding to the target vehicle control request is issued are obtained; Writing the vehicle control request identifier and the issuing time as second global vehicle control information into the vehicle control data monitoring table; and The vehicle control request identifier is written into the vehicle control data monitoring table as at least part of the second key node vehicle control information.
6. The method according to claim 5, characterized in that When the target vehicle control process is executed to the target key node, the TSP device where the target key node is located prints the vehicle control log of the target key node for collection by the vehicle control process monitoring device. The target key node is any key node in the target vehicle control process. Wherein, the TSP device where the target key node is located prints the vehicle control log of the target key node when the target vehicle control process is executed to the target key node, including: In response to determining that the vehicle control application background service device in the TSP completes encapsulation of the vehicle control instruction corresponding to the target vehicle control request, the vehicle control application background service device prints a command initialization log; In response to determining that the vehicle service device in the TSP receives the SMS sending result returned by the operator, the vehicle service device prints a SMS sending wake-up log; In response to determining that the vehicle service device in the TSP receives a TBOX login request sent by the TBOX via the EMQ, the device gateway and the message middleware Kafka, the vehicle service device prints a TBOX login log; In response to determining that the device gateway in the TSP receives the successfully received target vehicle control request message sent by the EMQ, the device gateway prints a send command to the EMQ log; In response to determining that the device gateway in the TSP receives the vehicle control instruction execution result sent by the TBOX via the EMQ, the device gateway prints the TBOX response log; In response to determining that the vehicle control application background service device in the TSP receives the vehicle control instruction execution result from Kafka, the vehicle control application background service prints and processes the TBOX log; In response to determining that the vehicle control application background service device in the TSP completes the business processing based on the TBOX response result, the vehicle control application background service prints a feedback execution result log.
7. The method according to claim 4, characterized in that When the TSP is executed to a key node in the target vehicle control process, the vehicle control log of the key node is screened and obtained, including: The vehicle control process monitoring device collects all logs of the key nodes when the TSP executes the target vehicle control process; After the TSP is executed to a key node in the target vehicle control process and the vehicle control log of the key node is printed, the vehicle control process monitoring device collects and obtains the vehicle control log of the key node; The vehicle control process monitoring device parses all the collected logs, and in response to determining that the logs include a vehicle control log identifier, screens the vehicle control logs of the key nodes.
8. The method according to claim 4, characterized in that The step of parsing the data in the vehicle control log and writing the vehicle control data obtained by the parsing as the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table includes: Using the log framework, all logs collected by the vehicle control process monitoring device are written into a log file; Use the log data collection tool to send all the data in the log file to the log parsing tool; When the log parsing tool determines that the target log includes the vehicle control log identifier, the target log is determined to be the vehicle control log; The log parsing tool uses a preset parsing rule to segment the data in the vehicle control log to obtain a parsed vehicle control log element, wherein the parsed vehicle control log element includes the second global vehicle control information and the second key node vehicle control information; Re-encapsulate the parsed vehicle control log elements into entity classes, and send the entity classes to the vehicle control process message topic of Kafka in the TSP; The vehicle control process monitoring device obtains the second global vehicle control information and the second key node vehicle control information from the vehicle control process message topic of Kafka, and writes them into the vehicle control data monitoring table.
9. The method according to claim 8, characterized in that The vehicle control process monitoring device obtains the second global vehicle control information and the second key node vehicle control information from the vehicle control process message topic of Kafka, and writes them into the vehicle control data monitoring table, including: The vehicle control process monitoring device obtains the vehicle control process message of the target vehicle control request from the Kafka; In response to determining that the vehicle control process message is at a command initialization process node, writing the first global vehicle control information, the second global vehicle control information, the first key node vehicle control information and at least part of the second key node vehicle control information into the vehicle control data monitoring table, wherein the at least part of the second key node vehicle control information includes a vehicle control request identifier of a target vehicle control request; In response to determining that the vehicle control process message is not at a command initialization process node, writing the remaining second key node vehicle control information of the executed key node into the vehicle control data monitoring table; In response to determining that the vehicle control process message is at the last node of the vehicle control process, third global vehicle control information is written into the vehicle control data monitoring table.
10. The method according to claim 1, characterized in that In response to determining that the TSP completes the execution of the target vehicle control process, writing third global vehicle control information into the vehicle control data monitoring table includes: In response to determining that the TSP completes the execution of the target vehicle control process, obtaining a total execution time of the target vehicle control process; The total execution time is written into the vehicle control data monitoring table as the third global vehicle control information.
11. The method according to claim 1, characterized in that: The second key node vehicle control information at least includes a vehicle control request identifier, an execution status and an execution time of the target vehicle control request; The execution status includes execution success, execution failure and execution in progress; In response to the execution status being execution failure, the second key node vehicle control information further includes at least one of a failure reason and a system log link.
12. The method according to claim 1, characterized in that The method of monitoring the vehicle control process by using the vehicle control data monitoring table includes: Obtaining a vehicle control data monitoring table corresponding to the target vehicle control request, and determining a reason for a failure to execute the target vehicle control request based on the vehicle control data monitoring table; or A vehicle control data monitoring table set corresponding to a target type vehicle control request of a target vehicle is obtained, and a vehicle control process early warning strategy or a vehicle control process optimization strategy is determined based on the vehicle control data monitoring table set.
13. A vehicle control process monitoring device, characterized in that: include: A generating module, configured to generate a vehicle control data monitoring table of the target vehicle control request in response to receiving the target vehicle control request; A writing module is configured to write first global vehicle control information and first key node vehicle control information into the vehicle control data monitoring table, wherein the first global vehicle control information includes user identification information, vehicle identification information and vehicle control instruction information corresponding to the target vehicle control request, and the first key node vehicle control information includes a predefined key node identification; The writing module is further configured to write second global vehicle control information and second key node vehicle control information into the vehicle control data monitoring table in response to determining that the TSP executes to a key node in the target vehicle control process when the vehicle networking content service providing platform TSP sequentially executes the target vehicle control process corresponding to the target vehicle control request, wherein the second global vehicle control information is a vehicle control request identifier of the target vehicle control request and a time when the vehicle control instruction corresponding to the target vehicle control request is issued, and at least part of the second key node vehicle control information includes the vehicle control request identifier of the target vehicle control request; The writing module is further configured to write third global vehicle control information into the vehicle control data monitoring table in response to determining that the TSP completes the execution of the target vehicle control process, and complete the vehicle control data monitoring table of the target vehicle control request, wherein the third global vehicle control information is the overall time consumed to execute the target vehicle control request; The monitoring module is configured to save the completed vehicle control data monitoring table in a database, and use the vehicle control data monitoring table to monitor the vehicle control process.
14. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 12 are implemented.
15. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 12 are implemented.
Citation Information
Patent Citations
Vehicle remote interaction event tracking system
CN111212133A
Full-process test analysis system and method for controlling vehicle through Android mobile phone APP
CN113691669A
Link analysis method and device, electronic equipment, storage medium and vehicle
CN114968643A
Link monitoring method based on mobile phone remote control vehicle machine
CN117479198A
Service abnormity monitoring method and device, electronic equipment and readable storage medium
CN117632644A
