A vehicle end remote control method and system, electronic equipment and storage medium

Abstract

Embodiments of the present application provide a vehicle end remote control method and system, electronic equipment and storage medium. Applied to a vehicle networking platform, the method comprises: receiving an application end instruction sent by a first standard software package of an application end; determining a device end instruction corresponding to the application end instruction and a target device end according to a target mapping relationship; sending the device end instruction to the target device end to control a second standard software package in the target device end to determine a vehicle end control instruction corresponding to the device end instruction based on an execution file in the target device end; and controlling a target controller in the target device end to perform a corresponding control operation according to the vehicle end control instruction. The purpose is to reduce the development cost and difficulty of vehicle remote control.

Description

Technical Field

[0001] This invention relates to the field of automotive remote control technology, and more particularly to a vehicle-side remote control method, system, electronic device, and storage medium. Background Technology

[0002] As remote control scenarios for smart cars become increasingly flexible and personalized, the development of apps, vehicle cloud platforms, and vehicle terminals becomes highly inefficient and maintenance costs are very high. The coupling between systems is also very high. This is especially true for traditional automakers, where there are both new energy and fuel vehicles operating in parallel, and the functional differences between models and series are also quite large. Each model needs to have its own remote control function developed, resulting in high manpower costs. Summary of the Invention

[0003] This invention provides a vehicle remote control method, system, electronic device, and storage medium, aiming to reduce the development cost and difficulty of vehicle remote control.

[0004] The first aspect of this invention provides a vehicle-side remote control method applied to a vehicle networking platform, the method comprising:

[0005] Receive application-side instructions sent by the first standard software package from the application;

[0006] Based on the target mapping relationship, determine the device-side instruction and target device corresponding to the application-side instruction;

[0007] The device-side instruction is sent to the target device to control the second standard software package in the target device to determine the vehicle-side control instruction corresponding to the device-side instruction based on the executable file in the target device.

[0008] According to the vehicle-side control command, the target controller in the target device terminal is controlled to perform the corresponding control operation.

[0009] Optionally, before receiving application-side instructions sent by the first standard software package of the application, the method further includes:

[0010] Construct device models corresponding to each vehicle model to obtain model definition files for each vehicle model;

[0011] Based on the vehicle model corresponding to each model definition file, each model definition file is sent to the second standard software package on the device side of the corresponding vehicle model for parsing to obtain the executable file on each device side.

[0012] Optionally, before receiving application-side instructions sent by the first standard software package of the application, the method further includes:

[0013] Based on the vehicle model corresponding to the application, determine the list of remote control and vehicle status functions corresponding to the vehicle model;

[0014] Based on the remote control and the vehicle status function list, determine the instruction list for the vehicle model;

[0015] Based on the instruction list, construct the application-side function code of the application and send the application-side function code to the first standard software package integrated into the target application of the application.

[0016] Optionally, determining the device-side instruction and target device-side instruction corresponding to the application-side instruction based on the target mapping relationship includes:

[0017] By parsing the application terminal instructions, the instruction code and vehicle identification code in the application terminal instructions are obtained;

[0018] Based on the target mapping relationship, the device-side instruction corresponding to the instruction code is determined, wherein the target mapping relationship is a one-to-one correspondence between each instruction code and each device-side instruction;

[0019] Based on the vehicle identification code, determine the target device terminal corresponding to the vehicle identification code.

[0020] Optionally, the second standard software package in the target device determines the vehicle control command corresponding to the device command based on the executable file in the target device, including:

[0021] The second standard software package in the target device determines the vehicle instruction code corresponding to the device instruction and the execution conditions corresponding to the vehicle instruction code based on the executable file in the target device.

[0022] If the execution conditions are verified by the second standard software package, the corresponding vehicle control command is generated based on the vehicle command encoding.

[0023] Optionally, the method further includes:

[0024] Receive the error code reported by the second standard software package, wherein the error code is fed back by the target controller executing the vehicle-side control command;

[0025] Based on the error code, determine the execution result corresponding to the error code, and report the execution result to the application.

[0026] Optionally, the second standard software package is the same standard software package that is configured on the device side of all vehicle models.

[0027] A second aspect of this invention provides a vehicle-side remote control method applied to a target device, the method comprising:

[0028] Receive instructions from the device;

[0029] According to the execution file, the vehicle control command corresponding to the device command is determined by the second standard software package. The execution file is obtained by the second standard software package by parsing the model definition file sent by the vehicle networking platform.

[0030] The vehicle-side control commands control the corresponding target controller to perform corresponding control operations.

[0031] Optionally, the method further includes:

[0032] The second standard software package in the target device determines, based on the executable file in the target device, whether the received monitoring data meets the reporting conditions for each event.

[0033] If all the monitoring data meet the reporting conditions for the target event, the target event will be reported to the vehicle network platform.

[0034] A third aspect of this invention provides a vehicle-side remote control method, applied to an application terminal, the method comprising:

[0035] Trigger the issuance of application-side commands through the target application;

[0036] The application terminal generates corresponding application terminal instructions based on the trigger operation using the first standard software package in the application terminal;

[0037] The application-side instructions are sent via the first standard software package.

[0038] Optionally, after receiving the application-side instruction sent by the first standard software package of the application, the application-side instruction is encrypted and verified, including:

[0039] The first standard software package received from the application terminal encrypts the generated application terminal instruction using an asymmetric encryption algorithm to obtain an encrypted application terminal instruction;

[0040] The encrypted application terminal command is verified according to the asymmetric encryption algorithm.

[0041] If the verification is successful, proceed to the following steps: determine the device-side instruction and target device corresponding to the application-side instruction based on the target mapping relationship.

[0042] Optionally, the device-side instruction is sent to the target device to control a second standard software package in the target device to determine the vehicle-side control instruction corresponding to the device-side instruction based on the executable file in the target device, including:

[0043] The device-side instructions are encrypted using the aforementioned asymmetric encryption algorithm.

[0044] The encrypted device-side command is sent to the target device.

[0045] The target device is controlled to verify the encrypted device commands based on the asymmetric encryption algorithm;

[0046] If the verification is successful, the second standard software package in the target device determines the vehicle control instruction corresponding to the device instruction based on the executable file in the target device.

[0047] A fourth aspect of this invention provides a vehicle-side remote control system applied to a vehicle networking platform, the system comprising:

[0048] The application-side instruction receiving module is used to receive application-side instructions sent by the first standard software package of the application.

[0049] The device instruction determination module is used to determine the device instruction and target device corresponding to the application instruction based on the target mapping relationship.

[0050] The device-side instruction sending module is used to send the device-side instruction to the target device-side, so as to control the second standard software package in the target device-side to determine the vehicle-side control instruction corresponding to the device-side instruction based on the executable file in the target device-side.

[0051] Optionally, the system further includes:

[0052] The model definition file determination module is used to construct the terminal object models of each device corresponding to the vehicle model, so as to obtain the model definition files corresponding to each vehicle model;

[0053] The model definition file sending module is used to send each model definition file to the second standard software package on the device side of the corresponding vehicle model for parsing, so as to obtain the executable file on each device side.

[0054] Optionally, the system further includes:

[0055] The application-side remote control and vehicle condition function list determination module is used to determine the remote control and vehicle condition function list corresponding to the vehicle model based on the vehicle model corresponding to the application-side.

[0056] The instruction list determination module is used to determine the instruction list of the vehicle model based on the remote control and the vehicle condition function list;

[0057] The application-side function code construction module is used to construct the application-side function code of the application based on the instruction list, and send the application-side function code to the first standard software package integrated in the target application of the application.

[0058] A fifth aspect of this invention provides a vehicle-side remote control system applied to a target device, the system comprising:

[0059] The device-side instruction receiving module is used to receive instructions from the device side.

[0060] The vehicle-side control command determination module is used to determine the vehicle-side control command corresponding to the device-side command based on the execution file and through a second standard software package. The execution file is obtained by the second standard software package by parsing the model definition file sent by the vehicle networking platform.

[0061] The control module is used to control the corresponding target controller to perform corresponding control operations through the vehicle-side control commands.

[0062] A sixth aspect of this invention provides a vehicle-side remote control system, applied to an application terminal, the system comprising:

[0063] The application-side command triggering module is used to trigger the issuance of application-side commands through the target application.

[0064] The application-side instruction generation module is used to generate corresponding application-side instructions based on the trigger operation using the first standard software package in the application.

[0065] The application-side instruction sending module is used to send the application-side instructions through the first standard software package.

[0066] A seventh aspect of the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the vehicle remote control method as described in the first aspect of the present invention.

[0067] An eighth aspect of the present invention provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the vehicle remote control method as described in the first aspect of the present invention.

[0068] The vehicle remote control method provided by this invention has the following advantages:

[0069] This invention provides a vehicle-side remote control method applied to a vehicle networking platform. First, it receives an application-side instruction sent by a first standard software package. Then, based on a target mapping relationship, it determines the device-side instruction corresponding to the application-side instruction and the target device. Next, it sends the device-side instruction to the target device, controlling a second standard software package in the target device to determine the vehicle-side control instruction corresponding to the device-side instruction based on the executable file in the target device. This second standard software package is a common standard software package configured on the device sides of all vehicle models; that is, a developed second standard software package can be configured on the device sides of all vehicle models. Finally, based on the vehicle-side control instruction, it controls the target device to execute the control operation corresponding to the vehicle-side control instruction.

[0070] This method addresses the differences in remote control functions across different vehicle models (e.g., some models have remote power control while others do not), and the potential variations in specific remote control commands between different models (e.g., even though both may control window opening, the specific remote control commands differ between models). The method constructs a model definition file corresponding to each vehicle model through a vehicle networking platform; that is, a unique model definition file is created for each model. The vehicle networking platform then sends these model definition files to the corresponding second standard software package for each model to parse and generate executable files for each model. This allows for different remote control functions and specific remote control commands for each vehicle model. Once each vehicle model has its own executable file, the second standard software package on the device can determine the corresponding vehicle control command based on this executable file, thus enabling vehicle control. Therefore, when the remote control function of a vehicle changes (such as when the remote pre-power-on control function was not available before but is now available), engineers do not need to perform secondary development on the vehicle and its equipment. Instead, engineers only need to adjust the original model definition file of the vehicle to obtain a new model definition file, and send it to the second software package on the equipment side for parsing to form a new executable file. This can also effectively reduce development costs. Attached Figure Description

[0071] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0072] Figure 1 This is a flowchart illustrating a vehicle-side remote control method according to an embodiment of the present invention;

[0073] Figure 2This is an interaction diagram of the application terminal, device terminal, and vehicle networking platform in a vehicle-side remote control method according to an embodiment of the present invention;

[0074] Figure 3 This is an architecture diagram of a standard software package in a vehicle-side remote control method according to an embodiment of the present invention;

[0075] Figure 4 This is a flowchart illustrating the command transmission process in a vehicle remote control method according to an embodiment of the present invention;

[0076] Figure 5 This is a schematic diagram of a vehicle-side remote control system according to an embodiment of the present invention. Detailed Implementation

[0077] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0078] refer to Figure 1 , Figure 1 This is a flowchart illustrating a vehicle-side remote control method according to an embodiment of the present invention. Figure 1 As shown, the vehicle-side remote control method of this embodiment is applied to a vehicle networking platform, and the method may include the following steps:

[0079] Step S1: Receive application-side instructions sent by the first standard software package of the application.

[0080] In this embodiment, the user first initiates an application-side command through the first standard software package on the application side. The vehicle-to-everything (V2X) platform then receives the application-side command sent by the first standard software package. The first standard software package is used to generate corresponding application-side commands based on the user's triggered operation. The first standard software package is preferably an SDK (Software Development Kit). It should be understood that this is only a preferred implementation of the first standard software package; it can also be other application-side control modules that can be used to generate corresponding application-side commands based on the user's triggered operation.

[0081] Step S2: Determine the device-side instruction and target device end corresponding to the application-side instruction based on the target mapping relationship.

[0082] In this embodiment, a mapping relationship between application-side instructions and device-side instructions is first established through a vehicle-to-everything (V2X) platform. Specifically, since different vehicle models have different functions, and the control signals for the same functions also differ across models, this invention first determines the service capabilities of the device-side corresponding to that vehicle model by using the function list of the application-side instructions applied to that vehicle model. Then, based on the application-side instructions of the application-side instructions for that vehicle model, the corresponding device-side instructions applied to the device-side instructions for that vehicle model are associated. The application-side includes any one of the following: an application-side instruction located on a mobile terminal (phone, iPad, laptop, etc.). Then, the application-side instructions sent by the application-side are received. According to the predefined target mapping relationship between application-side instructions and device-side instructions, the device-side instruction corresponding to the application-side instruction and the target device-side to which it will be sent are determined. This target device-side refers to the device-side on a specific vehicle.

[0083] Step S3: Send the device-side instruction to the target device to control the second standard software package in the target device to determine the vehicle-side control instruction corresponding to the device-side instruction based on the executable file in the target device.

[0084] In this embodiment, the determined device-side instruction is sent to the determined target device. The second standard software package in the target device determines the vehicle-side control instruction corresponding to the device-side instruction based on the pre-generated executable file. This vehicle-side control instruction is ultimately used to control the target controller corresponding to the vehicle to perform the corresponding control operation. The second standard software package is used to parse the model definition file received by the device and the received device-side instruction. The second standard software package is preferably an SDK (Software Development Kit). It should be understood that this is only a preferred implementation of the second standard software package; it can also be other device-side control modules that can be used to parse the model definition file received by the device and the received device-side instruction. This second standard software package is a preparatory step before the vehicle-side remote control method of this application can be implemented. That is, before the vehicle-side remote control method of this application can be implemented, a second standard software package is first configured for the device. This second standard software package only needs to be configured once. The second standard software package can determine the vehicle-side control instruction corresponding to the received device-side instruction based on the executable file. The specific determination method will be described in subsequent embodiments.

[0085] Step S4: According to the vehicle-side control command, control the target controller in the target device to perform the corresponding control operation.

[0086] In this embodiment, after the second standard software package on the target device determines the vehicle control instruction corresponding to the device instruction, it controls the second standard software package to send the vehicle control instruction to the corresponding target controller to perform the corresponding control operation. For example, the vehicle control instruction controls the controller that controls the driver's side window of the vehicle to perform the window closing operation.

[0087] In this embodiment, both the application and the device must undergo authentication when connecting to the vehicle networking platform to ensure the reliability of information transmission. The vehicle networking platform provides two authentication methods: one-way authentication and two-way authentication. The server provides an EMQX broker, which can be configured with ACLs for both the application and the device. One-way authentication involves both the client (device) and the client (application) verifying the certificate of the vehicle networking platform (server), and the server verifies the validity of the client's token. Two-way authentication involves the client verifying the server's certificate, and the server verifying the client's certificate. The standard software packages for both the application and the device encapsulate authentication certificates for one-way and two-way authentication connections, building basic connection capabilities to enable functional development based on the device's object model and to ensure two-way authentication between the device, the application, and the vehicle networking platform based on certificates. Timestamps and digital signatures are added to the requests and responses between the device, the application, and the vehicle networking platform to verify data integrity and origin, preventing replay or tampering attacks. One preferred implementation of certificate generation is to use the national cryptographic SM2 algorithm. It should be understood that this is only a preferred implementation, and certificate generation can also be done in other ways, which are not specifically limited here.

[0088] In this embodiment, when the various controllers in the vehicle are connected via a CAN bus, the vehicle-side control command corresponding to the device-side instruction determined by the second standard software package on the device side is the corresponding CAN message. After obtaining the CAN message, the second standard software package sends the CAN message onto the CAN bus. The CAN message is then transmitted to the corresponding target controller via the CAN bus to execute the corresponding control operation. Preferably, communication between the application end, the vehicle networking platform, and the vehicle's device end is based on the MQTT communication protocol. It should be understood that this is only a preferred implementation; communication between the application end, the vehicle networking platform, and the vehicle's device end can also be based on HTTPS, etc.

[0089] This invention provides a vehicle-side remote control method applied to a vehicle networking platform. First, it receives an application-side instruction sent by a first standard software package. Then, based on a target mapping relationship, it determines the device-side instruction corresponding to the application-side instruction and the target device. Next, it sends the device-side instruction to the target device, controlling a second standard software package in the target device to determine the vehicle-side control instruction corresponding to the device-side instruction based on the executable file in the target device. This second standard software package is a common standard software package configured on the device sides of all vehicle models; that is, a developed second standard software package can be configured on the device sides of all vehicle models. Finally, based on the vehicle-side control instruction, it controls the target device to execute the control operation corresponding to the vehicle-side control instruction.

[0090] This method addresses the differences in remote control functions across different vehicle models (e.g., some models have remote power control while others do not), and the potential variations in specific remote control commands between different models (e.g., even though both may control window opening, the specific remote control commands differ between models). The method constructs a model definition file corresponding to each vehicle model through a vehicle networking platform; that is, a unique model definition file is created for each model. The vehicle networking platform then sends these model definition files to the corresponding second standard software package for each model to parse and generate executable files for each model. This allows for different remote control functions and specific remote control commands for each vehicle model. Once each vehicle model has its own executable file, the second standard software package on the device can determine the corresponding vehicle control command based on this executable file, thus enabling vehicle control. Therefore, when the remote control function of a vehicle changes (such as when the remote pre-power-on control function was not available before but is now available), engineers do not need to perform secondary development on the vehicle and its equipment. Instead, engineers only need to adjust the original model definition file of the vehicle to obtain a new model definition file, and send it to the second software package on the equipment side for parsing to form a new executable file. This can also effectively reduce development costs.

[0091] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method. In this method, determining the model definition file includes steps S001 to S002:

[0092] Step S001: Construct the device models corresponding to each vehicle model to obtain the model definition files corresponding to each vehicle model.

[0093] In this embodiment, before performing remote control on the vehicle side, preparation work is first carried out on the device side of the vehicle. Specifically, since different vehicle models have different remote control functions, the vehicle network platform first determines the corresponding remote control and vehicle status function list for each vehicle model. Remote control refers to the functions that can be performed by the device side remotely, such as remotely controlling the vehicle to turn on the air conditioning in advance, or remotely controlling the vehicle to open the windows in advance. The vehicle status function list refers to the vehicle status information that can be fed back to the application side, such as the current temperature inside the vehicle, the current remaining battery power and / or fuel level, etc.

[0094] In this embodiment, since the construction of the device-side object model is the same for each vehicle model, the construction of the device-side object model is explained using one vehicle model as an example. Based on the remote control and vehicle condition (attribute) function list of the vehicle model, a device-side object model corresponding to that vehicle model is constructed. This device-side object model defines the attributes of each device on the vehicle, vehicle-side control commands, event reporting, and other functional models. Specifically, it defines the function of feeding back the current attributes of each device to the device and the vehicle network platform, the function of controlling the vehicle to execute corresponding control operations, and the function of event reporting when the vehicle condition meets certain conditions. Based on the constructed device-side object model, a corresponding model definition file is generated. Using the same implementation method, a corresponding model definition file will be constructed for each vehicle model through the vehicle network platform. That is, there is a one-to-one correspondence between the vehicle model type and the model definition file; each vehicle model has a corresponding model definition file. The model definition files will differ depending on the remote control functions of the vehicle model and / or the specific remote control command information.

[0095] Step S002: Based on the vehicle model corresponding to each model definition file, send each model definition file to the second standard software package on the device side of the corresponding vehicle model for parsing to obtain the executable file on each device side.

[0096] In this embodiment, after the vehicle networking platform constructs the model definition files corresponding to the vehicle models, it sends each model definition file to the corresponding vehicle model's device. Upon receiving the model definition files, each device parses them using the second standard software package to obtain the executable file for the vehicle. With the executable file and the second standard software package present, each vehicle's device has the ability to execute the vehicle control commands it supports.

[0097] In this embodiment, each model definition file includes preconditions for each reported event and each device instruction. Each reported event is triggered only when its preconditions are met. Similarly, each device instruction is triggered only when its preconditions are met, leading to the generation of the corresponding vehicle control instruction and the control of the corresponding target controller. For example, remotely starting the air conditioner requires determining whether the vehicle is in the off position, whether it is in remote start mode, and whether the engine is prohibited from starting (i.e., PowerStatusFeedback = 0 or PEPS_RemoteStartReq = 1 and EngineStartupInhibitSts = 0). After these conditions are met, TBOX_RemoteEngineStartupReq = 1 and TBOX_RemoteStartRunTime = the start time sent from the cloud are sent. Then, it is determined whether the engine has started successfully (i.e., PEPS_RemoteStartFeedback = 1). After the engine starts successfully, the air conditioner is started, and TBOX_RemoteAirCleanReq = 1 and TBOX_RemoteACStartupReq = 1 are sent. Next, it checks whether the air conditioning has started successfully, i.e., AC_RemoteStartFeedback = 1. If startup fails, feedback information about the startup failure is sent to the application through the vehicle networking platform.

[0098] In this embodiment, it should be understood that before obtaining the corresponding executable file by parsing the model definition file, it is necessary to configure a second standard software package for each vehicle's device. Only after each different vehicle model has its own second standard software package can it parse the received model definition file to form its own executable file.

[0099] In this embodiment, a device-specific signature encryption mechanism is added to the model definition file. Different devices use different keys for encryption to avoid plaintext transmission of the model definition file and ensure its security. Specifically, the second standard software package configured for the corresponding vehicle model has a corresponding decryption key, which can only decrypt the model definition file corresponding to its own vehicle model. This prevents the vehicle model from receiving model definition files from other vehicle models and parsing them to form corresponding executable files.

[0100] In this embodiment, the executable file upon which each vehicle model is based only needs to be configured once to be used for the implementation of all remote control functions included in that executable file. When the remote control functions of a vehicle model change (for example, some remote control functions are added), the vehicle networking platform only needs to adjust the original model definition file corresponding to that vehicle model and send the adjusted model definition file to the second standard software package on the device side of that vehicle model for parsing to form a new executable file.

[0101] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method. In this method, determining the first standard software package on the application side includes steps S01 to S03:

[0102] Step S01: Based on the vehicle model corresponding to the application terminal, determine the list of remote control and vehicle status functions corresponding to the vehicle model.

[0103] In this embodiment, steps S01 to S03 are the preparatory work before the technical solutions corresponding to steps S1 to S6 above can be realized. This preparatory work involves sending application-side function code to the first standard software package in the target application on the application side in advance. Since different application terminals control different vehicle models, and different vehicle models have different control functions, the remote control and vehicle status function list corresponding to the vehicle model controlled by the application terminal is first determined on the vehicle networking platform according to the vehicle model.

[0104] Step S02: Determine the instruction list for the vehicle model based on the remote control and the vehicle condition function list.

[0105] In this embodiment, the vehicle networking platform maintains a unified instruction library. After determining the list of remote control and vehicle status functions for the vehicle model controlled by the application, it selects instructions from the unified instruction library that correspond to each remote control and vehicle status function in the list to form an instruction list for that vehicle model. Based on the same implementation method, each vehicle model will form a corresponding instruction list according to its own functions, that is, there is a one-to-one correspondence between vehicle models and instruction lists, and each vehicle model will have a corresponding instruction list.

[0106] Step S03: Based on the instruction list, construct the application-side function code of the application terminal, and send the application-side function code to the first standard software package integrated into the target application of the application terminal.

[0107] In this embodiment, based on the instruction lists determined in step S02, application-side function codes corresponding to each instruction list are constructed. These application-side function codes are JSON strings used to configure the remote control functions of each target application. After constructing the application-side function codes for each vehicle model, the codes are sent to the target application within the application used to control that vehicle model. The first standard software package integrated within the target application then configures the remote control functions of that target application based on the application-side function codes. The target application triggers the issuance of each application-side instruction, and the first standard software package also generates corresponding application-side instructions based on the triggering operation of the target application.

[0108] In this embodiment, the first standard software package integrated in the target applications used to control different vehicle models is the same first standard software package. The functions of this first standard software package include obtaining application-side function code provided by the vehicle networking platform, configuring remote control functions for the target applications based on this application-side code, and generating corresponding application-side instructions based on the triggering operations of the target applications. When the application-side function code is different, the remote control functions configured in the target applications will also be different.

[0109] In this embodiment, the advantage of using the first standard software package on the application side is that the remote control functions will differ depending on the vehicle model controlled by the application side. Therefore, the development cost of developing complete control applications for various vehicle models with different remote control functions is currently very high. However, through this implementation method, only one first standard software package needs to be built for various vehicle models with different remote control functions, and then this first standard software package is integrated into the target applications in the application side that control various vehicle models. For any target application, the first standard software package in the target application obtains the application-side function code corresponding to the vehicle model controlled by the target application from the vehicle networking platform, and then the first standard software configures the remote control function of the target application based on the obtained application-side function code. This eliminates the need to develop separate control applications for various vehicle models with different remote control functions, thereby avoiding the need to develop network layer, service layer, API layer, and application layer during the development process when developing complete applications for application sides of various vehicle models with different remote control functions, thus effectively reducing development costs. Meanwhile, when the remote control function of the application terminal controlling a certain vehicle model changes, the vehicle networking platform sends new application function code to the target application of each application terminal corresponding to that vehicle model, so that the first standard software package in the target application can update the remote control function supported by the target application based on the new application function code.

[0110] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method. In this method, step S2 includes steps S21 to S23:

[0111] Step S21: By parsing the application terminal instruction, obtain the instruction code and vehicle identification code in the application terminal instruction.

[0112] In this embodiment, the vehicle network platform parses the received application instructions to obtain the vehicle identification code (CARID) used to determine which specific vehicle the application instructions control, and the instruction code used to identify the application instructions.

[0113] Step S22: Determine the device-side instruction corresponding to the instruction code according to the target mapping relationship, wherein the target mapping relationship is a one-to-one correspondence between each instruction code and each device-side instruction.

[0114] In this embodiment, based on the target mapping relationship between application-side instructions and device-side instructions predefined by the vehicle-to-everything (V2X) platform, the instruction code of the device-side instruction corresponding to the instruction code of the application-side instruction is determined. The corresponding device-side instruction is then determined based on the instruction code of the device-side instruction. The target mapping relationship records the one-to-one correspondence between each instruction code and each device-side instruction.

[0115] Step S23: Determine the target device terminal corresponding to the vehicle identification code based on the vehicle identification code.

[0116] In this embodiment, the specific vehicle to be controlled is determined based on the vehicle identification code, thereby determining the target device on that specific vehicle.

[0117] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method. In this method, step S3, controlling the second standard software package in the target device, determines the vehicle-side control command corresponding to the device-side command based on the executable file in the target device, including steps S31 to S32:

[0118] Step S31: Control the second standard software package in the target device to determine the vehicle instruction code corresponding to the device instruction and the execution conditions corresponding to the vehicle instruction code based on the executable file in the target device.

[0119] In this embodiment, after determining the device-side instruction and target device corresponding to the application-side instruction, the vehicle-to-everything (V2X) platform sends the device-side instruction to the target device. Upon receiving the device-side instruction, the target device parses it using its second standard software package to obtain the signal name. The second standard software package then determines the vehicle-side instruction code and corresponding execution conditions based on the mapping relationship between signal names and vehicle-side instruction codes defined in the executable file, and the mapping relationship between vehicle-side instruction codes and execution conditions.

[0120] Step S32: If the execution conditions are verified by the second standard software package, the corresponding vehicle control command is generated based on the instruction encoding.

[0121] In this embodiment, after determining the execution conditions corresponding to the vehicle-side command code, the second standard software package determines whether the current vehicle state meets the execution conditions. For example, if the vehicle-side control command is to turn on the air conditioner, it determines whether the vehicle engine has started. If the conditions are not met, the verification is deemed unsuccessful, and subsequent generation of the corresponding vehicle-side control command based on the vehicle-side command code is not performed. If the conditions are met, the verification is deemed successful, and subsequent generation of the corresponding vehicle-side control command based on the vehicle-side command code is performed.

[0122] In this embodiment, when the various controllers in the vehicle are connected via a CAN bus, the aforementioned vehicle-side command encoding corresponds to CAN signal values, and the aforementioned vehicle-side control commands are CAN messages. The specific implementation of steps S31 to S32 is as follows: Based on the execution file, the CAN signal value corresponding to the signal name of the device-side command and the execution conditions corresponding to that CAN signal value are determined. After the execution conditions are verified, the target information corresponding to that CAN signal value is determined based on the DBC file in the CAN network protocol. That is, the DBC file determines which controller needs to be controlled by that CAN signal value. After obtaining the target information, a completed CAN message is generated based on the target information and the CAN signal value. The DBC file (Database CAN) is the database file of the CAN network, which describes the CAN communication list. The target information includes at least: CANID, signal length, and signal start bit information.

[0123] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method. This method further includes steps S5 to S6:

[0124] Step S5: Receive the error code reported by the second standard software package, the error code being determined based on feedback information from the target controller executing the vehicle-side control command.

[0125] In this embodiment, after the vehicle-side control command controls the corresponding target controller to perform the corresponding control operation, the controller sends the corresponding feedback information to the second software package. Based on the feedback information, the second standard software package determines the corresponding error code and reports the error code to the vehicle network platform.

[0126] Step S6: Determine the execution result corresponding to the error code based on the error code, and report the execution result to the application terminal.

[0127] In this embodiment, after the vehicle-to-everything (V2X) platform receives the error code, it determines the execution result corresponding to the error code and reports the execution result to the application terminal to provide feedback to the user on whether the currently executed control operation was successful or failed, and to indicate the type of error encountered in the event of failure. It should be understood that all error codes also include a corresponding code indicating successful execution.

[0128] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method, in which the second standard software package is a common standard software package that is configured on the device side of all vehicle models.

[0129] In this embodiment, since the function of the second standard software package configured on different vehicle models is to parse the model definition files they receive and, based on the respective executable files obtained from parsing their model definition files, determine the vehicle control commands corresponding to the received device commands, the second standard software package configured on different vehicle models can be the same standard software package, as long as it has the above two capabilities. Therefore, to reduce development costs, the second standard software package configured on different vehicle models in this application is preferably the same standard software package, that is, the second standard software package configured on all vehicle models is the same standard software package. It should be understood that this is only a preferred implementation of the second standard software package, and the second standard software packages configured on different vehicle models can also be different standard software packages. It should also be understood that since the second standard software packages configured on different vehicle models have decryption keys that can only decrypt the model definition files corresponding to their own vehicle models, the second standard software packages configured on different vehicle models will at least have different decryption keys for decrypting the model definition files.

[0130] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method. In this method, step S1 may include: after receiving an application-side instruction sent by a first standard software package from the application side, encrypting and verifying the application-side instruction. Specifically, step S1 includes steps S11 to S13:

[0131] Step S11: Receive the encrypted application terminal instruction obtained by encrypting the generated application terminal instruction using the first standard software package of the application terminal according to the asymmetric encryption algorithm.

[0132] In this embodiment, the first standard software package is integrated into the target application on the application side. The first standard software package generates corresponding application-side instructions based on the received trigger operation of the target application.

[0133] In this embodiment, to ensure the security and reliability of information transmission and prevent it from being stolen or tampered with, the present invention uses an asymmetric encryption algorithm to encrypt the information during transmission, exposing only the public keys of the vehicle and the vehicle network platform. This enables identity verification between the two parties and prevents impersonation or forgery. Specifically: after the first standard software package on the application side generates the corresponding application-side instruction, an asymmetric encryption algorithm is used to encrypt the application-side instruction. Then, the encrypted application-side instruction is sent to the vehicle network platform through the first standard software package on the application side, and the vehicle network platform receives the encrypted application-side instruction.

[0134] Step S12: Verify the encrypted application terminal instruction according to the asymmetric encryption algorithm.

[0135] In this embodiment, after receiving the encrypted application terminal instruction, the vehicle network platform verifies the legality of the encrypted application terminal instruction based on an asymmetric encryption algorithm to determine whether the application terminal instruction is a stolen and / or tampered application terminal instruction and / or an application terminal instruction sent by an illegitimate application terminal.

[0136] Step S13: If the verification passes, proceed to step S2.

[0137] In this embodiment, step S2 of the present invention is executed only after the legality verification of the encrypted application-side command is passed.

[0138] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method. In this method, step S3 includes steps S301 to S304:

[0139] Step S301: Encrypt the device-side command using the asymmetric encryption algorithm.

[0140] In this embodiment, after the vehicle network platform determines the device instruction corresponding to the received application instruction based on the target mapping relationship between application-side instructions and device-side instructions, it encrypts the device instruction using an asymmetric encryption algorithm.

[0141] Step S302: Send the encrypted device-side command to the target device.

[0142] In this embodiment, the encrypted device-side command is sent to the target device through the vehicle networking platform.

[0143] Step S303: Control the target device to verify the encrypted device command based on the asymmetric encryption algorithm.

[0144] In this embodiment, based on the encrypted device-side command sent to the target device, the target device is controlled to perform a legality verification on the encrypted device-side command using an asymmetric encryption algorithm to determine whether the device-side command is a stolen and / or tampered device-side command and / or an application-side command sent by an illegitimate device.

[0145] Step S304: If the verification is successful, the second standard software package in the target device terminal determines the vehicle control instruction corresponding to the device terminal instruction based on the executable file in the target device terminal.

[0146] In this embodiment, after the legality verification of the encrypted device-side command is passed, the target device-side is controlled to parse the obtained device-side command based on the executable file using the second standard software package to obtain the vehicle-side control command.

[0147] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method, which is applied to a target device. The method includes:

[0148] Step S021: Receive instructions from the device.

[0149] In this embodiment, the target device receives device instructions sent by the vehicle networking platform.

[0150] Step S022: Based on the execution file, determine the vehicle control command corresponding to the device command through the second standard software package. The execution file is obtained by the second standard software package through parsing the model definition file sent by the vehicle networking platform.

[0151] In this embodiment, after the target device receives the device instruction sent by the vehicle networking platform, the second standard software package in the target device determines the vehicle control instruction corresponding to the device instruction based on the executable file in the target device. The executable file in the target device is obtained by the second standard software in the target device by parsing the model definition file sent to the target device by the vehicle networking platform.

[0152] Step S023: Control the corresponding target controller to perform the corresponding control operation through the vehicle-side control command.

[0153] In this embodiment, after the second standard software package determines the corresponding vehicle-side control command, it sends the vehicle-side control command to the target controller for executing the vehicle-side control command, so that the target controller performs the corresponding control operation.

[0154] In conjunction with the above embodiments, in one implementation, the present invention also provides a vehicle-side remote control method. This method further includes steps S024 to S025:

[0155] Step S024: The second standard software package in the target device determines, based on the executable file in the target device, whether the received monitoring data meets the reporting conditions for each event.

[0156] In this embodiment, the executable file defines various event reporting functions and corresponding reporting conditions for each event. Based on the executable file, the second standard software package on the target device can determine whether the received vehicle monitoring data meets the reporting conditions for each event recorded in the executable file.

[0157] Step S025: If all the monitoring data meet the reporting conditions for the target event, the target event is reported.

[0158] In this embodiment, an event that meets the reporting conditions is called a target event. Therefore, when it is determined that the monitoring results of various monitoring data meet the reporting conditions of an event, the event is identified as a target event, and the target event is reported to the vehicle network platform and then fed back to the corresponding application terminal through the vehicle network platform.

[0159] In conjunction with the above embodiments, in one implementation, this invention also provides a vehicle-side remote control method, applied to an application terminal. The method includes steps S031 to S033:

[0160] Step S031: Trigger the issuance of application-side commands through the target application.

[0161] In this embodiment, the target application is an application used for remote vehicle control. The target application itself only involves triggering the issuance of application-side commands. Specifically, the user triggers the issuance of application-side commands through the target application on the application side.

[0162] Step S032: Generate corresponding application-side instructions based on the trigger operation using the first standard software package in the application terminal.

[0163] In this embodiment, the first standard software package is integrated into the target application. The first standard software package generates corresponding application-side instructions based on the received trigger operation of the target application.

[0164] Step S033: Send the application-side command through the first standard software package.

[0165] In this embodiment, after the first standard software package generates the application-side instruction, the application-side instruction is sent to the vehicle network platform so that the vehicle network platform can receive the application-side instruction.

[0166] In the above embodiments of the present invention Figure 2 This is an interaction diagram of the application terminal, device terminal, and vehicle networking platform in a vehicle-side remote control method according to an embodiment of the present invention. Figure 2 As shown, application commands are sent via the application terminal. The application terminal also includes a data persistence layer for data storage and an IoT MQTT gateway. This allows application commands to be sent to the vehicle network platform via the application terminal's first standard software package. The vehicle network platform manages device-side object models, constructs these models, and sends the constructed model corresponding to the vehicle model to the vehicle's device terminals via the IoT MQTT gateway. It also provides authentication services for each device (device terminal and application terminal) connected to the vehicle network platform and provides runtime services to each device, such as monitoring device operation to report events when preconditions for event reporting are met. The vehicle's device terminals include a TBOX, a data acquisition center, a vehicle-mounted message center, and a data persistence layer.

[0167] In the above embodiments of the present invention Figure 3 This is an architecture diagram of a standard software package in a vehicle-side remote control method according to an embodiment of the present invention. Figure 3 As shown, the standard software package in this invention includes an application layer, an API layer, a service layer, and a network layer. The application layer includes a device-side application layer and an application-side application layer. The network layer includes the MQTT communication protocol, HTTPS, and other protocols. The service layer includes device connection services for device login and logout, an uplink channel service for parameter verification and data encryption / compression, and uploading of the encrypted / compressed data, a downlink channel service for decompressing and decrypting received data and performing data parsing and service orchestration, and service management services including crash analysis and version management during transmission.

[0168] In the above embodiments of the present invention Figure 4 This is a flowchart illustrating the command transmission process in a vehicle remote control method according to an embodiment of the present invention. Figure 4As shown, the application terminal issues commands. The application terminal's first standard software package performs a vehicle model and series lookup. Based on the vehicle model and series, it determines the command code for the application terminal command within that vehicle model and series, as well as the vehicle identification code of the vehicle on which the application terminal is located. Then, the application terminal command, including the command code and vehicle identification code, is sent to the vehicle network platform. The vehicle network platform verifies the application terminal command. After successful verification and confirmation of its validity, it determines the corresponding device terminal command based on the mapping relationship between application terminal commands and device terminal commands, and sends the device terminal command to the corresponding device terminal via topic subscription. Upon receiving the device terminal command, it verifies it. After successful verification and confirmation of its validity, it generates a CAN message based on the device terminal command for control. After execution, it sends an error code back to the vehicle network platform and converts the error code into an application terminal response result, which is then fed back to the application terminal.

[0169] Based on the same inventive concept, another embodiment of the present invention provides a vehicle-side remote control system. For example... Figure 5 As shown, the system 500, applied to a vehicle networking platform, includes:

[0170] The application instruction receiving module 501 is used to receive application instructions sent by the first standard software package of the application.

[0171] The device instruction determination module 502 is used to determine the device instruction and target device corresponding to the application instruction based on the target mapping relationship.

[0172] The device-side instruction sending module 503 is used to send the device-side instruction to the target device-side, so as to control the second standard software package in the target device-side to determine the vehicle-side control instruction corresponding to the device-side instruction based on the executable file in the target device-side.

[0173] Optionally, the system 500 further includes:

[0174] The model definition file determination module is used to construct the terminal object models of each device corresponding to the vehicle model, so as to obtain the model definition files corresponding to each vehicle model;

[0175] The model definition file sending module is used to send each model definition file to the second standard software package on the device side of the corresponding vehicle model for parsing, so as to obtain the executable file on each device side.

[0176] Optionally, the system 500 further includes:

[0177] The application-side remote control and vehicle condition function list determination module is used to determine the remote control and vehicle condition function list corresponding to the vehicle model based on the vehicle model corresponding to the application-side.

[0178] The instruction list determination module is used to determine the instruction list of the vehicle model based on the remote control and the vehicle condition function list;

[0179] The application-side function code construction module is used to construct the application-side function code of the application based on the instruction list, and send the application-side function code to the first standard software package integrated in the target application of the application.

[0180] Optionally, the device-side instruction determination module includes:

[0181] The application-side instruction parsing module is used to obtain the instruction code and vehicle identification code in the application-side instruction by parsing the application-side instruction;

[0182] The device instruction determination submodule is used to determine the device instruction corresponding to the instruction code according to the target mapping relationship, wherein the target mapping relationship is a one-to-one correspondence between each instruction code and each device instruction;

[0183] The target device determination module is used to determine the target device corresponding to the vehicle identification code based on the vehicle identification code.

[0184] Optionally, the system 500 further includes:

[0185] An error code receiving module is used to receive error codes reported by the second standard software package, wherein the error codes are fed back by the target controller executing the vehicle-side control command;

[0186] The execution result reporting module is used to determine the execution result corresponding to the error code based on the error code, and report the execution result to the application terminal.

[0187] Optionally, the second standard software package in the system 500 is the same standard software package that is configured on the device side of all vehicle models.

[0188] Optionally, the system 500 further includes:

[0189] The first receiving module is used to receive the encrypted application terminal instruction obtained by encrypting the generated application terminal instruction according to the first standard software package of the application terminal using an asymmetric encryption algorithm;

[0190] The first encryption verification module is used to verify the encrypted application terminal instructions according to the asymmetric encryption algorithm.

[0191] The execution module, upon successful verification, performs the following: determining the device-side instruction and target device corresponding to the application-side instruction based on the target mapping relationship.

[0192] Optionally, the system 500 further includes:

[0193] The first encryption module is used to encrypt the device-side instructions using the asymmetric encryption algorithm.

[0194] The first sending module is used to send the encrypted device-side command to the target device.

[0195] The first control module is used to control the target device to verify the encrypted device-side command based on the asymmetric encryption algorithm;

[0196] The second control module, upon successful verification, controls the second standard software package in the target device to determine the vehicle-side control command corresponding to the device-side command based on the executable file in the target device.

[0197] Based on the same inventive concept, another embodiment of the present invention provides a vehicle-side remote control system applied to a target device, the system comprising:

[0198] The device-side instruction receiving module is used to receive instructions from the device side.

[0199] The vehicle-side control command determination module is used to determine the vehicle-side control command corresponding to the device-side command based on the execution file and through a second standard software package. The execution file is obtained by the second standard software package by parsing the model definition file sent by the vehicle networking platform.

[0200] The control module is used to control the corresponding target controller to perform corresponding control operations through the vehicle-side control commands.

[0201] Optionally, the system further includes:

[0202] The reporting condition determination module is used to determine, based on the executable file and using the second standard software package, whether the received monitoring data meet the reporting conditions for each event.

[0203] The event reporting module is used to report the target event when all the monitoring data meet the reporting conditions of the target event.

[0204] Based on the same inventive concept, another embodiment of the present invention provides a vehicle-side remote control system for application purposes, the system comprising:

[0205] The application-side command triggering module is used to trigger the issuance of application-side commands through the target application.

[0206] The application-side instruction generation module is used to generate corresponding application-side instructions based on the trigger operation using the first standard software package in the application.

[0207] The application-side instruction sending module is used to send the application-side instructions through the first standard software package.

[0208] Based on the same inventive concept, another embodiment of the present invention provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program, when executed by the processor, implements the vehicle remote control method as described in the first aspect of the present invention.

[0209] Based on the same inventive concept, another embodiment of the present invention provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the vehicle remote control method as described in the first aspect of the present invention.

[0210] As the system implementation is basically similar to the method implementation, it is described in a relatively simple way. For relevant details, please refer to the description of the method implementation.

[0211] It should be noted that, for the sake of simplicity, the method embodiments are all described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0212] The various embodiments in this specification are described in a progressive manner, with each embodiment focusing on the differences from other embodiments. The same or similar parts between the various embodiments can be referred to each other.

[0213] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, embodiments of the present invention can take the form of entirely hardware embodiments, entirely software embodiments, or embodiments combining software and hardware aspects. Furthermore, embodiments of the present invention can take the form of computer program products implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0214] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, terminal devices (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing terminal device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing terminal device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0215] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing terminal device to operate in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0216] These computer program instructions can also be loaded onto a computer or other programmable data processing terminal equipment, causing a series of operational steps to be performed on the computer or other programmable terminal equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable terminal equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0217] Although preferred embodiments of the present invention have been described, those skilled in the art, upon learning the basic inventive concept, can make other changes and modifications to these embodiments. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments as well as all changes and modifications falling within the scope of the embodiments of the present invention.

[0218] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal device. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal device that includes said element.

[0219] The present invention has provided a detailed description of a vehicle-side remote control method, system, electronic device, and storage medium. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The descriptions of the above embodiments are only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, those skilled in the art will recognize that there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

Claims

1. A method for remotely controlling a vehicle end, characterized in that, The method is applied to a vehicle networking platform, and comprises the following steps: constructing each device-end object model corresponding to a vehicle model to obtain each model definition file corresponding to the vehicle model; sending the each model definition file to a second standard software package of a device end in the each corresponding vehicle model for analysis to obtain an execution file in each device end according to the each corresponding vehicle model of the each model definition file; determining a remote control and vehicle condition function list corresponding to the vehicle model according to the vehicle model corresponding to the application end; determining an instruction list of the vehicle model according to the remote control and the vehicle condition function list; constructing an application end function code of the application end according to the instruction list, and sending the application end function code to a first standard software package in a target application program integrated in the application end, the application end function code being used for configuring a remote control function of the application end; receiving an application end instruction sent by the first standard software package of the application end; determining a device end instruction and a target device end corresponding to the application end instruction according to a target mapping relationship; sending the device end instruction to the target device end to control the second standard software package in the target device end to determine a vehicle end control instruction corresponding to the device end instruction based on an execution file in the target device end; controlling a target controller in the target device end to perform a corresponding control operation according to the vehicle end control instruction; wherein the determining of the device end instruction and the target device end corresponding to the application end instruction according to the target mapping relationship comprises: obtaining an instruction code and a vehicle identification code in the application end instruction by analyzing the application end instruction; determining a device end instruction corresponding to the instruction code according to a target mapping relationship, the target mapping relationship being a one-to-one correspondence relationship between each instruction code and each device end instruction; determining a target device end corresponding to the vehicle identification code according to the vehicle identification code.

2. The method of claim 1, wherein, The controlling of the second standard software package in the target device end to determine the vehicle end control instruction corresponding to the device end instruction based on the execution file in the target device end comprises: controlling the second standard software package in the target device end to determine a vehicle end instruction code corresponding to the device end instruction and an execution condition corresponding to the vehicle end instruction code based on the execution file in the target device end; generating a corresponding vehicle end control instruction based on the vehicle end instruction code in a case where the execution condition is verified by the second standard software package.

3. The method of claim 2, wherein the vehicle end remote control method is characterized by, The method further comprises: receiving an error code reported by the second standard software package, the error code being fed back by a target controller executing the vehicle end control instruction; determining an execution result corresponding to the error code according to the error code, and reporting the execution result to the application end.

4. The method of claim any one of claims 1 to 3, wherein, The second standard software package is a same standard software package configured for device ends of all vehicle models.

5. The method of claim 1, wherein the vehicle end remote control method is characterized by, The method further comprises: the second standard software package in the target device end determines whether each item of monitoring data received satisfies a reporting condition of each event based on the execution file in the target device end; In the case that the monitoring data meets the reporting condition of the target event, the target event is reported.

6. The method of claim 1, wherein the vehicle end remote control method is characterized by, After receiving the application end instruction sent by the first standard software package of the application end, the application end instruction is encrypted and verified, including: The first standard software package of the application end encrypts the generated application end instruction according to the asymmetric encryption algorithm to obtain the encrypted application end instruction; The encrypted application end instruction is verified according to the asymmetric encryption algorithm; In the case of passing the verification, the step of determining the device end instruction corresponding to the application end instruction and the target device end according to the target mapping relationship is executed.

7. The method of claim 6, wherein the vehicle end remote control method is characterized by, The device end instruction is sent to the target device end to control the second standard software package in the target device end to determine the vehicle end control instruction corresponding to the device end instruction based on the execution file in the target device end, including: The device end instruction is encrypted by the asymmetric encryption algorithm; The encrypted device end instruction is sent to the target device end; The target device end controls the verification of the encrypted device end instruction based on the asymmetric encryption algorithm; In the case of passing the verification, the target device end controls the second standard software package in the target device end to determine the vehicle end control instruction corresponding to the device end instruction based on the execution file in the target device end.

8. A remote control system for a vehicle end, characterized in that Applied to a vehicle networking platform, the system comprises: A model definition file determination module is configured to construct each device end model corresponding to a vehicle model to obtain each model definition file corresponding to the vehicle model. A model definition file sending module is configured to send each model definition file to the second standard software package of the device end in the corresponding vehicle model according to the vehicle model corresponding to each model definition file to obtain the execution file in each device end. An application end remote control and vehicle condition function list determination module is configured to determine the remote control and vehicle condition function list corresponding to the vehicle model according to the vehicle model corresponding to the application end. An instruction list determination module is configured to determine the instruction list of the vehicle model according to the remote control and the vehicle condition function list. An application end function code construction module is configured to construct the application end function code of the application end according to the instruction list and send the application end function code to the first standard software package in the target application program integrated in the application end, and the application end function code is used for application end configuration remote control function. An application end instruction receiving module is configured to receive the application end instruction sent by the first standard software package of the application end. A device end instruction determination module is configured to determine the device end instruction corresponding to the application end instruction and the target device end according to the target mapping relationship. A device end instruction sending module is configured to send the device end instruction to the target device end to control the second standard software package in the target device end to determine the vehicle end control instruction corresponding to the device end instruction based on the execution file in the target device end. The device end instruction determination module comprises: An application end instruction analysis module is configured to obtain the instruction code and vehicle identification code in the application end instruction by analyzing the application end instruction. The device-side instruction determination sub-module is configured to determine a device-side instruction corresponding to the instruction code according to a target mapping relationship, the target mapping relationship being a one-to-one correspondence between each instruction code and each device-side instruction; The target device-side determination module is configured to determine a target device-side corresponding to the vehicle identification code according to the vehicle identification code.

9. An electronic device, comprising: The computer program is stored in the memory and executable on the processor, and when the computer program is executed by the processor, the vehicle-side remote control method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that The computer program is stored in the memory and executable on the processor, and when the computer program is executed by the processor, the vehicle-side remote control method according to any one of claims 1 to 7 is implemented.

Images