Vehicle cloud interaction method and device, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a vehicle cloud interaction method, which is applied to a cloud and comprises the following steps: receiving vehicle end data uploaded by a vehicle; analyzing the vehicle end data into standardized format data through a vehicle cloud protocol adaptation layer; updating a current object model corresponding to the vehicle based on the standardized format data to obtain an updated object model corresponding to the vehicle; matching the updated object model with a linkage scene corresponding to the vehicle, and determining a downlink instruction according to a matching result; and sending the determined downlink instruction to the vehicle, so that the vehicle executes the downlink instruction. According to the embodiment of the invention, the data uploaded during vehicle-cloud interaction is ensured not to be repeated, the problem that the data in each domain is transversely communicated after the data is uploaded to the cloud is solved, and the user experience is improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular to a vehicle-cloud interaction method, device, electronic device and storage medium. Background Art

[0002] With the development of vehicle intelligence, high-performance vehicle-cloud communication has become a core element to promote the development of the industry. Various scenarios such as vehicle remote control, intelligent driving, smart cockpit, big data and artificial intelligence all require integrated vehicle-cloud communication.

[0003] The existing vehicle-cloud interaction transmission method is mainly to define the vehicle-cloud protocol framework and protocol version at both ends of the vehicle-cloud, and reserve application extension parts. Based on specific vehicle-cloud interaction scenarios, the vehicle-cloud uplink and downlink interaction message format definitions are completed in JSON or XML format. However, when new vehicle models are connected, they are expanded based on business needs and forward compatibility is guaranteed. Incompatible scenarios are handled by adding new protocols, and then the overall link adaptation and development is carried out from access to application layers. This process cannot be standardized or generalized.

[0004] At the same time, there will be scenarios where data is uploaded in the cabin, driving, computing, and connection domains of smart cars. During the multi-channel and multi-business type upload process in each domain, there may be vertical domain data closed-loop transmission to ensure the integrity of each business. This also faces the problem of how to ensure that the data uploaded by the car to the cloud is not repeated, and how to connect the data of each domain horizontally after uploading the data to the cloud. Summary of the invention

[0005] In view of this, embodiments of the present application provide a vehicle-cloud interaction method, device, electronic device and storage medium to at least partially solve the above-mentioned problems.

[0006] According to a first aspect of an embodiment of the present application, a vehicle-cloud interaction method is provided, which is applied to a cloud side, and the method includes: receiving vehicle-side data uploaded by a vehicle; parsing the vehicle-side data into standardized format data through a vehicle-cloud protocol adaptation layer; updating a current object model corresponding to the vehicle based on the standardized format data to obtain an updated object model corresponding to the vehicle; matching the updated object model with a linkage scene corresponding to the vehicle, and determining a downlink instruction based on the matching result; and sending the determined downlink instruction to the vehicle so that the vehicle executes the downlink instruction.

[0007] According to the second aspect of an embodiment of the present application, a vehicle-cloud interaction device is provided, the device comprising: a data receiving module for receiving vehicle-side data uploaded by a vehicle; a data processing module for parsing the vehicle-side data into standardized format data through a vehicle-cloud protocol adaptation layer; and also for updating a current physical model corresponding to the vehicle based on the standardized format data, obtaining an updated physical model corresponding to the vehicle, and matching the updated physical model with a linkage scene corresponding to the vehicle, and determining a downlink instruction based on the matching result; and an execution module for sending the determined downlink instruction to the vehicle so that the vehicle executes the downlink instruction.

[0008] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising: a processor; and a memory storing a program, wherein the program comprises instructions which, when executed by the processor, cause the processor to execute the method as described in the first aspect.

[0009] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, characterized in that a computer program is stored in the computer-readable storage medium, and when the computer program runs on a computer, the computer implements any of the methods described above when executing.

[0010] To summarize, the embodiment of the present application parses the vehicle data received from the cloud into a standardized format through the vehicle-cloud protocol adaptation layer, thereby avoiding the problems of divergence and repeated definitions. At the same time, by determining the vehicle-cloud protocol adaptation layer, it is possible to quickly access vehicles of different models, and based on the standardized format data, the current object model corresponding to the vehicle is updated to obtain the updated object model corresponding to the vehicle; the updated object model is matched with the linkage scene corresponding to the vehicle, and a downlink instruction is determined according to the matching result; the determined downlink instruction is sent to the vehicle so that the vehicle executes the downlink instruction, which can quickly realize the rapid processing of different businesses, and through the linkage of the business with the latest related business data, it ensures that the data uploaded to the vehicle-cloud is not repeated, and also solves the problem of horizontal connection of data in various domains after the data is uploaded to the cloud, thereby improving the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0012] Figure 1 is a flow chart of a vehicle-cloud interaction method according to an embodiment of the present application;

[0013] Figure 2 This is a structural block diagram of a one-thing model of a vehicle-cloud interaction method according to an embodiment of the present application;

[0014] Figure 3 This is a logic block diagram of a one-thing model of a vehicle-cloud interaction method according to an embodiment of the present application;

[0015] Figure 4 This is a schematic diagram of updating one-object model data of a vehicle-cloud interaction method according to an embodiment of the present application;

[0016] Figure 5 This is a schematic diagram of the architecture of a vehicle-cloud interaction device according to an embodiment of the present application;

[0017] Figure 6 It is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0018] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present application, the technical solutions in the embodiments of the present application will be described clearly and in detail below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the embodiments of the present application should fall within the scope of protection of the embodiments of the present application.

[0019] The specific implementation of the embodiments of the present application is further explained below with reference to the accompanying drawings.

[0020] In view of the problem that the prior art cannot ensure that the data uploaded by the vehicle to the cloud is not duplicated, and there are difficulties in horizontally connecting the data in various domains after uploading the data to the cloud, an embodiment of the present application provides a vehicle-cloud interaction method. The specific implementation of each embodiment of the present disclosure will be described in detail below in conjunction with the accompanying drawings.

[0021] See also Figure 1 , electronic devices perform as Figure 1 The following process is shown to achieve vehicle-cloud interaction.

[0022] Step S102, receiving vehicle-side data uploaded by the vehicle.

[0023] In some embodiments, the physical model template is provided with lifecycle maintenance management. It can be understood that at the end of each lifecycle, the cloud receives the vehicle-side data uploaded by the vehicle and verifies the vehicle-side data uploaded by the vehicle. Furthermore, if the verification passes, the current physical model is updated based on the physical model template using the updated vehicle-side data. The update includes updating the physical model attributes or adding the physical model attributes. If the verification fails, the vehicle-side data uploaded by the current vehicle is not further processed.

[0024] Exemplarily, in some embodiments, lifecycle management is implemented through model editing, model query, and model state management.

[0025] Among them, in some embodiments, the vehicle-side data uploaded by the vehicle is verified by the vehicle-cloud gateway. Specifically, the vehicle is authenticated to complete the verification of the vehicle-side data uploaded by the vehicle. More specifically, the vehicle identification code (Vehicle Identification Number, VIN) is identified to confirm whether there is a matching vehicle-cloud protocol for the current vehicle in the cloud so that the vehicle-cloud gateway completes the authentication step and achieves the purpose of verification. It can be understood that the current vehicle is identified by the vehicle VIN code, and further, it is confirmed whether there is a matching vehicle-cloud protocol for the current vehicle in the cloud. If it exists, the authentication passes, that is, the verification passes; if it does not exist, the authentication fails, that is, the verification fails.

[0026] The car-to-cloud gateway is responsible for being compatible with various protocol access methods for different car models, such as TCP / UDP, MQTT, API, etc., and provides data upload interactive access services, connection authentication, connection management, etc.

[0027] For example, if the life cycle management of the object model is set to 3 hours on the cloud, the vehicle uploads the vehicle data every three hours. It is understandable that when this life cycle management ends, the cloud uses the updated vehicle data to update the current object model based on the object model template. Furthermore, when the next life cycle management is triggered, that is, 3 hours after the last triggering of the object model update, the vehicle uploads the current vehicle data again. It is understandable that when this life cycle management ends, the cloud uses the updated vehicle data to update based on the object model obtained at the end of the previous life cycle management. Among them, only the latest data is retained for the content under the same attribute, and the previous data under the same attribute is overwritten.

[0028] In some embodiments, the timestamp information attached to the data sent from the vehicle to the cloud is used as the basis for determining the latest data. More specifically, in other embodiments, the cloud takes a time snapshot of multiple data sent from the vehicle and uses this as the basis for determining the latest data.

[0029] Saving the latest data corresponding to different attributes makes it convenient for users to retrieve relevant data after certain vehicle-side events occur. In some embodiments, the data corresponding to the attribute can be retrieved based on the query "attribute". In other embodiments, the relevant attributes corresponding to the event can also be locked based on the query "event", and the corresponding data under each relevant attribute of the event can be retrieved.

[0030] Furthermore, the content included in the physical model template only provides initial properties and does not represent the entire content of the physical model. The initial properties of the physical model template can be customized according to needs or use the default template. Furthermore, when the current physical model is updated based on the physical model template using updated vehicle-side data, the elements included in the physical model can be expanded, and the properties can also be expanded.

[0031] In some embodiments, a physical model template is provided.

[0032] Wherein, illustratively, the default template of the object model template includes: object model attributes, object model events, and object model services;

[0033] Furthermore, the physical model attribute includes at least one of the physical model attribute name and the physical model data node; the physical model event includes at least one of the event identifier, event name, event type, event parameter and timestamp information; the physical model service includes at least one of the service identifier, service name, input parameter, output parameter, usage method and protocol information.

[0034] For example, the object model template is as follows: Figure 2 As shown, the physical model includes: vehicle-cloud protocol adaptation module, vehicle model physical model management module, physical model template management module, and scenario linkage module.

[0035] Specifically, the vehicle-cloud protocol adaptation module is associated with the vehicle-cloud protocol adaptation layer.

[0036] Exemplarily, when the vehicle-side data is uploaded to the cloud, in some embodiments, the vehicle model is identified by identifying the vehicle VIN code and the vehicle-cloud protocol adapted to the current vehicle is matched through the vehicle-cloud protocol adaptation layer.

[0037] It is understandable that the uploaded vehicle-side data will be standardized only after the vehicle is successfully identified. In some embodiments, the binary code stream, JSON, GZ ip, Protobuf and other format data of different vehicle models are uniformly parsed into standardized JSON format data according to the established protocol parsing template to standardize the uploaded vehicle-side data. Furthermore, in the vehicle model object model management module, in order to adapt to more vehicles, a object model template containing basic attributes, events, and services can be created first, including name, address, basic event definition and trigger rules, etc. The current object model is inherited and extended based on the basic template, thereby realizing the standardization of the object model definition of the associated vehicles under each vehicle model.

[0038] Specifically, the standardized data is used to update the corresponding attributes in the basic object model / or the current object model. Exemplarily, the vehicle model management module includes but is not limited to one or more of the following: model editing, model query, and model status management.

[0039] More specifically, after being standardized, the vehicle-side data will be abstracted into one of attributes, services, and events.

[0040] Among them, Figure 3 As shown, the attributes include attribute 1, attribute 2...attribute n. Furthermore, the attributes can be used to indicate more specific content in the associated business. Exemplarily, the content that the attributes can indicate includes one or more of the following: attribute identifier, attribute name, data, whether it is read-only, etc.

[0041] For example, the data includes: data type, data precision / length, data unit, data service identifier, and data timestamp. The data timestamp is used to indicate the time identifier of the current uploaded data or the current data to be processed when it is uploaded.

[0042] Exemplarily, data types include but are not limited to: int, long, flat, double, bool, text, date, enumeration, etc.

[0043] Among them, services include service 1, service 2...service n. Furthermore, the service can indicate more specific content in the associated business. For example, the content that the service can indicate includes one or more of the following: service identification, service name, input parameters, output parameters, usage methods, protocol information, etc.

[0044] For example, the output parameters may include synchronous output parameters and / or asynchronous output parameters.

[0045] Among them, events include event 1, event 2...event n. Furthermore, events can indicate more specific content in related services. For example, the content that an event can indicate includes one or more of the following: event identifier, event name, type, time parameter, timestamp, etc.

[0046] For example, the information indicated under the event includes but is not limited to: information, alarm, and fault. Among them, the timestamp is used to indicate the time mark of the current uploaded data or the current data to be processed when it is uploaded. For example, the current uploaded data is not sensitive to time, and the sensitivity of the current uploaded data to time can be increased by adding the time mark when uploading, that is, the timestamp.

[0047] Furthermore, the event parameters include: event parameter type, event parameter precision / length, and event parameter unit. For example, the event parameter type includes but is not limited to: int, long, flat, double, bullet, text, date, enumeration, etc.

[0048] Specifically, in the physical model template management module, exemplary, it includes but is not limited to: a template creation module, a last-shift update module, a template deletion module, and a template publishing module.

[0049] Exemplarily, the object model template also includes: attributes, services, and events.

[0050] Step S104, parsing the vehicle-side data into standardized format data through the vehicle-cloud protocol adaptation layer.

[0051] It can be understood that the car-cloud protocol adaptation layer contains available protocols adapted to different car models.

[0052] In some embodiments, whether a compatible protocol exists in the cloud for the current vehicle is determined based on the vehicle's VIN code. It is understandable that the same vehicle model includes many vehicles, and each vehicle has a unique VIN code.

[0053] Furthermore, the data types adapted by the protocol are extracted according to the adapted protocol, such as: i nt model, XML type. In some embodiments, these data are standardized into Json format through the protocol parsing template, avoiding the problems of disagreement and repeated definitions. At the same time, by determining the vehicle-cloud protocol adaptation layer, different models of vehicles can be quickly accessed.

[0054] Step S106 , updating the current physical model corresponding to the vehicle based on the standardized format data to obtain an updated physical model corresponding to the vehicle.

[0055] In some embodiments, the current object model corresponding to the vehicle is updated using standardized format data. Specifically, a certain attribute in the corresponding current object model is updated according to the vehicle-side data uploaded by the vehicle to complete the update of the current object model. More specifically, each time the vehicle-side data is uploaded by the vehicle, the latest time snapshot data will be left as the latest retained data under the current attribute, and the previous data will be overwritten. It can be understood that only the latest data is saved under each attribute.

[0056] Furthermore, the updated physical model is used as the current physical model when the next update action occurs, and the update is completed based on this.

[0057] In some embodiments, reference Figure 4 There are multi-channel uploads and single-channel uploads for vehicle-side data uploading, wherein the vehicle-side data uploaded by the vehicle is uploaded through a single business channel or multiple business channels; when uploading vehicle-side data through a single business channel, the business information corresponding to the vehicle-side data in the current object model is updated; when uploading vehicle-side data through multiple business channels to add or update the information corresponding to the object model, the latest time snapshot data of the data under the same business dimension is retained, and the latest time snapshot data of the same attribute data in different business dimensions is retained and stored in parallel.

[0058] The life management cycle can be set according to needs and is not limited here. It can be understood that the object model is always in a state to be updated, and the update of the object model can point to any event or any service, but in other embodiments, there is also a read-only situation in the update of the object model, that is, the updated object model does not point to any event / any service, and the updated data of the object model only updates the latest data under the attribute, and is only read-only.

[0059] Step S108, matching the updated object model with the linkage scene corresponding to the vehicle, and determining the downlink instruction according to the matching result.

[0060] In some embodiments, the updated object model attributes or event information in the updated object model are published to the consumer, so that the consumer can execute the scene linkage solution according to at least one scene linkage instruction pointed to by the updated object model attributes / or according to the rule so that the consumer can perform at least one specific behavior;

[0061] Furthermore, the scene linkage scheme includes: scene linkage rules and scene linkage execution. Furthermore, the scene linkage rules include: time rules, specific event rules, message sending rules, wherein the scene linkage execution executes differentiated scene linkage schemes according to the judgment results of the scene linkage rule conditions.

[0062] In some embodiments, the linkage scene is pre-set. Specifically, the linkage scene can be associated with a specific attribute. It can be understood that when a certain attribute or certain combination of attributes changes, the associated linkage scene does not point to a fixed solution. There is no limitation here and adjustments can be made according to actual conditions.

[0063] Exemplarily, after determining the vehicle model and related business in the rule definition stage, the corresponding scenario linkage rules are defined, mainly including: 1. Time rules: define how to calculate and process time dimension data; 2. Specific event rules: define event trigger access conditions, and the calculation and processing logic that meets specific event triggers; 3. Message sending rules: define specific business type or data change message sending access conditions, message sending topics, message formats, etc.

[0064] In the rule execution stage, the vehicle model data and attributes are used to determine whether to apply the physical model. The established time rules, specific event rules, and message sending rules are carried out one by one, and subsequent actions are performed according to the rule definitions.

[0065] For example, assuming that attribute 1 is the current temperature inside the car and attribute 2 is the current vehicle door and window posture, when the value of attribute 1 is greater than / or equal to 25 and attribute 2 both show off, the associated linkage scene is turning on the air conditioner. It can be understood that turning on the air conditioner is service 1; when the value of attribute 1 is greater than 20 but less than 25 and attribute 2 both show off, the associated linkage scene is opening the window. It can be understood that opening the window is service 2; when the value of attribute 1 is greater than / or equal to 25 and attribute 2 both show on, the associated linkage scene is prompting the user to close the doors and windows and turn on the air conditioner. It can be understood that prompting the user to close the doors and windows is event 1, and turning on the air conditioner is service 1; when the value of attribute 1 is greater than 20 but less than 25 and attribute 2 both show on, the updated object model does not point to any event / any service, and the updated data of the object model only updates the latest data under the attribute, and is only read-only. It can be understood that there is no associated linkage scene. Furthermore, the updated object model points to at least one scene linkage instruction / or there is a data update under at least one attribute / or according to the rules, the consumer performs at least one specific behavior to execute the scene linkage plan. Furthermore, different object models can wake up the same event, the same service or the same scene linkage plan.

[0066] Step S110, sending the determined downlink instruction to the vehicle, so that the vehicle executes the downlink instruction.

[0067] Published to the vehicle-side consumer, in some embodiments, the vehicle-side consumer refers to the vehicle shadow and / or the rule engine. It can be understood that the vehicle shadow is the vehicle-side data and the vehicle-side current parameters. For example, the vehicle-side data displayed on the LED display screen in the vehicle, or the vehicle-related app, can be an electronic device or data carrier that can feedback the vehicle-side data and the vehicle-side current parameters, which is not limited here.

[0068] In some embodiments, the consumer can also be the downstream receiver of the vehicle-side command. It can be understood that the downstream receiver of the vehicle-side command can be the next vehicle-side processing node pointed to by the current vehicle-side processing node. For example, assuming that attribute 1 is the current temperature in the car, attribute 3 is the current vehicle-side seat state, when the value of attribute 1 is 18, attribute 3 is the current vehicle-side seat state when the heating is not turned on, and the associated linkage scene is to turn on the vehicle-side seat heating. The updated object model will trigger the action of turning on the vehicle-side seat heating. At this time, the vehicle-side seat is the downstream receiver of the vehicle-side command, that is, the vehicle-side seat is the consumer at this time.

[0069] Further, illustratively, after the instruction is issued, it will go through the transfer, central control, and finally reach the implementation unit of the instruction.

[0070] Among them, in some embodiments, the rule engine judges and standardizes the instructions issued to consumers and publishes the instructions efficiently.

[0071] Furthermore, when the vehicle side receives a downlink instruction, it checks whether the current instruction can be recognized by the vehicle side. If the check passes, the downlink instruction is transmitted to the vehicle side for execution. If the check fails, the downlink instruction will not be transmitted to the vehicle side.

[0072] The embodiment of the present application parses the vehicle data received from the cloud into a standardized format through the vehicle-cloud protocol adaptation layer, thereby avoiding the problems of divergence and repeated definitions. At the same time, by determining the vehicle-cloud protocol adaptation layer, it is possible to quickly access vehicles of different models, and based on the standardized format data, the current object model corresponding to the vehicle is updated to obtain the updated object model corresponding to the vehicle; the updated object model is matched with the linkage scene corresponding to the vehicle, and a downlink instruction is determined according to the matching result; the determined downlink instruction is sent to the vehicle so that the vehicle executes the downlink instruction, which can quickly realize the fast processing of different businesses, and through the linkage of the business with the latest related business data, it ensures that the data uploaded to the vehicle-cloud is not repeated, and also solves the problem of horizontal connection of data in various domains after the data is uploaded to the cloud, thereby improving the user experience.

[0073] Figure 5 Schematic diagram of the architecture of the vehicle-cloud interaction device 500 of the exemplary embodiment of the present application, which mainly includes:

[0074] The data receiving module 501 is used to receive vehicle-side data uploaded by the vehicle.

[0075] The data processing module 502 is used to parse the vehicle-side data into standardized format data through the vehicle-cloud protocol adaptation layer;

[0076] It is also used to update the current physical model corresponding to the vehicle based on the standardized format data, obtain the updated physical model corresponding to the vehicle, match the updated physical model with the linkage scene corresponding to the vehicle, and determine the downlink instruction according to the matching result;

[0077] The execution module 503 is used to send the determined downlink instruction to the vehicle so that the vehicle executes the downlink instruction.

[0078] See also Figure 6 , shown is a schematic diagram of an electronic device of an embodiment of the present application. The specific embodiment of the present application does not limit the specific implementation of the electronic device.

[0079] like Figure 6 As shown, the electronic device may include: a processor (processor) 602 , a communication interface (Communications Interface) 604 , a memory (memory) 606 , and a communication bus 608 .

[0080] in:

[0081] The processor 602 , the communication interface 604 , and the memory 606 communicate with each other via a communication bus 608 .

[0082] The communication interface 604 is used to communicate with other electronic devices or servers.

[0083] Processor 602 is used to execute program 610, and specifically can execute relevant steps in the above-mentioned vehicle-cloud interaction method embodiment.

[0084] Specifically, the program 610 may include program codes, which include computer operation instructions.

[0085] The processor 602 may be a CPU, or an application specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0086] The memory 606 is used to store the program 610. The memory 606 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0087] The program 610 may include multiple computer instructions. Specifically, the program 610 may enable the processor 602 to execute operations corresponding to the vehicle-cloud interaction method described in any of the aforementioned method embodiments through multiple computer instructions.

[0088] The specific implementation of each step in program 610 can refer to the corresponding description of the corresponding steps and units in the above method embodiment, and has corresponding beneficial effects, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described devices and modules can refer to the corresponding process description in the above method embodiment, which will not be repeated here.

[0089] Through the electronic device of the embodiment of the present application, the vehicle data received from the cloud is parsed into a standardized format through the vehicle-cloud protocol adaptation layer, thereby avoiding the problems of disagreement and repeated definition. At the same time, by determining the vehicle-cloud protocol adaptation layer, it is possible to quickly access vehicles of different models, and the current object model corresponding to the vehicle is updated based on the standardized format data to obtain the updated object model corresponding to the vehicle; the updated object model is matched with the linkage scene corresponding to the vehicle, and a downlink instruction is determined according to the matching result; the determined downlink instruction is sent to the vehicle so that the vehicle executes the downlink instruction, which can quickly realize the fast processing of different businesses, and through the linkage of the business with the latest related business data, it is ensured that the data uploaded to the vehicle-cloud is not repeated, and the problem of horizontal connection of data in various domains after the data is uploaded to the cloud is solved, thereby improving the user experience.

[0090] The present application also provides a computer-readable storage medium storing instructions for causing a machine to execute the method described herein. Specifically, a system or device equipped with a storage medium may be provided, on which a software program code implementing the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or device is enabled to read and execute the program code stored in the storage medium.

[0091] In this case, the program code read from the storage medium itself can implement the function of any one of the above embodiments, so the program code and the storage medium storing the program code constitute part of the present application.

[0092] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer by a communication network.

[0093] An embodiment of the present application also provides a computer program product, including computer instructions, which instruct a computing device to perform any corresponding operation in the above-mentioned multiple method embodiments.

[0094] It should be pointed out that, according to the needs of implementation, the various components / steps described in the embodiments of the present application can be split into more components / steps, or two or more components / steps or partial operations of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of the present application.

[0095] The above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or implemented as a computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein can be stored in such software processing on a recording medium using a general-purpose computer, a dedicated processor or programmable or dedicated hardware (such as an ASIC or FPGA). It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code, and when the software or computer code is accessed and executed by a computer, a processor or hardware, the navigation method described herein is implemented. In addition, when a general-purpose computer accesses the code for implementing the navigation method shown herein, the execution of the code converts the general-purpose computer into a dedicated computer for executing the navigation method shown herein.

[0096] Those of ordinary skill in the art will appreciate that the units and method steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

[0097] The above implementation methods are only used to illustrate the embodiments of the present application, and are not limitations on the embodiments of the present application. Ordinary technicians in the relevant technical field can make various changes and modifications without departing from the spirit and scope of the embodiments of the present application. Therefore, all equivalent technical solutions also belong to the scope of the embodiments of the present application. The scope of patent protection of the embodiments of the present application should be limited by the claims.

Claims

1. A vehicle-cloud interaction method, characterized in that: Applied in the cloud, including: Receive vehicle-side data uploaded by the vehicle; Parsing the vehicle-side data into standardized format data through the vehicle-cloud protocol adaptation layer; Based on the standardized format data, the current physical model corresponding to the vehicle is updated to obtain an updated physical model corresponding to the vehicle; Matching the updated object model with the linkage scene corresponding to the vehicle, and determining a downlink instruction according to the matching result; The determined downlink instruction is sent to the vehicle, so that the vehicle executes the downlink instruction.

2. The method according to claim 1, characterized in that The current object model includes: object model attributes, object model events, and object model services; The physical model attribute includes at least one of a physical model attribute name and a physical model data node; The physical model event includes at least one of an event identifier, an event name, an event type, an event parameter, and a timestamp information; The object model service includes at least one of a service identifier, a service name, an input parameter, an output parameter, a usage method, and protocol information.

3. The method according to claim 1, characterized in that The method further comprises: After receiving the vehicle-side data, authenticating the vehicle; If the authentication is successful, the vehicle-side data is parsed into standardized format data through the vehicle-cloud protocol adaptation layer.

4. The method according to claim 1, characterized in that: The updating of the current physical model corresponding to the vehicle based on the standardized format data to obtain an updated physical model corresponding to the vehicle includes: Parsing the vehicle-side data uploaded by the vehicle through a protocol parsing template to obtain the standardized format data; receiving the standardized format data and updating a current object model corresponding to the vehicle; The vehicle-side data uploaded by the vehicle is uploaded through a single service channel or multiple service channels; When uploading the vehicle-side data through the single service channel, updating the service information corresponding to the vehicle-side data in the current object model; When uploading the vehicle-side data through the multi-business channel to add or update information corresponding to the object model, the latest time snapshot data of the data under the same business dimension is retained, and the latest time snapshot data of the same attribute data in different business dimensions is retained and stored in parallel.

5. The method according to claim 2, characterized in that: The object model attribute is used to indicate the read-only nature of the object model.

6. The method according to any one of claims 1 to 5, characterized in that: The matching of the updated object model with the linkage scene corresponding to the vehicle includes: Publishing updated object model attributes or event information in the updated object model to consumers; so that the consumer executes the scene linkage scheme according to at least one scene linkage instruction pointed to by the updated object model attribute, or makes the consumer perform at least one specific behavior to execute the scene linkage scheme according to the rule; The rules include time rules and specific event rules.

7. The method according to claim 6, characterized in that The scene linkage scheme includes: scene linkage rules and scene linkage execution; The scene linkage rules include: time rules, specific event rules, and message sending rules; The scene linkage execution executes differentiated scene linkage solutions according to the judgment results of the scene linkage rule conditions.

8. A vehicle-cloud interaction device, characterized in that: The device comprises: A data receiving module is used to receive vehicle-side data uploaded by the vehicle; A data processing module, used to parse the vehicle-side data into standardized format data through the vehicle-cloud protocol adaptation layer; It is also used to update the current physical model corresponding to the vehicle based on the standardized format data, obtain the updated physical model corresponding to the vehicle, match the updated physical model with the linkage scene corresponding to the vehicle, and determine the downlink instruction according to the matching result; An execution module is used to send the determined downlink instruction to the vehicle so that the vehicle executes the downlink instruction.

9. An electronic device, comprising: processor; as well as Memory for storing programs, The program includes instructions, which, when executed by the processor, cause the processor to perform the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed on a computer, the computer is enabled to execute the method according to any one of claims 1 to 7.

Images