CN117931217A - Data processing method, server and vehicle-mounted terminal - Google Patents

Abstract

The embodiment of the application discloses a data processing method, a server and a vehicle-mounted terminal, wherein the method comprises the following steps: acquiring first software and hardware interface data related to a vehicle control function of a vehicle; generating a script model data file based on the first software and hardware interface data; the script model data file is used for realizing the vehicle control function of the corresponding vehicle; and sending the script model data file to the vehicle-mounted terminal of the corresponding vehicle so that the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data file. Therefore, the script model data file for realizing the vehicle control function is generated based on the first software and hardware interface data related to the vehicle control function of the vehicle, so that the suitability of the script model data file and the vehicle control function of the vehicle-mounted terminal is ensured, the vehicle-mounted terminal is prevented from carrying out secondary development after the script model data file is obtained, and the complexity of writing the follow-up scene into the vehicle-mounted terminal is reduced.

Description

Data processing method, server and vehicle-mounted terminal

Technical Field

The present application relates to the field of vehicle data processing technologies, and in particular, to a data processing method, a server, and a vehicle terminal.

Background

At present, some automobiles in the market have the function of executing corresponding automobile control operation according to set scenes, one is a program for solidifying the scenes into the automobiles, and the other is a scene engine technology, and the configuration of the scenes is carried out by appointing rules through automobile ends and cloud ends. The first approach can only pre-cure some scenes and then want to update the scene either to go to a 4S store for a program update or to use Over-the-Air Technology (OTA) upgrades to write new scenes. The second scheme can enable the cloud to configure the subsequent scenes and push the subsequent scenes to the vehicle end, but if the corresponding agreed rules are changed or added (if the cloud adds a new scene), the vehicle end is required to cooperate with the corresponding secondary development, and meanwhile, the vehicle end is required to carry out OTA (over the air) upgrading to support the corresponding processing logic, so that the complexity of writing the subsequent scenes is increased.

Disclosure of Invention

In view of this, the embodiment of the application provides a data processing method, which can reduce the complexity of writing the subsequent scene into the vehicle-mounted terminal.

The technical scheme of the application is realized as follows:

The embodiment of the application provides a data processing method, which comprises the following steps:

acquiring first software and hardware interface data related to a vehicle control function of a vehicle;

generating a script model data file based on the first software and hardware interface data; the script model data file is used for realizing the vehicle control function of the corresponding vehicle;

And sending the script model data file to a vehicle-mounted terminal of a corresponding vehicle, so that the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data file.

An embodiment of the present application provides a server, which is characterized by comprising:

The first acquisition module is used for acquiring first software and hardware interface data related to a vehicle control function of the vehicle;

the first generation module is used for generating a script model data file based on the first software and hardware interface data; the script model data file is used for realizing the vehicle control function of the corresponding vehicle;

And the first sending module is used for sending the script model data file to a corresponding vehicle so that the vehicle-mounted terminal of the corresponding vehicle executes corresponding vehicle control operation based on the script model data file.

An embodiment of the present application provides a vehicle-mounted terminal, which is characterized by comprising:

The first receiving module is used for receiving the script model data file sent by the server; the script model data file is generated by the server based on the acquired first software and hardware interface data related to the vehicle control function of the vehicle where the vehicle-mounted terminal is located; the script model data file is used for realizing the vehicle control function of the vehicle in which the vehicle-mounted terminal is positioned;

and the first execution module is used for executing corresponding vehicle control operation based on the script model data file.

An embodiment of the present application provides another server, including: a first memory and a first processor;

the first memory stores a computer program capable of running on the processor, and when the processor executes the computer program, the data processing method applied to the server provided by the embodiment of the application is realized.

An embodiment of the present application provides another server, including: a second memory and a second processor;

The second memory stores a computer program capable of running on the processor, and when the processor executes the computer program, the data processing method applied to the vehicle-mounted terminal provided by the embodiment of the application is realized.

The embodiment of the application provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the data processing method applied to a server or the data processing method applied to a vehicle-mounted terminal provided by the embodiment of the application.

The embodiment of the application provides a data processing method, a server and a vehicle-mounted terminal, and by adopting the technical scheme, first software and hardware interface data related to a vehicle control function of a vehicle are acquired; generating a script model data file based on the first software and hardware interface data; the script model data file is used for realizing the vehicle control function of the corresponding vehicle; and sending the script model data file to the vehicle-mounted terminal of the corresponding vehicle so that the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data file. Therefore, the script model data file for realizing the vehicle control function is generated based on the first software and hardware interface data related to the vehicle control function of the vehicle, so that the suitability of the script model data file and the vehicle control function of the vehicle-mounted terminal is ensured, the vehicle-mounted terminal is prevented from carrying out secondary development after the script model data file is obtained, and the complexity of writing the follow-up scene into the vehicle-mounted terminal is reduced.

Drawings

FIG. 1 is a schematic flow chart of a data processing method according to an embodiment of the present application;

FIG. 2 is a flowchart illustrating another data processing method according to an embodiment of the present application;

FIG. 3 is a schematic flow chart of a method for implementing a dynamic scene engine of a vehicle according to an embodiment of the present application;

FIG. 4 is a schematic diagram of a process flow of a scene engine service according to an embodiment of the present application;

Fig. 5 is a schematic diagram of a composition structure of a server according to an embodiment of the present application;

fig. 6 is a schematic diagram of a composition structure of a vehicle-mounted terminal according to an embodiment of the present application;

fig. 7 is a schematic diagram of a composition structure of another server according to an embodiment of the present application;

Fig. 8 is a schematic diagram of a composition structure of another vehicle-mounted terminal according to an embodiment of the present application.

Detailed Description

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application.

The present application will be further described with reference to the accompanying drawings, in order to make the objects, technical solutions and advantages of the present application more apparent, and the described embodiments should not be construed as limiting the present application, and all other embodiments obtained by those skilled in the art without making any inventive effort are within the scope of the present application.

In the following description, reference is made to "some embodiments\other embodiments" which describe a subset of all possible embodiments, but it is to be understood that "some embodiments\other embodiments" can be the same subset or different subsets of all possible embodiments and can be combined with each other without conflict.

In the following description, the terms "first", "second", and the like are merely used to distinguish between similar objects and do not represent a particular ordering of the objects, it being understood that the "first", "second", or the like may be interchanged with one another, if permitted, to enable embodiments of the application described herein to be practiced otherwise than as illustrated or described herein.

Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of the application only and is not intended to be limiting of the application.

Based on the problems existing in the related art, the embodiment of the application provides a data processing method, which can be applied to a server, and the server can be a cloud server. Fig. 1 is a schematic flow chart of a data processing method according to an embodiment of the present application, where the method includes the following steps:

S101, acquiring first software and hardware interface data related to a vehicle control function of a vehicle.

It should be noted that the first software/hardware interface data may be data obtained from a first software/hardware interface, and the first software/hardware interface data may be an interface method, an in parameter, an out parameter, a verification parameter, etc. related to the vehicle control function. The first software and hardware interfaces include a software interface and a hardware interface, the software interface may include a function interface, a class interface, a controller application program interface (Application Programming Interface, API), etc., the hardware interface may include a communication interface, a data transmission interface, etc., and the first software and hardware interface may be a device operation interface, an abstraction interface, etc. related to a vehicle control function. The vehicle control functions include control of hardware devices of the vehicle (e.g., doors, seats, air conditioners, etc.), and may also include control of on-board software (e.g., music, navigation, fm radio, etc.).

In some embodiments, the first software and hardware interface data related to the vehicle control function of the vehicle may be acquired in real time, continuously or periodically, so as to obtain the first software and hardware interface data of the latest version of the vehicle, so that a scene scenario adapted to the current function of the vehicle may be generated based on the first software and hardware interface data of the latest version.

In some embodiments, the first software and hardware interface data of a plurality of different vehicles may be obtained by an automobile manufacturer or other third parties, and the first software and hardware interface data of each vehicle of a unified vehicle type is the same or similar, so after a large amount of first software and hardware interface data is obtained, the first software and hardware data of the same vehicle type may be correspondingly stored in a preset storage area.

S102, generating a script model data file based on the first software and hardware interface data.

It should be noted that the scenario model data file may be used to implement a vehicle control function of the corresponding vehicle. The scenario model data file may include identification information of vehicles and/or vehicle models, and scene information or scenario related to a vehicle control function, such as execution conditions, trigger conditions, etc. of the scene. The identification information of the vehicle may be a vehicle identification number (Vehicle Identification Number, VIN).

In some embodiments, after the first software and hardware data is obtained, the first software and hardware data may be parsed to obtain the control scene source data, where the control scene source data may be source data for generating a scene scenario, and after the control scene source data is obtained, a scenario model data file may be created based on the control scene source data and identification information of the vehicle.

And S103, transmitting the script model data file to the vehicle-mounted terminal of the corresponding vehicle, so that the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data file.

In some embodiments, the scenario model data file may be sent to the vehicle-mounted terminal by active pushing, or based on a scenario information acquisition request of the vehicle-mounted terminal. The scene information acquisition request is used for acquiring a scenario model data file. The vehicle-mounted terminal can acquire the script model data file sent by the server through power-on pulling or normal networking, and execute corresponding vehicle control operation according to the acquired script model data file.

In some embodiments, the cloud server may determine, based on the identification information of the vehicle in which the vehicle-mounted terminal is located, or the model identification information of the vehicle in which the vehicle-mounted terminal is located, a scenario model data file of the vehicle in which the vehicle-mounted terminal is located at present, where the identification information of the vehicle or the model identification information of the vehicle may be obtained in advance, or may be sent in real time by the vehicle-mounted terminal in which the vehicle is located.

In the embodiment of the application, first software and hardware interface data related to a vehicle control function of a vehicle are acquired; generating a script model data file based on the first software and hardware interface data; the script model data file is used for realizing the vehicle control function of the corresponding vehicle; and sending the script model data file to the vehicle-mounted terminal of the corresponding vehicle so that the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data file. Therefore, the script model data file for realizing the vehicle control function is generated based on the first software and hardware interface data related to the vehicle control function of the vehicle, so that the suitability of the script model data file and the vehicle control function of the vehicle-mounted terminal is ensured, the vehicle-mounted terminal is prevented from carrying out secondary development after the script model data file is obtained, and the complexity of writing the follow-up scene into the vehicle-mounted terminal is reduced.

In some embodiments of the present application, the scenario model data file is generated based on the vehicle control capability interface data, that is, step S102 may be implemented through steps S1021 to S1023 described below, and each step is described below.

S1021, analyzing the first software and hardware interface data to obtain vehicle control scene source data.

In some embodiments, the vehicle control scene source data may include a vehicle control function that the vehicle can currently implement, and the parsing of the first software and hardware interface data may be performing an escape process on the first software and hardware interface data, for example, analyzing a parameter entering, a parameter exiting, an interface method, and the like of the first software and hardware interface to determine the vehicle control function implemented by the first software and hardware interface.

S1022, determining scene attributes and scene rules based on the vehicle control scene source data.

In some embodiments, the scene attribute may include an interval time, a recommended number of times, an execution period, a running time, and the like of execution of the scene scenario, and the scene rule may include information such as an execution condition, an execution flow, and the like of the scene scenario. The method can analyze and process based on the vehicle control scene source data, generate scene rules, define scene attributes of the scene script and the like.

S1023, generating a script model data file according to the scene attribute and the scene rule.

In some embodiments, the scene attribute and the scene rule of different vehicles or different vehicle types may be different, so that the identification information of the vehicle where the vehicle-mounted terminal is located may be obtained, and the scene attribute and the scene rule associated with the vehicle where the vehicle-mounted terminal is located are determined according to the identification information. And generating scenario model file data of the vehicle in which the vehicle-mounted terminal is positioned according to the identification information, the scene attribute and the scene rule associated with the vehicle in which the vehicle-mounted terminal is positioned. When the method is realized, the identification information, the scene attribute and the scene rule of the vehicle where the vehicle-mounted terminal is located can be fused, so that the scenario model data file is obtained.

In some embodiments of the present application, the following steps S201 to S202 may be further performed before or after the step S101 of acquiring the first software/hardware interface data related to the vehicle control function of the vehicle, and each step is described below.

S201, receiving a scene data file sent by the vehicle-mounted terminal.

It should be noted that, the scene data file is generated by the vehicle-mounted terminal based on the second software and hardware interface data related to the vehicle control function in the vehicle where the vehicle-mounted terminal is located, and the first software and hardware interface data and the second software and hardware interface data are different. The second software interface may be complex or additionally encapsulated data relating to the vehicle control functions of the vehicle terminal. The second software-hardware interface data may be data obtained from a second software-hardware interface, and the first software interface and the second software interface may be different or the same. The second software and hardware interface data may also include interface methods, parameter entries, parameter exits, verification parameters, etc. related to the vehicle control function. The second software and hardware interface and the first software and hardware interface have the same attribute and can comprise a software interface and a hardware interface, the software interface can comprise a functional function interface, a class interface, a controller API and the like, the hardware interface can comprise a communication interface, a data transmission interface and the like, and the second software and hardware interface can also be a device operation interface, an abstract interface and the like related to a vehicle control function.

In some embodiments, for complex or additionally developed vehicle control functions, the vehicle-mounted terminal may generate a corresponding scene data file according to the obtained first software and hardware interface data, where the scene data file may be similar to the scenario model data file, and may include contents such as an execution condition and a trigger condition of the scenario. After determining the scene data file, the in-vehicle terminal may transmit the scene data file to the server.

S202, sending the scene data file to the vehicle-mounted terminals of other vehicles of the same vehicle type as the vehicle-mounted terminal, so that the vehicle-mounted terminals of the other vehicles execute corresponding vehicle control operation based on the scene data file.

In some embodiments, since the configuration of the vehicle control functions of the same vehicle type is the same, after the scene data file sent by the vehicle-mounted terminal is obtained, the scene data file may be sent to the vehicle-mounted terminals of other vehicles of the same vehicle type as the vehicle in which the current vehicle-mounted terminal is located, so that the vehicle-mounted terminals of the other vehicles may execute corresponding vehicle control operations based on the scene data file after the scene data file is obtained.

It can be understood that the scene data file generated by the vehicle-mounted terminal is sent to the vehicle-mounted terminals of other vehicles of the same vehicle type as the vehicle in which the vehicle-mounted terminal is positioned, so that the vehicle-mounted terminals of the other vehicles can obtain the scene data file, the vehicle-mounted terminals of the other vehicles do not need to generate the same scene data file based on the second software and hardware interface data of the vehicle-mounted terminals of the other vehicles, and the scene richness of the other vehicles of the same vehicle type is improved.

In some embodiments of the present application, the scenario model data file includes at least one, that is, the scenario model data file sent to the vehicle-mounted terminal may include one or more, and after the scenario model data file is sent to the vehicle-mounted terminal of the corresponding vehicle, so that the vehicle-mounted terminal performs the corresponding vehicle control operation based on the scenario model data file, that is, after step S101, the following steps S301 to S302 may be further performed, and each respective step is described below.

S301, confidence information of each scenario model data file sent by a vehicle-mounted terminal of a vehicle is obtained.

The confidence information is determined by user feedback information obtained after the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data file. The confidence information is used to indicate the user's acceptability level for the corresponding transcript model data file.

In some embodiments, the vehicle-mounted terminal may actively send the confidence information corresponding to each scenario to the server, or the server may send a feedback information acquisition request to the vehicle-mounted terminal, where the vehicle-mounted terminal sends the confidence information corresponding to each scenario to the server based on the feedback information acquisition request.

S302, updating at least one scenario model data file based on the confidence information.

In some embodiments, the confidence information includes confidence levels for each transcript model data file, the confidence levels being indicative of the user's acceptability of the transcript model data file.

In some embodiments, a higher confidence level indicates a higher user acceptability to the transcript model data file, for example. If the confidence level is divided into a first level, a second level and a third level, the third level indicates that the user has the highest acceptable degree on the script model data file.

In other embodiments, a higher confidence level indicates a lower user acceptability with the transcript model data file. For example, if the confidence level is divided into a first, second, and third level, the first level indicates that the user has the highest level of acceptability to the transcript model data file.

In some embodiments, when updating at least one scenario model data file based on the confidence information, it may be determined whether the confidence level of the scenario model data file satisfies a preset condition. The preset condition may be the lowest acceptable level of the user, and if the execution degree level is classified into one level, two levels and three levels, the confidence degree level satisfying the preset condition may be that the confidence degree reaches one level, if the confidence degree level is higher, the higher the confidence degree indicates the acceptable level; in the case where a higher confidence level indicates a lower acceptable level, if the execution level is classified into a first level, a second level, and a third level, the confidence level satisfying the preset condition may be that the confidence level reaches the third level.

In some embodiments, if it is determined that the confidence level of the scenario model data file meets the preset condition, it is indicated that the user has a lower acceptable level for the current scenario model data file, and the corresponding scenario model data file may be deleted.

It can be understood that when the confidence level of the scenario model data file is determined to meet the preset condition, the corresponding scenario model data file is deleted, so that the scenario model data file is updated according to the preference of the user, and the user experience is improved.

Fig. 2 is a schematic flow chart of another data processing method according to an embodiment of the present application, where the method relates to an interaction process between a server and a vehicle terminal, and the data processing method is described below by taking fig. 2 as an example.

S401, receiving a script model data file sent by a server.

The scenario model data file is generated by the server based on the acquired first software and hardware interface data related to the vehicle control function of the vehicle where the vehicle-mounted terminal is located. The script model data file is used for realizing the vehicle control function of the vehicle where the vehicle-mounted terminal is located.

In some embodiments, the vehicle-mounted terminal may pull the scenario model data file sent by the server after power-up, or may pull the scenario model data file sent by the server after normal networking.

In some embodiments, the foregoing steps S101 to S103 may also be sequentially performed before step S401.

S101, acquiring first software and hardware interface data related to a vehicle control function of a vehicle.

In some embodiments, the server may acquire the first software and hardware interface data related to the vehicle control function of the vehicle in real time, continuously or periodically, so as to acquire the first software and hardware interface data of the latest version of the vehicle, so that a scenario adapted to the current function of the vehicle may be generated based on the first software and hardware interface data of the latest version.

In some embodiments, the first software and hardware interface data of a plurality of different vehicles may be obtained by an automobile manufacturer or other third parties, and the first software and hardware interface data of each vehicle of a unified vehicle type is the same or similar, so after a large amount of first software and hardware interface data is obtained, the first software and hardware data of the same vehicle type may be correspondingly stored in a preset storage area.

S102, generating a script model data file based on the first software and hardware interface data.

In some embodiments, after obtaining the first software and hardware data, the server may parse the first software and hardware data to obtain the vehicle control scene source data, where the vehicle control scene source data may be source data for generating a scene scenario, and after obtaining the vehicle control scene source data, may create a scenario model data file based on the vehicle control scene source data and identification information of the vehicle.

And S103, transmitting the script model data file to the vehicle-mounted terminal of the corresponding vehicle, so that the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data file.

In some embodiments, the server may send the scenario model data file to the vehicle-mounted terminal through active pushing, or based on a scenario information acquisition request of the vehicle-mounted terminal. The scene information acquisition request is used for acquiring a scenario model data file. The vehicle-mounted terminal can acquire the script model data file sent by the server through power-on pulling or normal networking, and execute corresponding vehicle control operation according to the acquired script model data file.

In some embodiments, the cloud server may determine, based on the identification information of the vehicle in which the vehicle-mounted terminal is located, or the model identification information of the vehicle in which the vehicle-mounted terminal is located, a scenario model data file of the vehicle in which the vehicle-mounted terminal is located at present, where the identification information of the vehicle or the model identification information of the vehicle may be obtained in advance, or may be sent in real time by the vehicle-mounted terminal in which the vehicle is located.

After step S103, the following step S402 may also be performed.

S402, executing corresponding vehicle control operation based on the script model data file.

In some embodiments, after receiving the scenario model data file sent by the server, the vehicle-mounted terminal may execute a corresponding vehicle control operation according to the scenario triggering condition and the scenario triggering logic defined in the scenario model data file.

In some embodiments, after receiving the scenario model data file of the vehicle-mounted terminal, the vehicle-mounted terminal may further update a scenario model data file previously in advance in the local area of the vehicle-mounted terminal based on the scenario model data file to obtain an updated scenario model data file; and executing corresponding vehicle control operation based on the updated script data file.

For example, in some embodiments, the obtained scenario model data file may be compared with a locally stored scenario model data file, and if a new scenario model data file different from the local scenario model data file exists, the new scenario model data file is added to the local scenario model data file list; and if a first script model data file which is different from the received script model data file exists in the local script model data file list, deleting the first script model data file from the local script model data file list.

It can be understood that, because the script model data file received by the vehicle-mounted terminal is generated by the server based on the acquired first software and hardware interface data related to the vehicle control function of the vehicle where the vehicle-mounted terminal is located, the vehicle-mounted terminal can execute the corresponding vehicle control function based on the script model data file without secondary development, thereby reducing the complexity of writing the scene script.

In some embodiments of the present application, the scenario model data file includes at least one, and after performing the corresponding vehicle control operation based on the scenario model data file, the following steps S501 to S503 may be further performed, and each step is described below.

S501, obtaining user feedback information obtained after corresponding vehicle control operation is executed based on the script model data file.

In some embodiments, the user feedback information may include acceptance, cancellation, timeout, etc. of performing the corresponding vehicle control operation based on the scenario model data file, and the vehicle-mounted terminal may actively collect feedback information of the user on each scenario model data file, for example, whether the user receives the execution operation based on the current scenario model data file, whether the user cancels the execution operation based on the current scenario model data file, or whether the user does not perform feedback based on the execution operation of the current scenario model data file within a preset time period.

S502, according to user feedback information, confidence information of each script model data file is determined.

In some embodiments, confidence information is used to indicate the user's acceptability level for the corresponding scenario model data file. The confidence information may include a confidence level that indicates the user's acceptability with respect to the transcript model data file.

In some embodiments, a higher confidence level indicates a higher user acceptability to the transcript model data file, for example. If the confidence level is divided into a first level, a second level and a third level, the third level indicates that the user has the highest acceptable degree on the script model data file.

In other embodiments, a higher confidence level indicates a lower user acceptability with the transcript model data file. For example, if the confidence level is divided into a first, second, and third level, the first level indicates that the user has the highest level of acceptability to the transcript model data file.

In some embodiments, the execution mode of the scenario model data file may be classified into direct execution and query execution, and when the execution mode of the scenario model data file is direct execution, the in-vehicle terminal may immediately execute scenario operations in an order specified by the engine. When the execution mode of the scenario model data file is query execution, the vehicle-mounted terminal can decide whether to execute the scenario operation according to feedback of a user.

In some embodiments, the vehicle-mounted terminal may first determine a confidence level of the user for the scenario model data file, and determine a confidence level according to the confidence level. The confidence value range can be divided into a plurality of confidence levels according to the confidence values, for example, if the execution degree value range is [0, 100], the confidence value with the value of [0, 30] can be determined as one level; the confidence level of (30, 80) is determined as a second level and the confidence level of (80, 100) is determined as a third level.

Illustratively, after the user makes the corresponding feedback (accept/cancel/timeout), the user's confidence in the transcript model data file may change in an exponential order of 2: when the user continuously feeds back forward (accepts) N times, the confidence increases by power N of 2. Vice versa, when the user continuously feeds back negatively (cancel or timeout) N times, the confidence decreases by power of 2N. Wherein N is an integer greater than 1. When the user feedback is discontinuous (e.g., last positive, next negative), N again starts from 1. The continuous count of N is not affected after crossing confidence levels. For example, the initial confidence is at the second level (confidence level), and after 3 times of forward feedback, the confidence reaches a level exceeding the second level to the first level, and at this time, after the forward feedback again, the step size increases to the 3-th power of 2.

And S503, sending the confidence information to a server so that the server updates each script model data file based on the confidence information.

In some embodiments, after determining the confidence information of each scenario model data file, the vehicle-mounted terminal may send the confidence information of each scenario model data file to the server, so that the server may update each scenario model data file according to the confidence information.

In some embodiments of the present application, the following steps S601 to S603 may also be performed before or after receiving the scenario model data file sent by the server, i.e. step S501, and each step is described below separately.

S601, acquiring second software and hardware interface data related to a vehicle control function of a vehicle where the vehicle-mounted terminal is located.

The second software and hardware interface data is different from the first software and hardware interface data. The second software-hardware interface data may be data obtained from a second software-hardware interface, and the first software interface and the second software interface may be different or the same. The second software and hardware interface data may also include interface methods, parameter entries, parameter exits, verification parameters, etc. related to the vehicle control function. The second software and hardware interface and the first software and hardware interface have the same attribute and can comprise a software interface and a hardware interface, the software interface can comprise a functional function interface, a class interface, a controller API and the like, the hardware interface can comprise a communication interface, a data transmission interface and the like, and the second software and hardware interface can also be a device operation interface, an abstract interface and the like related to a vehicle control function.

In some embodiments, the vehicle-mounted terminal may acquire, in real time, or continuously acquire, or periodically acquire second software and hardware interface data related to a vehicle control function of the vehicle in which the vehicle-mounted terminal is located through the third party device or the vehicle in which the vehicle-mounted terminal is located. The second software and hardware interface data may be complex or additionally encapsulated data related to the vehicle control function.

S602, generating a scene data file based on the second software and hardware interface data.

In some embodiments, the scenario data file may be a scenario file generated based on complex or additionally packaged energy data related to vehicle control functions, and the scenario file may include contents such as execution conditions, execution flows and the like of the scenario, similar to the scenario model data file.

And S603, storing the scene data file, and sending the scene data file to a server so as to transmit the scene data file to the vehicle-mounted terminal of other vehicles of the same vehicle type as the vehicle-mounted terminal through the server.

In some embodiments, the vehicle-mounted terminal may store the scene data file created by itself, so that the corresponding vehicle control operation is performed based on the scene data file after the scene trigger condition is met later. In addition, the vehicle-mounted terminal can also send the scene data file to the server, so that the server can send the scene data file to the vehicle-mounted terminals of other vehicles with the same vehicle type as the vehicle-mounted terminal, and the vehicle-mounted terminals of other vehicles can execute corresponding vehicle control operation directly based on the scene data file.

It can be understood that the scene data file is generated based on the acquired second software and hardware interface data, so that the server is prevented from processing complex, additionally developed or unsuitable functional data of the vehicle end, a more comprehensive scene script can be obtained, and the user experience is improved.

In the embodiment of the application, first software and hardware interface data related to a vehicle control function of a vehicle are acquired; generating a script model data file based on the first software and hardware interface data; the script model data file is used for realizing the vehicle control function of the corresponding vehicle; and sending the script model data file to the vehicle-mounted terminal of the corresponding vehicle so that the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data file. Therefore, the script model data file for realizing the vehicle control function is generated based on the first software and hardware interface data related to the vehicle control function of the vehicle, so that the suitability of the script model data file and the vehicle control function of the vehicle-mounted terminal is ensured, the vehicle-mounted terminal is prevented from carrying out secondary development after the script model data file is obtained, and the complexity of writing the follow-up scene into the vehicle-mounted terminal is reduced.

Next, an implementation process of the application embodiment in an actual application scenario is described.

In some embodiments, as shown in fig. 3, a flow chart of a method for implementing a vehicle dynamic scene engine according to an embodiment of the present application is provided, and the method relates to an interaction process between a vehicle end and a cloud end, and may be implemented through the following steps S701 to S704, and the method is described below with reference to fig. 3.

S701, the cloud scene engine manages and configures an equipment operation interface or an abstract capability interface (equivalent to the first software and hardware interface data in other embodiments) of the vehicle end, and finally realizes the escape processing from cloud configuration to the script.

In some embodiments, the cloud may configure one or more scenarios based on the device operation interface or the abstract capability interface (equivalent to "generate scenario model data file based on the first software and hardware interface data" in other embodiments), the specific configuration includes: scene name, scene description, scene classification, scene execution period, maximum recommended number, minimum pushing interval (minutes), priority coding SwitchNumbers (continuous accepting/rejecting number), orientation information, uploading script/dynamic scenario rule generation and other elements, and finally forming the scene scenario. The dynamic scenario generation rule generates a corresponding scenario according to judgment conditions (a certain time/place/person occurrence/time occurrence) configured by personnel, logic conditions (any condition is met/all conditions are met), an operation (vehicle/application) is executed, an execution mode (automatic execution/query execution) is adopted to generate the corresponding scenario, and meanwhile, the scenario is issued to a vehicle end in an orientation range (manual assignment/group circle selection/unlimited mode and the like) by means of a vehicle cloud communication technology.

The equipment operation interface of the vehicle end is continuously collected through the cloud end, the continuous expansion of the scene capability and the continuous optimization of the scene script can be realized without changing the vehicle end, and the subsequent expansion is greatly facilitated. In addition to the directional pushing of the cloud management engine and the feedback of the user operation behaviors, the cloud also provides a series of auxiliary judging and calculating capabilities, analyzes and deduces the user intention, controls the life cycle of the scene scenario and the like.

S702, configuring scene rules by a vehicle-end scene engine, and generating scene configuration in a script uploading mode.

In some embodiments, the vehicle-end scene engine may continuously collect the device interface (corresponding to "acquiring second software and hardware interface data related to the vehicle and the vehicle control function where the vehicle-mounted terminal is located" in other embodiments), collect the combined command additionally packaged by the vehicle-end, and perform scene rule configuration on the collected data (corresponding to "generating a scene data file based on the second software and hardware interface data" in other embodiments), so that capability expansion of the scene script can be realized without updating and iterating, and the SDK may abstract the vehicle-end device operation interface according to the characteristic requirement, so that usability and expansibility are greatly improved.

In some embodiments, step S701 and step S702 may be performed simultaneously, or step S701 is performed before step S702, or step S701 is performed after step S702.

S703, matching the scenario script information which is matched and oriented by the cloud end through the frame number, and assembling a script model data file to be sent to the vehicle end.

In some embodiments, the vehicle end may report the VIN code to the cloud end, after the cloud end obtains the VIN code of the vehicle end, the cloud end may determine scenario information corresponding to the vehicle end according to the VIN code, perform escape processing based on the scenario information to obtain scenario model data files, and issue the scenario model data files to the vehicle end.

S704, analyzing the script model data file to obtain a script model after the vehicle end receives the scene package, comparing the local script model, updating the local script model, and identifying the scene script in the script model.

In some embodiments, after the vehicle end receives the scenario model data file sent by the cloud end, analysis is performed to obtain a scenario model, the scenario model is compared with a scenario model stored locally, and the scenario model stored locally is updated, so that the scenario model stored locally is consistent with the scenario model sent by the cloud end (which is equivalent to 'updating a scenario model data file in advance in the vehicle terminal locally based on the scenario model data file, so as to obtain an updated scenario model data file'), and then the scenario model after the update is identified to obtain a scenario, and the scenario is stored.

Illustratively, the scene scenario includes the following scene scenario factors:

(1) The triggering condition-the judging condition generated by the cloud according to the condition capability and the logic capability refers to a condition set for judging whether a scenario is triggered or not. The engine makes a real-time decision on the current conditions to decide whether or not execution of the scenario will take place. The trigger condition is typically a combination of multiple strips and forms an and/or relationship according to the logic condition.

When the trigger condition is satisfied, the scenario enters arbitration. Arbitration is a pre-execution decision of multiple scenarios waiting to be executed at the same time to determine which scenarios are executed first, which scenarios are executed later, and which service scenarios are executed (which scenarios are not executed). The arbitration logic includes execution cycles, maximum recommended number of times, minimum push interval (minutes), and priority encoding.

(2) Execution cycle-each time, each ignition cycle, daily, weekly, monthly; refers to a defined range of unit time periods.

(3) The maximum recommended number of times-refers to the number of times that the recommended execution scenario is maximally available for the limited unit time period range.

(4) Minimum time interval (minutes) -refers to the time that the scenario has met the trigger condition from the last trigger execution minimum interval.

(5) Priority coding-means that when a plurality of scripts are triggered to be executed at the same time, the vehicle-end engine executes the scripts in sequence according to the serial numbers of the priority coding.

(6) The execution mode-execution mode is divided into automatic execution and query execution, including (voice/display/voice & display), and the final execution mode is determined according to the configuration execution mode of the script and user operation feedback.

1) When the execution mode of the script is direct execution, the vehicle end immediately executes the script operation according to the sequence appointed by the engine.

2) When the execution mode of the scenario is query execution, the vehicle end decides whether to execute the scenario operation according to the feedback of the user.

In some embodiments, the query card includes a title, content for executing the query, a positive feedback button, and a negative feedback button. And recording user operation feedback records according to button selections of a user so as to facilitate the decision condition of the execution mode when the scenario is triggered subsequently.

In some embodiments, the vehicle end can determine to execute the execution operation in the scene scenario by combining the multidimensional sensing information such as the vehicle body sensor, the map navigation, the time, the weather and the like with the judgment condition statement configured in the scene scenario, the execution operation comprises the vehicle and the application, the corresponding execution mode is calculated and evolved according to the execution mode (automatic execution/query execution) of the scene scenario before the execution operation is executed, the operation record feedback of the user is combined, and finally the corresponding operation can be executed according to the execution statement, so that better experience is brought to the user.

In some embodiments, a cloud scene engine configuration platform and a vehicle-end scene engine SDK form a vehicle cloud scene engine, as shown in fig. 4, which is a schematic diagram of a processing flow of a scene engine service provided by an embodiment of the present application, and a processing procedure of the scene engine service provided by the present application is described below by taking fig. 4 as an example.

S801, continuously collecting scene capability by the cloud end and analyzing the scene capability.

Wherein the scenario capability includes data obtained from a device operation interface and an abstract capability interface. Parsing may be the identification of data obtained from the device operation interface and the abstract capability interface.

S802, creating scene basic attributes and high-level rules by the cloud.

The cloud may construct scene data based on the parsed scene capabilities, including high-level rules of the scene, such as execution conditions, execution logic, etc. of the scene, and basic attributes of the scene may include execution cycle, runtime, recommended number of times, etc. of the scene.

S803, generating a scene scenario and issuing the scene scenario to a vehicle end.

The cloud end can generate a scene script based on the created scene basic attribute and the high-level rule, and transmit the scene script to the vehicle end in an active issuing or passive issuing mode.

S804, the vehicle end pulls up the latest scenario list through pushing or powering up.

After the vehicle end is powered on or after the network is normally connected, the latest scenario list sent by the server can be pulled.

S805, triggering the controller API in real time.

And the vehicle end can trigger the controller API after determining that the trigger condition is met according to the obtained latest scenario list.

S806, judging whether the execution mode of the script is automatic execution or not.

If it is determined that the execution mode of the scenario is automatic, the following step S807 is executed; if the scenario is executed in the inquiry mode, the following steps S808 to S809 are executed.

S807, executing the script operation statement according to the execution mode.

The implementation manner may include voice, display, or voice plus display, and the script operation statement may be implemented by voice, display, or voice plus display.

S808, judging whether the feedback information of the user is accepted.

If yes, go to step S807; otherwise, if the feedback information of the user is timeout or no response, the following step S809 is performed.

S809, not executing the script operation statement.

In some embodiments, after determining that the operation sentence is not executed, the scenario list locally stored in the vehicle-mounted terminal may be updated based on the feedback information of the user, for example, a scenario in which the feedback information of the user is timeout or no response is deleted from the scenario list.

In some embodiments, the confidence value of each scene can be calculated according to the feedback of the user, so that the scene engine can continuously evolve, the cloud end can enable the user experience to be better, and the intelligent scene service can intelligently push corresponding scene scenario operations according to the current state of the user.

In some embodiments, the scene may be a plurality of user groups, the operation in cloud big data and car interaction will make the owner user to make a plurality of labels, the cloud will define crowd portraits of the owner according to information/quantity/threshold range of the labels, etc., and the cloud will recommend corresponding scene scripts according to the groups.

In addition, the scene scenario is provided for free at present, and the cloud can be used for fine granularity of scene scenario information and payment OTA derived scene products according to operator configuration, big data accumulation analysis and user operation feedback. And part of scene capability can be opened to enable the user to customize the content of the scene and make the content closer to the user.

It can be understood that the implementation method of the vehicle dynamic scene engine provided by the embodiment of the application supports dynamic configuration of multiple vehicle types and multiple scene scripts and issues in time. The user can conduct targeted issuing according to the scenario targeted circling operation and the confidence coefficient, and finally the cloud end is evolved to use relevant scenes according to targeted pushing of cloud end management personnel and operation feedback of the user, thousands of people and thousands of faces can be evolved continuously, and the conversion rate is improved.

The present application further provides a server, fig. 5 is a schematic diagram of a composition structure of a server provided in an embodiment of the present application, as shown in fig. 5, a server 900 includes:

A first obtaining module 901, configured to obtain first software/hardware interface data related to a vehicle control function of a vehicle;

a first generating module 902, configured to generate a scenario model data file based on the first software-hardware interface data; the script model data file is used for realizing the vehicle control function of the corresponding vehicle;

The first sending module 903 is configured to send the scenario model data file to a corresponding vehicle, so that an on-vehicle terminal of the corresponding vehicle performs a corresponding vehicle control operation based on the scenario model data file.

In some embodiments, the first generating module 902 further comprises:

the first analysis submodule is used for analyzing the first software and hardware interface data to obtain vehicle control scene source data;

the first determining submodule is used for determining scene attributes and scene rules based on the vehicle control scene source data;

And the first generation sub-module is used for generating a script model data file according to the scene attribute and the scene rule.

In some embodiments, the first generation sub-module further comprises:

The first acquisition unit is used for acquiring the identification information of the vehicle where the vehicle-mounted terminal is located;

The first determining unit is used for determining scene attributes and scene rules associated with the vehicle where the vehicle-mounted terminal is located according to the identification information;

the first generation unit is used for generating script model file data of the vehicle where the vehicle-mounted terminal is located according to the identification information, the scene attribute and the scene rule associated with the vehicle where the vehicle-mounted terminal is located.

In some embodiments, server 900 further comprises:

The second receiving module is used for receiving the scene data file sent by the vehicle-mounted terminal; the scene data file is generated by the vehicle-mounted terminal based on second software and hardware interface data related to a vehicle control function in a vehicle where the vehicle-mounted terminal is located, and the first software and hardware interface data and the second software and hardware interface data are different;

And the second sending module is used for sending the scene data file to the vehicle-mounted terminals of other vehicles of the same vehicle type as the vehicle-mounted terminal, so that the vehicle-mounted terminals of the other vehicles execute corresponding vehicle control operation based on the scene data file.

In some embodiments, server 900 further comprises:

The second acquisition module is used for acquiring the confidence information of each script model data file sent by the vehicle-mounted terminal of the vehicle, wherein the confidence information is determined by user feedback information obtained after the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data files; the confidence information is used for indicating the acceptability of the user to the corresponding script model data file;

and the first updating module is used for updating the at least one script model data file based on the confidence information.

It should be noted that, the description of the server in the embodiment of the present application is similar to the description of the embodiment of the data processing method applied to the server, and has similar beneficial effects as the embodiment of the method, so that a detailed description is omitted. For technical details not disclosed in the present apparatus embodiment, please refer to the description of the method embodiment of the present application for understanding.

The present application further provides a vehicle-mounted terminal, fig. 6 is a schematic diagram of a composition structure of a vehicle-mounted terminal provided in an embodiment of the present application, as shown in fig. 6, the vehicle-mounted terminal 10 includes:

A first receiving module 11, configured to receive a scenario model data file sent by a server; the script model data file is generated by the server based on the acquired first software and hardware interface data related to the vehicle control function of the vehicle where the vehicle-mounted terminal is located; the script model data file is used for realizing the vehicle control function of the vehicle in which the vehicle-mounted terminal is positioned;

The first execution module 12 is configured to execute a corresponding vehicle control operation based on the scenario model data file.

In some embodiments, the scenario model data file comprises at least one; the in-vehicle terminal 10 further includes:

the third acquisition module is used for acquiring user feedback information obtained after corresponding vehicle control operation is executed based on the script model data file;

the first determining module is used for determining the confidence information of each script model data file according to the user feedback information; the confidence information is used for indicating the acceptability of the user to the corresponding script model data file;

And the third sending module is used for sending the confidence information to the server so that the server can update the script model data files based on the confidence information.

In some embodiments, the in-vehicle terminal 10 further includes:

the fourth acquisition module is used for acquiring second software and hardware interface data related to the vehicle control function of the vehicle where the vehicle-mounted terminal is located; the second software and hardware interface data is different from the first software and hardware interface data;

The second generating module is used for generating a scene data file based on the second software and hardware interface data;

And the storage module is used for storing the scene data file and sending the scene data file to the server so as to transmit the scene data file to the vehicle-mounted terminal of other vehicles of the same vehicle type as the vehicle in which the vehicle-mounted terminal is positioned through the server.

It should be noted that, the description of the vehicle-mounted terminal in the embodiment of the present application is similar to the description of the embodiment of the data processing method applied to the vehicle-mounted terminal, and has similar beneficial effects as the embodiment of the method, so that a detailed description is omitted. For technical details not disclosed in the present apparatus embodiment, please refer to the description of the method embodiment of the present application for understanding.

It should be noted that, in the embodiment of the present application, if the above-mentioned data processing method is implemented in the form of a software functional module, and sold or used as a separate product, the data processing method may also be stored in a computer readable storage medium. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied essentially or in a part contributing to the related solutions, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a magnetic disk, an optical disk, or other various media capable of storing program codes. Thus, embodiments of the application are not limited to any specific combination of hardware and software.

Accordingly, an embodiment of the present application provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the data processing method applied to a server or the data processing method applied to a vehicle-mounted terminal provided in the above embodiment.

The embodiment of the application also provides a server. Fig. 7 is a schematic diagram of a composition structure of another server according to an embodiment of the present application, as shown in fig. 7, the server 20 includes: a first memory 21, a first processor 22, a first communication interface 23 and a first communication bus 24. Wherein the first memory 21 is used for storing executable data processing instructions; the first processor 22 is configured to execute the executable data processing instructions stored in the memory, so as to implement the data processing method applied to the server provided in the above embodiment.

The embodiment of the application also provides a vehicle-mounted terminal. Fig. 8 is a schematic diagram of a composition structure of another vehicle-mounted terminal according to an embodiment of the present application, as shown in fig. 8, the vehicle-mounted terminal 30 includes: a second memory 31, a second processor 32, a second communication interface 33 and a second communication bus 34. Wherein the second memory 31 is used for storing executable data processing instructions; the second processor 32 is configured to execute the executable data processing instructions stored in the memory, so as to implement the data processing method applied to the vehicle-mounted terminal provided in the above embodiment.

The description of the server, the in-vehicle terminal, and the storage medium embodiments above is similar to that of the method embodiments described above, with similar advantageous effects as the method embodiments. For technical details not disclosed in the embodiments of the server and the storage medium of the present application, please refer to the description of the method embodiments of the present application.

It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising at least one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.

In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other ways. The above described device embodiments are only illustrative, e.g. the division of the units is only one logical function division, and there may be other divisions in practice, such as: multiple units or components may be combined or may be integrated into another system, or some features may be omitted, or not performed. In addition, the various components shown or discussed may be coupled or directly coupled or communicatively coupled to each other via some interface, whether indirectly coupled or communicatively coupled to devices or units, whether electrically, mechanically, or otherwise.

The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units; can be located in one place or distributed to a plurality of network units; some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may be separately used as one unit, or two or more units may be integrated in one unit; the integrated units may be implemented in hardware or in hardware plus software functional units.

One of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, where the program, when executed, performs steps including the above method embodiments; and the aforementioned storage medium includes: various media capable of storing program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.

Or the above-described integrated units of the application may be stored in a computer-readable storage medium if implemented in the form of software functional modules and sold or used as separate products. Based on such understanding, the technical solutions of the embodiments of the present application may be embodied essentially or in part in the form of a software product stored in a storage medium, including instructions for causing a product to perform all or part of the methods described in the various embodiments of the present application. And the aforementioned storage medium includes: various media capable of storing program codes, such as a removable storage device, a ROM, a magnetic disk, or an optical disk.

The foregoing is merely illustrative embodiments of the present application, and the present application is not limited thereto, and any person skilled in the art will readily appreciate variations and substitutions within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A data processing method applied to a server, the method comprising:

acquiring first software and hardware interface data related to a vehicle control function of a vehicle;

generating a script model data file based on the first software and hardware interface data; the script model data file is used for realizing the vehicle control function of the corresponding vehicle;

And sending the script model data file to a vehicle-mounted terminal of a corresponding vehicle, so that the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data file.

2. The method of claim 1, wherein generating scenario model data files based on the vehicle control capability interface data comprises:

analyzing the first software and hardware interface data to obtain vehicle control scene source data;

Determining scene attributes and scene rules based on the vehicle control scene source data;

And generating a script model data file according to the scene attribute and the scene rule.

3. The method of claim 2, wherein generating a scenario model data file according to the scenario attributes and scenario rules comprises:

Acquiring identification information of a vehicle in which the vehicle-mounted terminal is positioned;

Determining scene attributes and scene rules associated with vehicles where the vehicle-mounted terminal is located according to the identification information;

And generating script model file data of the vehicle in which the vehicle-mounted terminal is positioned according to the identification information, the scene attribute and the scene rule associated with the vehicle in which the vehicle-mounted terminal is positioned.

4. The method as recited in claim 1, further comprising:

Receiving a scene data file sent by a vehicle-mounted terminal; the scene data file is generated by the vehicle-mounted terminal based on second software and hardware interface data related to a vehicle control function in a vehicle where the vehicle-mounted terminal is located, and the first software and hardware interface data and the second software and hardware interface data are different;

and sending the scene data file to the vehicle-mounted terminals of other vehicles of the same vehicle type as the vehicle-mounted terminal, so that the vehicle-mounted terminals of the other vehicles execute corresponding vehicle control operation based on the scene data file.

5. The method of any one of claims 1 to 4, wherein the scenario model data file comprises at least one; the method further comprises the steps of:

The method comprises the steps of obtaining confidence information of each script model data file sent by a vehicle-mounted terminal of a vehicle, wherein the confidence information is determined by user feedback information obtained after the vehicle-mounted terminal executes corresponding vehicle control operation based on the script model data files; the confidence information is used for indicating the acceptability of the user to the corresponding script model data file;

and updating the at least one script model data file based on the confidence information.

6. The data processing method is applied to the vehicle-mounted terminal and is characterized by comprising the following steps:

Receiving a script model data file sent by a server; the script model data file is generated by the server based on the acquired first software and hardware interface data related to the vehicle control function of the vehicle where the vehicle-mounted terminal is located; the script model data file is used for realizing the vehicle control function of the vehicle in which the vehicle-mounted terminal is positioned;

and executing corresponding vehicle control operation based on the script model data file.

7. The method of claim 6, wherein the scenario model data file comprises at least one; the method further comprises the steps of:

Acquiring user feedback information obtained after corresponding vehicle control operation is executed based on the script model data file;

Determining confidence information of each script model data file according to the user feedback information; the confidence information is used for indicating the acceptability of the user to the corresponding script model data file;

And sending the confidence information to the server, so that the server updates the script model data files based on the confidence information.

8. The method according to claim 6 or 7, further comprising:

Acquiring second software and hardware interface data related to a vehicle control function of a vehicle where the vehicle-mounted terminal is located; the second software and hardware interface data is different from the first software and hardware interface data;

generating a scene data file based on the second software and hardware interface data;

And storing the scene data file, and sending the scene data file to the server so as to transmit the scene data file to the vehicle-mounted terminal of other vehicles of the same vehicle type as the vehicle-mounted terminal through the server.

9. A server, comprising:

The first acquisition module is used for acquiring first software and hardware interface data related to a vehicle control function of the vehicle;

the first generation module is used for generating a script model data file based on the first software and hardware interface data; the script model data file is used for realizing the vehicle control function of the corresponding vehicle;

And the first sending module is used for sending the script model data file to a corresponding vehicle so that the vehicle-mounted terminal of the corresponding vehicle executes corresponding vehicle control operation based on the script model data file.

10. A vehicle-mounted terminal, characterized by comprising:

The first receiving module is used for receiving the script model data file sent by the server; the script model data file is generated by the server based on the acquired first software and hardware interface data related to the vehicle control function of the vehicle where the vehicle-mounted terminal is located; the script model data file is used for realizing the vehicle control function of the vehicle in which the vehicle-mounted terminal is positioned;

and the first execution module is used for executing corresponding vehicle control operation based on the script model data file.