CN118796612B

CN118796612B - Vehicle control process monitoring method, device, electronic equipment and storage medium

Info

Publication number: CN118796612B
Application number: CN202411269058.6A
Authority: CN
Inventors: 杨鹏作; 魏建军
Original assignee: Chengdu Seres Technology Co Ltd
Current assignee: Chengdu Seres Technology Co Ltd
Priority date: 2024-09-11
Filing date: 2024-09-11
Publication date: 2024-11-26
Anticipated expiration: 2044-09-11
Also published as: CN118796612A

Abstract

The application relates to the technical field of intelligent vehicles, and provides a vehicle control flow monitoring method, a device, electronic equipment and a storage medium. According to the method, key nodes are extracted from a process of executing vehicle control on the TSP, a vehicle control data monitoring table is generated when a target vehicle control request is received, first global vehicle control information and first key node vehicle control information are written, then second global vehicle control information and second key node vehicle control information are written into the key nodes in the process of executing the TSP, further third global vehicle control information is written into the process of executing the TSP after the completion of the target vehicle control process, the vehicle control data monitoring table of the target vehicle control request is completed, and finally the completed vehicle control data monitoring table is stored in a database to monitor the vehicle control process by utilizing the vehicle control data monitoring table, so that the execution condition information of the key nodes in the execution process can be obtained, the monitoring information flow is greatly improved, and powerful data support is provided for follow-up fault removal and vehicle control data analysis.

Description

Vehicle control flow monitoring method and device, electronic equipment and storage medium

Technical Field

The present application relates to the field of intelligent vehicles, and in particular, to a method and apparatus for monitoring a vehicle control flow, an electronic device, and a storage medium.

Background

The internet of vehicles content service providing platform (TELEMATICS SERVICE Provider, TSP) refers to a service Provider that provides intelligent services for automobiles based on the internet and communication network. The system is an indispensable part of an automobile networking system, and mainly relates to functions of vehicle safety, vehicle monitoring, navigation, communication, infotainment, driving behavior analysis and the like. The TSP plays an important role in connecting vehicles with bridges in the Internet world, and can realize the functions of vehicle state monitoring, remote monitoring, early warning, command and the like through information exchange between vehicle-mounted equipment and the Internet. Meanwhile, the TSP can provide functions of intelligent navigation, entertainment, online updating and the like for the vehicle owner, so that a driver has more convenient and comfortable driving experience.

The process of TSP and vehicle interaction involves a very large number of systems, any of which are problematic and can result in the user not being able to use the controls. Meanwhile, because the system is very involved in the interaction process of the TSP and the vehicle, the problem of any link can cause that the user cannot use the vehicle control. Furthermore, the technicians cannot know that the vehicle is healthy and stable in operation in advance.

Disclosure of Invention

In view of the above, the embodiments of the present application provide a method, an apparatus, an electronic device, and a storage medium for monitoring a vehicle control process, so as to solve the problems of insufficient fine monitoring and early warning lag in the vehicle control process in the prior art.

In a first aspect of the embodiment of the present application, there is provided a vehicle control flow monitoring method, which is executed by a vehicle control flow monitoring device, including:

In response to receiving the target vehicle control request, the vehicle control flow monitoring equipment 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 in the vehicle control data monitoring table;

When the TSP provides a content service providing platform of the Internet of vehicles to sequentially execute a target vehicle control process corresponding to the target vehicle control request, responding to determining that the TSP is executed to a key node in the target vehicle control process, and 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 the TSP completes execution of the target vehicle control flow, writing 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;

And storing the finished vehicle control data monitoring table in a database, and monitoring the vehicle control flow by using the vehicle control data monitoring table.

In a second aspect of the embodiment of the present application, there is provided a vehicle control flow monitoring device, including:

the generation module is configured to respond to the received target vehicle control request, and the vehicle control flow monitoring equipment generates a vehicle control data monitoring table of the target vehicle control request;

The writing module is configured to write first global vehicle control information and first key node vehicle control information in the vehicle control data monitoring table;

The writing module is further configured to write second global vehicle control information and second key node vehicle control information in the vehicle control data monitoring table in response to determining that the TSP is executed to a key node in the target vehicle control flow when the vehicle networking content service providing platform TSP sequentially executes the target vehicle control flow corresponding to the target vehicle control request;

The writing module is further configured to write third global vehicle control information in the vehicle control data monitoring table in response to determining that the TSP completes execution of the target vehicle control flow, and complete the vehicle control data monitoring table of the target vehicle control request;

And the monitoring module is configured to store the completed vehicle control data monitoring table in the database and monitor the vehicle control flow by using the vehicle control data monitoring table.

In a third aspect of the embodiments of the present application, there is provided an electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the above method when executing the computer program.

In a fourth aspect of the embodiments of the present application, there is provided a computer readable storage medium storing a computer program which, when executed by a processor, implements the steps of the above method.

Compared with the prior art, the embodiment of the application has the beneficial effects that: according to the embodiment of the application, the key nodes are extracted from the flow of the TSP executing the vehicle control, the vehicle control data monitoring table is generated when the target vehicle control request is received, the first global vehicle control information and the first key node vehicle control information are written first, then when the TSP executes to the key nodes in the vehicle control flow, the second global vehicle control information and the second key node vehicle control information are written in the vehicle control data monitoring table, further after the TSP completes the execution of the target vehicle control flow, the third global vehicle control information is written in the vehicle control data monitoring table, the vehicle control data monitoring table of the target vehicle control request is completed, and finally the completed vehicle control data monitoring table is stored in the database to monitor the vehicle control flow by utilizing the vehicle control data monitoring table, so that the detailed monitoring of the vehicle control flow is realized, the execution result of the vehicle control request can be monitored, the execution condition information of the key nodes in the execution flow can be obtained, the monitoring information flow is greatly improved, and powerful data support is provided for the follow-up fault elimination and vehicle control data analysis.

Furthermore, by adopting the technical scheme of the embodiment of the application, abundant vehicle control flow monitoring data can be provided, and the time and cost for technical staff to check the problems are reduced; whether the vehicle control can influence the user experience such as time and failure rate can be perceived in advance by analyzing the data in the vehicle control data monitoring table, so that the fault tolerance rate of the vehicle control application is improved; the data in the vehicle control data monitoring table can be analyzed in advance, so that the problem can be rapidly solved when the user feedback is problematic, the real-time performance of vehicle control application fault processing is improved, and meanwhile, the stability of a vehicle control system is improved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic view of an application scenario according to an embodiment of the present application.

Fig. 2 is a flow chart of a vehicle control flow monitoring method according to an embodiment of the present application.

Fig. 3 is a flowchart of a method 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 flow, which is provided in an embodiment of the present application.

Fig. 4 is a flowchart of another method 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 the TSP is executed to a key node in a target vehicle control flow according to an embodiment of the present application.

Fig. 5 is a flow chart of a method for printing a vehicle control log of a target key node when a TSP device where the target key node is located performs a target vehicle control process to the target key node according to an embodiment of the present application.

Fig. 6 is a flow chart of a method for screening a vehicle control log of a key node when a TSP executes to the key node in a target vehicle control flow according to an embodiment of the present application.

Fig. 7 is an interaction diagram of a vehicle control flow execution method according to an embodiment of the present application.

Fig. 8 is a flow chart of a method for analyzing data in a vehicle control log and writing analyzed vehicle control data into a vehicle control data monitoring table as second global vehicle control information and second key node vehicle control information according to an embodiment of the present application.

Fig. 9 is a flow chart of a method for acquiring second global control information and second key node control information from a control flow message theme of Kafka and writing the second global control information and the second key node control information into a control data monitoring table by using the control flow monitoring device according to the embodiment of the present application.

Fig. 10 is a flowchart of a method for writing third global control information in a control data monitoring table in response to determining that TSP completes execution of a target control flow according to an embodiment of the present application.

FIG. 11 is a flow chart of a method for collecting, parsing, storing and displaying system logs according to an embodiment of the present application.

Fig. 12 is a flow chart of a method for monitoring a vehicle control flow using a vehicle control data monitoring table according to an embodiment of the present application.

Fig. 13 is a schematic diagram of a graphical display interface for monitoring a vehicle control flow according to an embodiment of the present application.

Fig. 14 is a schematic diagram of a monitoring interface of a vehicle control flow monitoring device according to an embodiment of the present application.

Fig. 15 is a schematic diagram of a vehicle control flow monitoring device according to an embodiment of the present application.

Fig. 16 is a schematic diagram of an electronic device according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

A method and apparatus for monitoring a vehicle control flow according to embodiments of the present application will be described in detail with reference to the accompanying drawings.

In the related art, a host factory of a vehicle generally provides an Application (APP), and the APP can control the vehicle and realize the functions of vehicle state monitoring and early warning. TSP in the cloud platform is a support providing capability for the owner APP, so the position of TSP in the internet of vehicles is very central.

As mentioned above, since the TSP and the vehicle are involved in a very large number of systems, any one of the links has a problem, which results in that the user cannot use the vehicle control. Meanwhile, the technicians cannot know that the vehicle is healthy and stable to operate in advance.

Fig. 1 is a schematic view of an application scenario according to an embodiment of the present application. As shown in fig. 1, the TSP may be divided into three parts, namely a vehicle end, a cloud end, and an EMQ. The vehicle end comprises a TBOX, the cloud end comprises an APP, an APP background service, a vehicle equipment service, a Kafka and an equipment gateway, and the EMQ is a bridge for interaction between the vehicle end and the cloud end.

The traditional vehicle control flow is that an APP sends a vehicle control instruction to an APP background service, and after the APP background service receives the vehicle control instruction, the APP background service calls a device center to send a vehicle control request to a vehicle device service, and the vehicle device service sends the request to a Kafka message center. Further, the vehicle equipment service center also returns a task identifier (identity document, id) to the APP background service, and the APP background service further returns a task id to the APP.

The equipment gateway subscribes to the vehicle control request message in Kafka, acquires the vehicle control request after the Kafka receives the vehicle control request, encapsulates the vehicle control request protocol, and then sends the encapsulated protocol to the EMQ. The TBOX subscribes to the vehicle control request message at the EMQ, acquires the vehicle control request protocol after the EMQ receives the encapsulated protocol, and executes the vehicle control request after analyzing the vehicle control instruction. After the TBOX executes the vehicle control request, the vehicle control request task execution result is sent to the EMQ, the equipment gateway subscribes the vehicle control request result message in the EMQ, acquires the vehicle control execution result after the EMQ receives the vehicle control request task execution result sent by the TBOX, and sends the vehicle control execution result to the Kafka message center.

And the APP background service subscribes to the vehicle control execution result message in Kafka, and acquires and stores the vehicle control execution result to the local after the Kafka receives the vehicle control execution result sent by the equipment gateway. Meanwhile, after the APP receives the task id, the task id can be used for periodically acquiring the vehicle control execution result from the APP background service, and after the APP background service receives the vehicle control execution result from the Kafka, the APP background service acquires and displays the vehicle control execution result.

In the related art, the vehicle control flow monitoring can acquire information such as an issuing instruction, an executing state, issuing time, a user mobile phone number, a vehicle identification code (Vehicle Identification Number, VIN), an executing result and the like. That is, the related art can conveniently obtain the result of each operation of the vehicle control instruction by the user, for example, whether the execution of the current vehicle control execution succeeds or fails, and can also obtain the total time consumption of executing the vehicle control instruction in real time. However, the vehicle control flow monitoring method in the related art cannot know in detail which link and key node have problems, and statistically analyze which vehicles may have problems in which links, and the problems are problems of hardware, network, software and the like.

That is, the related art lacks a scheme for monitoring the flow of car control on the TSP platform of the internet of vehicles, and generally simply records the operation record of the car control. With the existing TSP monitoring method, a technician cannot sense in advance whether a user can normally use a car control instruction or not, and can only wait for user feedback, but the problem during user feedback may be serious.

Further, too many systems are involved in the process of TSP and vehicle interaction; the number of times of the user operating the vehicle control is relatively large, and a technician does not know which vehicle control has a problem or which time period has a problem, so that the problem of positioning cannot be quickly solved. Moreover, because too many systems are involved, many systems or components are executing asynchronously, it is not possible to concatenate logs generated at each system for a particular request.

Furthermore, the vehicle control flow monitoring scheme in the related art cannot dynamically check the time-consuming condition of remote control of the vehicle, for example, a user uses a vehicle main Application (APP) in a certain period of time, the TSP bears great pressure, and the time consumption of remote control in a certain period of time is long, so that the user experience is affected.

In addition, when the vehicle control cannot be normally executed, the vehicle control flow monitoring scheme in the related technology cannot quickly and accurately locate whether the vehicle end communication module (TBOX) is abnormal or a cloud service flow is abnormal.

In view of this, the embodiment of the application provides a vehicle control flow monitoring method, a key node is extracted from a flow of performing vehicle control on a TSP, a vehicle control data monitoring table is generated when a vehicle control request is received, first global vehicle control information and first key node vehicle control information are written first, then when the TSP is performed to a key node in the vehicle control flow, second global vehicle control information and second key node vehicle control information are written in the vehicle control data monitoring table, further after the TSP is performed on the target vehicle control flow, third global vehicle control information is written in the vehicle control data monitoring table, the vehicle control data monitoring table of the target vehicle control request is completed, and finally the completed vehicle control data monitoring table is stored in a database to monitor the vehicle control flow by using the vehicle control data monitoring table, so that the vehicle control flow is monitored in detail, the vehicle control flow can be monitored and informed, the execution result of the vehicle control request can be monitored, the execution condition information of the key node in the execution flow can be obtained, and powerful data support is provided for subsequent fault removal and vehicle control data analysis.

Fig. 2 is a flow chart of a vehicle control flow monitoring method according to an embodiment of the present application. As shown in fig. 2, the method comprises the steps of:

In step S201, in response to receiving the target vehicle control request, the vehicle control flow 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 in the vehicle control data monitoring table.

In step S202, when the internet of vehicles content service providing platform TSP sequentially executes the target vehicle control flow corresponding to the target vehicle control request, in response to determining that the TSP is executed to the key node in the target vehicle control flow, the second global vehicle control information and the second key node vehicle control information are written in the vehicle control data monitoring table.

In step S203, in response to determining that the TSP completes execution of the target vehicle control flow, third global vehicle control information is written in the vehicle control data monitoring table, completing the vehicle control data monitoring table of the target vehicle control request.

In step S204, the completed vehicle control data monitoring table is stored in the database, and the vehicle control flow is monitored by using the vehicle control data monitoring table.

In the embodiment of the application, the vehicle control flow monitoring method can be executed by the vehicle control flow monitoring equipment. The vehicle control flow monitoring device can be a terminal device, a server or a distributed device. The vehicle control flow monitoring equipment can be configured with a log acquisition tool, a log data acquisition tool and a log analysis tool, and can also communicate with the TSP so as to encapsulate the log elements obtained by analysis into entity types and then send the entity types to the Kafka, and the entity types are used as vehicle control flow messages in the Kafka for consumption by a message consumer group.

In the embodiment of the application, the vehicle control flow monitoring equipment can generate the vehicle control data monitoring table of 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 in the vehicle control data monitoring table. The target automobile control request is an automobile control request sent to an APP background service by the APP, and the automobile control flow monitoring equipment is used for monitoring an automobile control flow, so that the automobile control request sent by the APP can also be received. After receiving the target vehicle control request, the vehicle control flow monitoring device can generate a vehicle control data monitoring table corresponding to the current vehicle control request. It should be noted that, the content of each item in the newly-built vehicle control data monitoring table is blank, and related information needs to be obtained and written in different modes later.

In the embodiment of the application, after the vehicle control data monitoring table of the target vehicle control request is generated, the vehicle control flow monitoring device can firstly acquire 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.

In the embodiment of the application, the vehicle control flow monitoring equipment can acquire the logs of each key node in the vehicle control flow when the TSP sequentially executes the target vehicle control flow corresponding to the target vehicle control request, screen the logs to obtain the vehicle control log, analyze the vehicle control log to obtain the vehicle control information, and write the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table.

In the embodiment of the application, the vehicle control flow monitoring device can also acquire the third global vehicle control information after the TSP finishes the execution of the target vehicle control flow, and write the third global vehicle control information into the vehicle control data monitoring table, thereby finishing the vehicle control data monitoring table of the target vehicle control request.

And finally, the vehicle control flow monitoring equipment stores the finished vehicle control data monitoring table in a database so that a user can monitor the vehicle control flow by using the vehicle control data monitoring table.

According to the technical scheme provided by the embodiment of the application, the key nodes are extracted from the TSP executing flow, the vehicle control data monitoring table is generated when the target vehicle control request is received, the first global vehicle control information and the first key node vehicle control information are written first, then the second global vehicle control information and the second key node vehicle control information are written in the vehicle control data monitoring table when the TSP executes to the key nodes in the vehicle control flow, further the third global vehicle control information is written in the vehicle control data monitoring table after the TSP completes the execution of the target vehicle control flow, the vehicle control data monitoring table of the target vehicle control request is completed, and finally the completed vehicle control data monitoring table is stored in the database to monitor the vehicle control flow by utilizing the vehicle control data monitoring table, so that the detailed monitoring of the vehicle control flow is realized, the execution result of the vehicle control request can be monitored and known, the execution condition information of the key nodes in the execution flow can be obtained, the monitoring information flow is greatly improved, and the data support is provided for the follow-up fault removal and vehicle control data analysis.

In the embodiment of the application, the first global vehicle control information and the first key node vehicle control information are written in the vehicle control data monitoring table, and the user identification information, the vehicle identification information and the key node identification are obtained; acquiring vehicle control instruction information corresponding to a target vehicle control request; and writing the vehicle control instruction information corresponding to the user identification information, the vehicle identification information and the target vehicle control request into the vehicle control data monitoring table as first global vehicle control information, and writing the key node identification into the vehicle control data monitoring table as first key node vehicle control information.

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, where the user identification information, the vehicle identification information, and the vehicle control instruction information corresponding to the target vehicle control request may be acquired from the target vehicle control request. The first key node vehicle control information may include a key node identification, which may be predefined and recorded as a default item in the vehicle control data monitoring table.

Fig. 3 is a flowchart of a method 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 flow, which is provided in an embodiment of the present application. As shown in fig. 3, the method comprises the steps of:

In step S301, logs are collected and screened from the TSP device where each key node is located, and when the TSP executes to the key node in the target vehicle control flow, vehicle control logs of the key node are obtained through screening.

In step S302, the data in the vehicle control log is analyzed, and the analyzed vehicle control data is used as the second global vehicle control information and the second key node vehicle control information to be written into the vehicle control data monitoring table.

In the embodiment of the application, the second global vehicle control information and the second key node vehicle control information can be obtained by acquiring the logs of each key node in the vehicle control process by the vehicle control process monitoring equipment, screening out the vehicle control logs and analyzing the vehicle control logs. That is, the vehicle control process monitoring device may collect and screen logs from the TSP device where each key node is located, and screen and obtain the vehicle control log of the key node when the TSP is executed to the key node in the target vehicle control process. Furthermore, the vehicle control flow monitoring device can analyze the data in the vehicle control log, and write the analyzed vehicle control data serving as second global vehicle control information and second key node vehicle control information into the vehicle control data monitoring table.

In the embodiment of the application, key nodes in a target vehicle control flow comprise a command initialization flow node, a short message sending wake-up flow node, a vehicle-mounted communication module TBOX login flow node, a command sending to an EMQ flow node, a TBOX response flow node obtaining, a TBOX response flow node processing and an execution result feedback flow node.

The command initialization flow node is used for immediately carrying out legal inspection on the vehicle control request parameters after the APP background service receives the APP end vehicle control request, checking the vehicle control authority, checking the vehicle state and the like, and carrying out vehicle control instruction encapsulation on the vehicle control request parameters after the inspection is completed to obtain an instruction which can be identified by TBOX; it is not until this point that the command has completed initialization.

The node of the wake-up flow of the short message sending means that the TBOX loaded on the vehicle is in a sleep mode (the TBOX and the EMQ in the sleep mode are in a disconnected mode, that is, the vehicle control instruction issued by the cloud cannot be received), the cloud is required to issue the short message to the TBOX in a telecommunication, mobile and communication mode, and the TBOX actively initiates connection to the EMQ after receiving the short message.

The TBOX login flow node is actively connected to the EMQ after receiving a short message sent by the cloud, and then actively initiates a login request through the EMQ, and after the cloud verifies the validity of the login request after receiving the login request, the cloud changes the state of the TBOX from off-line to on-line.

The command is sent to the EMQ process node, namely the vehicle control command is finally sent to the EMQ successfully after being transmitted by each system of the cloud, and the EMQ replies that the cloud has received the vehicle control command.

The TBOX response flow node is used for receiving the vehicle control instruction from the EMQ, converting the vehicle control instruction into a command which can be executed by the vehicle and transmitting the command to the vehicle for execution, and after the vehicle execution is finished, transmitting the vehicle control execution result to the EMQ.

The TBOX response flow node is used for analyzing, storing and processing relevant business logic of result data after TBOX response is given to a cloud end vehicle control result.

The feedback execution result flow node is used for pushing the vehicle control result message to the APP, or the APP actively calls the vehicle control acquisition interface to acquire the vehicle control result.

Fig. 4 is a flowchart of another method 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 the TSP is executed to a key node in a target vehicle control flow according to an embodiment of the present application. As shown in fig. 4, the method comprises the steps of:

In step S401, in response to determining that the TSP is executed to the command initialization flow node, a vehicle control request identifier of the target vehicle control request and a time of issuing a vehicle control instruction corresponding to the target vehicle control request are acquired.

In step S402, the vehicle control request identifier and the issuing time are written into the vehicle control data monitoring table as second global vehicle control information.

In step S403, the vehicle control request identifier is written into the vehicle control data monitoring table as at least part of the vehicle control information of the second key node.

In the embodiment of the application, the second global control information may be a control request identifier of the target control request and a issuing time of a control instruction corresponding to the target control request. Further, 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, in the vehicle control data monitoring table, the vehicle control request identifier of the target vehicle control request may be recorded as global information in the header, and further, the vehicle control request identifier of the target vehicle control request may also be recorded in a list in which the vehicle control information of each key node is recorded. 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 flow node.

That is, when the TSP executes to the command initialization flow node, the command initialization log is 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 issuing time corresponding to the target vehicle control request. Therefore, the vehicle control flow monitoring device can acquire 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. And then, the vehicle control request identification and the issuing time are used as second global vehicle control information to be written into a vehicle control data monitoring table, and the vehicle control request identification is used as at least part of second key node vehicle control information to be written into the vehicle control data monitoring table.

In the embodiment of the application, when the TSP equipment where the target key node is located executes the target vehicle control process to the target key node, the vehicle control log of the target key node is printed for the vehicle control process monitoring equipment to collect, and the target key node is any key node in the target vehicle control process.

Fig. 5 is a flow chart of a method for printing a vehicle control log of a target key node when a TSP device where the target key node is located performs a target vehicle control process to the target key node according to an embodiment of the present application. As shown in fig. 5, the method comprises the steps of:

In step S501, 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 step S502, in response to determining that the vehicle service device in the TSP receives the transmission short message result returned by the operator, the vehicle service device prints a transmission short message wakeup log.

In step S503, 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 step S504, in response to determining that the device gateway in the TSP receives the successful reception target vehicle control request message of the EMQ transmission, the device gateway prints a transmission command to the EMQ log.

In step S505, in response to determining that the device gateway in the TSP receives the result of execution of the vehicle control instruction transmitted by the TBOX via the EMQ, the device gateway prints the TBOX response log.

In step S506, in response to determining that the vehicle control application backend service device in the TSP receives a vehicle control instruction execution result from Kafka, the vehicle control application backend service prints the processing TBOX log.

In step S507, in response to determining that the vehicle control application background service device in the TSP completes the service processing based on the TBOX response result, the vehicle control application background service prints a feedback execution result log.

In the embodiment of the present application, when the TSP device where the target key node is located executes the target vehicle control flow to the target key node, the vehicle control log of the printing target key node may be a vehicle control application background service device print command initialization log 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. And when the vehicle service equipment in the TSP receives a short message sending result returned by the operator, the vehicle service equipment prints a short message sending awakening log. And when 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. And when the equipment gateway in the TSP receives the successful receiving target vehicle control request message sent by the EMQ, the equipment gateway prints a sending command to the EMQ log. And when the device gateway in the TSP receives the execution result of the vehicle control instruction sent by the TBOX through the EMQ, the device gateway prints a TBOX response log. And when the vehicle control application background service equipment in the TSP receives the execution result of the vehicle control instruction from the Kafka, the vehicle control application background service prints and processes the TBOX log. And when the vehicle control application background service equipment in the TSP completes business processing based on the TBOX response result, the vehicle control application background service prints a feedback execution result log.

If the TBOX is not in the dormant state, the SMS sending wake-up control flow is not executed, and at the moment, the SMS sending wake-up log is not required to be printed. On the other hand, if the TBOX is in the logged-in state, the TBOX login request traffic flow sent by the TBOX via the EMQ, the device gateway, and the message middleware Kafka may not be executed, and at this time, the TBOX login log does not need to be printed.

Fig. 6 is a flow chart of a method for screening a vehicle control log of a key node when a TSP executes to the key node in a target vehicle control flow according to an embodiment of the present application. As shown in fig. 7, the method includes the steps of:

in step S601, the vehicle control process monitoring device collects all logs of the key nodes when the TSP executes the target vehicle control process.

In step S602, after the TSP executes to the key node in the target vehicle control process and finishes printing the vehicle control log of the key node, the vehicle control process monitoring device acquires the vehicle control log of the key node.

In step S603, the vehicle control flow monitoring device parses all the collected logs, determines that the logs include vehicle control log identifiers in response to parsing, and screens vehicle control logs of the key nodes.

In the embodiment of the application, when the TSP executes the target vehicle control process, the vehicle control process monitoring equipment can continuously collect all logs of the key nodes and analyze all collected logs. Further, after the TSP executes to the key node in the target vehicle control process and finishes printing the vehicle control log of the key node, the vehicle control process monitoring device collects the vehicle control log of the key node. At the moment, the vehicle control flow monitoring equipment determines that the vehicle control log mark is contained in the log through analyzing the log, and can determine that the log is the vehicle control log.

Fig. 7 is an interaction diagram of a vehicle control flow execution method according to an embodiment of the present application. As shown in fig. 7, the APP may send a vehicle control request to the APP background service, which encapsulates the vehicle control instruction and returns the result to the APP waiting for execution. Further, the APP background service may further send a vehicle control instruction to the vehicle device service, where after receiving the vehicle control instruction, the vehicle control device service may send a sms wakeup request to the operator, where the operator returns a sms sending result, and the APP background service receives the sms sending return result and records a sms result log.

On the other hand, the operator sends a short message to the TBOX, the TBOX analyzes the short message and completes waking up, and then sends a login request to the EMQ. The EMQ pushes the login request to the device gateway, which sends the login request to the vehicle device service via Kafka and related intermediary services.

After receiving the login request, the vehicle equipment service processes the login request and prints a TBOX login log to modify the vehicle state to a logged-in state. Then, the vehicle service device sends a vehicle control instruction to the Kafka, the Kafka pushes the vehicle control instruction to the device gateway, the device gateway further sends the vehicle control instruction to the EMQ, the EMQ sends the vehicle control instruction to the TBOX, meanwhile, a result is returned to the device gateway, and the device gateway prints a sending command to the EMQ log after receiving the returned result.

The TBOX executes the received vehicle control instruction, the execution result is sent to the EMQ, the EMQ pushes the received execution result to the equipment gateway, and the equipment gateway prints a TBOX response log after receiving the execution result. The device gateway further sends the execution result to Kafka, and the Kafka pushes the execution result to the APP background service. The APP background service processes the TBOX response results and prints the TBOX log. Further, the APP acquired service changes the execution result of the vehicle control instruction, pushes the message and prints a feedback execution result log. The APP obtains the car control result from the APP background service, or the APP background service feeds back the response result to the APP.

In an example, the APP may call a car control interface provided by the APP background service, for example: v0/public/vecle-remote-control/send-vecle-control-command. Further, a WINDOW opening command may be input, for example CommandType =window, command=on, and vin=xx.

After receiving the APP request, the APP background service generates a vehicle control request identifier (requestId) corresponding to the target vehicle control request by using a function UUID.randomUUID (). ToString (), then performs parameter verification, encapsulates the vehicle control request identifier requestId and a remote control instruction, and finally prints a command initialization log.

The APP background service invokes the vehicle equipment service to send a vehicle control interface, such as/v 0/public/vehicle/remote-instructions, a remote control instruction to control the vehicle, and a vehicle control request identifier requestId. The vehicle equipment service invokes the operator interface to send a short message to the user identification (Subscriber Identity Module, SIM) card in the TBOX installed on the vehicle, an incoming vehicle control request identification requestId, and an instruction to wake up the TBOX.

The vehicle equipment service prints and sends a short message result log and waits for a TBOX login request. And the TBOX wakes up after receiving the short message, logs in to the cloud through a vehicle cloud protocol, and transmits the basic information of the vehicle and the vehicle control request identifier requestId. And after receiving the TBOX login request, the vehicle equipment service prints a TBOX login log, and verifies that the vehicle basic information modifies the vehicle state to be online. The vehicle equipment service transmits a vehicle control instruction and a vehicle control request identification requestId to Kafka. The device gateway receives the vehicle control instruction and the vehicle control request identifier requestId from Kafka, and verifies the validity of the vehicle control instruction. The equipment gateway sends the vehicle control instruction to the EMQ, and the EMQ returns to the equipment gateway after receiving the vehicle control instruction to indicate successful receiving.

And the equipment gateway print vehicle control instruction is sent to the EMQ result log. The TBOX receives the vehicle control instruction from the EMQ, checks the instruction legitimacy and then gives the vehicle control instruction to execute the vehicle control instruction. The TBOX sends the result of the execution of the vehicle control instruction (carrying the on-board vehicle control request identifier requestId) to the EMQ. And the equipment gateway receives the TBOX instruction execution result from the EMQ, analyzes the TBOX instruction execution result according to the vehicle cloud protocol, and obtains the execution result content and the vehicle control request identifier requestId. And print the get TBOX response log. The device gateway transmits the instruction execution result and the vehicle control request identifications requestId to Kafka. The APP background service obtains the instruction execution result and the car control request identifier requestId from Kafka, and prints and processes the TBOX response log. And the APP background service receives the TBOX response result and then executes service processing, such as pushing information to the APP and modifying the state of the execution result of the vehicle control instruction, and prints feedback APP execution result log.

Fig. 8 is a flow chart of a method for analyzing data in a vehicle control log and writing analyzed vehicle control data into a vehicle control data monitoring table as second global vehicle control information and second key node vehicle control information according to an embodiment of the present application. As shown in fig. 8, the method includes the steps of:

In step S801, all logs acquired by the vehicle control flow monitoring device are written into a log file by using a log framework.

In step S802, all data in the log file is transmitted to the log parsing tool using the log data collection tool.

In step S803, when it is determined that the target log includes the vehicle control log identifier, the log parsing tool determines that the target log is the vehicle control log.

In step S804, the log parsing tool uses a preset parsing rule to segment data in the vehicle control log, so as to obtain parsed vehicle control log elements.

The parsed vehicle control log element comprises second global vehicle control information and second key node vehicle control information.

In step S805, the parsed control log element is repackaged into an entity class, and the entity class is sent to the Kafka' S control flow message theme in the TSP.

In step S806, the vehicle control flow monitoring device obtains the second global vehicle control information and the second key node vehicle control information from the vehicle control flow message subject of Kafka, and writes the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table.

In the embodiment of the application, when the log acquired by the vehicle control flow monitoring equipment is analyzed, the log frame can be utilized to write all the logs acquired by the vehicle control flow monitoring equipment into the log file. In one example, the log framework may be slf4j, for example. Next, all data in the log file may be sent to a log parsing tool using a log data collection tool. In an example, the log data collection tool may be filebeat, for example, and the log parsing tool may be logStash, for example.

In the embodiment of the application, a log analysis tool analyzes logs one by one, and uses a preset analysis rule to divide data in the vehicle control log to obtain analyzed vehicle control log elements, wherein the analyzed vehicle control log elements can comprise second global vehicle control information and second key node vehicle control information. The parsed control log elements may then be repackaged into entity classes and the entity classes sent to the Kafka's control flow message theme in the TSP.

The vehicle control flow monitoring device may subscribe to the vehicle control flow message in Kafka, and further acquire the second global vehicle control information and the second key node vehicle control information from the vehicle control flow message theme when the vehicle control flow message theme of Kafka is updated, for example, when a new entity class obtained by packaging the vehicle control log element is received and stored, and write the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table.

That is, the log may be output to the file through the log framework slf4j, and the log content may be obtained from the file through the log data collection tool filebeat and sent to the log parsing tool logStash. The log analysis tool logstash analyzes a log and judges whether the log belongs to a log related to the vehicle control flow, if yes, the log is sent to a vehicle control flow message theme (topic) corresponding to Kafak. Further, the parsed system logs may be stored in the database ES, and then the logs of all the requested systems may be displayed by the visualization platform kibana. The vehicle control flow monitoring service can acquire the data of each key node corresponding to the vehicle control from the vehicle control flow message topic corresponding to Kafka. The control flow monitoring service may also be stored in a database such as mysql, mongodb.

In the embodiment of the present application, the log format corresponding to each key node may be, for example:

Command initialization:

log.info("CONTROLLOG#INITIALIZE#{}#{}#{}#{}#{}#{}" ,phone，pdid，commandType,command,result,reason);

and (5) sending a short message to wake up:

log.info("CONTROLLOG#WAKEUP#{}#{}#{}#{}#{}",pdid，commandType,command,result,reason);

TBOX login:

log.info("CONTROLLOG#LOGIN#{}#{}#{}#{}#{}", pdid,commandType,command,result,reason);

command send EMQ:

log.info("CONTROLLOG#SENDEMQ#{}#{}#{}#{}#{}",pdid,commandType,command,result,reason);

Acquiring TBOX response:

log.info("CONTROLLOG#GETTBOX#{}#{}#{}#{}#{}",pdid,commandType,command,result,reason);

treatment of TBOX response:

log.info("CONTROLLOG#HANDTBOX#{}#{}#{}#{}#{}",pdid,commandType,command,result,reason);

And feeding back an APP execution result:

log.info("CONTROLLOG#SENDAPPMSG#{}#{}#{}#{}#{}",pdid,commandType,command,result,reason)。

Wherein CONTROLLOG is a vehicle control log identifier, INITIALIZE indicates that the node type is a command initialization flow node, WAKEUP indicates that the node type is a wake-up flow node for sending short messages, LOGIN indicates that the node type is a TBOX login flow node, SENDEMQ indicates that the node type is an EMQ flow node for sending commands, GETTBOX indicates that the node type is a TBOX response flow node, HANDTBOX indicates that the node type is a TBOX response flow node processing, SENDAPPMSG indicates that the node type is a feedback APP execution result flow node.

Further, pdid is the device number; commandType is a command type, such as LOCK; command is an instruction action, for example, ON indicates unlock and OFF indicates lock; result represents the key node execution result, which can be success or failure; the reason for failure is indicated by reason.

When the log is output to the file through the log frame slf4j, the log may be constructed into text by the log frame slf4j, for example, by "# CONTROLLOG # INITIALIZE #LOCK #ON #success #" and then the next vehicle control request identifier requestId is incorporated ON the log, # CONTROLLOG # INITIALIZE #LOCK #ON #success #ba462c3043044a82940f5a38b23677f6.

The log file data is then collected by log data collection tool filebeat and sent to log parsing tool logStash channel. Log parsing tool logStash receives the log: # CONTROLLOG # SKEV2024XX# INITIALIZE# LOCK# ON# success# ba462c3043044a82940f5a38b23677f6, determine if the log text is to: # CONTROLLOG beginning, if the log is a vehicle control flow key log, explaining that the analysis is needed, and sending the analysis result to Kafka. Dividing according to # by using a preset analysis rule in step 804 in the embodiment shown in fig. 8, storing the divided data in sequence and storing the data in an array of a data structure CONTROLLOG, SKEV2024XX, INITIALIZE, LOCK, ON, success, and successfully; the first element in the array: CONTROLLOG, second element: SKEV2024XX, third element: INITIALIZE, fourth element: LOCK, fifth element: ON, sixth element: success; seventh element: success; eighth element: ba462c3043044a82940f5a38b23677f6.

And packaging the parsed elements on corresponding entity classes, converting the elements into a lightweight data exchange format json, and sending the lightweight data exchange format json to corresponding Kafka message middleware. In one example, the eight elements and the vehicle control request identifier requestId, the current system time, may be packaged into a lightweight data exchange format json, such as {" "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"：" succeeded ", requestId": ba462c3043044a82940f5a38b23677f6"," time ": "2024-06-15 09:32:21:100"}. The encapsulated json message is then sent into topic= "VehicleControlProcessTopic" in Kafka.

The vehicle control flow service defines that the message consumer group consumes a vehicle control flow message corresponding to topic in Kafka as VehicleControlProcessTopic.

Fig. 9 is a flow chart of a method for acquiring second global control information and second key node control information from a control flow message theme of Kafka and writing the second global control information and the second key node control information into a control data monitoring table by using the control flow monitoring device according to the embodiment of the present application. As shown in fig. 9, the method includes the steps of:

in step S901, the vehicle control flow monitoring device acquires a vehicle control flow message of a target vehicle control request from Kafka.

In step S902, in response to determining that the vehicle control flow message is at the command initialization flow node, the first global vehicle control information, the second global vehicle control information, the first key node vehicle control information, and at least a portion of the second key node vehicle control information are written into the vehicle control data monitoring table.

The at least part of the second key node vehicle control information comprises a vehicle control request identifier of the target vehicle control request.

In step S903, in response to determining that the vehicle control flow message is not at the command initialization flow node, the remaining second key node vehicle control information of the executed key node is written into the vehicle control data monitoring table.

In step S904, in response to determining that the vehicle control flow message is at the last node of the vehicle control flow, the third global vehicle control information is written into the vehicle control data monitoring table.

In the embodiment of the application, the vehicle control flow monitoring equipment acquires the second global vehicle control information and the second key node vehicle control information from the vehicle control flow message theme of the Kafka, and when the vehicle control information and the second key node vehicle control information are written into the vehicle control data monitoring table, the vehicle control flow message can be subscribed in the Kafka by the vehicle control monitoring equipment. Thus, when the vehicle control flow message in Kafka is updated, for example, an entity class formed by information elements in a key node log corresponding to a target vehicle control request is written under the topic of the vehicle control flow message in Kafka, the vehicle control flow monitoring device can acquire the written entity class, and extract information needing to be written into the vehicle control monitoring data table.

Further, when information is extracted, the vehicle control flow monitoring device may first determine whether the vehicle control flow message is at a command initialization flow node, if yes, it indicates that the vehicle control flow is just started to be executed, the log of the key node is not printed yet, 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 may be written into the vehicle control data monitoring table, and meanwhile, the execution state of the key node that has not been executed may also be set to be executed.

Otherwise, if the vehicle control flow message is not in the command initialization flow node, the vehicle control information of the other second key nodes of the executed key nodes can be written into the vehicle control data monitoring table. In addition, for the key node which has written the vehicle control information, the execution state of the key node can be changed from to-be-executed to execution success or execution failure. For the key node with the execution failure, the failure reason or the system log link can be written in the list corresponding to the key node in the vehicle control data monitoring table, or the failure reason and the system log link can be written at the same time.

In the embodiment of the application, when information is extracted, the vehicle control flow monitoring equipment can also determine whether the vehicle control flow message is at the last node of the vehicle control flow, namely, the printing feedback execution result node. If so, the current time of the system can be obtained, the overall time consumption of the target vehicle control request is calculated, and then the overall time consumption is used as third global vehicle control information to be written into a vehicle control data monitoring table. Otherwise, only the vehicle control information of the key node updated by the current message is stored.

That is, when a message is acquired by a group of subscribers, the results may be filtered and the assembly parameters stored in the database. In one aspect, after the message is obtained and parsed, it may be determined whether the node in the message is a command initialization (initialization) flow node. If the first step is that the mobile phone number, the device number pdid, the command type commandType, the command action command, the vehicle control request identifier requestId and the time in the message are stored in the vehicle control flow monitoring table tsp_vehicle_control_monitor, the execution result is set to be in an executing state, the time is not filled temporarily, and the data is updated after the execution is completed. The second step stores the vehicle control request identifier requestId, the type of the flow monitoring node, the execution time point, the reason request, the result, and the system kibna address in the detail table tsp_vehicle_control_monitor_detail of the vehicle control flow monitoring table. If not, only the control request identifier requestId, the flow monitoring node type, the execution time point, the reason, and the result are stored in the tsp_vehicle_control_monitor_detail table.

On the other hand, after the message is acquired and parsed, it can be determined whether the message is the last node of the vehicle control flow, i.e. whether the node is equal to SENDAPPMSG. If so, firstly acquiring the corresponding command time for starting to issue the current automobile control from the tsp_vehicle_control_monitor according to the automobile control request identifier requestId, and subtracting the current message time to obtain costTime automobile control time. Then determine whether the current SENDAPPMSG is successful, if so, update the execution results and time-consuming in the tsp_vector_control_monitor table. And finally, storing the vehicle control request identifier requestId, the type of the flow monitoring node, the execution time point, the reason, the result, the system kibna address and the tsp_vehicle_control_monitor_detail table.

If not, the vehicle control request identifier requestId, the type of the flow monitoring node, the execution time point, the reason request, the result and the system kibna address are stored in a tsp_vehicle_control_monitor_detail table.

Fig. 10 is a flowchart of a method for writing third global control information in a control data monitoring table in response to determining that TSP completes execution of a target control flow according to an embodiment of the present application. As shown in fig. 10, the method includes the steps of:

In step S1001, in response to determining that the TSP completes execution of the target vehicle control flow, the total time consumed for execution of the target vehicle control flow is acquired.

In step S1002, the total execution time is written as third global control information into the control data monitoring table.

In the embodiment of the present application, the third global control message may be the total time consumed for executing the target control flow. Therefore, in response to determining that the TSP completes execution of the target vehicle control flow, writing the third global vehicle control information in the vehicle control data monitoring table may be to obtain total execution time of the target vehicle control flow when it is determined that the TSP completes execution of the target vehicle control flow, and then write the total execution time as the third global vehicle control information in the vehicle control data monitoring table.

FIG. 11 is a flow chart of a method for collecting, parsing, storing and displaying system logs according to an embodiment of the present application. As shown in fig. 11, system logs may be collected from each service through a log collection framework and converted to log files by filebeat. The log file may be transferred to logstash, parsed in logstash and stored to a database (ES) and Kafka, respectively. The log data in the ES may be presented through the visualization platform kibana. The log data in Kafka can be subscribed by the vehicle control flow monitoring service, and the vehicle control flow monitoring service generates a vehicle control flow monitoring table based on the log data and further stores the vehicle control flow monitoring table into a mysql database.

Table 1 is a vehicle control flow monitoring table provided in an embodiment of the present application. As shown in Table 1, the vehicle control flow monitoring table comprises a main table and a key node table. The master table includes fields of a user identifier, a vehicle control instruction, a time for issuing the vehicle control instruction, an execution result, total time consumption and a vehicle control request identifier requestId, and each key node table includes a vehicle control request identifier requestId, a key node identifier, an execution state, a failure reason, an execution time period and a system log link field. Table 1 gives exemplary information for each field, where execution status success indicates execution success.

TABLE 1 vehicle control flow monitor

That is, in the embodiment of the present application, the second key node control information at least includes a control request identifier, an execution state and an execution time of the target control request. Wherein the execution state includes execution success, execution failure and execution. And responding to the execution state as the execution failure, wherein the second key node vehicle control information further comprises at least one of failure reasons and system log links.

Fig. 12 is a flow chart of a method for monitoring a vehicle control flow using a vehicle control data monitoring table according to an embodiment of the present application. As shown in fig. 12, the method includes the steps of:

in step S1201, a vehicle control data monitoring table corresponding to the target vehicle control request is acquired, and a cause of failure in execution of the target vehicle control request is determined based on the vehicle control data monitoring table.

In step S1202, a set of vehicle control data monitoring tables corresponding to the target type vehicle control request of the target vehicle is obtained, and a vehicle control flow early warning strategy or a vehicle control flow optimization strategy is determined based on the set of vehicle control data monitoring tables.

In the embodiment of the application, the vehicle control flow is monitored by using the vehicle control data monitoring table, wherein the vehicle control data monitoring table corresponding to the target vehicle control request is obtained, and the failure reason of the execution of the target vehicle control request is determined based on the vehicle control data monitoring table.

The front end of the vehicle control flow monitoring device can call an interface v0/vehicle/control/monitor provided by the TSP cloud, and the vehicle control flow monitoring device transmits an instruction, an execution state, a issuing time period, a user identifier and a VIN code. After receiving the request, the TSP cloud determines whether the VIN has a value, if yes, the VIN queries the device number pdid corresponding to the vehicle, and if the command, the execution state, the issuing time period, and the user identifier are returned to the front end from the query data list in the tsp_vehicle_control_monitor table, the query data list is displayed on the page.

In an example, the vehicle control data monitoring table may be directly graphically displayed on a user interface of the vehicle control flow monitoring device, so that a user may monitor the vehicle control flow execution process in real time.

Fig. 13 is a schematic diagram of a graphical display interface for monitoring a vehicle control flow according to an embodiment of the present application. As shown in the upper graph of fig. 13, the total time spent costTime for executing the vehicle control flow of the vehicle control request is 1.2 seconds, the time spent on executing requeid of the present vehicle control request and each key node is shown in the interface, and all key nodes of the present vehicle control flow are successfully executed.

On the other hand, as shown in the lower diagram of fig. 13, the total time taken for the vehicle control flow execution of the present vehicle control request is 1 second, but the key node fails to process the TBOX response execution, so that the execution state of the APP execution result fed back by the subsequent node is unexecuted. Furthermore, the time consumption of requeid of the current vehicle control request and the execution time consumption of the key node which has been successfully executed are displayed in the interface, and the failure reason of the key node which has failed to be executed and the system log link are also displayed in the interface.

In the embodiment of the application, the vehicle control flow is monitored by using the vehicle control data monitoring table, namely, a vehicle control data monitoring table set corresponding to the target type vehicle control request of the target vehicle is acquired, and the vehicle control flow early warning strategy or the vehicle control flow optimization strategy is determined based on the vehicle control data monitoring table set.

That is, all users can also be monitored for failure distribution, time consumption distribution of various remote total numbers and critical task node types at different time periods. For example, the total number of remote controls and the rate of mission critical node type failures may be counted. In an example, the front end may call an interface v 0/vehicle/control/fat/count provided by the TSP cloud, and transmit a period of time selected by the user, such as a start time and an end time. After receiving the front-end request, the TSP cloud end inquires out the vehicle control record of the execution failure from the tsp_vehicle_control_monitor, and the total number of remote control failures can be obtained. If there is a failure at which node from the tsp_cycle_control_monitor_detail query fails, then the packet sums are performed according to the critical node type to obtain a failure rate for each critical node far controlled, such as 100 total failures, where 10 times of processing HANDTBOX (processing TBOX response) critical task node type failures are performed, with a 10/100=10% ratio.

For another example, the remote control time consumption can also be counted separately. In an example, the front end may call an interface v 0/veccle/control/time/count provided by the TSP cloud, and enter a period of time selected by the user, such as a start time, an end time. The TSP cloud receives the front-end request, filters out records of successful vehicle control from the tsp_vehicle_control_monitor, then groups the records according to the type of the vehicle control (for example, the vehicle lock is of one type, the vehicle window is of another type, and different time consumption distribution exists under the corresponding condition of each type), and time-sequences data of each type by using an bubbling sequencing algorithm and is recorded as costTime in a container set. Statistics are then performed at preset intervals, e.g., 100 ms, 0-100,100-200, …,1000-1100, …, e.g., 0-100, sequentially traversing 0-100 from costTime, and the like for 100-200, …. TSP returns to front end results, such as 0-100 of LOCK (LOCK), 600-700, 10%,800-900, 50%,900-1000, 30%, 1000-1100, 9%,1100-1200, 1%, and the whole remote control time-consuming condition can be clearly known from data, so that a vehicle control application provider can be helped to know the whole system more clearly, whether the performance affects the use of a user or not, and the user feedback such as that the result is not equal is not found from the data analysis in advance, and the problem is checked.

Fig. 14 is a schematic diagram of a monitoring interface of a vehicle control flow monitoring device according to an embodiment of the present application. As shown in fig. 14, in the monitoring interface of the vehicle control flow monitoring device, the user may query the vehicle control flow execution information by inputting one or more of an issue instruction, an execution state, an issue time, a user identifier (user mobile phone number) and a vehicle VIN code. The queried information is displayed in the formats of the mobile phone number, the issuing instruction, the VIN, the execution state, the execution result and the issuing time of the user. The issuing instruction refers to a vehicle control instruction issued by a user through a vehicle owner APP, for example, CHARGE: ON, where CHARGE indicates the CHARGE control command type, ON indicates ON. The execution status indicates the final execution result of the vehicle control instruction, for example, fixed=success, ABNORMAL =failure. The execution result represents a description of the cause of the failure of the execution result. The issuing time is the initiating time of the user clicking the car control instruction at the car owner APP.

That is, when the tester or the owner APP user fails to use the vehicle control, the technician is required to check, and at this time, the technician can input the vehicle VIN through the vehicle control data monitoring interface to inquire about the result of each vehicle control request operated by the current tester or the owner APP user; then, through the vehicle control execution failure flow chart shown in the lower chart in fig. 13, information such as which key link fails, failure reasons, time consumption and the like is clearly seen, if the reason why the vehicle control fails is not judged at this time, a technician directly clicks a system log button link below to jump to a visualization platform kibana log, and a vehicle control request identifier requestId is transmitted to inquire about the starting time and the ending time of the log. The efficiency of locating a positioning problem in this way is improved by several times.

By adopting the technical scheme of the embodiment of the application, the flow monitoring of each time of vehicle control on the TSP platform can be realized, and the state of the vehicle control is marked every time the vehicle control passes through a key node. Parsing is performed according to a specific parsing log data rule, and the parsing is stored in a database (having a component for storing data). Displaying the execution states of each vehicle and different types of remote control at different key nodes through a vehicle control flow monitoring page of the TSP management platform; the completion of the vehicle control is time-consuming; request number of system log. All users can be monitored in different time periods, and various remote control failure rates, time consumption distribution and remote control failure distribution are distributed on different key nodes.

Any combination of the above optional solutions may be adopted to form an optional embodiment of the present application, which is not described herein.

The following are examples of the apparatus of the present application that may be used to perform the method embodiments of the present application. For details not disclosed in the embodiments of the apparatus of the present application, please refer to the embodiments of the method of the present application.

Fig. 15 is a schematic diagram of a vehicle control flow monitoring device according to an embodiment of the present application. As shown in fig. 15, the apparatus includes:

The generating module 1501 is configured to generate, in response to receiving the target vehicle control request, a vehicle control data monitoring table of the target vehicle control request.

The writing module 1502 is configured to write the first global control information and the first critical node control information in the control data monitoring table.

The writing module 1502 is further configured to write, when the internet of vehicle content service providing platform TSP sequentially executes the target vehicle control flow corresponding to the target vehicle control request, 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 is executed to the key node in the target vehicle control flow.

The writing module 1502 is further configured to write third global control information in the control data monitoring table in response to determining that the TSP completes execution of the target control flow, completing the control data monitoring table of the target control request.

The monitoring module 1503 is configured to store the completed vehicle control data monitoring table in a database, and monitor the vehicle control process using the vehicle control data monitoring table.

In the embodiment of the application, the first global vehicle control information and the first key node vehicle control information are written in the vehicle control data monitoring table, and the method comprises the following steps: acquiring user identification information, vehicle identification information and key node identification; acquiring vehicle control instruction information corresponding to a target vehicle control request; and writing the vehicle control instruction information corresponding to the user identification information, the vehicle identification information and the target vehicle control request into the vehicle control data monitoring table as first global vehicle control information, and writing the key node identification into the vehicle control data monitoring table as first key node vehicle control information.

In the embodiment of the application, in response to determining that the TSP is executed to a key node in a target vehicle control flow, writing second global vehicle control information and second key node vehicle control information in a vehicle control data monitoring table, wherein the method comprises the following steps: collecting and screening logs from TSP equipment where each key node is located, and screening to obtain vehicle control logs of the key nodes when the TSP executes to the key nodes in the target vehicle control flow; analyzing the data in the vehicle control log, and writing the analyzed vehicle control data serving as second global vehicle control information and second key node vehicle control information into a vehicle control data monitoring table.

In the embodiment of the application, the key nodes in the target vehicle control flow comprise: the method comprises the steps of commanding an initialization flow node, sending a short message wake-up flow node, logging in a flow node by a vehicle-mounted communication module TBOX, sending commands to a cloud native message server and a flow processing database EMQ flow node, obtaining a TBOX response flow node, processing the TBOX response flow node and feeding back an execution result flow node.

In the embodiment of the application, in response to determining that the TSP is executed to a key node in a target vehicle control flow, writing second global vehicle control information and second key node vehicle control information in a vehicle control data monitoring table, wherein the method comprises the following steps: responding to the confirmation TSP execution to the command initialization flow node, and acquiring a vehicle control request identifier of a target vehicle control request and the issuing time of a vehicle control instruction corresponding to the target vehicle control request; writing the vehicle control request identification and the issuing time into a vehicle control data monitoring table as second global vehicle control information; and writing the vehicle control request identification into a vehicle control data monitoring table as at least part of the vehicle control information of the second key nodes.

In the embodiment of the application, when TSP equipment where a target key node is located executes a target vehicle control process to the target key node, a vehicle control log of the target key node is printed for acquisition by vehicle control process monitoring equipment, and the target key node is any key node in the target vehicle control process; when the TSP equipment where the target key node is located executes the target vehicle control flow to the target key node, printing a vehicle control log of the target key node, including: responding to determining that the vehicle control application background service equipment in the TSP completes the encapsulation of the vehicle control instruction corresponding to the target vehicle control request, and printing a command initialization log by the vehicle control application background service equipment; in response to determining that the vehicle service equipment in the TSP receives a short message sending result returned by the operator, the vehicle service equipment prints a short message sending awakening log; responsive 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 successful receipt target vehicle control request message sent by the EMQ, the device gateway prints a send command to the EMQ log; responsive to determining that a device gateway in the TSP receives a vehicle control instruction execution result sent by the TBOX via the EMQ, the device gateway prints a TBOX response log; in response to determining that the vehicle control application background service equipment in the TSP receives a vehicle control instruction execution result from Kafka, the vehicle control application background service prints and processes a TBOX log; in response to determining that the vehicle control application background service device in the TSP completes business processing based on the TBOX response result, the vehicle control application background service prints a feedback execution result log.

In the embodiment of the application, when the TSP executes to the key node in the target vehicle control flow, the vehicle control log of the key node is obtained by screening, and the method comprises the following steps: the method comprises the steps that when a TSP executes a target vehicle control process, vehicle control process monitoring equipment collects all logs of key nodes; after the TSP executes the key nodes in the target vehicle control process and finishes printing the vehicle control logs of the key nodes, the vehicle control process monitoring equipment acquires the vehicle control logs of the key nodes; the vehicle control flow monitoring equipment analyzes all the collected logs, and responds to analysis to determine that the logs comprise vehicle control log identifications, and vehicle control logs of key nodes are obtained through screening.

In the embodiment of the application, analyzing the data in the vehicle control log, and writing the analyzed vehicle control data serving as the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table, wherein the method comprises the following steps: writing all logs acquired by the vehicle control flow monitoring equipment into log files by using a log frame; using a log data acquisition tool to send all data in the log file to a log analysis tool; when the log analysis tool determines that the target log comprises the vehicle control log identification, determining that the target log is the vehicle control log; the log analysis tool uses a preset analysis rule to divide data in the vehicle control log to obtain analyzed vehicle control log elements, wherein the analyzed vehicle control log elements comprise second global vehicle control information and second key node vehicle control information; repackaging the parsed vehicle control log elements into entity classes, and sending the entity classes to a vehicle control flow message theme of Kafka in the TSP; the vehicle control flow monitoring equipment acquires second global vehicle control information and second key node vehicle control information from the vehicle control flow message theme of Kafka, and writes the second global vehicle control information and the second key node vehicle control information into a vehicle control data monitoring table.

In the embodiment of the application, the vehicle control flow monitoring device acquires the second global vehicle control information and the second key node vehicle control information from the vehicle control flow message theme of Kafka, writes the second global vehicle control information and the second key node vehicle control information into a vehicle control data monitoring table, and comprises the following steps: the vehicle control flow monitoring equipment acquires a vehicle control flow message of a target vehicle control request from Kafka; in response to determining that the vehicle control flow message is at the command initialization flow node, writing first global vehicle control information, second global vehicle control information, first key node vehicle control information and at least part of second key node vehicle control information into a vehicle control data monitoring table, wherein at least part of second key node vehicle control information comprises a vehicle control request identifier of a target vehicle control request; in response to determining that the vehicle control flow message is not at the command initialization flow node, writing vehicle control information of the other second key nodes of the executed key nodes into a vehicle control data monitoring table; and in response to determining that the vehicle control flow message is at the last node of the vehicle control flow, writing third global vehicle control information into the vehicle control data monitoring table.

In the embodiment of the present application, in response to determining that the TSP completes execution of the target vehicle control flow, writing third global vehicle control information in the vehicle control data monitoring table includes: in response to determining that the TSP completes execution of the target vehicle control flow, acquiring total time consumption of execution of the target vehicle control flow; and writing the total execution time consumption serving as third global vehicle control information into a vehicle control data monitoring table.

In the embodiment of the application, the second key node vehicle control information at least comprises a vehicle control request identifier, an execution state and execution time of a target vehicle control request; the execution state comprises execution success, execution failure and execution; and responding to the execution state as the execution failure, wherein the second key node vehicle control information further comprises at least one of failure reasons and system log links.

In the embodiment of the application, the vehicle control flow is monitored by using a vehicle control data monitoring table, which comprises the following steps: acquiring a vehicle control data monitoring table corresponding to the target vehicle control request, and determining a failure cause of the execution of the target vehicle control request based on the vehicle control data monitoring table; or acquiring a vehicle control data monitoring list set corresponding to the target type vehicle control request of the target vehicle, and determining a vehicle control flow early warning strategy or a vehicle control flow optimization strategy based on the vehicle control data monitoring list set.

It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.

Fig. 16 is a schematic diagram of an electronic device according to an embodiment of the present application. As shown in fig. 16, 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. The steps of the various method embodiments described above are implemented when the processor 1601 executes the computer program 1603. Or the processor 1601, when executing the computer program 1603, performs the functions of the modules/units of the various device embodiments described above.

The electronic device 16 may be a desktop computer, a notebook computer, a palm computer, a cloud server, or the like. The electronic device 16 may include, but is not limited to, a processor 1601 and a memory 1602. It will be appreciated by those skilled in the art that fig. 16 is merely an example of the electronic device 16 and is not limiting of the electronic device 16 and may include more or fewer components than shown, or different components.

The Processor 1601 may be a central processing unit (Central Processing Unit, CPU), or other general purpose Processor, digital signal Processor (DIGITAL SIGNAL Processor, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), field-Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like.

The memory 1602 may be an internal storage unit of the electronic device 16, such as 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, such as a plug-in hard disk, a smart memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD), etc. that are provided on the electronic device 16. Memory 1602 may also include both internal and external storage units of electronic device 16. The memory 1602 is used to store computer programs and other programs and data required by the electronic device.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit.

The integrated modules/units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiment, or may be implemented by a computer program to instruct related hardware, and the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. The computer program may comprise computer program code, which may be in source code form, object code form, executable file or in some intermediate form, etc. The computer readable medium may include: any entity or device capable of carrying computer program code, a recording medium, a U disk, a removable hard disk, a magnetic disk, an optical disk, a computer Memory, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), an electrical carrier signal, a telecommunications signal, a software distribution medium, and so forth.

The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. A vehicle control flow monitoring method, wherein the method is performed by a vehicle control flow monitoring device, and comprises:

in response to receiving a target vehicle control request, the vehicle control flow monitoring equipment 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 in the vehicle control data monitoring table, wherein the first global vehicle control information comprises 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 comprises a predefined key node identification;

When a TSP (traffic control) of a content service providing platform of the Internet of vehicles) sequentially executes a 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 second global vehicle control information and second key node vehicle control information in 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 issuing time of a vehicle control instruction corresponding to the target vehicle control request, and at least part of the second key node vehicle control information comprises a vehicle control request identifier of the target vehicle control request;

In response to determining that the TSP completes execution of the target vehicle control flow, writing 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, wherein the third global vehicle control information is the whole time consumption for executing the target vehicle control request;

2. The method of claim 1, wherein writing the first global control information and the first critical node control information in the control data monitoring table comprises:

Acquiring user identification information, vehicle identification information and key node identification;

acquiring vehicle control instruction information corresponding to a target vehicle control request;

And writing the vehicle control instruction information corresponding to the user identification information, the vehicle identification information and the target vehicle control request into the vehicle control data monitoring table as first global vehicle control information, and writing the key node identification into the vehicle control data monitoring table as first key node vehicle control information.

3. The method of claim 1, wherein the writing second global control information and second key node control information in the control data monitoring table in response to determining that TSP is executing to a key node in the target control flow comprises:

collecting and screening logs from TSP equipment where each key node is located, and screening to obtain vehicle control logs of the key nodes when the TSP executes to the key nodes in the target vehicle control flow;

Analyzing the data in the vehicle control log, and writing the analyzed vehicle control data serving as second global vehicle control information and second key node vehicle control information into the vehicle control data monitoring table.

4. The method of claim 3, wherein the key nodes in the target vehicular flow comprise:

the method comprises the steps of commanding an initialization flow node, sending a short message wake-up flow node, logging in a flow node by a vehicle-mounted communication module TBOX, sending commands to a cloud native message server and a flow processing database EMQ flow node, obtaining a TBOX response flow node, processing the TBOX response flow node and feeding back an execution result flow node.

5. The method of claim 4, wherein writing second global control information and second key node control information in the control data monitoring table in response to determining that TSP is executing to a key node in the target control flow comprises:

Responding to determining that TSP is executed to a command initialization flow node, and acquiring a vehicle control request identifier of a target vehicle control request and issuing time of a vehicle control instruction corresponding to the target vehicle control request;

Writing the vehicle control request identifier and the issuing time into the vehicle control data monitoring table as second global vehicle control information; and

And writing the vehicle control request identification serving as at least part of vehicle control information of the second key node into the vehicle control data monitoring table.

6. The method of claim 5, wherein when the target vehicle control process is performed to the target key node, the TSP device where the target key node is located prints a vehicle control log of the target key node for the vehicle control process monitoring device to collect, where the target key node is any key node in the target vehicle control process;

when the target vehicle control process is executed to the target key node, the TSP device where the target key node is located prints a vehicle control log of the target key node, including:

responding to determining that a vehicle control application background service device in the TSP completes packaging of a vehicle control instruction corresponding to a target vehicle control request, wherein the vehicle control application background service device prints a command initialization log;

Responding to the fact that vehicle service equipment in the TSP receives a short message sending result returned by an operator, and printing a short message sending awakening log by the vehicle service equipment;

responsive to determining that a vehicle service device in the TSP receives a TBOX login request sent by the TBOX via the EMQ, device gateway, and message middleware Kafka, the vehicle service device prints a TBOX login log;

In response to determining that a device gateway in the TSP receives a successful receipt target vehicle control request message sent by the EMQ, the device gateway prints a send command to an EMQ log;

responsive to determining that a device gateway in the TSP receives a vehicle control instruction execution result sent by the TBOX via the EMQ, the device gateway prints a TBOX response log;

In response to determining that a 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 a TBOX log;

And in response to determining that the vehicle control application background service equipment in the TSP completes business processing based on the TBOX response result, the vehicle control application background service prints a feedback execution result log.

7. The method of claim 4, wherein the screening the vehicle control log of the key node when the TSP executes to the key node in the target vehicle control flow comprises:

the vehicle control flow monitoring equipment acquires all logs of the key nodes when the TSP executes the target vehicle control flow;

After the TSP executes the key nodes in the target vehicle control process and finishes printing the vehicle control logs of the key nodes, the vehicle control process monitoring equipment acquires the vehicle control logs of the key nodes;

And the vehicle control flow monitoring equipment analyzes all the collected logs, and responds to the analysis to determine that the logs comprise vehicle control log identifications, and screens the vehicle control logs of the key nodes.

8. The method according to claim 4, wherein the parsing the data in the control log and writing the parsed control data as second global control information and second key node control information into the control data monitoring table includes:

writing all logs acquired by the vehicle control flow monitoring equipment into log files by using a log frame;

Using a log data acquisition tool to send all data in the log file to a log analysis tool;

When determining that the target log comprises a vehicle control log identifier, the log analysis tool determines that the target log is a vehicle control log;

the log analysis tool uses a preset analysis rule to divide data in the vehicle control log to obtain analyzed vehicle control log elements, wherein the analyzed vehicle control log elements comprise the second global vehicle control information and the second key node vehicle control information;

repackaging the parsed vehicle control log element into an entity class, and sending the entity class to a vehicle control flow message theme of Kafka in the TSP;

and the vehicle control flow monitoring equipment acquires the second global vehicle control information and the second key node vehicle control information from the vehicle control flow message theme of the Kafka and writes the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table.

9. The method of claim 8, wherein the vehicle control flow monitoring device obtains the second global vehicle control information and the second key node vehicle control information in the vehicle control flow message topic of Kafka, writes the second global vehicle control information and the second key node vehicle control information into the vehicle control data monitoring table, and comprises:

the vehicle control flow monitoring equipment acquires a vehicle control flow message of the target vehicle control request from the Kafka;

In response to determining that the vehicle control flow message is at a command initialization flow node, writing first global vehicle control information, second global vehicle control information, first key node vehicle control information and at least part of second key node vehicle control information into the vehicle control data monitoring table, wherein the at least part of second key node vehicle control information comprises a vehicle control request identifier of a target vehicle control request;

In response to determining that the vehicle control flow message is not at a command initialization flow node, writing vehicle control information of the other second key nodes of the executed key nodes into the vehicle control data monitoring table;

And in response to determining that the vehicle control flow message is at the last node of the vehicle control flow, writing third global vehicle control information into the vehicle control data monitoring table.

10. The method of claim 1, wherein writing third global control information in the control data monitoring table in response to determining that TSP completes execution of the target control flow comprises:

in response to determining that the TSP completes execution of the target vehicle control flow, obtaining a total time consumption of execution of the target vehicle control flow;

and writing the total execution consumption time serving as third global vehicle control information into the vehicle control data monitoring table.

11. The method of claim 1, wherein the second critical node vehicle control information includes at least a vehicle control request identification, an execution status, and an execution time of the target vehicle control request;

The execution state comprises execution success, execution failure and execution;

And responding to the execution state as the execution failure, wherein the second key node vehicle control information further comprises at least one of failure reasons and system log links.

12. The method of claim 1, wherein monitoring the vehicle control flow using the vehicle control data monitoring table comprises:

Acquiring a vehicle control data monitoring table corresponding to a target vehicle control request, and determining a failure reason of the target vehicle control request based on the vehicle control data monitoring table; or alternatively

And acquiring a vehicle control data monitoring list set corresponding to the target type vehicle control request of the target vehicle, and determining a vehicle control flow early warning strategy or a vehicle control flow optimization strategy based on the vehicle control data monitoring list set.

13. The utility model provides a car accuse flow monitoring device which characterized in that includes:

the generation module is configured to respond to receiving a target vehicle control request, and the vehicle control flow monitoring equipment generates a vehicle control data monitoring table of the target vehicle control request;

The writing module is configured to write first global vehicle control information and first key node vehicle control information in the vehicle control data monitoring table, wherein the first global vehicle control information comprises user identification information, vehicle identification information and vehicle control instruction information corresponding to a target vehicle control request, and the first key node vehicle control information comprises 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 in the vehicle control data monitoring table in response to determining that the TSP is executed to a key node in the target vehicle control process when the target vehicle control process corresponding to the target vehicle control request is sequentially executed by the vehicle networking content service providing platform TSP, wherein the second global vehicle control information is a vehicle control request identifier of the target vehicle control request and issuing time of a vehicle control instruction corresponding to the target vehicle control request, and at least part of the second key node vehicle control information comprises a vehicle control request identifier of the target vehicle control request;

The writing module is further configured to write third global vehicle control information in the vehicle control data monitoring table in response to determining that the TSP completes execution of the target vehicle control process, the third global vehicle control information being an overall time consuming execution of the target vehicle control request;

and the monitoring module is configured to store the completed vehicle control data monitoring table in a database, and monitor the vehicle control flow by using the vehicle control data monitoring table.

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 the processor implements the steps of the method according to any one of claims 1 to 12 when the computer program is executed.

15. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the steps of the method according to any one of claims 1 to 12.