Monitoring method and device based on remote control of vehicle networking system and medium

Abstract

The specification provides a monitoring method and device based on remote control of a vehicle networking system and a medium. The method comprises: obtaining process information of each stage in the process of a remote control instruction being issued from a mobile terminal to a vehicle terminal; establishing a stage number corresponding to the process information of each stage; determining an instruction identifier of the remote control instruction and a vehicle identifier corresponding to the vehicle terminal, and integrating the process information of each stage according to the corresponding stage number to obtain a target log, with the instruction identifier and the vehicle identifier as the association field. The stage number in the target log is used to locate an abnormal stage in the remote control process of the vehicle networking system, and the process information corresponding to the abnormal stage in the target log is used to analyze the cause of the abnormality, thereby achieving monitoring of the remote control instruction issuing process and improving the efficiency of troubleshooting of the remote control instruction issuing process.

Description

Technical Field

[0001] This specification relates to one or more embodiments in the field of vehicle networking remote control, and in particular to a monitoring method, device and medium based on remote control of a vehicle networking system. Background Technology

[0002] With the rapid development of vehicle networking technology, remote control has become one of the core functions of vehicle networking service platforms (TSPs). It mainly enables users to issue remote control commands through mobile terminal applications, and complete the remote control of vehicles through multiple links such as cloud services and vehicle terminals, greatly improving the convenience of users' vehicle use.

[0003] Existing technologies have achieved end-to-end transmission of remote control commands, meeting users' basic needs for remote vehicle control. However, in practical applications, if an anomaly occurs during remote control, technicians need to troubleshoot the cause of the anomaly step by step, resulting in low troubleshooting efficiency. Summary of the Invention

[0004] In view of the above, one or more embodiments of this specification provide the following technical solutions: According to a first aspect of one or more embodiments of this specification, a monitoring method for remote control based on a vehicle-to-everything (V2X) system is provided. The V2X system includes: a mobile terminal, a cloud server, and an in-vehicle terminal. The mobile terminal is used to send remote control commands to the in-vehicle terminal via the cloud server. The method includes: Acquire process information of each stage that the remote control command goes through as it is sent from the mobile terminal to the vehicle terminal; Establish stage numbers corresponding to the process information of each stage, and the stage numbers are used to indicate the order in which the remote control command is issued. The instruction identifier of the remote control command and the vehicle identifier corresponding to the vehicle terminal are determined. The process information of each stage is integrated according to the corresponding stage number using the instruction identifier and the vehicle identifier as association fields to obtain the target log. The stage number in the target log is used to locate the stage where an anomaly occurred during the remote control process of the vehicle networking system, and the process information corresponding to the abnormal stage in the target log is used to analyze the cause of the anomaly.

[0005] According to a second aspect of one or more embodiments of this specification, a monitoring device based on remote control of a vehicle-to-everything (V2X) system is provided. The V2X system includes: a mobile terminal, a cloud server, and an in-vehicle terminal. The mobile terminal is used to send remote control commands to the in-vehicle terminal via the cloud server. The device includes: The acquisition module is used to acquire process information of each stage that the remote control command goes through during the process of being sent from the mobile terminal to the vehicle terminal; A module is established to establish the stage sequence number corresponding to the process information of each stage, wherein the stage sequence number is used to indicate the order in which the remote control command is issued. An integration module is used to determine the instruction identifier of the remote control command and the vehicle identifier corresponding to the vehicle terminal, and integrate the process information of each stage according to the corresponding stage number using the instruction identifier and the vehicle identifier as association fields to obtain the target log. The stage number in the target log is used to locate the stage where an anomaly occurred during the remote control process of the vehicle networking system, and the process information corresponding to the abnormal stage in the target log is used to analyze the cause of the anomaly.

[0006] According to a third aspect of this specification, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first aspect.

[0007] According to a fourth aspect of this specification, a computer program product includes a computer program / instructions that, when executed by a processor, implement the steps of the method described in the first aspect.

[0008] As can be seen from the above embodiments, this specification defines preset stage sequence numbers for the entire link process of remote control commands being sent between the mobile terminal, cloud server, and vehicle terminal, and uses command identifier and vehicle identifier as associated fields to sequentially integrate the process information of each stage to generate a unified target log. This achieves full-link monitoring of the remote control process and can quickly locate the specific stage where anomalies occur during the remote control process of the vehicle networking system based on the target log. It can also use the process information of the corresponding stage for targeted analysis, effectively improving the efficiency of fault diagnosis and the accuracy of system monitoring. Attached Figure Description

[0009] Figure 1 This is an architecture diagram of a vehicle networking system shown in the embodiments disclosed in this specification; Figure 2 This is a flowchart illustrating a remote control monitoring method based on a vehicle networking system, as shown in the embodiments disclosed in this specification. Figure 3This is a schematic flowchart illustrating another monitoring method based on remote control of a vehicle networking system, as shown in the embodiments disclosed in this specification. Figure 4 This is a schematic diagram of the remote control command issuance process shown in the embodiments disclosed in this specification. Figure 1 ; Figure 5 This is a schematic diagram of the remote control command issuance process shown in the embodiments disclosed in this specification. Figure 2 ; Figure 6 This is a schematic diagram of the remote control command issuance process shown in the embodiments disclosed in this specification. Figure 3 ; Figure 7 This is a schematic structural diagram of an electronic device shown in the embodiments of this specification; Figure 8 This is a schematic diagram of the structure of a monitoring device based on remote control of a vehicle networking system, as shown in the embodiments of this specification. Detailed Implementation

[0010] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this manual are all information and data authorized by the user or fully authorized by all parties. The collection, use and processing of related data shall comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation portals shall be provided for users to choose to authorize or refuse.

[0011] Figure 1 This is a schematic diagram of the architecture of a vehicle-to-everything (V2X) system provided in an exemplary embodiment. For example... Figure 1 As shown, the system may include at least a mobile terminal 12, a cloud server 14, and an in-vehicle terminal 16.

[0012] Mobile terminal 12 is a user-held mobile terminal, such as a smartphone, which includes at least an instruction processing module. The instruction processing module generates remote control instructions and sends these instructions to a cloud server 14, which then transmits the remote control instructions to the vehicle-mounted terminal 16.

[0013] Cloud server 14 is a backend server deployed in the cloud, on which at least a vehicle-to-everything (V2X) service platform, a distributed message queue, a caching module, a communication message middleware, and a downlink consumption service module are deployed. The V2X service platform is used to forward received remote control commands to the vehicle-mounted terminal via the distributed message queue, caching module, communication message middleware, and downlink consumption service module.

[0014] The vehicle terminal 16 is the core vehicle device for executing the key generation and Bluetooth broadcast control described in this specification. It is integrated inside the vehicle and includes at least an execution module. The execution module is used to execute the remote control command received from the cloud server 14.

[0015] Figure 2 This is a flowchart illustrating an exemplary embodiment of a monitoring method based on a vehicle networking system for remote control. This method can be executed by a monitoring platform deployed on cloud server 14, or by a monitoring platform deployed on other servers, such as... Figure 2 As shown, the method may include the following steps: Step 202: Obtain process information of each stage that the remote control command goes through as it is sent from the mobile terminal to the vehicle terminal.

[0016] In this process, the user interacts with a mobile terminal, which generates control commands. The mobile terminal then sends the control commands to a cloud server. The cloud server processes the control commands and sends them to the vehicle terminal. The vehicle terminal executes the remote control commands, thus enabling the user to remotely control the vehicle using the mobile terminal.

[0017] Remote control commands include: remote start, remote stop, air conditioning on / off, door unlock, door lock, window operation, horn homing, and light flashing. Each remote control command carries a unique command identifier, vehicle identifier, command content, generation timestamp, and security authentication information (such as a digital signature or token). The command identifier is typically a UUID (Universally Unique Identifier). The vehicle identifier is typically a VIN (Vehicle Identification Number), used to uniquely identify the vehicle and associate it with all vehicle-related logs and commands. The command content refers to the specific vehicle operation to be performed by the remote control command; for example, "TRUNK_OPEN" indicates opening the trunk.

[0018] It is understandable that the process of sending remote control commands from a mobile terminal device to the vehicle terminal for execution of the remote control commands is divided into multiple stages, each with its own process information.

[0019] In this manual, each process information includes an instruction identifier and a vehicle identifier. Each process information may also include other content, such as the corresponding timestamp, participating components, and operation results, which are not limited in this manual.

[0020] Step 204: Establish the stage number corresponding to the process information of each stage.

[0021] The stage number is used to indicate the sequence of the remote control command issuance process.

[0022] The process of issuing remote control commands refers to the process by which a mobile terminal device sends a remote control command to the vehicle terminal to execute the remote control command.

[0023] In this manual, the remote control command issuance process can be pre-divided into multiple stages, and then a corresponding stage number is preset for each stage. A smaller number indicates that the corresponding stage runs earlier, and a larger number indicates that the corresponding stage runs later.

[0024] In some embodiments, the process information for each stage includes the instruction identifier and the vehicle identifier, and the target log includes process information for at least one of the following stages: first-stage process information of the mobile terminal sending the remote control instruction to the cloud server; second-stage process information of the cloud server sending the remote control instruction to the vehicle terminal; third-stage process information of the vehicle terminal sending a confirmation message to the cloud server; and fourth-stage process information of the vehicle terminal executing the remote control instruction.

[0025] In this specification, stages one, two, three, and four should be run sequentially. If stage one malfunctions, stage two cannot run. If stage two malfunctions, stage three cannot run. If stage three runs, stage four cannot run. Therefore, the target log includes the following: stage one process information; stage one process information and stage two process information; stage one process information, stage two process information, and stage three process information; stage one process information, stage two process information, stage three process information, and stage four process information.

[0026] The first stage involves the user operating the mobile terminal application, which sends remote control commands to its backend, and the backend forwards these commands to the cloud server.

[0027] Furthermore, the first-stage process information includes: the instruction identifier, the vehicle identifier, the time when the mobile terminal sends the remote control instruction, the user identifier corresponding to the operation of the mobile terminal, and the instruction content in the remote control instruction.

[0028] The second stage involves the cloud server sending the remote control command to the vehicle-mounted terminal, including verification and forwarding of the command. The third stage involves the vehicle-mounted terminal sending a confirmation message to the cloud server. The fourth stage involves the vehicle-mounted terminal executing the remote control command.

[0029] It is understood that the fourth-stage process information includes: instruction identifier, vehicle identifier, execution result, and execution result return time. The execution result includes whether the execution was successful or failed. After the vehicle terminal completes the execution of the remote control instruction, it returns the execution result to the mobile terminal via the cloud server. The execution result return time can be either the time the execution result is sent from the vehicle terminal or the time the cloud server receives the execution result.

[0030] Step 206: Determine the instruction identifier of the remote control command and the vehicle identifier corresponding to the vehicle terminal, and integrate the process information of each stage according to the corresponding stage number using the instruction identifier and the vehicle identifier as association fields to obtain the target log.

[0031] In this embodiment, the process information can be parsed to obtain the instruction identifier and vehicle identifier corresponding to each process information.

[0032] In some embodiments, step 206 includes: integrating at least one of the first-stage process information, the second-stage process information, the third-stage process information, and the fourth-stage process information, where both the instruction identifier and the vehicle identifier are the same, according to the sequential order of the stage numbers, to obtain the target log; and determining that the associated fields of the target log are the instruction identifier and the vehicle identifier.

[0033] In this embodiment, if the monitoring platform receives first-stage process information, second-stage process information, third-stage process information, and fourth-stage process information with different instruction identifiers and vehicle identifiers, the monitoring platform can parse each of these information sets to obtain the instruction identifier and vehicle identifier contained in each stage. The first-stage process information, second-stage process information, third-stage process information, and fourth-stage process information with identical instruction identifiers and vehicle identifiers are then integrated according to their stage numbers to obtain the target log.

[0034] For example, the target logs obtained by the monitoring platform for different command identifiers and vehicle identifiers are shown in Table 1: Table 1 In Table 1, each target log has a corresponding associated field (instruction identifier and vehicle identifier). In the target log, each process information is associated with the corresponding stage number, and the process information is integrated in the order of the stage number.

[0035] The stage number in the target log is used to locate the stage where an anomaly occurred during the remote control process of the vehicle networking system, and the process information corresponding to the abnormal stage in the target log is used to analyze the cause of the anomaly.

[0036] It is understandable that the target log corresponding to the instruction identifier and vehicle identifier can be located based on the association between the instruction identifier and vehicle identifier and the target log. Then, the stage where the anomaly occurred can be located based on the stage sequence number included in the target log. Finally, the process information of the remaining stage can be searched and analyzed to determine the cause of the anomaly.

[0037] For example, a mobile terminal sends a remote control command (e.g., command identifier a2, vehicle identifier b1) to an in-vehicle terminal to control the vehicle to start, but the vehicle fails to start. To determine the reason for the vehicle starting failure, the corresponding target log can be obtained based on command identifier a2 and vehicle identifier b1. This target log includes: stage number ①: first stage process information c1; stage number ②: second stage process information c2. Then, the target log can be analyzed to determine the reason for the vehicle starting failure.

[0038] By acquiring the process information of each stage during the transmission of remote control commands from the mobile terminal to the vehicle terminal, this specification enables the acquisition of information across the entire remote control chain. Furthermore, by defining preset stage numbers for the entire transmission process of remote control commands between the mobile terminal, cloud server, and vehicle terminal, and using command identifiers and vehicle identifiers as associated fields, the process information of each stage is sequentially integrated to generate a unified target log. This integration of process information from each stage facilitates the rapid location of specific stages where anomalies occur during the remote control process of the vehicle networking system based on the target log. Targeted analysis can then be performed using the process information of the corresponding stage, effectively improving troubleshooting efficiency and system monitoring accuracy.

[0039] Figure 3 This is a flowchart illustrating another monitoring method based on remote control of a vehicle networking system, as shown in an exemplary embodiment of this specification. Figure 3 As shown, the method may also include the following steps: Step 302: Establish the sub-stage sequence number corresponding to each sub-stage process information.

[0040] It is understood that the second stage includes multiple sub-stages, and therefore the process information of the second stage includes at least one sub-stage process information. Each sub-stage has a preset sub-stage number, and this embodiment can establish an association between the process information of each sub-stage and its corresponding sub-stage number.

[0041] Step 304: The process information of each sub-stage with the same instruction identifier and vehicle identifier is integrated according to the associated sub-stage sequence number to obtain the integrated second stage process information.

[0042] In some embodiments, if the second-stage process information includes a sub-stage process information, the target log may include: the stage number of the second-stage process information (e.g., ②), the sub-stage number of the sub-stage process information (e.g., (1)) and the sub-stage process information.

[0043] If the second-stage process information includes at least one sub-stage process information, the target log may include: the stage number of the second-stage process information (e.g., ②), the sequence number of each sub-stage, and the sub-stage process information associated with each sub-stage sequence number.

[0044] Each sub-stage process information includes an instruction identifier and a vehicle identifier. These identifiers can be obtained by parsing the sub-stage process information. Then, the sub-stage process information with identical instruction and vehicle identifiers is integrated according to its associated sub-stage sequence number to obtain the integrated second-stage process information. This integrated second-stage process information is used for target log integration.

[0045] The cloud server is equipped with a vehicle-to-everything (TSP) service platform, a distributed message queue, a caching module, a communication message middleware, and a downlink consumption service module. Among them, the distributed message queue is such as the Kafka message queue, the caching module is such as the Redis caching module, the communication message middleware is such as the EMQX message service, and the downlink consumption service module is such as the IoT downlink consumption service.

[0046] In some embodiments, the vehicle network service platform is used to verify the received remote control command; if the verification result is successful and the vehicle terminal is online, the vehicle network service platform is also used to send the remote control command to the distributed message queue; if the verification result is successful and the vehicle terminal is offline, the vehicle network service platform is also used to call the SMS wake-up interface to send a wake-up command to the vehicle terminal. If the verification result is a verification failure, the at least one sub-stage process information includes: the verification process information of the vehicle network service platform verifying the remote control command; If the verification result is successful and the vehicle terminal is online, the at least one sub-stage process information includes: the verification process information and the writing process information of the vehicle network service platform writing the remote control command to the distributed message queue; If the verification result is successful and the vehicle terminal is offline, the at least one sub-stage process information includes: the verification process information and the SMS wake-up process information in which the vehicle network service platform calls the SMS wake-up interface to send a wake-up command to the vehicle terminal. In the target log, the sub-stage number of the verification process information (e.g., (1)) is less than the sub-stage number of the delivery process information (e.g., (2)) and the sub-stage number of the SMS wake-up process information (e.g., (3)).

[0047] In some embodiments, if the SMS wake-up interface is successfully invoked, the vehicle network service platform is used to cache the remote control command in the cache module, and the communication message middleware is used to listen for the online event of the vehicle terminal. The at least one sub-stage process information also includes: caching process information of the vehicle network service platform caching the remote control command in the caching module and listening process information of the vehicle network service platform listening to the online event of the vehicle terminal; In the target log, the sub-stage sequence number of the monitoring process information is greater than the sub-stage sequence number of the caching process information, and the sub-stage sequence number of the caching process information is greater than the sub-stage sequence number of the SMS wake-up process information.

[0048] In this specification, if the online event of the vehicle terminal is detected within the cache duration threshold, the remote control command in the cache module is sent to the distributed message queue. If the online event of the vehicle terminal is not detected within the cache duration threshold, or if the online event of the vehicle terminal is detected within the cache duration threshold but the online time is less than a preset online time threshold, the remote control command in the cache module is deleted. In some embodiments, the downlink consumption service module is used to obtain the remote control command from the distributed message queue and send the remote control command to the communication message middleware; The at least one sub-stage process information further includes: instruction acquisition process information of the downlink consumption service module obtaining the remote control instruction from the distributed message queue, or, the acquisition process information and instruction sending process information of sending the remote control instruction to the communication message middleware; In the target log, the sub-stage sequence number of the instruction acquisition process information is greater than the sub-stage sequence number of the online monitoring process information and the writing process information; the sub-stage sequence number of the instruction sending process information is greater than the sub-stage sequence number of the instruction acquisition process information.

[0049] The instruction acquisition process information includes: the instruction identifier, the vehicle identifier, the acquisition time, and the instruction acquisition result information; the instruction sending process information includes: the instruction identifier, the vehicle identifier, the corresponding instruction sending time, and the instruction sending result information.

[0050] In summary, the stages that remote control commands go through from the mobile terminal to the vehicle terminal can be categorized into the following three situations: Scenario 1: Reference Figure 4 This is a schematic diagram of a remote control command issuance process provided in this specification. Figure 1 ,exist Figure 4 In this process, the mobile terminal sends a remote control command to the TSP platform, and then the TSP platform verifies the remote control command. If the verification fails, it returns an error to the mobile terminal to inform the user that the remote control command has failed to be sent.

[0051] In this scenario, the remote control command issuance process includes a first stage (the mobile terminal sends the remote control command to the TSP platform) and a second stage (the TSP platform verifies the received remote control command). The second stage only includes one sub-stage, which is the verification stage.

[0052] Specifically, in the first phase, the user issues a remote control command through the mobile terminal application. Upon receiving the command, the application's backend generates a unique command identifier and forwards the command (carrying the command identifier, user identifier, vehicle identifier, and command content) to the TSP platform's remote control API (Application Programming Interface). Simultaneously, the first-phase process information (including the command identifier, vehicle identifier, the time the remote control command was sent, the user identifier, and the command content) is synchronized to a unified monitoring platform, enabling the monitoring platform to access this first-phase process information.

[0053] It is understandable that a new synchronization module is added to the application background to collect information from the first stage of the process and send the collected information to the monitoring platform.

[0054] Furthermore, in the verification phase of the second stage, after receiving the remote control command, the TSP platform initiates the permission verification process. The specific verification phase includes verifying the user's data permissions, the existence of the vehicle corresponding to the vehicle identifier, and whether the in-vehicle terminal is online. Simultaneously, the newly added permission verification monitoring module on the TSP platform begins recording verification process information, including verification time, user identifier, vehicle identifier, and verification items (such as user data permissions, vehicle existence, and the online status of the in-vehicle terminal).

[0055] Case 1 refers to the scenario where verification fails. In this case, the verification process information includes the verification failure itself and the reason for the failure (such as the user lacking data permissions and / or the vehicle not being entered). The permission verification monitoring module can send the recorded verification process information as sub-stage process information to the monitoring platform.

[0056] Furthermore, if the verification fails, the TSP platform returns an error message to the mobile terminal, which may include the reason for the verification failure.

[0057] In summary, in scenario one, the monitoring platform can obtain process information for the first stage and process information for the second stage (including one sub-stage, the "verification stage"). The resulting target log is shown in Table 2. Table 2 Table 2 shows the complete record of the relevant information for the entire process of issuing the remote control command in the target log, which can be used by staff for subsequent analysis.

[0058] Scenario 2: Reference Figure 5 This is a schematic diagram of a remote control command issuance process provided in this specification. Figure 2 ,exist Figure 5 In this process, the mobile terminal sends a remote control command to the TSP platform. The TSP platform then verifies the remote control command. If the verification is successful and the vehicle terminal is online, the remote control command is written into a distributed message queue. The downlink consumption service module consumes the remote control command from the distributed message queue and then sends the obtained remote control command to the communication message middleware. The communication message middleware pushes the remote control command to the vehicle terminal, which executes the remote control command and sends a confirmation message back to the TSP platform via the communication message middleware, the downlink message service module, and the distributed message queue. The TSP platform then returns information to the mobile terminal indicating that the command has been sent.

[0059] In scenario two, the remote control command issuance process includes a first stage (the mobile terminal sends the remote control command to the TSP platform), a second stage of verification (the TSP platform verifies the received remote control command), and a second stage of command issuance (the vehicle network service platform sends the remote control command to the distributed message queue). Specifically, in scenario two, the process information for the first stage is the same as in scenario one, and you can refer to the relevant content of scenario one above, which will not be repeated here.

[0060] Furthermore, in the verification phase of the second stage, after receiving the remote control command, the TSP platform initiates the permission verification process. The specific verification phase includes verifying the user's data permissions, the existence of the vehicle corresponding to the vehicle identifier, and whether the in-vehicle terminal is online. Simultaneously, the newly added permission verification monitoring module on the TSP platform begins recording verification process information, including verification time, user identifier, vehicle identifier, and verification items (such as user data permissions, vehicle existence, and the online status of the in-vehicle terminal).

[0061] Scenario two refers to a situation where verification is successful and the vehicle-mounted terminal is online. In this scenario, successful verification means the user has data permissions and the vehicle exists; therefore, the verification process information also includes "verification successful." The permission verification monitoring module can send the recorded verification process information as sub-stage process information to the monitoring platform.

[0062] Furthermore, the TSP platform writes remote control commands to the distributed message queue. The message queue monitoring module, pre-deployed on the TSP platform, records the writing process information, including: write time, command identifier, vehicle identifier, and write status (successful or failed). The message queue monitoring module synchronizes the recorded writing process information to the monitoring platform.

[0063] In this specification, the writing process is a sub-stage of the second stage, and the corresponding writing process information is also the process information of one of the sub-stages.

[0064] If the write operation fails, a failure message can be returned to the mobile terminal, and the remote control process can be terminated. If the write operation fails, the write status in the write process information will be "write failed," and the monitoring platform can obtain the process information of the first stage and the sub-stage process information of the second stage (verification stage and write stage). The sub-stage number (2) corresponding to the write process information is greater than the sub-stage number (1) corresponding to the verification process information. Based on this, the target log is shown in Table 3: Table 3 If the write is successful, the write status in the write process information will be "write successful". Further, the downlink consumption service module obtains remote control instructions from the distributed message queue for consumption. At this time, the consumption monitoring module pre-deployed in the downlink consumption service module records the acquisition process information of the remote control instructions. The acquisition process information includes: acquisition time, instruction identifier, vehicle identifier and consumption status (consumption successful or consumption failed).

[0065] Furthermore, if the consumption status is "consumption failed", a failure message can be returned to the mobile terminal, and then the remote control process can be terminated.

[0066] In some implementations, a consumption time (e.g., 30 seconds) can be preset. The timer starts when a remote control command is written to the distributed message queue. If the downlink consumption service module does not obtain the remote control command within 30 seconds, the consumption is determined to have failed.

[0067] If consumption fails, the monitoring platform can obtain the process information of the first stage and the sub-stage process information of the second stage (verification stage, writing stage, and consumption stage). Among them, the sub-stage sequence number (6) of the instruction to obtain process information in the consumption stage is greater than the sub-stage sequence number (2) of the writing process information. Based on this, the target log is shown in Table 4: Table 4 If the consumption status is successful, the downlink consumption service module forwards the remote control command to the communication message middleware. The communication message monitoring module, pre-deployed in the communication message middleware, records the command transmission process information, including: command transmission time, command identifier, vehicle identifier, and transmission status (successful or failed). This information is then synchronized to the monitoring platform. If the transmission status in the command transmission process information is "failed," the information also includes the reason for the error (e.g., the vehicle terminal is offline, or the communication message middleware service is malfunctioning).

[0068] If the downlink consumption service module fails to forward the remote control command to the communication message middleware, the monitoring platform can obtain the process information of the first stage and the sub-stage process information of the second stage (verification stage, writing stage, consumption stage, command sending stage). Among them, the sub-stage sequence number (7) of the command sending process information is greater than the sub-stage sequence number (6) of the command acquisition process information. Based on this, the target log is shown in Table 5: Table 5 If the downlink consumption service module fails to forward the remote control command to the communication message middleware, the current remote control process can be terminated.

[0069] Then, if the downlink consumption service module successfully forwards the remote control command to the communication message middleware, the middleware can push the remote control command to the vehicle's onboard terminal. Upon receiving the command, the onboard terminal can return an acknowledgment (ACK) message to the TSP platform via the communication message middleware, the downlink consumption service module, and the distributed message queue. The feedback monitoring module, pre-deployed on the TSP platform, can then record the third-stage process information, including: (if an acknowledgment message is received) the message reception time, command identifier, vehicle identifier, and acknowledgment message status (acknowledgment message reception successful or failed). The feedback monitoring module sends the recorded third-stage process information to the monitoring platform. If the TSP platform does not receive an acknowledgment message within a preset time (e.g., 1 minute), it marks the acknowledgment message reception as failed.

[0070] In some embodiments, a communication message middleware may receive the confirmation message and then feed back the third-stage process information to the monitoring platform; this specification does not limit this to that.

[0071] In some embodiments, if message reception failure is confirmed, the third-stage process information also includes: instruction issuance records and the online status of the vehicle terminal.

[0072] If message reception fails, the monitoring platform can obtain process information for the first stage, the second stage (verification stage, writing stage, consumption stage, and command sending stage), and the third stage. Based on this, the target log is shown in Table 6. Table 6 In some embodiments, after receiving a remote control command, the vehicle terminal begins executing the command. After executing the command, the vehicle terminal can return the execution result to the TSP platform via a communication message middleware, a downlink consumption service module, or a distributed message queue. Simultaneously, if the TSP platform receives the execution result, it records the fourth-stage process information using a pre-deployed feedback reception monitoring module. This fourth-stage process information includes: the time of receipt of the execution result, the command identifier, the vehicle identifier, and the execution result (successful or failed). If the TSP platform does not receive the execution result within a preset time, the fourth-stage process information includes: the command identifier, the vehicle identifier, and a loss anomaly. The feedback reception monitoring module synchronizes the recorded fourth-stage process information to the monitoring platform.

[0073] The monitoring platform can obtain process information for the first stage, the second stage (verification stage, writing stage, consumption stage, and command sending stage), the third stage, and the fourth stage. Based on this, the target log is shown in Table 7. Table 7 In summary, when the verification result is successful and the vehicle terminal is online, this manual can monitor the process information of the entire remote control link under this condition, and then integrate the process information to obtain an orderly target log, which facilitates the subsequent location and analysis of problems.

[0074] Scenario 3: Reference Figure 6 This is a schematic diagram of a remote control command issuance process provided in this specification. Figure 3 ,exist Figure 6 In this process, the mobile terminal sends a remote control command to the TSP platform. The TSP platform then verifies the remote control command. If the verification is successful and the vehicle terminal is offline, the vehicle network service platform calls the SMS wake-up interface of the SMS service to send a wake-up command to the vehicle terminal. After sending the wake-up command to the vehicle terminal, the SMS service returns the SMS sending result to the TSP platform through the SMS wake-up interface. The SMS wake-up process is a sub-process of the second stage, and the SMS wake-up process information is the process information of one of these sub-stages.

[0075] In some embodiments, the SMS wake-up process information can be recorded by a pre-deployed SMS wake-up monitoring module in the TSP platform, and then synchronized to the monitoring platform. The SMS wake-up process information includes: vehicle terminal identifier, vehicle identifier, command identifier, interface call time, SMS sending result (success, failure, or SMS sent), and the response time of the SMS wake-up interface. If the SMS sending result is a failure, the SMS wake-up process information also includes a flag indicating that the SMS wake-up interface call failed, and then the current remote control process is terminated.

[0076] If the SMS sending fails, the monitoring platform can obtain process information for the first stage and the second stage (verification stage and wake-up stage). Based on this, the target log is shown in Table 8: Table 8 If the SMS message is sent successfully (meaning the SMS wake-up interface call was successful), the TSP caches the remote control command in the cache module and returns a message to the mobile terminal indicating that the vehicle is offline. Then, the cache monitoring module records the caching process information and synchronizes this information to the monitoring platform. This caching process information includes: command identifier, vehicle identifier, cache time, and cache duration threshold.

[0077] The aforementioned cache monitoring module can be embedded in the cache module, or it can be a standalone module deployed on a cloud server and connected to the cache module via an interface. This specification does not limit this.

[0078] Furthermore, after caching remote control commands in the caching module, the online / offline monitoring module of the communication message middleware continuously listens for the online events of the vehicle terminal, and can also record the listening process information and synchronize the recorded listening process information to the monitoring platform.

[0079] If no online event is detected from the vehicle terminal within the cache duration threshold, the remote control command will be deleted from the cache module. The recorded monitoring process information includes: command identifier, vehicle identifier, and the reason for cache deletion being timeout. Additionally, the monitoring process information may also include: the vehicle terminal's historical online records, the vehicle's last location information, and any anomalies such as no response to SMS wake-up. If no online event is detected from the vehicle terminal, the remote control process can be terminated.

[0080] This specification circumvents the limitation of not being able to monitor SMS transmission from the operator's SMS service to the vehicle terminal. By using the SMS sending results returned through the SMS wake-up interface and the vehicle terminal's online feedback, accurate marking of anomalies such as no SMS wake-up response can be achieved. Simultaneously, the vehicle terminal's historical online records can help technicians deduce the cause of the anomaly; for example, a historically weak signal suggests a problem with the vehicle terminal's signal. Therefore, the monitoring process information obtained through this application can improve the accuracy of anomaly detection.

[0081] If no online event of the vehicle terminal is detected, the monitoring platform can obtain the process information of the first stage and the process information of the second stage (verification stage, wake-up stage, caching stage, and monitoring stage). Based on this, the target log is shown in Table 9: Table 9 If an offline event is triggered shortly after the vehicle terminal goes online (e.g., within 1 minute), the monitoring information includes: command identifier, vehicle identifier, online time, offline time, terminal online instability, and online duration. In this case, the TSP platform can be triggered to resend remote control commands to the vehicle terminal.

[0082] If the vehicle terminal goes online within the cache duration threshold (e.g., 5 minutes), the recorded listening process information includes: instruction identifier, vehicle identifier, online time, online duration, and SMS wake-up success. When the vehicle terminal goes online, the communication message middleware triggers the cache module to send the remote control instruction to the distributed message queue, and then enters the instruction acquisition stage corresponding to sub-stage number (6).

[0083] The buffer duration threshold can be dynamically adjusted based on the historical online response time of the vehicle terminal and the signal strength in the current area (combined with the vehicle's last reported location information). For example, if the historical response time is relatively fast, the buffer duration threshold can be set to 3 minutes; if the signal is weak, the buffer duration threshold can be set to 8 minutes. This method can further improve the accuracy of SMS wake-up anomaly detection.

[0084] The monitoring platform in this embodiment can also be replaced by the ELK component (a classic open-source suite for log collection, storage, retrieval, and visualization). The ELK component collects information sent by each monitoring module, and then performs centralized analysis and relationship analysis to achieve anomaly location and tracing.

[0085] The process after entering the instruction acquisition stage can refer to the relevant content of Case 2 above, and will not be repeated here.

[0086] In summary, the monitoring platform can receive logs synchronized from various monitoring modules in real time. Using command identifiers and vehicle identifiers as correlation fields, it associates information recorded at all stages, including command initiation, permission verification, SMS wake-up, caching process, command issuance, and vehicle terminal feedback, forming a complete target log. If a user reports a remote control anomaly, technicians can use the monitoring platform to input the command identifier and / or vehicle identifier to query the complete target log of that remote control command, quickly locate the abnormal node (such as SMS wake-up failure or consumption anomaly) and the cause of the anomaly, and complete the anomaly investigation and problem resolution.

[0087] All monitoring functions in this manual are implemented by embedding monitoring modules into existing modules such as the existing TSP platform, caching module, distributed message queue, communication message middleware, and vehicle terminal to record relevant process information. No additional hardware equipment or interfaces with operators are required, making it fully compatible with the existing technical architecture and ready for direct implementation.

[0088] In addition, this manual also realizes the integration and association of scattered information through instruction identifiers and vehicle identifiers to obtain target logs, which solves the problem of independent logs and inability to be associated in the prior art, and can quickly locate the abnormal stage when an anomaly occurs, thus improving the efficiency of investigation.

[0089] Furthermore, this manual sets corresponding exception markers for different abnormal situations. For example, when a permission verification error occurs, the target log will include markers indicating that the user does not have data permissions and / or the vehicle has not been recorded. When an SMS wake-up error occurs, the target log will include markers indicating that the interface call is abnormal and / or that there is no response during wake-up. These exception markers enable technical personnel to quickly identify the cause of the error and improve the efficiency of error troubleshooting.

[0090] In some embodiments, the method further includes: determining the largest stage number in the target log as the target stage number; and analyzing the process information of the target stage corresponding to the target stage number in the target log to obtain the anomalies that occurred in the target stage.

[0091] If it is necessary to analyze anomalies in the process of issuing remote control commands, the corresponding target log can be found first based on the command identifier and vehicle identifier. Then, the largest stage number in the target log can be determined as the target stage number, and the process information corresponding to the target stage number can be analyzed.

[0092] It is understandable that if an anomaly occurs in a stage, the corresponding remote control process will end, and the next stage will not run. That is, there will be no process information for the next stage in the target log. Therefore, it is only necessary to analyze the process information corresponding to the stage with the largest sequence number.

[0093] As can be seen, this manual does not require analyzing the entire target log when locating anomalies in command issuance. It can achieve efficient location of command issuance anomalies without requiring technicians to investigate each step one by one.

[0094] Referring to Table 1, if the instruction identifier is a2 and the vehicle identifier is b1, then the largest stage number is stage number ③. Therefore, we only need to analyze the third stage process information d3.

[0095] In this embodiment, the entire target log can also be analyzed, and this is not limited. Furthermore, this specification does not limit the specific method of log analysis.

[0096] In some embodiments, the method further includes: if the largest stage sequence number in the target log is associated with the second stage process information, then the largest sub-stage sequence number in the target log is determined as the target sub-stage sequence number; and the target sub-stage process information corresponding to the target sub-stage sequence number is analyzed in the target log to obtain the anomaly that occurred in the target sub-stage.

[0097] If the largest stage number in the target log is determined to be ②, since the second stage includes multiple sub-stages, we can only analyze the process information of the sub-stage with the largest sub-stage number.

[0098] It is understandable that if an anomaly occurs in a sub-stage, the corresponding remote control process will end, and therefore the next sub-stage will not run. In other words, there will be no process information for the next sub-stage in the target log. Therefore, it is only necessary to analyze the process information of the sub-stage corresponding to the largest sub-stage sequence number.

[0099] Referring to Table 4, the largest stage number is ②. The corresponding largest sub-stage number is (6). Therefore, we can obtain process information by analyzing only the instructions.

[0100] In this embodiment, the entire second-stage process information can also be analyzed, and there is no limitation on this.

[0101] As can be seen, this embodiment can monitor the target log of the entire link during the remote control command issuance process, so as to facilitate efficient analysis of remote control command issuance anomalies and improve the efficiency of anomaly troubleshooting.

[0102] This manual reduces the probability of remote control failures by quickly locating and resolving remote control malfunctions. Furthermore, it enables rapid response and resolution when remote control malfunctions occur, preventing user dissatisfaction due to failures, effectively improving the user experience and reducing market complaint rates.

[0103] Furthermore, the target logs of this application can be retained for a long time, which can be used not only for real-time anomaly investigation, but also for review and analysis of subsequent anomalies, summarizing the patterns of anomaly occurrence, optimizing remote control processes, and further reducing the anomaly occurrence rate.

[0104] Figure 7 This is a schematic structural diagram of an electronic device according to an exemplary embodiment. Please refer to... Figure 7 At the hardware level, the electronic device includes a processor, internal bus, network interface, memory, and non-volatile memory, and may also include other necessary hardware. The processor reads the corresponding computer program from the non-volatile memory into memory and then runs it, forming a monitoring device for remote control based on a vehicle networking system at the logical level. Of course, in addition to software implementation, this specification does not exclude other implementation methods, such as logic devices or a combination of hardware and software, etc. That is to say, the execution subject of the following processing flow is not limited to individual logic units, but can also be hardware or logic devices.

[0105] Corresponding to the aforementioned embodiment of a monitoring method based on remote control of a vehicle networking system, this specification also provides an embodiment of a device for generating a digital car key.

[0106] Please refer to Figure 8 , Figure 8 This is a schematic diagram illustrating the structure of a monitoring device based on a vehicle networking system for remote control, as shown in an exemplary embodiment. Figure 8 As shown, in the software implementation, the vehicle networking system includes: a mobile terminal, a cloud server, and an in-vehicle terminal. The mobile terminal is used to send remote control commands to the in-vehicle terminal through the cloud server. The device includes: The acquisition module 802 is used to acquire process information of each stage that the remote control command goes through during the process of being sent from the mobile terminal to the vehicle terminal; A module 804 is established to establish the stage sequence number corresponding to the process information of each stage, wherein the stage sequence number is used to indicate the order in which the remote control command is issued. Integration module 806 is used to determine the instruction identifier of the remote control instruction and the vehicle identifier corresponding to the vehicle terminal, and integrate the process information of each stage according to the corresponding stage number using the instruction identifier and the vehicle identifier as association fields to obtain the target log. The stage number in the target log is used to locate the stage where an anomaly occurred during the remote control process of the vehicle networking system, and the process information corresponding to the abnormal stage in the target log is used to analyze the cause of the anomaly.

[0107] Optionally, the request receiving unit is specifically used for: When the digital car key is created for the first time on the target vehicle, the key generation request sent by the target vehicle along with the vehicle certificate generation request is received; When the digital car key is deactivated on the target vehicle, the key generation request sent along with the vehicle certificate update request on the target vehicle is received.

[0108] Optionally, the process information at each stage includes the instruction identifier and the vehicle identifier, and the target log includes process information for at least one of the following stages: first-stage process information of the mobile terminal sending the remote control instruction to the cloud server; second-stage process information of the cloud server sending the remote control instruction to the vehicle terminal; third-stage process information of the vehicle terminal sending a confirmation message to the cloud server; and fourth-stage process information of the vehicle terminal executing the remote control instruction. The integration module 806 integrates the process information of each stage according to the corresponding stage number, using the instruction identifier and the vehicle identifier as associated fields, to obtain the target log, which is used for: The target log is obtained by integrating at least one of the following: the first-stage process information, the second-stage process information, the third-stage process information, and the fourth-stage process information, where both the instruction identifier and the vehicle identifier are the same. The associated fields of the target log are determined to be the instruction identifier and the vehicle identifier.

[0109] Optionally, the second stage process information includes at least one sub-stage process information. The module 804 is also used to establish the sub-stage sequence number corresponding to each sub-stage process information; The integration module 806 is also used to integrate the process information of each sub-stage where the instruction identifier and vehicle identifier are the same according to the associated sub-stage sequence number to obtain the integrated second-stage process information.

[0110] Optionally, the cloud server is equipped with a vehicle-to-everything (V2X) service platform and a distributed message queue. The V2X service platform verifies the received remote control command. If the verification result is successful and the vehicle terminal is online, the V2X service platform also sends the remote control command to the distributed message queue. If the verification result is successful and the vehicle terminal is offline, the V2X service platform also calls the SMS wake-up interface to send a wake-up command to the vehicle terminal. If the verification result is a verification failure, the at least one sub-stage process information includes: the verification process information of the vehicle network service platform verifying the remote control command; If the verification result is successful and the vehicle terminal is online, the at least one sub-stage process information includes: the verification process information and the writing process information of the vehicle network service platform writing the remote control command to the distributed message queue; If the verification result is successful and the vehicle terminal is offline, the at least one sub-stage process information includes: the verification process information and the SMS wake-up process information in which the vehicle network service platform calls the SMS wake-up interface to send a wake-up command to the vehicle terminal. In the target log, the sub-stage number of the verification process information is less than the sub-stage number of the delivery process information and the sub-stage number of the SMS wake-up process information.

[0111] Optionally, the cloud server is also equipped with a caching module and a communication message middleware; if the SMS wake-up interface is successfully called, the vehicle network service platform is used to cache the remote control command in the caching module, and the communication message middleware is used to listen for the online event of the vehicle terminal. The at least one sub-stage process information also includes: caching process information of the vehicle network service platform caching the remote control command in the caching module and listening process information of the vehicle network service platform listening to the online event of the vehicle terminal; In the target log, the sub-stage sequence number of the monitoring process information is greater than the sub-stage sequence number of the caching process information, and the sub-stage sequence number of the caching process information is greater than the sub-stage sequence number of the SMS wake-up process information.

[0112] Optionally, the cloud server is further equipped with a downlink consumption service module, which is used to obtain the remote control command from the distributed message queue and send the remote control command to the communication message middleware. The at least one sub-stage process information further includes: instruction acquisition process information of the downlink consumption service module obtaining the remote control instruction from the distributed message queue, or, the acquisition process information and instruction sending process information of sending the remote control instruction to the communication message middleware; In the target log, the sub-stage sequence number of the instruction acquisition process information is greater than the sub-stage sequence number of the online monitoring process information and the writing process information; the sub-stage sequence number of the instruction sending process information is greater than the sub-stage sequence number of the instruction acquisition process information.

[0113] Optionally, the device further includes: The determination module is used to determine the largest stage number in the target log as the target stage number; The analysis module is used to analyze the process information of the target stage corresponding to the target stage number in the target log, so as to obtain the anomalies that occur in the target stage.

[0114] Optionally, the device further includes: The determination module is used to determine the target sub-stage number as the target sub-stage number if the largest stage sequence number in the target log is associated with the second stage process information. The analysis module is used to analyze the target sub-stage process information corresponding to the target sub-stage sequence number in the target log to obtain the anomalies that occur in the target sub-stage.

[0115] For the device embodiments, since they basically correspond to the method embodiments, the relevant parts can be referred to in the description of the method embodiments. The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the solution in this specification according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0116] Based on the same concept as the methods described above, this specification also provides a computer-readable storage medium having computer instructions stored thereon that, when executed by a processor, implement the steps of the methods as described in any of the above embodiments.

[0117] Based on the same concept as the methods described above, this specification also provides a computer program product, including a computer program / instructions that, when executed by a processor, implement the steps of the methods as described in any of the above embodiments.

[0118] The embodiments of the subject matter and functional operation described in this specification can be implemented in the following ways: digital electronic circuits, tangibly embodied computer software or firmware, computer hardware including the structures disclosed in this specification and their structural equivalents, or combinations thereof. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible, non-transitory program carrier for execution by a data processing apparatus or for controlling the operation of a data processing apparatus. Alternatively or additionally, the program instructions may be encoded on artificially generated propagation signals, such as machine-generated electrical, optical, or electromagnetic signals, which are generated to encode information and transmit it to a suitable receiving device for execution by the data processing apparatus. The computer storage medium may be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or combinations thereof.

[0119] The processing and logic flow described in this specification can be executed by one or more programmable computers that execute one or more computer programs to perform corresponding functions by operating on input data and generating output. The processing and logic flow can also be executed by dedicated logic circuitry—such as FPGAs (Field-Programmable Gate Arrays) or ASICs (Application-Specific Integrated Circuits), and the device can also be implemented as dedicated logic circuitry.

[0120] Computers suitable for executing computer programs include, for example, general-purpose and / or special-purpose microprocessors, or any other type of central processing unit. Typically, the central processing unit receives instructions and data from read-only memory and / or random access memory. The basic components of a computer include a central processing unit for implementing or executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more mass storage devices for storing data, such as disks, magneto-optical disks, or optical disks, or the computer will be operatively coupled to such mass storage devices to receive data from or transfer data to them, or both. However, a computer is not required to have such devices. Furthermore, a computer can be embedded in another device, such as a mobile phone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a GPS receiver, or a portable storage device such as a universal serial bus (USB) flash drive, to name a few.

[0121] Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media, and memory devices, such as semiconductor memory devices (e.g., EPROM, EEPROM, and flash memory devices), magnetic disks (e.g., internal hard disks or removable disks), magneto-optical disks, and CD-ROM and DVD-ROM disks. Processors and memory may be supplemented by or incorporated into dedicated logic circuitry.

[0122] While this specification contains numerous specific implementation details, these should not be construed as limiting the scope of any invention or the scope of the claims, but rather are primarily intended to describe features of specific embodiments of a particular invention. Certain features described in the various embodiments herein may also be implemented in combination in a single embodiment. Conversely, various features described in a single embodiment may also be implemented separately in various embodiments or in any suitable sub-combination. Furthermore, while features may function in certain combinations as described above and even initially claimed in this way, one or more features from a claimed combination may be removed from that combination in some cases, and a claimed combination may refer to a sub-combination or a variation thereof.

[0123] Similarly, although the operations are depicted in a specific order in the accompanying drawings, this should not be construed as requiring these operations to be performed in the specific order shown or sequentially, or requiring all illustrated operations to be performed to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system modules and components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0124] Therefore, specific embodiments of the subject matter have been described. Furthermore, the processes depicted in the figures are not necessarily shown in a specific order or sequence to achieve the desired result. In some implementations, multitasking and parallel processing may be advantageous.

[0125] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.

Claims

1. A monitoring method based on remote control of a vehicle networking system, characterized in that, The vehicle networking system includes: a mobile terminal, a cloud server, and an in-vehicle terminal. The mobile terminal is used to send remote control commands to the in-vehicle terminal through the cloud server. The method includes: Acquire process information of each stage that the remote control command goes through as it is sent from the mobile terminal to the vehicle terminal; Establish stage numbers corresponding to the process information of each stage, and the stage numbers are used to indicate the order in which the remote control command is issued. The instruction identifier of the remote control command and the vehicle identifier corresponding to the vehicle terminal are determined, and the process information of each stage is integrated according to the corresponding stage number using the instruction identifier and the vehicle identifier as association fields to obtain the target log. The stage number in the target log is used to locate the stage where an anomaly occurred during the remote control process of the vehicle networking system, and the process information corresponding to the abnormal stage in the target log is used to analyze the cause of the anomaly.

2. The method according to claim 1, characterized in that, The process information for each stage includes the instruction identifier and the vehicle identifier. The target log includes process information for at least one of the following stages: the first stage process information of the mobile terminal sending the remote control instruction to the cloud server; the second stage process information of the cloud server sending the remote control instruction to the vehicle terminal; the third stage process information of the vehicle terminal sending a confirmation message to the cloud server; and the fourth stage process information of the vehicle terminal executing the remote control instruction. The process information of each stage is integrated according to the corresponding stage number, using the instruction identifier and the vehicle identifier as associated fields, to obtain the target log, which includes: The target log is obtained by integrating at least one of the following: the first-stage process information, the second-stage process information, the third-stage process information, and the fourth-stage process information, where both the instruction identifier and the vehicle identifier are the same. The associated fields of the target log are determined to be the instruction identifier and the vehicle identifier.

3. The method according to claim 2, characterized in that, The second stage process information includes at least one sub-stage process information, and the method further includes: Establish sub-stage sequence numbers corresponding to the process information of each sub-stage; The process information of each sub-stage with the same instruction identifier and vehicle identifier is integrated according to the associated sub-stage sequence number to obtain the integrated second-stage process information.

4. The method according to claim 3, characterized in that, The cloud server is equipped with a vehicle network service platform and a distributed message queue. The vehicle network service platform is used to verify the received remote control command. If the verification result is successful and the vehicle terminal is online, the vehicle network service platform is also used to send the remote control command to the distributed message queue. If the verification result is successful and the vehicle terminal is offline, the vehicle network service platform is also used to call the SMS wake-up interface to send a wake-up command to the vehicle terminal. If the verification result is a verification failure, the at least one sub-stage process information includes: the verification process information of the vehicle network service platform verifying the remote control command; If the verification result is successful and the vehicle terminal is online, the at least one sub-stage process information includes: the verification process information and the writing process information of the vehicle network service platform writing the remote control command to the distributed message queue; If the verification result is successful and the vehicle terminal is offline, the at least one sub-stage process information includes: the verification process information and the SMS wake-up process information in which the vehicle network service platform calls the SMS wake-up interface to send a wake-up command to the vehicle terminal. In the target log, the sub-stage number of the verification process information is less than the sub-stage number of the delivery process information and the sub-stage number of the SMS wake-up process information.

5. The method according to claim 4, characterized in that, The cloud server is also equipped with a caching module and a communication message middleware. If the SMS wake-up interface is successfully called, the vehicle network service platform is used to cache the remote control command in the caching module, and the communication message middleware is used to listen for the online event of the vehicle terminal. The at least one sub-stage process information also includes: caching process information of the vehicle network service platform caching the remote control command in the caching module and listening process information of the vehicle network service platform listening to the online event of the vehicle terminal; In the target log, the sub-stage sequence number of the monitoring process information is greater than the sub-stage sequence number of the caching process information, and the sub-stage sequence number of the caching process information is greater than the sub-stage sequence number of the SMS wake-up process information.

6. The method according to claim 5, characterized in that, The cloud server is also equipped with a downlink consumption service module, which is used to obtain the remote control command from the distributed message queue and send the remote control command to the communication message middleware. The at least one sub-stage process information further includes: instruction acquisition process information of the downlink consumption service module obtaining the remote control instruction from the distributed message queue, or, the acquisition process information and instruction sending process information of sending the remote control instruction to the communication message middleware; In the target log, the sub-stage sequence number of the instruction acquisition process information is greater than the sub-stage sequence number of the online monitoring process information and the writing process information; the sub-stage sequence number of the instruction sending process information is greater than the sub-stage sequence number of the instruction acquisition process information.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The largest stage number in the target log is determined as the target stage number; The process information of the target stage corresponding to the target stage number is analyzed in the target log to identify any anomalies that occur in the target stage.

8. The method according to any one of claims 3 to 6, characterized in that, The method further includes: If the largest stage sequence number in the target log is associated with the second stage process information, then the largest sub-stage sequence number in the target log is the target sub-stage sequence number. The process information of the target sub-stage corresponding to the target sub-stage number is analyzed in the target log to obtain the anomalies that occurred in the target sub-stage.

9. A monitoring device based on remote control of a vehicle networking system, characterized in that, The vehicle networking system includes: a mobile terminal, a cloud server, and an in-vehicle terminal. The mobile terminal is used to send remote control commands to the in-vehicle terminal via the cloud server. The device includes: The acquisition module is used to acquire process information of each stage that the remote control command goes through during the process of being sent from the mobile terminal to the vehicle terminal; A module is established to establish the stage sequence number corresponding to the process information of each stage, wherein the stage sequence number is used to indicate the order in which the remote control command is issued. An integration module is used to determine the instruction identifier of the remote control command and the vehicle identifier corresponding to the vehicle terminal, and to integrate the process information of each stage according to the corresponding stage number using the instruction identifier and the vehicle identifier as association fields to obtain the target log. The stage number in the target log is used to locate the stage where an anomaly occurred during the remote control process of the vehicle networking system, and the process information corresponding to the abnormal stage in the target log is used to analyze the cause of the anomaly.

10. A computer-readable storage medium, characterized in that, It stores computer instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 8.

11. A computer program product, characterized in that, Includes a computer program / instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 8.

Images