Vehicle remote control method and device, medium and electronic equipment

Abstract

The invention provides a vehicle remote control method and device, a medium and electronic equipment. The method comprises the following steps: acquiring an execution command which is triggered by a user at a vehicle control application end and aims at a target vehicle function; a software version number of vehicle control software installed on a target vehicle is obtained and serves as a target software version number, and the target vehicle is a vehicle which is about to execute the target vehicle function; on the basis of a pre-configured function strategy table, the execution command is converted into a vehicle control interaction protocol and a remote control signal matched with the target software version number, and the function strategy table is used for recording the corresponding relation between different software version numbers and different vehicle control interaction protocols; and sending the remote control signal to the target vehicle to control the target vehicle to execute the target vehicle function. According to the invention, the adaptability between the vehicle control application end and the vehicle control software can be efficiently improved.

Description

Technical Field

[0001] This application relates to the field of vehicle and remote control technology, and more specifically, to a vehicle remote control method, device, medium and electronic equipment. Background Technology

[0002] Currently, after vehicles are launched on the market, the vehicle control software (vehicle controller software) is optimized, iterated, or updated via OTA (over-the-air) to meet the changing needs of users who want to remotely control their vehicles through vehicle control applications (such as mobile apps). However, OTA upgrades can lead to compatibility issues between vehicle control applications and vehicle control software. On one hand, since it's impossible to ensure that all deployed vehicles have completed the upgrade, the vehicle control application needs to handle different versions of the software simultaneously. On the other hand, inconsistent software upgrade times can also make it difficult for the application to accurately adapt to new software features. Currently, the industry's common solution is to pre-define compatibility logic for older software versions when developing new versions, identifying different versions and designing corresponding processing code to achieve cross-version functionality adaptation. However, this solution requires adding compatibility logic to existing stable code, which can easily cause conflicts between old and new functions, increasing the risk of overall functionality failure. Therefore, how to efficiently improve the compatibility between vehicle control applications and vehicle control software has become a pressing technical problem to be solved in the field of vehicle remote control. Summary of the Invention

[0003] The embodiments of this application provide a vehicle remote control method, device, computer program product or computer program, computer-readable storage medium, or electronic device, which can at least to some extent efficiently improve the compatibility between the vehicle control application terminal and the vehicle control software.

[0004] Other features and advantages of this application will become apparent from the following detailed description, or may be learned in part from practice of this application.

[0005] According to one aspect of the embodiments of this application, a vehicle remote control method is provided, the method comprising: acquiring an execution command for a target vehicle function triggered by a user on a vehicle control application terminal; acquiring the software version number of vehicle control software installed on the target vehicle as the target software version number, wherein the target vehicle is a vehicle to execute the target vehicle function; converting the execution command into a remote control signal that matches the vehicle control interaction protocol and the target software version number based on a pre-configured function strategy table, wherein the function strategy table is used to record the correspondence between different software version numbers and different vehicle control interaction protocols; and sending the remote control signal to the target vehicle to control the target vehicle to execute the target vehicle function.

[0006] In some embodiments of this application, based on the foregoing scheme, obtaining the software version number of the vehicle control software installed on the target vehicle includes: receiving the software version number actively reported by the target vehicle through an OTA platform; and / or, requesting the software version number of the latest installed vehicle control software from the vehicle-side system of the target vehicle through a periodic synchronization task of the OTA platform.

[0007] In some embodiments of this application, based on the foregoing scheme, the step of converting the execution command into a remote control signal that matches the vehicle control interaction protocol and the target software version number based on a pre-configured function strategy table includes: searching the function strategy table for at least one vehicle control interaction protocol that matches the target vehicle function; determining the target vehicle control interaction protocol bound to the target software version number from the at least one vehicle control interaction protocol; and converting the execution command into a remote control signal based on the target vehicle control interaction protocol.

[0008] In some embodiments of this application, based on the foregoing scheme, after sending the remote control signal to the target vehicle, the method further includes: receiving execution feedback information of the target vehicle function reported by the target vehicle, the feedback information including at least the function execution result; determining, based on the execution feedback information, whether there is an anomaly in the binding between the target software version number and the target vehicle control interaction protocol; if there is an anomaly in the binding, updating the vehicle control interaction protocol bound to the target software version number in the function strategy table.

[0009] In some embodiments of this application, based on the foregoing scheme, the method further includes: if there is no vehicle control interaction protocol bound to the target software version number in the at least one vehicle control interaction protocol, then generating a prompt message to upgrade the vehicle control software version in the target vehicle; and triggering the vehicle control application to display the prompt message.

[0010] In some embodiments of this application, based on the foregoing scheme, the function strategy table is further used to record the correspondence between different vehicle models and different vehicle function configurations. The method further includes: obtaining the target vehicle model of the target vehicle; determining the target vehicle function configuration that matches the target vehicle model based on the function strategy table; triggering the vehicle control application to display the target vehicle function configuration, and / or triggering the vehicle control application to hide vehicle function configurations other than the target vehicle function configuration.

[0011] In some embodiments of this application, based on the foregoing scheme, the method is executed in the cloud, and the method further includes: sending the prompt information to the corresponding vehicle control application terminal to trigger the vehicle control application terminal to display the prompt information; and / or sending the target vehicle function configuration to the corresponding vehicle control application terminal to trigger the vehicle control application terminal to display the target vehicle function configuration.

[0012] In some embodiments of this application, based on the foregoing scheme, after the target vehicle function configuration is sent to the corresponding vehicle control application, the method further includes: calculating the execution success rate of the vehicle functions in the target vehicle function configuration in vehicles with the target vehicle model; if the execution success rate is greater than or equal to a preset threshold, then sending the target vehicle function configuration to all vehicle control applications bound to the target vehicle model; if the execution success rate is less than the preset threshold, then prohibiting the sending of the target vehicle function configuration to all vehicle control applications bound to the target vehicle model.

[0013] In some embodiments of this application, based on the foregoing scheme, the method is executed on the vehicle control application terminal, and the method further includes: before converting the execution command into a remote control signal that matches the vehicle control interaction protocol and the target software version number based on a pre-configured function strategy table, obtaining the function strategy table issued by the cloud.

[0014] According to one aspect of the embodiments of this application, a vehicle remote control device is provided. The device includes: a first acquisition unit, configured to acquire an execution command triggered by a user on a vehicle control application terminal for a target vehicle function; a second acquisition unit, configured to acquire the software version number of vehicle control software installed on the target vehicle, as the target software version number, wherein the target vehicle is a vehicle to execute the target vehicle function; a conversion unit, configured to convert the execution command into a remote control signal that matches the vehicle control interaction protocol and the target software version number based on a pre-configured function strategy table, wherein the function strategy table is used to record the correspondence between different software version numbers and different vehicle control interaction protocols; and a sending unit, configured to send the remote control signal to the target vehicle to control the target vehicle to execute the target vehicle function.

[0015] According to one aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods described in the above embodiments.

[0016] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, on which a computer program is stored, which, when executed by a processor, implements the method described in the above embodiments.

[0017] According to one aspect of the embodiments of this application, an electronic device is provided, including: one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to perform the method described in the above embodiments.

[0018] Based on the technical solution proposed in this application, the compatibility between the vehicle control application and the vehicle control software can be improved to a certain extent. Specifically, by establishing a correspondence between the software version number and the vehicle control interaction protocol through a function strategy table, there is no need to add complex cross-version compatibility logic to the vehicle control application or vehicle control software, nor is there any need to modify the code of the old version of the vehicle control software or vehicle control application that is already running stably. Multi-version adaptation can be achieved simply by configuring the function strategy table, which simplifies the program structure, reduces the difficulty of code development and maintenance, effectively avoids the risk of conflicts between new and old functions, and ensures the stability of system operation. At the same time, the executed command will accurately match the corresponding vehicle control interaction protocol according to the target software version number, avoiding the problem of function execution failure due to protocol mismatch, improving the accuracy and reliability of vehicle remote control, and the entire adaptation process is completed automatically without manual user intervention, improving the user experience, especially suitable for batch adaptation scenarios after large-scale vehicle OTA upgrades.

[0019] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0020] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort. In the drawings: Figure 1 A schematic diagram of a scenario for remote vehicle control according to an embodiment of this application is shown; Figure 2 A flowchart of a vehicle remote control method according to an embodiment of this application is shown; Figure 3 A schematic diagram of a scenario for remote vehicle control according to an embodiment of this application is shown; Figure 4A schematic diagram of a scenario for remote vehicle control according to an embodiment of this application is shown; Figure 5 A block diagram of a vehicle remote control device according to an embodiment of this application is shown; Figure 6 A schematic diagram of the structure of a computer system suitable for implementing the electronic device of the present application is shown. Detailed Implementation

[0021] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided to make this application more comprehensive and complete, and to fully convey the concept of the exemplary embodiments to those skilled in the art.

[0022] Furthermore, the described features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. Numerous specific details are provided in the following description to give a thorough understanding of embodiments of this application. However, those skilled in the art will recognize that the technical solutions of this application can be practiced without one or more of the specific details, or other methods, components, apparatuses, steps, etc., can be employed. In other instances, well-known methods, apparatuses, implementations, or operations are not shown or described in detail to avoid obscuring various aspects of this application.

[0023] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0024] The flowchart shown in the attached diagram is for illustrative purposes only and does not necessarily include all content and operations / steps, nor does it necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined. Therefore, the actual execution order may change depending on the actual situation.

[0025] It should be noted that "multiple" in this article refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0026] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such uses of these terms can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described.

[0027] With the rapid development of the new energy vehicle industry, users' demands for remote vehicle control functions are becoming increasingly diversified, and the vehicle control functions supported by vehicle control applications (such as mobile apps) are also increasing and becoming more complex. The realization of these vehicle control functions depends heavily on the precise coordination between the vehicle control application and the vehicle control software (vehicle-side controller software) in terms of protocols, signal transmission, and action timing.

[0028] Figure 1 A schematic diagram of a vehicle remote control scenario according to an embodiment of this application is shown.

[0029] like Figure 1 As shown, to meet the ever-changing needs of users and optimize the product experience, after vehicle 102 is launched to the market, manufacturers typically use the cloud-based OTA (Over-The-Air) platform 100 to optimize, iterate, or add new functions to the vehicle control software installed on vehicle 102. However, there are two core problems in the OTA platform upgrade process, making it difficult for the vehicle control application terminal 101 and the vehicle control software to achieve efficient adaptation: On the one hand, due to differences in user habits, network environment, etc., it cannot be guaranteed that all deployed vehicles 102 can complete the vehicle control software upgrade in a timely manner, requiring the vehicle control application terminal 101 to deal with multiple different versions of vehicle control software simultaneously; on the other hand, the upgrade times of different vehicles 102 are inconsistent, making it difficult for the vehicle control application terminal 101 to accurately predict the adaptation time of new software functions, thus affecting the user experience of the new functions.

[0030] Currently, the common solution in the industry is to pre-define compatibility logic for older versions of vehicle control software when developing new versions. This involves identifying different versions of the vehicle control software and designing corresponding processing code to achieve cross-version functional adaptation. However, this solution has significant drawbacks: adding compatibility logic to existing stable code not only increases the complexity of the program structure but also easily leads to conflicts between new and old functions, significantly increasing the risk of overall functional failure and seriously affecting the reliability of vehicle remote control. Therefore, this application proposes a vehicle remote control solution to efficiently improve the compatibility between the vehicle control application and the vehicle control software.

[0031] The implementation details of the technical solutions in the embodiments of this application are described below: See Figure 2The diagram shows a flowchart of a vehicle remote control method according to an embodiment of the present application, the method being executed by a computing device with computing capabilities.

[0032] like Figure 2 As shown, the vehicle remote control method includes at least steps 210 to 240, which are described in detail below: Step 210: Obtain the execution command for the target vehicle function triggered by the user on the vehicle control application.

[0033] Step 220: Obtain the software version number of the vehicle control software installed on the target vehicle, and use it as the target software version number. The target vehicle is the vehicle to be executed with the target vehicle function.

[0034] Step 230: Based on the pre-configured function strategy table, the execution command is converted into a remote control signal that matches the vehicle control interaction protocol and the target software version number. The function strategy table is used to record the correspondence between different software version numbers and different vehicle control interaction protocols.

[0035] Step 240: Send the remote control signal to the target vehicle to control the target vehicle to perform the target vehicle function.

[0036] In this application, the vehicle control application (such as a mobile app) can provide users with a visual interface for operating vehicle functions. The interface includes various remotely controllable vehicle function options such as vehicle unlocking, air conditioning start, window raising and lowering, and charging control. When a user needs to remotely control a target vehicle, they can trigger an execution command for that target vehicle function by clicking the corresponding function option on the interface. The vehicle control application or cloud captures the execution command in real time and records the target vehicle function type corresponding to the command.

[0037] In this application, the target vehicle is pre-installed with vehicle control software at the factory, and the vehicle control software may also be updated after the target vehicle leaves the factory. The vehicle control software has a version identifier (i.e., software version number), and the version number of the vehicle control software currently installed on the target vehicle can be obtained through a preset information acquisition channel and defined as the target software version number. The target vehicle is the vehicle whose function is to be triggered by the user, and it can be located through unique identifiers such as the vehicle identification number (VIN).

[0038] Next, a pre-configured function strategy table can be invoked. This function strategy table can be a structured data table pre-configured in the cloud or on the vehicle control application. Its core function is to establish a one-to-one or many-to-many correspondence between different software version numbers and different vehicle control interaction protocols. That is, a certain software version number can be matched with a specific vehicle control interaction protocol to implement the corresponding vehicle function.

[0039] In this application, based on the acquired target vehicle functions and target software version number, a matching vehicle control interaction protocol can be queried in the function strategy table. Following the format requirements of this protocol, user-triggered execution commands are converted into remote control signals. These remote control signals meet the parsing requirements of the vehicle control software corresponding to the target software version number, ensuring that the vehicle control software can accurately identify the meaning of the signals.

[0040] Finally, the converted remote control signal can be sent to the vehicle-side system (such as the T-BOX controller) of the target vehicle via a wireless communication network (such as 4G, 5G, vehicle-to-everything). After receiving the signal, the vehicle-side system transmits it to the corresponding vehicle control software, which then drives the relevant hardware modules of the vehicle (such as the air conditioning controller, door lock controller, etc.) to execute the target vehicle functions required by the user.

[0041] To enable those skilled in the art to better understand this application, a specific embodiment will be described below.

[0042] In one specific embodiment, assume that a user triggers a remote start command for the air conditioning via a mobile vehicle control app (vehicle control application), and the target vehicle is a new energy vehicle of model A with vehicle control software version V2.3. The pre-configured function strategy table records the corresponding relationships shown in Table 1 below: Table 1 Functional Strategy Table 1

[0043] First, the vehicle control app receives the remote air conditioning start command triggered by the user and sends it to the TSP platform in the cloud. Then, the TSP platform interacts with the OTA platform to obtain the target vehicle's vehicle control software version number, which is V2.3 (i.e., the target software version number). Next, it searches the function policy table for the vehicle control interaction protocol corresponding to the remote air conditioning start function, determining that the protocol bound to version V2.3 is P3. Finally, according to the rules of protocol P3, the remote air conditioning start command is converted into a corresponding remote control signal (such as a signal encoded as "0x120x340x56") and sent to the target vehicle. Upon receiving the signal, the vehicle executes the air conditioning start operation.

[0044] Based on the technical solution proposed in this application, the compatibility between the vehicle control application and the vehicle control software can be improved to a certain extent. Specifically, by establishing a correspondence between the software version number and the vehicle control interaction protocol through a function strategy table, there is no need to add complex cross-version compatibility logic to the vehicle control application or vehicle control software, nor is there any need to modify the code of the old version of the vehicle control software or vehicle control application that is already running stably. Multi-version adaptation can be achieved simply by configuring the function strategy table, which simplifies the program structure, reduces the difficulty of code development and maintenance, effectively avoids the risk of conflicts between new and old functions, and ensures the stability of system operation. At the same time, the executed command will accurately match the corresponding vehicle control interaction protocol according to the target software version number, avoiding the problem of function execution failure due to protocol mismatch, improving the accuracy and reliability of vehicle remote control, and the entire adaptation process is completed automatically without manual user intervention, improving the user experience, especially suitable for batch adaptation scenarios after large-scale vehicle OTA upgrades.

[0045] Next, this application will provide a more detailed explanation of the various technical details in the above-mentioned vehicle remote control solution.

[0046] In step 220 above, obtaining the software version number of the vehicle control software installed on the target vehicle can be performed according to the following steps 221 and / or 222: Step 221: Receive the software version number actively reported by the target vehicle through the OTA platform.

[0047] In this application, after the target vehicle's vehicle control software completes an OTA upgrade, it can automatically trigger a version number reporting logic. This involves sending the updated software version number to the OTA platform in the cloud via the wireless communication module of the vehicle-side system (such as a T-BOX terminal). Furthermore, if the vehicle has not undergone an upgrade, but the vehicle control software detects an abnormal change in its version information (such as a version identifier being corrupted due to accidental operation and subsequently repaired), it can also proactively report the current software version number to the OTA platform. Upon receiving this version number, the OTA platform stores it in its database and synchronizes it to the vehicle control application or the TSP platform in the cloud for subsequent use in matching vehicle control interaction protocols.

[0048] Step 222: Through the OTA platform's periodic synchronization task, request the latest software version number of the vehicle control software installed on the target vehicle's on-board system.

[0049] In this application, periodic synchronization tasks can be pre-configured in the OTA platform, with a set task execution cycle (e.g., 12 hours / time, 24 hours / time, adjustable according to actual needs). At the task execution time, the OTA platform sends a version number request command to the target vehicle's on-board system via the vehicle network. This command contains the target vehicle's unique identifier (e.g., VIN) for the on-board system to confirm the request object. After receiving the request command, the target vehicle's on-board system reads the version number of the currently installed vehicle control software and feeds it back to the OTA platform via the wireless communication network. After receiving the feedback information, the OTA platform updates the software version number corresponding to the target vehicle in its database and synchronizes it to the vehicle control application terminal or the TSP platform in the cloud for subsequent matching of vehicle control interaction protocols.

[0050] In this application, the two methods for obtaining the software version number can be used individually or in combination: for example, the active reporting mode is the main method, and the periodic request mode is the auxiliary method. When the OTA platform does not receive the active reporting information of the target vehicle within a preset time, the periodic request task is automatically triggered to further ensure the timeliness of the version number information.

[0051] Based on the aforementioned software version number acquisition scheme, the proactive reporting mode can obtain the latest version number as soon as the vehicle control software version changes, ensuring the real-time nature of version information and avoiding adaptation errors caused by version update delays. The periodic request mode can compensate for the shortcomings of the proactive reporting mode, such as scenarios where proactive reporting fails due to vehicle network anomalies or when users disable the reporting function. Periodic requests ensure the accuracy and completeness of version number information, reducing the risk of missing information. The two methods can be flexibly combined to adjust the execution logic according to actual application scenarios, balancing real-time performance and reliability. This provides solid data support for the accurate matching of subsequent execution commands and vehicle control interaction protocols. Furthermore, the entire version number acquisition process is implemented through the OTA platform, eliminating the need for manual user operation and improving the system's automation level and user experience.

[0052] In step 230 above, the conversion of the execution command into a remote control signal that matches the vehicle control interaction protocol and the target software version number based on the pre-configured function strategy table can be performed according to the following steps 231 to 233: Step 231: Search the function strategy table for at least one vehicle control interaction protocol that matches the function of the target vehicle.

[0053] Step 232: Determine the target vehicle control interaction protocol that is bound to the target software version number among the at least one vehicle control interaction protocol.

[0054] Step 233: Based on the target vehicle control interaction protocol, convert the execution command into a remote control signal.

[0055] In this application, the function strategy table not only records the correspondence between software version numbers and vehicle control interaction protocols, but also associates the correspondence between vehicle functions and vehicle control interaction protocols. That is, the same vehicle function may correspond to multiple different vehicle control interaction protocols (each of which should be adapted to a different software version number). First, based on the target vehicle function triggered by the user (such as "window lifting"), the function strategy table is searched to filter out all vehicle control interaction protocols associated with the target vehicle function, forming a protocol set corresponding to that function (containing at least one vehicle control interaction protocol).

[0056] Within the selected protocol set, further searches can be conducted based on the acquired target software version number to identify the vehicle control interaction protocol bound to that version number. The function strategy table clearly indicates the range or specific version number of the software version number it is compatible with for each vehicle control interaction protocol. For example, protocol "Protocol_B-002" is compatible with versions V2.0-V2.3, and protocol "Protocol_B-004" is compatible with versions V2.4 and above. By comparing version numbers, a uniquely matching target vehicle control interaction protocol can be determined. If multiple protocols are compatible with the same version number (such as a step-by-step execution protocol for complex functions), the target protocol can be selected according to the preset priority order in the function strategy table.

[0057] After determining the target vehicle control interaction protocol, the user-triggered execution commands can be converted according to the data format, encoding rules, signal field definitions, and other requirements specified in the protocol. The execution commands can be in a user-understandable natural language format (such as "lower the window to 50% opening") or a logical instruction format within the app. In this application, they can be converted into binary or hexadecimal signals that the vehicle control software can parse, ensuring that the signals contain the execution parameters of the target vehicle function (such as window opening, execution time, etc.), ultimately forming a remote control signal.

[0058] To enable those skilled in the art to better understand this application, a specific embodiment will be described below.

[0059] In a specific embodiment, assuming a user triggers a "remotely unlock car door" command through the vehicle control application, the target vehicle's VIN is "JTEBU52KX0007890", and its vehicle control software version number is V4.2 (target software version number). Some records in the pre-configured function strategy table are shown in Table 2 below: Table 2 Functional Strategy Table 1

[0060] First, based on the target vehicle function "remote door unlocking," the matching vehicle control interaction protocols (Q1, Q2, and Q3) can be filtered from the function policy table. Then, among protocols Q1, Q2, and Q3, the protocol bound to the target software version V4.2 can be found, confirming that the target vehicle control interaction protocol is Q3. Finally, the "remote door unlocking" execution command can be converted into a remote control signal according to the signal format specified by protocol Q3 (e.g., "command header + function code + checksum"). Assuming the signal format required by protocol Q3 is "0x780x010x9A," the converted remote control signal will be this code.

[0061] Based on the technical solutions in steps 231 to 233 above, the step-by-step logic of function matching, version binding, and signal conversion ensures that each step has a clear basis, avoiding the blindness of protocol matching and improving the accuracy of remote control signals. Furthermore, the same vehicle function corresponds to multiple vehicle control interaction protocols adapted to different versions, enabling the vehicle control application to flexibly cope with multiple versions of vehicle control software without modifying the core code. This enhances the scalability and compatibility of remote control. Simultaneously, the protocol filtering and binding process is automated, resulting in high efficiency and rapid response to user remote control requests, reducing signal conversion delays. Moreover, the function strategy table pre-sets protocol adaptation ranges and priorities, providing clear rules for protocol matching, reducing errors that may result from human intervention, and ensuring the stability of vehicle function execution.

[0062] In this application, as Figure 2 After step 240, i.e., after sending the remote control signal to the target vehicle, steps 251 to 253 can also be performed: Step 251: Receive the execution feedback information of the target vehicle function reported by the target vehicle, the feedback information including at least the function execution result.

[0063] Step 252: Based on the execution feedback information, determine whether there is an anomaly in the binding between the target software version number and the target vehicle control interaction protocol.

[0064] Step 253: If there is an anomaly in the binding, update the vehicle control interaction protocol bound to the target software version number in the function strategy table.

[0065] In this application, after the remote control signal is sent to the target vehicle, the vehicle control software executes the corresponding vehicle function, and can provide feedback information upon completion (or in case of an exception during execution). This feedback information includes at least the function execution result (e.g., "execution successful" or "execution failed"), and may also include auxiliary information such as execution time and exception cause code (e.g., "protocol parsing failed" or "hardware failure"). The vehicle-side system reports this feedback information to the cloud or vehicle control application terminal via a wireless communication network, and the cloud or vehicle control application terminal receives and stores this feedback information in real time.

[0066] In this application, anomaly detection rules can be preset to verify the binding relationship between the target software version number and the target vehicle control interaction protocol based on the received execution feedback information. The specific detection logic can be: If the function execution result in the feedback information is "execution successful," then the binding is considered normal. If the execution result is "execution failed," and the exception reason code points to protocol-related issues such as "protocol parsing failure" or "signal incompatibility," then the binding is considered abnormal. If the reason for the execution failure is due to non-protocol factors such as hardware failure (e.g., damaged window motor) or vehicle status restrictions (e.g., prohibiting window lowering while the vehicle is in motion), then the binding is considered normal, and the execution failure is unrelated to protocol binding.

[0067] In this application, if an anomaly is detected in the binding, it may be due to an error by the technician when maintaining the function strategy table, resulting in a mismatch between the binding relationship between the software version number and the vehicle control interaction protocol. In this case, the technician can be notified to update the function strategy table, or the automatic update process of the function strategy table can be initiated. In the automatic update process of the function strategy table, firstly, other vehicle control interaction protocols associated with the target vehicle function and the target software version number can be found in the function strategy table. Then, according to the preset priority order, the next compatible vehicle control interaction protocol is selected, re-bound to the target software version number, and the corresponding record in the function strategy table is updated. If there are no other compatible protocols in the protocol set, an anomaly alarm message is generated, notifying the technician to optimize the protocol or add a new compatible protocol.

[0068] For example, in a specific embodiment, assuming the target vehicle's vehicle control software version is V2.6, and the user triggers the "remotely open the trunk" command, according to the function policy table, the vehicle control interaction protocol bound to version V2.6 and the "remotely open the trunk" function is P7. Therefore, the execution command can be converted into a remote control signal and sent to the vehicle according to protocol P7. After receiving the signal, the vehicle attempts to execute the trunk opening operation, but due to the compatibility issue between protocol P7 and the V2.6 version of the vehicle control software, the operation fails. The vehicle reports execution feedback information to the vehicle control application or cloud, including "VIN: LSG9H83K4MF123456; Function: Remotely open the trunk. Execution result: Failure. Reason for failure: Protocol incompatibility." After receiving this feedback information, the vehicle control application or cloud can first check the network status (confirming normal signal transmission) and the vehicle hardware status (confirming that the trunk lock is not faulty). After ruling out the above factors, it is determined that there is an anomaly in the binding between version V2.6 and protocol P7. Subsequently, the vehicle control application or cloud automatically searches the function policy table for the alternative protocol (preset in the policy table) for the "remotely open trunk" function corresponding to version V2.6. Finding that the alternative protocol is "P7", the application updates the protocol corresponding to this function from "P7". After the update, when other vehicles of the same version trigger this function, the vehicle control application or cloud will switch the control signal according to protocol "P7" to ensure successful execution.

[0069] Based on the technical solutions in steps 251 to 253 above, by introducing an execution feedback closed-loop mechanism, protocol binding anomalies can be detected in a timely manner, preventing abnormal binding relationships from continuously affecting function execution. This enhances the self-correction capability of the vehicle control system. Simultaneously, the protocol binding relationships in the function strategy table are dynamically updated, allowing the function strategy table to be continuously optimized based on actual application conditions, resulting in continuously improving adaptation accuracy. This is particularly suitable for scenarios with frequent iterations of vehicle control software versions. Furthermore, the anomaly judgment rules are clear, only updating bindings for protocol-related execution failures, avoiding erroneous updates due to non-protocol factors, and ensuring the stability of the function strategy table. The entire process eliminates the need for technicians to manually troubleshoot protocol binding issues; the vehicle control system automatically completes anomaly detection and updates, reducing maintenance costs and improving the operational efficiency of the vehicle control system.

[0070] In this application, steps 234 to 235 may also be performed: Step 234: If there is no vehicle control interaction protocol bound to the target software version number in the at least one vehicle control interaction protocol, then generate a prompt message to upgrade the vehicle control software version in the target vehicle.

[0071] Step 235: The vehicle control application is triggered to display the prompt information.

[0072] In step 232 above, after searching the function strategy table for a set of protocols matching the target vehicle's functions, a further search is conducted to determine if any vehicle control interaction protocols bound to the target software version number exist within that set. If the search result is empty (i.e., none of the vehicle control interaction protocols in the set are compatible with the target software version number), it is determined that no vehicle control interaction protocol is bound to the target software version number. This situation is largely due to the target software version number being too low, meaning the vehicle control software corresponding to the target software version number does not support the target vehicle in executing the target vehicle's functions.

[0073] In the above situation, a prompt message can be generated based on a preset prompt message template. The prompt message may include the name of the target vehicle function, the reason why the function cannot be executed (the current vehicle control software version does not have an compatible protocol), and suggested operation (upgrade the vehicle control software version). It may also include auxiliary information such as the recommended upgrade version number and upgrade instructions to ensure that the user can clearly understand and perform the operation.

[0074] Finally, the generated prompt message can be sent to the corresponding vehicle control application, triggering the application's display function. Display methods may include pop-up notifications, message center notifications, and labels next to function buttons, ensuring users see the prompt message promptly. Simultaneously, the priority of the prompt message can be set to ensure it is not obscured by other irrelevant information.

[0075] For example, in a specific implementation, a user triggers the "remote charging reservation" function through the vehicle control application. The target vehicle's vehicle control software version is V3.2. The function policy table filters out the vehicle control interaction protocols corresponding to the "remote charging reservation" function as protocols R1 and R2. Protocol R1 is bound to version V3.3, and protocol R2 is bound to version V3.4. No protocol bound to version V3.2 is found. At this point, a prompt message can be generated: "The current vehicle control software version (V3.2) does not support the remote charging reservation function. It is recommended to upgrade to version V3.3 or above to use this function." Subsequently, the vehicle control application can be triggered to display this prompt message in a pop-up window.

[0076] Based on the technical solutions in steps 234 to 235 above, a clear processing solution is provided for scenarios without an adapted protocol, avoiding no response or only vague prompts after the user triggers the function. This can improve the user experience and the interactivity of the system. The prompt message will clearly inform the user of the reason why the function is unavailable and the solution, guiding the user to upgrade the vehicle control software. This not only helps the user to use the target function normally, but also promotes the iterative update of the vehicle control software version and reduces the complexity of multi-version adaptation.

[0077] In this application, the function strategy table can also be used to record the correspondence between different vehicle models and different vehicle function configurations.

[0078] Furthermore, in this application, steps 261 to 263 may also be performed: Step 261: Obtain the target vehicle model.

[0079] Step 262: Based on the function strategy table, determine the target vehicle function configuration that matches the target vehicle model.

[0080] Step 263: Trigger the vehicle control application to display the target vehicle function configuration, and / or trigger the vehicle control application to hide vehicle function configurations other than the target vehicle function configuration.

[0081] In this application, in addition to recording the correspondence between software version number and vehicle control interaction protocol, the function strategy table can also record the correspondence between vehicle model and vehicle function configuration, ensuring that the vehicle control application only displays functions supported by the target vehicle and avoids users triggering unsupported functions.

[0082] In this application, the vehicle model is a core attribute of the vehicle, which can be stored in the configuration file of the vehicle-side system and synchronized to the OTA platform in the cloud during vehicle registration. The vehicle application or cloud can obtain the target vehicle model in two ways: first, by synchronously obtaining it from the OTA platform or vehicle-side system when obtaining the target software version number; second, by directly retrieving it from the APP database when the user binds the vehicle to the vehicle control application, since the vehicle model information has already been entered.

[0083] In this application, due to differences in hardware configuration and factory settings, different vehicle models may support different vehicle functions (e.g., low-end models do not have seat heating, while high-end models support automatic parking). Therefore, based on the obtained target vehicle model, the matching vehicle function configuration can be retrieved from the function strategy table. This configuration is a set of all supported vehicle functions preset for that vehicle model, and is defined as the target vehicle function configuration.

[0084] After determining the target vehicle's functional configuration, the function display control logic of the vehicle control APP (vehicle control application terminal) can be triggered. There are two control methods: First, display control, where the vehicle control APP only displays the functions in the target vehicle's functional configuration on the function operation interface (e.g., displaying "automatic parking" and "seat heating" functions on high-end models). Second, hiding control, where the vehicle control APP hides all functions except those in the target vehicle's functional configuration (e.g., hiding the "automatic parking" function button on low-end models). These two control methods can be used individually or in combination (i.e., simultaneously displaying the target functional configuration and hiding non-target functional configurations) to ensure that the vehicle control APP interface only displays functions supported by the target vehicle.

[0085] For example, in a specific embodiment, the function strategy table records the correspondence between vehicle models and function configurations as shown in Table 3 below: Table 3 Functional Strategies

[0086] Assuming the user's target vehicle model is Vehicle Model 1, after the user logs into the vehicle control APP, the APP first reads the model information entered when the user bound the vehicle from the APP database to confirm that the target vehicle model is Vehicle Model 1. Then, it searches the function policy table for the corresponding vehicle function configuration and determines that the target vehicle function configuration is vehicle unlock, air conditioning start, and window lift. Subsequently, the display control logic of the vehicle control APP can be triggered. The vehicle control APP only displays these three functions in the target vehicle function configuration on the function operation interface, while hiding the function buttons for seat heating and ventilation and automatic parking, which are not target function configurations. The user cannot see these hidden functions in the vehicle control APP interface to avoid accidentally triggering unusable vehicle functions.

[0087] Based on the technical solutions in steps 261 to 263 above, the function strategy table records the correspondence between vehicle models and function configurations, enabling personalized display of functions based on vehicle models. This makes the vehicle control APP interface more closely match the actual vehicle configuration, improving user experience. Simultaneously, it can hide functions not supported by the vehicle, preventing users from accidentally triggering unavailable functions, reducing invalid operations and user confusion, and lowering resource consumption caused by the vehicle control system processing invalid requests. Furthermore, it eliminates the need to develop separate vehicle control APP versions for different vehicle models; multi-model adaptation can be achieved simply through the function strategy table configuration, reducing development and maintenance costs and enhancing the versatility of the vehicle control system. In addition, the function configuration display control logic is simple and efficient, without affecting the running speed of the vehicle control APP, ensuring users can quickly find the required functions and improving operational efficiency.

[0088] In one embodiment of this application, the vehicle remote control method proposed herein can be executed in the cloud.

[0089] See Figure 3 This illustration shows a scenario diagram of remote vehicle control according to an embodiment of this application. Figure 3 As shown, the function strategy table 103 can be stored in the cloud 100. Therefore, all execution steps of the vehicle remote control method (including command acquisition, target software version number acquisition, protocol matching, feedback processing, sending remote control signals to the target vehicle 102A, function configuration determination, etc.) are executed in the cloud (such as the TSP platform). The vehicle control application terminal 101A is only responsible for receiving user operations, displaying relevant information and functions, and transmitting execution commands and remote control signals. It does not need to undertake complex logic processing, which reduces the performance requirements of the vehicle control application terminal.

[0090] Furthermore, this embodiment may also perform the following steps 2351 and / or 2631: Step 2351: Send the prompt information to the corresponding vehicle control application terminal to trigger the vehicle control application terminal to display the prompt information.

[0091] In this step, after the cloud generates the upgrade prompt, it can associate the target vehicle's unique identifier (such as the VIN) with the corresponding vehicle control application account (the account the user uses to log in to the APP). The prompt is then sent to the vehicle control application logged into by that account via a communication channel between the cloud and the APP (such as HTTP / HTTPS protocol or WebSocket protocol). Upon receiving the prompt, the APP triggers its display according to a preset method (pop-up window, message notification, etc.).

[0092] Step 2631: Send the target vehicle function configuration to the corresponding vehicle control application terminal to trigger the vehicle control application terminal to display the target vehicle function configuration.

[0093] In this step, after the cloud determines the target vehicle's function configuration, it can associate the corresponding vehicle control application account with the target vehicle's unique identifier and send the target vehicle's function configuration to the vehicle control application in the form of structured data (such as JSON format). After receiving the configuration data, the APP parses it and triggers the function display control logic to display the target function configuration and hide the non-target function configuration.

[0094] In this application, after step 1631 above, that is, after the target vehicle function configuration is sent to the corresponding vehicle control application terminal, the following steps 2632 to 2634 can also be performed: Step 2632: Calculate the success rate of the execution of vehicle functions in the target vehicle function configuration in vehicles with the target vehicle model.

[0095] Step 2633: If the execution success rate is greater than or equal to a preset threshold, then the target vehicle function configuration is sent to all vehicle control application terminals bound to the target vehicle model.

[0096] Step 2634: If the execution success rate is less than the preset threshold, then the distribution of the target vehicle function configuration to all vehicle control application terminals bound to the target vehicle model is prohibited.

[0097] In this application, after the cloud distributes the target vehicle's function configuration to some vehicle control applications (such as the first batch of users or test users of this vehicle model), it can initiate a success rate statistics task. The statistical object can be each vehicle function in the target vehicle's function configuration, and the statistical scope includes all vehicles with the same model as the target vehicle. The statistical period can be preset (e.g., 7 days, 15 days), and the statistical indicator is the success rate = (number of successful function executions / total number of function triggers) × 100%. For example, if the target vehicle model is vehicle model 2, and the target vehicle's function configuration includes the "automatic parking" function, with a statistical period of 7 days, and within 7 days, 1000 users of this model trigger the "automatic parking" function, with 950 successful executions and 50 failures, then the success rate of the "automatic parking" function is 95%.

[0098] Furthermore, a success rate threshold can be preset in the cloud (e.g., 90%, which can be adjusted according to the importance of the function and user experience requirements; the threshold for core functions can be set to above 95%, and the threshold for non-core functions can be set to above 85%). After the statistical period ends, the success rate of each function can be compared with the preset threshold to determine whether the conditions for distribution are met.

[0099] Afterwards, different distribution strategies can be implemented based on the comparison results. If the execution success rate of all functions in the target vehicle's function configuration is greater than or equal to the preset threshold, the function configuration is determined to be stable and reliable. The cloud can then distribute the target vehicle's function configuration to all vehicle control applications bound to the target vehicle model (including users who have already received the configuration and those who have not), ensuring that all users of this model can use the relevant functions. If the execution success rate of at least one function in the target vehicle's function configuration is less than the preset threshold, the function configuration is determined to have reliability issues (such as incomplete protocol adaptation or functional logic defects). The cloud can then prohibit the distribution to vehicle control applications that have not received the configuration and suspend the provision of the function to users who have already received it (a pop-up notification can be sent via the app indicating that the function is temporarily unavailable). At the same time, technical personnel will be notified to investigate the problem and optimize the function configuration.

[0100] Based on the technical solutions in steps 2632 to 2634 above, the reliability of the function configuration is verified by executing success rate statistics. This avoids the distribution of defective function configurations to a large number of users, reduces user complaints and poor experiences, protects product reputation, and allows the preset threshold to be flexibly adjusted according to the importance of the function. This balances the stability of core functions with the iteration efficiency of non-core functions, enhances the practicality of vehicle functions, and prohibits the distribution of low success rate function configurations. This reduces invalid function triggering and execution failures, lowers resource consumption in the cloud and vehicle systems, improves the overall system operating efficiency, and can also promptly identify problems in function configurations and trigger optimization processes, promoting continuous iteration and improvement of functions, and enhancing product competitiveness and user satisfaction.

[0101] In one embodiment of this application, the vehicle remote control method proposed in this application can also be executed on the vehicle control application terminal (such as a mobile APP).

[0102] See Figure 4 This illustration shows a scenario diagram of remote vehicle control according to an embodiment of this application. Figure 4 As shown, the function strategy table 104 can be stored in the vehicle control application terminal 101B. Therefore, all execution steps of the vehicle remote control method (including command acquisition, target software version number acquisition, protocol matching, feedback processing, sending remote control signals to the target vehicle 102B, function configuration determination, etc.) are executed locally on the vehicle control application terminal 101B. The cloud 100 is only responsible for maintaining and distributing the function strategy table and does not participate in the specific logic processing.

[0103] Furthermore, this embodiment may also perform the following step 201: Step 201: Before converting the execution command into a remote control signal that matches the vehicle control interaction protocol and the target software version number based on the pre-configured function strategy table, obtain the function strategy table issued by the cloud.

[0104] Specifically, the vehicle control application can retrieve the function strategy table upon startup, user login, or periodic (e.g., every 24 hours) automatic updates. After retrieving the function strategy table, the application can store it locally and directly call the locally stored table when performing subsequent signal conversions. If retrieval fails (e.g., due to network failure), the application can use the previously cached function strategy table and prompt the user with "Function strategy table update failed; some functions may not function properly."

[0105] In this embodiment, the proposed vehicle remote control method is executed locally on the vehicle control application terminal. Protocol matching and signal conversion do not rely on real-time cloud computing, which can reduce the requirements for the network environment. It can be executed normally even in scenarios with unstable network or no network (the policy table has been obtained in advance), thus improving the robustness of vehicle remote control.

[0106] The following describes an embodiment of the apparatus described in this application, which can be used to execute the vehicle remote control method described in the above embodiments of this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the vehicle remote control method described in the above applications.

[0107] Figure 5 A block diagram of a vehicle remote control device according to an embodiment of this application is shown.

[0108] Reference Figure 5As shown, a vehicle remote control device 500 according to an embodiment of this application includes a first acquisition unit 501, a second acquisition unit 502, a conversion unit 503, and a sending unit 504.

[0109] The system comprises: a first acquisition unit 501, used to acquire execution commands for target vehicle functions triggered by the user on the vehicle control application terminal; a second acquisition unit 502, used to acquire the software version number of the vehicle control software installed on the target vehicle, which serves as the target software version number, and the target vehicle being the vehicle to execute the target vehicle function; a conversion unit 503, used to convert the execution commands into remote control signals that match the vehicle control interaction protocol and the target software version number based on a pre-configured function strategy table, wherein the function strategy table records the correspondence between different software version numbers and different vehicle control interaction protocols; and a sending unit 504, used to send the remote control signals to the target vehicle to control the target vehicle to execute the target vehicle function.

[0110] In some embodiments of this application, based on the foregoing scheme, the second acquisition unit 502 is configured to: receive the software version number actively reported by the target vehicle through the OTA platform; and / or, request the software version number of the latest installed vehicle control software from the vehicle-side system of the target vehicle through the periodic synchronization task of the OTA platform.

[0111] In some embodiments of this application, based on the foregoing scheme, the conversion unit 503 is configured to: search the function strategy table for at least one vehicle control interaction protocol that matches the function of the target vehicle; determine the target vehicle control interaction protocol bound to the target software version number from the at least one vehicle control interaction protocol; and convert the execution command into a remote control signal based on the target vehicle control interaction protocol.

[0112] In some embodiments of this application, based on the foregoing scheme, the device further includes: an update unit, configured to, after sending the remote control signal to the target vehicle, receive execution feedback information of the target vehicle function reported by the target vehicle, the feedback information including at least the function execution result; based on the execution feedback information, determine whether there is an anomaly in the binding between the target software version number and the target vehicle control interaction protocol; if there is an anomaly in the binding, update the vehicle control interaction protocol bound to the target software version number in the function strategy table.

[0113] In some embodiments of this application, based on the foregoing scheme, the device further includes: a first triggering unit, configured to generate a prompt message for upgrading the vehicle control software version in the target vehicle if there is no vehicle control interaction protocol bound to the target software version number in the at least one vehicle control interaction protocol; and trigger the vehicle control application terminal to display the prompt message.

[0114] In some embodiments of this application, based on the foregoing scheme, the function strategy table is further used to record the correspondence between different vehicle models and different vehicle function configurations. The device further includes: a second triggering unit, used to obtain the target vehicle model of the target vehicle; determine the target vehicle function configuration that matches the target vehicle model based on the function strategy table; trigger the vehicle control application to display the target vehicle function configuration, and / or trigger the vehicle control application to hide vehicle function configurations other than the target vehicle function configuration.

[0115] In some embodiments of this application, based on the foregoing scheme, the device is located in the cloud, and the first triggering unit is configured to: send the prompt information to the corresponding vehicle control application terminal to trigger the vehicle control application terminal to display the prompt information; and / or, the second triggering unit is configured to: send the target vehicle function configuration to the corresponding vehicle control application terminal to trigger the vehicle control application terminal to display the target vehicle function configuration.

[0116] In some embodiments of this application, based on the foregoing scheme, the device further includes: a statistics unit, configured to, after the target vehicle function configuration is sent to the corresponding vehicle control application terminal, calculate the execution success rate of the vehicle functions in the target vehicle function configuration in vehicles with the target vehicle model; if the execution success rate is greater than or equal to a preset threshold, then send the target vehicle function configuration to all vehicle control application terminals bound to the target vehicle model; if the execution success rate is less than the preset threshold, then prohibit sending the target vehicle function configuration to all vehicle control application terminals bound to the target vehicle model.

[0117] In some embodiments of this application, based on the foregoing scheme, the device is located on the vehicle control application terminal, and the device further includes: a third acquisition unit, used to acquire the function strategy table issued by the cloud before converting the execution command into a remote control signal that matches the vehicle control interaction protocol and the target software version number based on a pre-configured function strategy table.

[0118] As another embodiment of this application, a computer program product or computer program is also provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the methods described in the above embodiments.

[0119] As another embodiment of this application, a computer-readable storage medium is also provided. This computer-readable storage medium may be included in the electronic device described in the above embodiments; or it may exist independently and not assembled into the electronic device. The aforementioned computer-readable storage medium carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods described in the above embodiments.

[0120] Based on the same inventive concept, embodiments of this application also provide an electronic device. (Reference) Figure 6 The diagram illustrates a structural schematic of a computer system suitable for implementing an electronic device according to embodiments of the present application. The electronic device includes one or more memories 604, one or more processors 602, and at least one computer program (program code) stored in the memories 604 and executable on the processors 602. When the processors 602 execute the computer program, they implement the methods described above.

[0121] Among them, Figure 6 In this document, a bus architecture (represented by bus 600) is used. Bus 600 may include any number of interconnected buses and bridges, linking various circuits including one or more processors represented by processor 602 and memory represented by memory 604. Bus 600 may also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. Bus interface 605 provides an interface between bus 600 and receiver 601 and transmitter 603. Receiver 601 and transmitter 603 may be the same element, i.e., a transceiver, providing a unit for communicating with various other devices over a transmission medium. Processor 602 is responsible for managing bus 600 and general processing, while memory 604 can be used to store data used by processor 602 during operation.

[0122] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions or codes on or transmitted via a computer-readable medium. Other examples and embodiments are within the scope and spirit of this application and the appended claims. For example, due to the nature of software, the functions described above may be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Furthermore, the functional units may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit.

[0123] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0124] The units described as separate components may or may not be physically separate. Similarly, the components of the control device may or may not be physical units; they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment, depending on actual needs.

[0125] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium, including instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, read-only memory (ROM), random access memory (RAM), portable hard drives, magnetic disks, or optical disks.

[0126] The above description is merely an embodiment of this application and is not intended to limit this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for remote vehicle control, characterized in that, The method includes: Obtain the execution commands for the target vehicle function triggered by the user in the vehicle control application; Obtain the software version number of the vehicle control software installed on the target vehicle, and use it as the target software version number. The target vehicle is the vehicle to be executed with the target vehicle function. Based on a pre-configured function strategy table, the execution command is converted into a remote control signal that matches the vehicle control interaction protocol and the target software version number. The function strategy table is used to record the correspondence between different software version numbers and different vehicle control interaction protocols. The remote control signal is sent to the target vehicle to control the target vehicle to perform the target vehicle functions.

2. The method according to claim 1, characterized in that, The step of obtaining the software version number of the vehicle control software installed on the target vehicle includes: Receive the software version number actively reported by the target vehicle through the OTA platform; and / or, The OTA platform uses a periodic synchronization task to request the latest software version number of the vehicle control software installed on the target vehicle's on-board system.

3. The method according to claim 1, characterized in that, The method based on a pre-configured function strategy table converts the execution command into a remote control signal that matches the vehicle control interaction protocol and the target software version number, including: Find at least one vehicle control interaction protocol in the function strategy table that matches the target vehicle function; In the at least one vehicle control interaction protocol, a target vehicle control interaction protocol bound to the target software version number is determined; Based on the target vehicle control interaction protocol, the execution command is converted into a remote control signal.

4. The method according to claim 3, characterized in that, After sending the remote control signal to the target vehicle, the method further includes: Receive execution feedback information of the target vehicle function reported by the target vehicle, wherein the feedback information includes at least the function execution result; Based on the execution feedback information, determine whether there is an anomaly in the binding between the target software version number and the target vehicle control interaction protocol; If there is an anomaly in the binding, the vehicle control interaction protocol bound to the target software version number will be updated in the function strategy table.

5. The method according to claim 3, characterized in that, The method further includes: If none of the at least one vehicle control interaction protocol is bound to the target software version number, a prompt message for upgrading the vehicle control software version in the target vehicle is generated. The vehicle control application is triggered to display the prompt message.

6. The method according to claim 5, characterized in that, The function strategy table is also used to record the correspondence between different vehicle models and different vehicle function configurations, and the method further includes: Obtain the target vehicle model; Based on the aforementioned functional strategy table, determine the target vehicle functional configuration that matches the target vehicle model; The vehicle control application is triggered to display the target vehicle's function configuration, and / or the vehicle control application is triggered to hide vehicle function configurations other than the target vehicle's function configuration.

7. The method according to claim 6, characterized in that, The method is executed in the cloud, and the method further includes: The prompt message is sent to the corresponding vehicle control application to trigger the vehicle control application to display the prompt message; and / or, The target vehicle function configuration is sent to the corresponding vehicle control application terminal to trigger the vehicle control application terminal to display the target vehicle function configuration.

8. The method according to claim 7, characterized in that, After distributing the target vehicle function configuration to the corresponding vehicle control application, the method further includes: The success rate of execution of vehicle functions in the target vehicle function configuration in vehicles of the target vehicle model is statistically analyzed. If the execution success rate is greater than or equal to a preset threshold, the target vehicle function configuration is sent to all vehicle control application terminals bound to the target vehicle model. If the execution success rate is less than the preset threshold, the distribution of the target vehicle function configuration to all vehicle control application terminals bound to the target vehicle model is prohibited.

9. The method according to any one of claims 1 to 6, characterized in that, The method is executed on the vehicle control application terminal, and the method further includes: Before converting the execution command into a remote control signal that matches the vehicle control interaction protocol and the target software version number based on the pre-configured function strategy table, the function strategy table issued by the cloud is obtained.

10. An electronic device, characterized in that, The electronic device includes one or more processors and one or more memories, wherein at least one piece of program code is stored in the one or more memories, and the at least one piece of program code is loaded and executed by the one or more processors to implement the method as claimed in any one of claims 1 to 9.

Images