WO2017219883A1 - Data pushing method, apparatus and device - Google Patents

Abstract

Provided are a data pushing method, apparatus and device. The method comprises: acquiring scene data; and respectively pushing at least part of the scene data to a plurality of receiving objects borne by a transportation tool, wherein the scene data is used for displaying. By means of the embodiments, diversified scene data is displayed by means of a plurality of receiving objects, so that it is convenient for a user to view information, and the user can also acquire diversified information.

Description

Data push method, device and device

The present application claims priority to Chinese Patent Application No. Serial No. No. No. No. No. No. No. No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

Technical field

The present application relates to Internet technologies, and in particular, to a method, device and device for pushing data applied to a vehicle.

Background technique

At present, vehicles have become a common means of transportation in people's lives, which not only facilitates people's travel, but with the deepening of intelligent development of various brands of vehicles, today's vehicles are also rich for people on the road. Entertainment features and useful features.

In the prior art, in order to facilitate the user to understand related information during the running of the vehicle, the related information is generally displayed to the user through the display device inside the vehicle. The display devices inside the vehicle are mainly the instrument panel and the center console. For example, the navigation information is displayed on the center console, and the vehicle status information (such as the amount of oil, the vehicle speed, etc.) monitored by various vehicle sensors is displayed on the dashboard.

However, in the prior art, the display device inside the vehicle displays very limited information and is not convenient for the user to view.

Summary of the invention

The present application provides a method, device, and device for pushing data to solve the technical problem that the display information displayed by the display device inside the vehicle is very limited and is inconvenient for the user to view.

In a first aspect, the present invention provides a method for pushing data, including: acquiring scene data;

At least part of the scene data is respectively pushed to a plurality of receiving objects carried by the vehicle, and the scene data is used for display.

In a feasible implementation manner, among the scene data pushed to the plurality of receiving objects, there is a difference in scene data in which at least two receiving objects are pushed.

In a possible implementation, before the at least part of the scene data is pushed to the plurality of receiving objects carried by the vehicle, the method further includes:

Processing the scene data to obtain a plurality of sub-scene data;

Obtaining a receiving object corresponding to each of the sub-scene data;

And pushing the at least part of the scene data to the plurality of receiving objects carried by the vehicle, respectively, including:

Each of the sub-scene data is pushed to a corresponding receiving object.

After acquiring the scene data, the embodiment processes the scene data to obtain at least two sub-scene data, and pushes each sub-scene data to its corresponding receiving object according to the corresponding relationship between the sub-scene data and the receiving, so that each receiving The object can obtain the corresponding sub-scene data, fully utilizes the internal space of the vehicle, avoids receiving redundant scene data by each receiving object, and improves the rationality and simplicity of receiving the scene data of each receiving object, and Since the receiving object is two, it is also possible to output more scene data to the user, so that the user can obtain the required data by targeted.

In a second aspect, the present invention provides a data pushing device, including: a data acquiring module, configured to acquire scene data;

And a pushing module, configured to push at least part of the scene data to the plurality of receiving objects carried by the vehicle, where the scene data is used for display.

In a third aspect, the present invention provides a data pushing device, including: an input device, configured to acquire scene data;

And a processor coupled to the output device and the input device, configured to control the output device to respectively push at least part of the scene data to a plurality of receiving objects carried by the vehicle, where the scene data is used for display.

In a fourth aspect, the present invention provides a vehicle control apparatus comprising: an onboard output device, an onboard input device, and an onboard processor coupled to the onboard output device and the onboard input device;

The onboard input device is configured to acquire scene data;

The onboard processor is configured to control the onboard output device to push at least part of the scene data to a plurality of receiving objects carried by the vehicle, where the scene data is used for display.

In a fifth aspect, the present invention provides an in-vehicle Internet operating system, including:

Input control unit, controlling the vehicle input device to acquire scene data;

And an output control unit that controls the vehicle-mounted output device to respectively push at least part of the scene data to the plurality of receiving objects carried by the vehicle, where the scene data is used for display.

The data sending method, device, and device provided by the embodiment, by acquiring the scene data, respectively push at least part of the scene data to the plurality of receiving objects carried by the vehicle, and the scene data is used for display, thereby realizing a diversified scene. The data is displayed through a plurality of receiving objects, so that the user can obtain diversified information, and the user can view the information through multiple receiving objects according to individual needs.

DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, a brief description of the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

FIG. 1 is a schematic diagram of networking of a data pushing apparatus according to an embodiment of the present invention;

2 is a schematic diagram of an application scenario of a data pushing method according to an embodiment of the present invention;

3 is a schematic flowchart of a method for pushing data according to an embodiment of the present invention;

4 is a schematic flowchart of a method for pushing data according to an embodiment of the present invention;

FIG. 5 is a schematic flowchart of a method for acquiring sub-scenario data provided by the present invention;

FIG. 6 is a schematic diagram of a display interface according to an embodiment of the present invention;

FIG. 7 is a schematic diagram of a display interface according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of a display interface according to an embodiment of the present invention;

FIG. 9 is a schematic structural diagram of a data pushing apparatus according to an embodiment of the present invention;

FIG. 10 is a schematic structural diagram of a data pushing apparatus according to an embodiment of the present invention;

FIG. 11 is a schematic structural diagram of hardware of a data pushing device according to an embodiment of the present invention;

FIG. 12 is a schematic structural diagram of an in-vehicle Internet operating system according to an embodiment of the present invention.

detailed description

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with aspects of the invention as detailed in the appended claims.

The vehicle involved in the embodiments of the present invention includes, but is not limited to, an automobile or a motorcycle, an electric car or a motorcycle, an electric bicycle, an electric balance vehicle, a remote control vehicle, and the like, and a small aircraft (for example, an unmanned aerial vehicle, a person) Small aircraft, remotely piloted aircraft, and various variants. The vehicle involved herein may be a single oil road vehicle, a single steam road vehicle, a fuel-air combined vehicle, or a power-assisted electric vehicle. The embodiment of the present invention does not do the type of the vehicle. limited.

The embodiment of the invention relates to a data sending method, device and device, which can be applied to the networking mode shown in FIG. 1 . FIG. 1 is a schematic diagram of networking of a data pushing apparatus according to an embodiment of the present invention. The network architecture in FIG. 1 may include a vehicle and a cloud server and a smart home device in communication with the vehicle. The vehicle carries a plurality of data collection devices, and the cloud server can be a plurality of types of servers, and the smart terminals can be devices such as smart homes, which can collect scene data. The details are described below separately.

A plurality of data collection devices are disposed in the vehicle, and the vehicle is provided with a plurality of data collection devices, and the data collection devices can also be integrated into the vehicle during the production process. Optionally, the data collection device may be a camera, a sensor, or the like. The sensor may be a temperature sensor, a speed sensor, or the like of the water tank, and the camera may be a rear view camera, a side view camera, or the like. The data collection device may also be a hardware module, a software module, or a combination of soft and hard modules inside the vehicle. The data collection device can also be a device within the vehicle that can implement near field communication such that the vehicle can communicate with other vehicles or other devices in near field.

Optionally, the cloud server may also collect scene data, and the vehicle may interact with the cloud server through the wireless network to obtain the scene data. The wireless network may be a 2G network, a 3G network, a 4G network or a 5G network, a Wireless Fidelity (WIFI) network, or the like. The specific type or specific form of the wireless network is not limited in the embodiment of the present invention, as long as it can provide an interface for the vehicle to access the network.

Those skilled in the art can understand that in order to facilitate obtaining various data information, each vehicle can be bound to various account numbers, and the information related to the account can be obtained from the corresponding server. For example, if the account is an e-commerce account, it can receive various information pushed by the e-commerce server, such as logistics information, payment information, and the like. The account can also be an email account, and can receive various emails and other information pushed by the email server.

Further, for the convenience of operation, a vehicle account may also be set for the vehicle, and the vehicle account is associated with another account, for example, the vehicle account is associated with an e-commerce account, a social server account, an e-commerce account, etc., ie, After logging in to the vehicle account, the user can obtain other accounts associated with the account and obtain related information under other accounts.

The smart home device can communicate with the vehicle through the Internet of Things or the Internet, and feed back information about the smart home to the vehicle.

Optionally, in the method of the embodiment of the present invention, the execution entity may be a data pushing device, where the data pushing device may be a cloud server, a device on a vehicle, or a cloud server and a traffic. The management device between the devices on the tool, for example, may be a device that manages communication resources for communication between the cloud server and the device on the vehicle. The type of the data pushing device is not limited in the embodiment of the present invention. Optionally, the device on the vehicle may be a central control unit on the vehicle, or may be other control on the vehicle. Equipment for communication and communication functions. For example, the vehicle is a vehicle, and the equipment on the vehicle may be a vehicle on the vehicle, a center console of the vehicle, a driving recorder on the vehicle, a smart rearview mirror, a vehicle dashboard, etc., and the following embodiments The vehicles involved are all examples of vehicles. Regardless of the type of data push device, the data push device can centrally manage the data and distribute the scene data to the receiving object carried on the vehicle in a targeted manner for a specific driving scenario. Optionally, the receiving object may be at least two of a dashboard of the vehicle, a center console of the vehicle, a user equipment, and a head up display (HUD) smart rearview mirror, and the user equipment may be in the vehicle. The internal device may be a user's mobile phone, a tablet, a wearable device such as a smart watch, a wristband, a virtual reality (VR) device, an augmented reality (AR) device, or the like. Optionally, the receiving object is only an example, and the embodiment of the present invention is not limited thereto.

2 is a schematic diagram of an application scenario of a data pushing method according to an embodiment of the present invention. Referring to FIG. 2, the data pushing device 201 and a plurality of receiving objects may be used. The multiple receiving objects may be a dashboard 202-1 in a vehicle. , the center console 202-2, the head up display 202-3, the rear view mirror 202-4, etc., the data pushing device 201 can acquire the scene data, and push the scene data to a plurality of different receiving objects, so that a plurality of different receiving After receiving the scene data, the object displays the scene data, so that the diversified scene data is displayed through multiple receiving objects, so that the user can obtain diversified information, and the user can pass multiple according to individual needs. Receive objects to view information.

The technical solutions of the present invention will be described in detail below with specific embodiments. The following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in some embodiments.

For the sake of clarity, the definition of a particular word or phrase used in the present invention is first described.

In one aspect, the scene data involved in the embodiment of the present invention includes scene data sent by at least one of a data collection device, a cloud server, and a smart home device in communication with the vehicle. The scene data is different according to the type of the data collection device, the type of the cloud server, and the smart terminal.

The data acquisition device can be a sensor, a camera, a center console, etc. carried in the vehicle.

When the data acquisition device is a sensor, the scene data may be a vehicle related to the vehicle's speed, fuel consumption, speed, remaining oil, room temperature, odometer, engine status, tire status, seat belt status, etc. Status data.

When the data collection device is an imaging device, the scene data may be information such as photos, videos, and the like around the vehicle.

When the data collection device is the center console, the scene data can be the music playing information controlled by the center console. Play information, etc.

A person skilled in the art can understand that the foregoing embodiment only schematically shows the type of the data collection device and the content of the obtained scene data. For the specific implementation manner of the data collection device and the specific content of the scene data, this embodiment A data collection device capable of providing users with information required for driving, living, working, entertainment, etc., which is not particularly limited, can be applied to the present invention.

The cloud server can be a navigation server, a life server, or the like.

When the cloud server is a navigation server, the scene data may be various navigation data. For example, various data that the navigation server can provide, such as a navigation overview map, a travel indication logo, a remaining mileage overview map, road congestion information, road clear information, and road accident information.

When the cloud server is a life server, such as an e-commerce server, a social server, a mail server, or a subscription server, the scene data may be various life scene data, such as goods logistics information, credit card due repayment information, and social information. , booking information, travel information, phone bills, order information, etc.

A person skilled in the art can understand that the foregoing embodiment only shows the type of the cloud server and the content of the obtained scenario data. For the specific implementation of the cloud server and the specific content of the scenario data, this embodiment does not A cloud server having special restrictions and capable of providing users with information required for driving, living, working, entertainment, and the like can be applied to the present invention.

The smart home device can communicate with the vehicle via the Internet of Things or the Internet. The scene data may be cooking information of the rice cooker, work information of the sweeping robot, operation information of the air conditioner, etc. For example, the rice cooker starts cooking at 7 o'clock in the evening, the sweeping robot starts to sweep the ground at 10 o'clock in the morning, and the air conditioner turns on at 5 o'clock in the afternoon. The setting mode is cooling and the temperature is 28 °C.

A person skilled in the art can understand that the foregoing embodiment only schematically shows the type of the smart home and the content of the obtained scene data. For the specific implementation manner of the smart home and the specific content of the scene data, this embodiment does not A smart home that can provide users with the necessary information for living, entertainment, and the like can be applied to the present invention.

On the other hand, the types of scenes involved in the embodiments of the present invention are mainly classified into a navigation scene, an entertainment scene, a life scene, and the like. That is, the scene data is divided according to the function of the scene data. The scenario data may be obtained in the case of determining the navigation scenario, or may be determined according to the currently obtained scenario data.

In the navigation scenario, the navigation function is provided to the user, and the scene data that is pushed to the receiving object includes the scene data corresponding to the navigation scenario, that is, the data acquired by the navigation server. For example, a navigation overview map, a driving indication logo, and the like. Optionally, the road abnormal navigation scene and the normal navigation scene of the road may also be classified according to road conditions. The scene data corresponding to the road abnormal navigation scene may include: the scene data corresponding to the normal navigation scene of the road includes a navigation overview map, traffic condition data, and status data of the vehicle.

In the entertainment scenario, the user is provided with an entertainment function, and the scene data that is pushed to each receiving object includes the scene data corresponding to the entertainment scene, that is, the data acquired through the center console. For example, music playback information, video playback information, radio playback information, and the like.

In the life scenario, the user provides a life service function, and the scene data corresponding to the life scene is mainly used for the data acquired through the life server and/or the smart home. For example, goods logistics information, credit card due repayment information, air conditioning operation information, etc.

In another aspect, the data type of the sub-scene involved in the embodiment of the present invention is mainly processed from two dimensions. One of the dimensions is processed according to the type of the scene, and the other dimension is processed according to the importance of the data to the user. The data type of the sub-scene corresponds to the sub-scene data, and the sub-scene data is processed by the scene data to obtain a plurality of sub-scene data.

First, the manner in which processing is performed according to the type of scene will be explained. The scene type can be divided into a scene type related to driving, a scene type related to the user, and a scene type related to the smart home.

The type of scene associated with driving. For example, in a road abnormal navigation scenario, the data type of the sub-scene corresponding to the road abnormal navigation scenario includes at least two of the following: a navigation overview map, traffic condition data, and vehicle status data; if the navigation scenario is a normal navigation of the road For the scenario, the data type of the sub-scene corresponding to the normal navigation scene of the road includes at least two of the following: a navigation overview map, a driving indication identifier, a remaining mileage overview map, and status data of the vehicle. If the scene type is an entertainment scene, the data type of the sub-scene corresponding to the entertainment scene includes at least two of the following: entertainment data, traffic condition data, and status data of the vehicle.

The type of scene associated with the user. For example, if the scene type is an e-commerce life scene, the data type of the sub-scene corresponding to the e-commerce life scene includes logistics data, payment data, and product evaluation data.

The type of scene associated with the smart home. For example, if the scene type is a home life scene, the data type of the sub-scenario corresponding to the home life scene includes the running information of the working smart home and the faulty smart home information.

Next, a method of processing according to the degree of importance to the user will be described. According to the degree of importance, the data types of the sub-scenarios related to driving include: driving assistance data, emergency data, full amount of information data, and driving necessary data. The data types of the sub-scenarios related to the user include: necessary data for living, and living auxiliary data. The data types of the sub-scenarios related to the smart home include: necessary home data, auxiliary home data.

In a further aspect, the sub-scene data involved in the embodiment of the present invention is mainly a data class of the sub-scene related to the foregoing. The corresponding sub-scene data. For example, the traffic condition data corresponds to data such as road congestion and road accidents; the state data of the vehicle corresponds to data such as speed, speed, odometer, engine state, etc.; driving necessary data corresponds to data such as speed, remaining oil, road indication, etc.; driving assistance The data corresponds to the remaining mileage overview map; the necessary data for life corresponds to credit card repayment date, mobile phone arrears information and other data, life assistance data includes social information, goods logistics information, etc.; necessary household data corresponds to the information of the running home equipment, household equipment The fault information, etc., the auxiliary home data corresponds to the information of the home equipment to be operated after the preset time period, the information that the home equipment is insufficient, and the like.

It can be understood by those skilled in the art that the foregoing only schematically shows the specific implementation manners of the scene data, the scene type, the data type of the sub-scene, and the sub-scene data, which are not limited to the present invention. For other implementation manners, the implementation is implemented. There are no special restrictions here.

FIG. 3 is a schematic flowchart of a method for pushing data according to an embodiment of the present invention. Referring to FIG. 3, the method may include:

S301. Acquire scene data.

S302. Push at least part of the scene data to a plurality of receiving objects carried by the vehicle, where the scene data is used for display.

For the scene data obtained in this embodiment, reference may be made to the scene data described in the foregoing embodiments. The scene data may be a text form, a picture form, a voice form, a video form, or the like.

After acquiring the scene data, the acquired at least part of the scene data is pushed to the plurality of receiving objects carried by the vehicle, that is, all the scene data may be pushed to the receiving object, or part of the scene data may be pushed to the receiving object, and each receiving object is The scene data to be pushed may be the same, different, or partially identical, or there may be differences in scene data in which at least two received objects are pushed into the scene data pushed by the plurality of receiving objects. This embodiment is not particularly limited herein.

When part of the scene data is pushed to multiple receiving objects and is not the same, the scene data may be randomly split into multiple parts and then pushed to different receiving objects; or the scene data may be processed by a preset rule to obtain multiple Part and then push to different recipients.

Optionally, the receiving object may include at least two of the following receiving objects: a dashboard, a center console, a head-up display HUD, a rear view mirror, a mirror, a projection device, a smart terminal having a communication connection with the vehicle, and the like. The terminal device may be a terminal device such as a mobile phone or a tablet located in the vehicle. After the receiving object receives the scene data, the receiving object performs different processing on the received scene data according to the type of the receiving object.

Optionally, when the receiving object is a display device, after the receiving object receives the scene data, the receiving object may display the scene data; when the receiving object is the projection device, the receiving object may receive the received scene data. Projected onto a matching projection screen to cause scene data to be displayed on the projection screen. In the actual application process, the type of each receiving object can be set according to actual needs, which is not specifically limited in the present invention.

The invention obtains at least part of the scene data by using the scene data to obtain the scene data, and the scene data is used for display, so that the diversified scene data is displayed through multiple receiving objects, so that the user can Obtain diversified information, and users can view information through multiple recipients according to individual needs.

On the basis of the embodiment shown in FIG. 3, in order to make reasonable use of the internal space of the vehicle, the scene data is displayed as much as possible through the receiving object for the user to view, and the acquired scene data is reasonably pushed to different receiving objects. The corresponding scene data can be pushed to each receiving object. For details, refer to the embodiment shown in FIG. 4 .

FIG. 4 is a schematic flowchart of a method for pushing data according to an embodiment of the present invention. On the basis of the embodiment shown in FIG. 3, refer to FIG. 4, the method may include:

S401. Acquire scene data.

S402. Process the scene data to obtain multiple sub-scene data.

S403. Acquire a receiving object corresponding to each sub-scene data.

S404: Push each sub-scene data to a corresponding receiving object.

In the actual application process, after obtaining the scene data of the vehicle, the scene data is processed to obtain a plurality of sub-scene data, and each sub-scene data is part or all of the scene data.

Alternatively, the scene data may be randomly split into a plurality of sub-scene data. For example, the data may be randomly divided into multiple sub-scene data with equal data amount according to the amount of data of the scene data. The scene data may be split into multiple sub-scene data according to the sequence of the acquired scene data. A specific implementation manner of randomly splitting the scene data into multiple sub-scene data is not described herein again in this embodiment.

Optionally, the correspondence between the data type of the receiving object and the sub-scene may be preset, and the corresponding relationship may be preset by the user, or may be determined according to the type of the receiving object and the data type of each sub-scene. Correspondingly, the scene data may be processed according to the correspondence relationship to obtain a plurality of sub-scene data. Optionally, in the plurality of sub-scene data, there is a difference between the at least two sub-scene data. Specifically, each sub-scene data is different, or some sub-scene data is different. details as follows:

A feasible implementation: each sub-scene data is different. For example, suppose that the scene data includes 10 data, which are respectively recorded as data 1 - data 10, and then it is assumed that the 10 scene data are processed to obtain 3 sub-scene data, and the data included in the three sub-scene data can be as shown in Table 1. Show:

Table 1

Identification of sub-scene data	Identification of data included in sub-scene data
Sub-scenario data 1	Data 1, data 2, data 3
Sub-scenario data 2	Data 4, data 5, data 6
Sub-scenario data 3	Data 7, data 8, data 9, data 10

The sub-scene data shown in Table 1 does not include duplicate data. It should be noted that Table 1 merely illustrates the sub-scene data included in the scene data and the data included in each sub-scene data. This is not a limitation.

Another possible implementation: some sub-scene data is different. For example, suppose that the scene data includes 10 data, which are respectively recorded as data 1 - data 10, and then the 10 scene data are processed to obtain 3 sub-scene data, and the data included in the three sub-scene data can be as shown in Table 2. :

Table 2

Identification of sub-scene data	Identification of data included in sub-scene data
Sub-scenario data 1	Data 1, data 2, data 3, data 5
Sub-scenario data 2	Data 4, data 5, data 6
Sub-scenario data 3	Data 4, data 5, data 6

Among the respective sub-scene data shown in Table 2, the sub-scene data 2 and the sub-scene data 3 include identical data. It should be noted that Table 2 only illustrates the sub-scene data included in the scene data and the data included in each sub-scene data by way of example, and is not limited thereto.

After obtaining the plurality of sub-scene data, the receiving object corresponding to each sub-scene data is acquired, and the sub-scene data is pushed to the corresponding receiving object. For example, if the receiving object corresponding to the sub-scene data 1 is a dashboard, the sub-scene data 1 is pushed to the dashboard, and the sub-scene data 1 is displayed by the dashboard; the receiving object corresponding to the sub-scene data 2 is the center console. Then, the sub-scene data 2 is pushed to the center console, and the sub-scene data 2 is displayed by the center console.

In the embodiment shown in FIG. 4, after acquiring the scene data, the scene data is processed to obtain at least two sub-scene data, and each sub-scene data is pushed to the corresponding according to the sub-scene data and the corresponding correspondence corresponding to the reception. The receiving object enables each receiving object to obtain the corresponding sub-scene data, fully utilizes the internal space of the vehicle, avoids receiving redundant scene data by each receiving object, and improves the reasonable reception of the scene data by each receiving object. Sexuality and simplicity, and since the number of receiving objects is two, it is also possible to output more scene data to the user, so that the user can obtain the required data by targeted.

On the basis of the embodiment shown in FIG. 4, the scenario data can be processed by the following two feasible implementation manners to obtain multiple sub-scene data (S402 in the embodiment shown in FIG. 4), specifically:

A feasible implementation manner is: processing the scene data according to a data type of the sub-scene to obtain a plurality of sub-scene data.

In this feasible implementation, optionally, the data type of the sub-scene may include: driving assistance data, emergency data, full amount of information data, and driving necessary data. The data type of each sub-scene may include scene data of at least one data type. For example, the driving assistance data may include at least one of traffic condition data and a remaining mileage overview map; the driving necessary data may include at least one of status data of the vehicle, a driving indication identifier; the full amount information data may include a navigation overview map, At least one of the entertainment data, the emergency data may include abnormal data of the vehicle.

In the actual application process, after obtaining the scene data of the vehicle, the data type of the sub-scene to which the data belongs may be determined according to the correspondence between the type of each data in the scene data and the data type of the sub-scene, thereby obtaining multiple sub-scenarios. Scene data.

Exemplarily, it is assumed that the acquired scene data includes: a remaining mileage overview map, driving speed (status data of the vehicle), remaining oil quantity (status data of the vehicle), a front 100 m left turn logo (driving indication mark), To navigate the overview map, the determined sub-scene data is shown in Table 3:

table 3

Sub-scenario data type	Type of data included in the sub-scene data
Driving necessary data	Driving speed, remaining oil, front 100m left turn logo
Driving assistance data	Remaining mileage overview
Full amount of information data	Navigation overview

Those skilled in the art can understand that the number of data types of the sub-scene is greater than or equal to the number of obtained sub-scene data. That is, the data type of the sub-scene includes five types, but in the actual application process, only the scene data corresponding to the data type of the three seed scenes is acquired, and therefore, the number of obtained sub-scene data is 3.

Another feasible implementation manner: processing the scene data according to the scene type of the vehicle, and obtaining at least two sub-scene data. Specifically, please refer to the embodiment shown in FIG. 5.

FIG. 5 is a schematic flowchart of a method for obtaining sub-scenario data according to the present invention. Referring to FIG. 5, the method may include:

S501. Determine a scene type according to the scene data.

S502: Obtain a data type of the sub-scene corresponding to the scene type according to the correspondence between the scene type and the data type of the sub-scene;

S503. Process the scene data according to the data type of the sub-scene to obtain a plurality of sub-scene data.

In the embodiment shown in FIG. 5, after acquiring the scene data, when the sub-scene data needs to be acquired, the scene type is determined according to the acquired scene data, and the scene type may include a navigation scene, an entertainment scene, a high-speed scene, Urban scenes, reversing scenes, etc. Optionally, the data type in the scene data can be analyzed to determine the type of the scene.

For example, it may be determined whether the navigation data is included in the scene data. If yes, the scene type may be determined as a navigation scene; whether the multimedia data (such as music, video, etc.) may be included in the scene data, and if yes, the scene type may be determined as music. Scenes. Optionally, if the scene data includes both a navigation line and multimedia data, the scene type may be determined according to the priority of the navigation line and the multimedia data. For example, if the priority of the navigation line is higher than the priority of the multimedia data, it may be determined that the scene type is a navigation scene. When the location information of the vehicle is included in the scene data, the scene type may be determined as a high-speed scene or an urban scene according to the location information of the vehicle. Of course, when the scene data includes the traveling speed of the vehicle, the vehicle may also be driven according to the vehicle. Speed determines the type of scene.

After determining the type of the scene, the corresponding relationship between the scene type and the data type of the sub-scene is obtained, and the corresponding relationship may be determined according to an empirical value, or may be preset by the user. Then, the data types of the plurality of sub-scene corresponding to the scene type are obtained according to the corresponding relationship, and the scene data is processed according to the data type of the sub-scene to obtain a plurality of sub-scene data.

Exemplarily, the correspondence between the scene type and the data type of the sub-scene is as shown in Table 4:

Table 4

Scene type	Sub-scenario data type
Road abnormal navigation scene	Navigation overview map, traffic status data, vehicle status data
Normal navigation scene	Navigation overview map, driving indication logo, remaining mileage overview map
Entertainment scene	Entertainment data, traffic status data, vehicle status data

Assume that the obtained scene data is as shown in Table 5:

table 5

Navigation overview
100 meters in front of congestion
500 traffic accidents ahead
1000 meters ahead
60 km/h

10 liters of remaining oil
23 degrees Celsius at room temperature

And determining, according to the scene data, that the scene type is a road abnormal navigation scene, acquiring a data type of the sub-scene corresponding to the road abnormal navigation scene: a navigation overview map, traffic condition data, and vehicle status data, and according to each data in the scene data. The correspondence between the type and the data type of the sub-scene determines the data type of the sub-scene to which each data belongs, thereby obtaining a plurality of sub-scene data. As shown in Table 6:

Table 6

In the embodiment shown in FIG. 5, the data type of the sub-scene corresponding to the scene type is determined according to the scene type, and the scene data is processed according to the data type of the sub-scene to obtain a plurality of sub-scene data, and the obtained sub-scene data is determined. Corresponding to the current scene of the vehicle, thereby improving the accuracy of the determined sub-scene data.

On the basis of any of the above embodiments, when it is necessary to acquire a receiving object corresponding to each sub-scene data (S403 in the embodiment shown in FIG. 4). Optionally, the receiving object corresponding to each sub-scene data may be determined according to the data type of the sub-scene. Specifically, the receiving object corresponding to each sub-scene data may be determined by the following two feasible implementation manners:

A feasible implementation manner is: determining a receiving object corresponding to each sub-scene data according to a pushing priority corresponding to a data type of each sub-scene.

In this feasible implementation manner, the data type of each sub-scene has its corresponding push priority, and different push priorities correspond to different receiving objects. The push priority corresponding to the data type of each sub-scene may be preset by the user, or may be determined according to historical experience values. In the actual application process, the priority of the data type of each sub-scene and the receiving object corresponding to each push priority may be set according to actual needs.

Exemplarily, it is assumed that the scene data is processed to obtain three seed scene data, which are respectively recorded as sub-scene data 1 - sub-scene data 3, the data type of each seed scene, and the push priority of the data type of each sub-scene, Correspondence between the priority of the push target and the received object, and the correspondence between the sub-scene data and the received object. As shown in Table 7:

Table 7

Sub-scenario data	Sub-scenario data type	Push priority	Receiving object
Sub-scenario data 1	Vehicle status data	3	dash board
Sub-scenario data 2	Entertainment data, navigation overview	2	Center console
Sub-scenario data 3	Traffic status data	1	rearview mirror

In this embodiment, according to the push priority of the data type of each sub-scene, the information absolutely necessary for the user to drive (for example, the state data of the vehicle) is pushed to the receiving object that is convenient for viewing by the user, such as a dashboard or a HUD, and correspondingly, The priority of the vehicle's status data is set to 3 (highest). Pushing sub-scene data (such as entertainment data, navigation overview maps, etc.) that users frequently view to the receiving object that the user can conveniently view but does not affect the user's driving, such as the center console, correspondingly, can enter entertainment data, navigation overview The priority of the graph is set to 2. Urgent information that needs to be understood by the user and other secondary driving assistance information (such as traffic condition data) are pushed to the receiving object that the user does not often use, such as a rear view mirror, and accordingly, the priority of the traffic condition data can be set to 1 Therefore, targeted data is pushed to the user.

Another feasible implementation manner is: determining a receiving object corresponding to each sub-scene data according to a preset correspondence between a data type of each sub-scene and each receiving object.

In this feasible implementation manner, the system may preset a correspondence between a data type of each sub-scene and each received object. The user can also preset the correspondence between the data type of each sub-scenario and each receiving object according to actual needs. Specifically, the data type of each sub-scene and each received object may be output to the user, and the corresponding relationship determined by the user is received. A feasible implementation manner is that the data type of each sub-scene and each receiving object are output to the user in the form of text, so that the user can perform an associating operation on the data type of each sub-scene and each receiving object, and according to the user input. The association operation determines the data type of each sub-scene and the corresponding relationship of each received object. Optionally, the association operation may be a data type of the sub-scene and a connection operation of the receiving object, a selection operation, and the like; another feasible implementation manner is: outputting the data type of each sub-scenario to the user in the form of voice and Each of the receiving objects is such that the user inputs the correspondence between the data type of each sub-scene and each receiving object in the form of voice or text according to the received data type of each sub-scene and each received object.

When the receiving object corresponding to each sub-scene data needs to be determined, the preset correspondence relationship between the data type of each sub-scene and each receiving object may be acquired, and the receiving object corresponding to each sub-scene data is determined according to the corresponding relationship.

Exemplarily, after processing the scene data, three seed scene data are obtained, which are respectively recorded as sub-scene data 1 - sub-scene data 3, data types of sub-scene corresponding to each sub-scene data, data types of each sub-scene, and each The correspondence between the receiving objects is shown in Table 8:

Table 8

Sub-scenario data	Sub-scenario data type	Receiving object
Sub-scenario data 1	Full amount of information data	Center console
Sub-scenario data 2	Emergency data	Rearview mirror or mirror
Sub-scenario data 3	Driving necessary data	Dashboard or HUD

Then, according to the correspondence between the data type of each sub-scene of the data type of the sub-scene corresponding to each sub-scene data shown in Table 8 and each receiving object, the correspondence between each sub-scene data and the receiving object can be determined.

Hereinafter, the method of pushing data shown in the above method embodiment will be described in detail by the following two examples.

Example 1, assuming that the acquired scene data is as shown in Table 9:

Table 9

Navigation overview
500 meters ahead road construction
700 meters ahead of the road is congested
1 km traffic accident ahead
60 km/h
Engine speed 5000 rpm

According to the scenario data shown in Table 9, the scenario type is a road abnormal navigation scenario, and then the data type of the sub-scene corresponding to the scenario type is obtained, and the data type of the sub-scene corresponding to the road abnormal navigation scenario is: The map, the traffic status data, and the status data of the vehicle can be determined according to the scene data and the data type of the sub-scene shown in Table 9, and each sub-scene data and the corresponding receiving object are as shown in Table 10:

Table 10

After determining the data of each sub-scene, the corresponding object of each sub-scene data may be determined according to the correspondence between the data type of each sub-scene and each receiving object, and the data type of the sub-scene is assumed to be a navigation overview map. The receiving object is the center console. If the data type of the sub-scene is traffic condition data, the corresponding receiving object is the rear view mirror, and when the data type of the sub-scene is the state data of the vehicle, the corresponding receiving object is the dashboard.

After obtaining the correspondence between the sub-scene data and the receiving object, push the “Navigation Overview Map” to the center console, and push “100 meters ahead of the traffic, 500 traffic accidents ahead, and 1000 meters ahead” to the rear view mirror. “Speed 60 km/h, engine speed 5000 rpm” is pushed to the dashboard.

After each receiving object receives its corresponding scene data, the receiving object displays the corresponding scene data. Specifically, FIG. 6 is a schematic diagram of a display interface according to an embodiment of the present invention. Referring to FIG. 6, a center console interface 601, a rearview mirror interface 602, and a dashboard interface 603 are included. among them,

A navigation overview map is displayed in the center console interface 601. The navigation overview map includes the navigation route (the route where the positions A, B, and C are located) and the traffic condition of the navigation route, as shown by the interface 601. The current position of the user is position A, the traffic is congested in the section from position B to position C, and the traffic of other sections is smooth. The navigation indicator is also included in the navigation overview map (200 meters ahead to enter the cultural road) and the remaining distance is 25Km. The arrival time is 18:43, and the arrival time is 43 minutes. It should be noted that the interface 601 merely illustrates the data included in the overview map by way of example. Of course, in the actual application process, the navigation can be set according to actual needs. The data included in the map is displayed. At this time, only the basic road condition information of the road is displayed in the navigation overview map, and additional information such as construction and accidents are not superimposed, thereby ensuring the simplicity and readability of the interface of the center console.

The traffic condition data is displayed on the rearview mirror interface 602: "500 meters ahead of the road construction, 700 meters ahead of the road, and 1 km ahead traffic accident".

The status data of the vehicle is displayed in the dashboard interface 603: "speed of 60 km/h, engine speed of 5000 rpm".

In the above process, after acquiring the scene data of the vehicle, the different sub-scene data in the scene data is uniformly pushed to the center console, the rearview mirror, and the dashboard, so that the center console, the rearview mirror, and The dashboard can acquire scene data in synchronization and in real time. Further, a simple navigation overview map is displayed in the center console, road condition information is displayed in the rearview mirror, and status data of the vehicle is displayed in the dashboard, according to the receiving object. The role of the scenario is to push the corresponding scene data to the receiving object, so as to realize the reasonable distribution of the scene data, so that the user can easily View the view data.

Example 2, assuming that the acquired scene data is as shown in Table 11:

Table 11

Navigation overview
Remaining mileage overview
200 meters ahead into the cultural road
60 km/h
Engine speed 5000 rpm

According to the scenario data shown in Table 11, the scenario type is a normal navigation scenario of the road, and then the data type of the sub-scene corresponding to the scenario type is obtained, and the data type of the sub-scene corresponding to the normal navigation scenario of the road is: The map, the driving indication logo, the remaining mileage overview map, and the status data of the vehicle, according to the scene data and the data type of the sub-scene shown in Table 11, can determine each sub-scene data and the corresponding receiving object as shown in Table 12:

Table 12

After determining the data of each sub-scene, the corresponding object of each sub-scene data may be determined according to the correspondence between the data type of each sub-scene and each receiving object, and the data type of the sub-scene is a driving overview map, corresponding to When the receiving object is the center console, and the data type of the sub-scene is the remaining mileage overview map, the corresponding receiving object is the rearview mirror. If the data type of the sub-scene is the driving indication identifier or the state data of the vehicle, the corresponding receiving The object is a dashboard.

After obtaining the correspondence between the sub-scene data and the receiving object, the “Navigation Overview Map” is pushed to the center console, and the “Remaining Mileage Overview Map” is pushed to the rearview mirror, and the “200 meters ahead enters the cultural road and the speed. 60 km/h, engine speed 5000 rpm” is pushed to the dashboard.

After each receiving object receives its corresponding scene data, the receiving object displays the corresponding scene data. Specifically, FIG. 7 is a schematic diagram of a display interface according to an embodiment of the present invention. Please refer to Figure 7, including the center console Interface 701, rearview mirror interface 702, and dashboard interface 703, wherein

A navigation overview map is displayed in the center console interface 701. The navigation overview map includes navigation routes (the lines where the positions A, B, C, and D are located) and traffic conditions of the navigation route, such as interface 701. The starting position of the navigation route is position A, the ending position of the navigation route is position D, the current position of the user is position B, and the road map is also included in the navigation overview map, for example, the speed limit at position C is 80 km/h. In the navigation overview map, the driving indication sign (200 meters ahead to enter the cultural road), the remaining distance 25Km, the arrival time 18:43, and the arrival time of 43 minutes are included. It should be noted that the interface 701 is only an example. The form indicates the data included in the overview map. Of course, in the actual application process, the data included in the navigation overview map can be set according to actual needs.

A remaining mileage overview map is displayed in the rearview mirror interface 702.

In the dashboard interface 703, the driving indication flag "200 meters ahead of the cultural road" and the state data of the vehicle are displayed: "speed of 60 km/h, engine speed of 5000 rpm".

In the above process, after acquiring the scene data of the vehicle, the different sub-scene data in the scene data is uniformly pushed to the center console, the rearview mirror, and the dashboard, so that the center console, the rearview mirror, and The dashboard can acquire the scene data in synchronization and in real time. Further, by displaying the map and navigation information (navigation overview map) in the center console, the remaining mileage overview map is displayed in the rearview mirror, and the driving is displayed in the dashboard. The status data of the indicator and the vehicle are indicated, and the scene data is reasonably allocated, so that the user can view the scene data.

On the basis of any of the above examples, after the vehicle completes a mileage, the line overview map of the mileage can be displayed on the rearview mirror, and the average speed of the current mileage can also be displayed in the rearview mirror. Average fuel consumption, full time, full mileage, etc. FIG. 8 is a schematic diagram of a display interface according to an embodiment of the present invention. Referring to FIG. 8 , the interface 801 is a rear view mirror interface, including a line overview map, a starting point of the line (Xixi Butterfly Garden), and an end point of the line (Wuzhen East Gate Parking). Field), full range (86Km), average speed (79Km/h), full time (71min), average fuel consumption (6.9L/Km), it should be noted that Figure 8 is only shown as an example in the rearview mirror The scene data in the rear view mirror can be set according to actual needs in the actual application process, which is not specifically limited in the present invention.

It should be understood by those skilled in the art that in the foregoing embodiments, some scene data and corresponding relationships are described in the form of a table for convenience of description and description, but the embodiment is not limited to the existence of the data and the corresponding relationship. Forms, for example, can also be distinguished by term breakers, punctuation, and the like. The correspondence can also be implemented by means of pointers, mappings, and the like. The specific implementation manner of the data and the corresponding relationship is not limited herein.

A push device for data according to one or more embodiments of the present invention will be described in detail below. Push of these data The delivery device can be implemented in the infrastructure of the vehicle or terminal device, or can be implemented in an interactive system between the server and the client. Those skilled in the art will appreciate that the push devices for such data can be constructed using commercially available hardware components configured by the steps taught by the present scheme. For example, the processor component (or processing module, processing unit) can use components such as a microcontroller, a microcontroller, a microprocessor, etc. from Texas Instruments, Intel Corporation, ARM, and the like.

FIG. 9 is a schematic structural diagram of a data pushing apparatus according to an embodiment of the present invention. As shown in FIG. 9, the data sending apparatus provided in this embodiment includes:

The data acquisition module 10 is configured to acquire scene data.

The pushing module 11 is configured to respectively push at least part of the scene data to a plurality of receiving objects carried by the vehicle, where the scene data is used for display.

The pushing device of the data provided in this embodiment may be used to perform the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.

FIG. 10 is a schematic structural diagram of a data pushing apparatus according to an embodiment of the present invention. The embodiment is implemented on the basis of the embodiment of FIG.

Optionally, among the scene data pushed to the plurality of receiving objects, there is a difference in scene data in which at least two receiving objects are pushed.

Optionally, the processing module 12 and the object obtaining module 13 are further included.

The processing module 12 is configured to process the scene data to obtain a plurality of sub-scene data;

The object obtaining module 13 is configured to acquire a receiving object corresponding to each of the sub-scene data.

The pushing module 11 is specifically configured to push each of the sub-scene data to a corresponding receiving object.

Optionally, the processing module 12 is specifically configured to process the scene data according to a data type of the sub-scene to obtain a plurality of sub-scene data.

Optionally, the number of data types of the sub-scene is greater than or equal to the number of obtained sub-scene data.

Optionally, the method further includes: a type obtaining module 14, determining, according to the scene data, a scene type;

Obtaining a data type of the sub-scene corresponding to the scene type according to the correspondence between the scene type and the data type of the sub-scene.

Optionally, the object obtaining module 13 is specifically configured to determine, according to a data type of the sub-scene, a receiving object corresponding to each of the sub-scene data.

Optionally, the object obtaining module 13 is specifically configured to determine, according to a pushing priority corresponding to a data type of each of the sub-scene, a receiving object corresponding to the sub-scene data.

Optionally, the object obtaining module 13 is specifically configured to acquire a preset correspondence between a data type of each of the sub-scene and each received object;

And determining, according to the correspondence, a receiving object corresponding to each of the sub-scene data.

Optionally, the method further includes: a relationship obtaining module 15 configured to output, to the user, a data type of each of the sub-scene and each of the receiving objects, and receive the corresponding relationship determined by the user.

Optionally, the scene type includes:

Navigation scene

Entertainment scene.

Optionally, if the navigation scenario is a road abnormal navigation scenario, the data type of the sub-scene corresponding to the road abnormal navigation scenario includes at least two of the following:

Navigation overview maps, traffic status data, and vehicle status data.

Optionally, if the data type of the sub-scene is a navigation overview view, the corresponding receiving object is a central control station;

If the data type of the sub-scene is traffic condition data, the corresponding receiving object is a rearview mirror;

If the data type of the sub-scene is status data of the vehicle, the corresponding receiving object is a dashboard.

Optionally, if the navigation scenario is a normal navigation scenario, the data type of the sub-scene corresponding to the normal navigation scenario includes at least two of the following:

Navigation overview map, driving indication logo, remaining mileage overview map, and vehicle status data.

Optionally, if the data type of the sub-scene is a driving overview map, the corresponding receiving object is a central control station;

If the data type of the sub-scene is a remaining mileage overview map, the corresponding receiving object is a rearview mirror;

If the data type of the sub-scene is the driving indication identifier or the status data of the vehicle, the corresponding receiving object is a dashboard.

Optionally, if the scene type is an entertainment scene, the data type of the sub-scene corresponding to the entertainment scene includes at least two of the following:

Entertainment data, traffic condition data, and status data of the vehicle.

Optionally, if the data type of the sub-scene is entertainment data, the corresponding receiving object is a central control station;

If the data type of the sub-scene is traffic condition data, the corresponding receiving object is a rearview mirror;

If the data type of the sub-scene is status data of the vehicle, the corresponding receiving object is a dashboard.

Optionally, the data type of the sub-scene includes at least two of the following:

Driving assistance data, emergency data, full amount of information data, and driving necessary data.

Optionally, the driving assistance data includes at least one of traffic condition data and a remaining mileage overview map;

The driving necessary data includes at least one of status data of the vehicle and a driving indication identifier;

The full amount of information data includes at least one of a navigation overview map and entertainment data;

The emergency data includes abnormal data of the vehicle.

Optionally, if the data type of the sub-scene is driving assistance data or emergency data, the corresponding receiving object is a rear view mirror or a rear view mirror;

If the data type of the sub-scene is full information data, the corresponding receiving object is a central control station;

If the data type of the sub-scene is driving necessary data, the corresponding receiving object is a dashboard or a HUD.

Optionally, the data acquiring module 10 is specifically configured to acquire the scenario data sent by at least one of a data collection device, a cloud server, and a smart home device that is in communication connection with the vehicle. .

Optionally, the receiving object includes at least two of the following:

A dashboard, a center console, a head-up display HUD, a rearview mirror, a mirror, and a smart terminal in communication with the vehicle.

The pushing device of the data provided in this embodiment may be used to perform the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.

FIG. 11 is a schematic structural diagram of hardware of a data pushing device according to an embodiment of the present invention. As shown in FIG. 11, the push device of the data includes:

Input device 20, processor 21, output device 22, memory 23, and at least one communication bus 24. Communication bus 24 is used to implement a communication connection between the components. The memory 23 may include a high speed RAM memory, and may also include a non-volatile memory NVM, such as at least one disk memory, in which various programs may be stored for performing various processing functions and implementing the method steps of the present embodiment.

Optionally, the processor 21 can be, for example, a central processing unit (CPU), an application specific integrated circuit (ASIC), a digital signal processor (DSP), a digital signal processing device (DSPD), and programmable logic. A device (PLD), field programmable gate array (FPGA), controller, microcontroller, microprocessor or other electronic component is implemented that is coupled to the input device 20 and the output device 22 by a wired or wireless connection.

Optionally, the input device 20 may include multiple input devices, for example, at least one of a device-oriented device interface, a software programmable interface, and a transceiver. The output device 22 described above can include a variety of output devices, such as at least one of a programmable interface that can include software, a transceiver, and a device-oriented in-vehicle device interface.

Optionally, the device-oriented device interface may be a wired interface used for data transmission between the device and the device, or may be a hardware insertion interface (for example, a USB interface, a serial port, etc.) for data transmission between the device and the device. Optionally, the programmable interface of the foregoing software may be, for example, an entry for the user to edit or modify the program, such as an input pin interface or an input interface of the chip; optionally, the transceiver may be a communication function. RF transceiver chip, baseband processing chip, and transceiver antenna.

The push device for data in the embodiment of the present invention is a general data push device. It can be applied to any control system or push device or other type of device. Alternatively, the push device of the data may be a push device for data of the vehicle, for example, a push device that may be data for the vehicle, a push device for data of the aircraft, data for the waterway transporter Push equipment, etc. Regarding the specific content of the push device for data of the vehicle, the present invention provides another embodiment for introduction. Please refer to the following embodiments, which will not be described in detail herein.

In this embodiment, the input device 20 is configured to acquire scene data.

The processor 21 is coupled to the output device 22 and the input device 20 for controlling the output device 22 to respectively push at least part of the scene data to a plurality of receiving objects carried by the vehicle, the scene data being used for display.

Optionally, the processor 21 is further configured to: process the scene data, obtain a plurality of sub-scene data, and acquire a receiving object corresponding to each of the sub-scene data;

The processor 21 is specifically configured to control the output device 22 to push each of the sub-scene data to a corresponding receiving object.

Optionally, the processor 21 is configured to process the scene data according to a data type of the sub-scene to obtain a plurality of sub-scene data.

Optionally, the processor 21 is further configured to determine, according to a data type of the sub-scene, a receiving object corresponding to each of the sub-scene data.

Optionally, the processor 21 is specifically configured to determine, according to a push priority corresponding to a data type of each of the sub-scene, a receiving object corresponding to each of the sub-scene data.

Optionally, the processor 21 is configured to: obtain a preset correspondence between a data type of each of the sub-scene and each received object, and determine, according to the correspondence, a receiving object corresponding to each of the sub-scene data. .

Optionally, the input device 20 is specifically configured to acquire the scenario data sent by at least one of a data collection device, a cloud server, and a smart home device in a communication connection with the vehicle.

The pushing device of the data provided in this embodiment may be used to perform the foregoing method embodiments, and the implementation principle and technical effects are similar, and details are not described herein again.

Based on the description of the general data pushing device of the embodiment shown in FIG. 11 above, the present invention further provides a vehicle control device, which is a data pushing device for a specific implementation of the vehicle. .

Optionally, the vehicle control device may be a vehicle device, an attached device after the vehicle leaves the factory, and the like.

In particular, the vehicle control device can include an onboard output device, an onboard input device, and an onboard processor coupled to the onboard output device and the onboard input device.

It should be noted that the airborne in the "airborne input device", "airborne output device", and "airborne processor" according to the embodiments of the present invention may be an "vehicle input device" carried on a vehicle, "Vehicle output device" and "vehicle processor" may also be "onboard input device", "onboard output device", "onboard processor" carried on the aircraft, or may be carried on other types of vehicles. The above device does not limit the meaning of "airborne" in the embodiment of the present invention. Taking the vehicle as an example, the onboard input device may be an in-vehicle input device, the onboard processor may be an onboard processor, or the onboard output device may be an onboard output device.

Depending on the type of vehicle being installed, the above-described in-vehicle input device may include a variety of input devices, such as at least one of a device-oriented in-vehicle device interface, an in-vehicle programmable interface of software, and a transceiver. Optionally, the device-oriented in-vehicle device interface may be a wired interface for data transmission between the device and the device (for example, a connection interface with a driving recorder on a center console of the vehicle), or may be used for the device. A hardware insertion interface (for example, a USB interface, a serial port, etc.) for data transmission between the device; optionally, the in-vehicle programmable interface of the above software may be, for example, an entry in the vehicle control system that can be edited or modified by the user, such as in a vehicle. The input pin interface or the input interface of the large and small chips involved; optionally, the transceiver may be a radio frequency transceiver chip with a communication function in the vehicle, a baseband processing chip, and a transceiver antenna, etc., so that the vehicle can be connected with the cloud server. Perform data interaction. According to the method in the embodiment corresponding to FIG. 1 to FIG. 8 above, the onboard input device is configured to acquire scene data. For example, when the message control device for the vehicle described above is a central control unit or other device on the vehicle, the onboard input device may be a transceiver that establishes communication with the cloud server, or may also be internal to the vehicle. The device transmission interface through which the service source communicates.

The onboard processor can use various application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (depending on the type of vehicle installed). PLD), field programmable gate array (FPGA), central processing unit (CPU), controller, microcontroller, microprocessor or other electronic component implementation and used to perform the above methods. The above airborne processor is routed through the car or A wireless connection is coupled to the onboard input device and the onboard output device described above. The airborne processor can perform the method in the embodiment corresponding to the foregoing FIG. 1 to FIG. 8. For example, the onboard processor can process the scene data to obtain a plurality of sub-scene data, and the control output device pushes each sub-scene data to the corresponding one. Receive object.

The above-mentioned onboard output device may be a device interface capable of data transmission with a receiving object (for example, a center console, a dashboard), or may be wirelessly established with a user device or the like, depending on the type of the installed vehicle. A transmitting transceiver that can be coupled to the onboard input device and the onboard processor via an in-vehicle line or wirelessly.

The airborne output device of this embodiment can perform the method in the embodiment corresponding to FIG. 1 to FIG. 8 described above.

The invention also provides an in-vehicle internet operating system. It can be understood by those skilled in the art that the hardware of the push device that can manage and control the above data, or the hardware of the vehicle control device according to the present invention and the computer program of the software resources involved in the present invention are directly operated. System software on the push device or vehicle control device of the above data. The operating system is the interface of the data push device or the vehicle control device, and is also the interface between the hardware and other software.

The in-vehicle Internet operating system provided by the present invention can interact with other modules or functional devices on the vehicle to control the functions of the corresponding modules or functional devices.

Specifically, the vehicle in the above embodiment is a vehicle, and the pushing device of the data is an in-vehicle terminal device. Based on the development of the in-vehicle Internet operating system and the vehicle communication technology provided by the present invention, the vehicle is no longer independent of the communication network. In addition, the vehicle can be connected to the server to form a network to form an in-vehicle Internet. The in-vehicle Internet system can provide voice communication services, location services, navigation services, mobile internet access, vehicle emergency rescue, vehicle data and management services, in-vehicle entertainment services, and the like.

The structure of the in-vehicle Internet operating system provided by the present invention is described in detail below. FIG. 12 is a schematic structural diagram of an in-vehicle Internet operating system according to an embodiment of the present invention. As shown in FIG. 12, the operating system provided by the present invention includes an input control unit 30 and an output control unit 31.

The input control unit 30 controls the in-vehicle input device to acquire scene data;

The output control unit 31 controls the vehicle-mounted output device to respectively push at least part of the scene data to the plurality of receiving objects carried by the vehicle, and the scene data is used for display.

Specifically, the in-vehicle input device in this embodiment may include the input device in the above embodiment, and the input control unit 30 may control the in-vehicle input device to perform the step 301 in the embodiment of FIG. 3 to acquire the scene data.

The output control unit 31 can control the vehicle-mounted output device to perform at least part of the scene data to the plurality of receiving objects carried by the vehicle by performing step 302 in the above embodiment of FIG. 3 .

Optionally, in the structural diagram shown in FIG. 12, a push control unit is further included;

The push control unit, the control data push system performs step 402 in the embodiment of FIG. 4 to process the scene data to obtain a plurality of sub-scene data;

The push control unit further controls the data pushing system to perform step 403 in the embodiment of FIG. 4 to acquire a receiving object corresponding to each of the sub-scene data;

The output control unit further controls the in-vehicle output device to perform step 404 in the embodiment of FIG. 4 to push each of the sub-scene data to a corresponding receiving object.

Optionally, the push control unit further controls the data pushing system to process the scene data according to the data type of the sub-scene to obtain a plurality of sub-scene data.

Optionally, the push control unit further controls the data pushing system to perform step 501 and step 502 in the embodiment of FIG. 5, and determines a scene type according to the scene data, and according to the scene type and the data of the sub-scene. The data type of the sub-scene corresponding to the scene type is obtained.

Optionally, the pushing control unit further controls the data pushing system to determine a receiving object corresponding to each of the sub-scene data according to a data type of the sub-scene.

Optionally, the pushing control unit further controls the data pushing system to determine a receiving object corresponding to each of the sub-scene data according to a pushing priority corresponding to a data type of each of the sub-scene.

Optionally, the pushing control unit further controls the data pushing system to obtain a preset correspondence between a data type of each of the preset sub-scene and each receiving object, and determine, according to the corresponding relationship, each of the sub-scene data. Corresponding receiving object.

Optionally, the input control unit further controls the onboard input device to acquire the scene sent by at least one of a data collection device, a cloud server, and a smart home device having a communication connection with the vehicle. data.

The data pushing system may be a function implemented by an operating system, or the data pushing system may be a function implemented by a processor in the foregoing embodiment.

Further, the in-vehicle Internet operating system may control the corresponding components to perform the above-mentioned FIG. 1 to FIG. 1 through the above-mentioned input control unit 30, output control unit 31, push control unit or on the basis of the above two units, in combination with other units. All or part of the steps of 8 have similar beneficial effects as described above, and are not described herein again.

The present invention also provides a processor readable storage medium having program instructions stored therein for causing a processor to perform the methods described in FIGS. 1-8 of the above-described embodiments.

The above readable storage medium may be any type of volatile or non-volatile storage device or group thereof Implementations such as static random access memory (SRAM), electrically erasable programmable read only memory (EEPROM), erasable programmable read only memory (EPROM), programmable read only memory (PROM), read only memory (ROM), magnetic memory, flash memory, disk or optical disk.

The terms used in the embodiments of the present invention are for the purpose of describing particular embodiments only and are not intended to limit the invention. The singular forms "a", "the" and "the"

It should be understood that although the terms first, second, third, etc. may be used to describe XXX in embodiments of the invention, these XXX should not be limited to these terms. These terms are only used to distinguish XXX from each other. For example, the first XXX may also be referred to as a second XXX without departing from the scope of the embodiments of the present invention. Similarly, the second XXX may also be referred to as a first XXX.

Depending on the context, the words "if" and "if" as used herein may be interpreted to mean "when" or "when" or "in response to determining" or "in response to detecting." Similarly, depending on the context, the phrase "if determined" or "if detected (conditions or events stated)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event) "Time" or "in response to a test (condition or event stated)".

It should also be noted that the terms "including", "comprising" or "comprising" or any other variations thereof are intended to encompass a non-exclusive inclusion, such that the item or system comprising a plurality of elements includes not only those elements but also Other elements, or elements that are inherent to such goods or systems. An element defined by the phrase "comprising a ..." does not exclude the presence of additional identical elements in the item or system including the element, without further limitation.

Finally, it should be noted that the above embodiments are only for explaining the technical solutions of the present application, and are not limited thereto; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that The technical solutions described in the foregoing embodiments may be modified, or some or all of the technical features may be equivalently replaced; and the modifications or substitutions do not deviate from the technical solutions of the embodiments of the present application. range.

Claims (51)

1. A method for pushing data, characterized in that it comprises:

   Obtaining scene data;

   At least part of the scene data is respectively pushed to a plurality of receiving objects carried by the vehicle, and the scene data is used for display.
2. The method according to claim 1, wherein there is a difference in scene data in which at least two received objects are pushed into the scene data pushed to the plurality of receiving objects.
3. The method according to claim 1, wherein before the pushing the at least part of the scene data to the plurality of receiving objects carried by the vehicle, the method further comprises:

   Processing the scene data to obtain a plurality of sub-scene data;

   Obtaining a receiving object corresponding to each of the sub-scene data;

   And pushing the at least part of the scene data to the plurality of receiving objects carried by the vehicle, respectively, including:

   Each of the sub-scene data is pushed to a corresponding receiving object.
4. The method according to claim 3, wherein in the plurality of sub-scene data, there is a difference in at least two sub-scene data.
5. The method according to claim 3, wherein the processing the scene data to obtain a plurality of sub-scene data comprises:

   The scene data is processed according to the data type of the sub-scene to obtain a plurality of sub-scene data.
6. The method according to claim 5, wherein the number of data types of the sub-scene is greater than or equal to the number of obtained sub-scene data.
7. The method according to claim 5, wherein the processing of the scene data according to the data type of the sub-scene to obtain the plurality of sub-scene data further includes:

   Determining a scene type according to the scene data;

   Obtaining a data type of the sub-scene corresponding to the scene type according to the correspondence between the scene type and the data type of the sub-scene.
8. The method according to claim 3, wherein the obtaining the receiving object corresponding to each of the sub-scene data comprises:

   The receiving object corresponding to each of the sub-scene data is determined according to the data type of the sub-scene.
9. The method according to claim 8, wherein the determining the receiving object corresponding to each of the sub-scene data according to the data type of the sub-scene comprises:

   And determining, according to a push priority corresponding to the data type of each of the sub-scene, a receiving object corresponding to each of the sub-scene data.
10. The method according to claim 8, wherein the determining the receiving object corresponding to each of the sub-scene data according to the data type of the sub-scene comprises:

    Obtaining a preset correspondence between a data type of each of the sub-scene and each received object;

    And determining, according to the correspondence, a receiving object corresponding to each of the sub-scene data.
11. The method according to claim 10, further comprising: before acquiring the preset correspondence between the data type of each of the sub-scene and each receiving object,

    Outputting, to the user, a data type of each of the sub-scene and each of the received objects;

    Receiving the correspondence determined by the user.
12. The method according to claim 7, wherein the scene type comprises:

    Navigation scene

    Entertainment scene.
13. The method according to claim 12, wherein if the navigation scenario is a road abnormal navigation scenario, the data type of the sub-scene corresponding to the road abnormal navigation scenario includes at least two of the following:

    Navigation overview maps, traffic status data, and vehicle status data.
14. The method according to claim 13, wherein if the data type of the sub-scene is a navigation overview map, the corresponding receiving object is a center console;

    If the data type of the sub-scene is traffic condition data, the corresponding receiving object is a rearview mirror;

    If the data type of the sub-scene is status data of the vehicle, the corresponding receiving object is a dashboard.
15. The method of claim 12, wherein the data type of the sub-scene corresponding to the normal navigation scene of the road comprises at least two of the following if the navigation scene is a normal navigation scene of the road:

    Navigation overview map, driving indication logo, remaining mileage overview map, and vehicle status data.
16. The method according to claim 15, wherein if the data type of the sub-scene is a driving overview map, the corresponding receiving object is a central control station;

    If the data type of the sub-scene is a remaining mileage overview map, the corresponding receiving object is a rearview mirror;

    If the data type of the sub-scene is the driving indication identifier or the status data of the vehicle, the corresponding receiving object is a dashboard.
17. The method according to claim 12, wherein if the scene type is an entertainment scene, the data type of the sub-scene corresponding to the entertainment scene includes at least two of the following:

    Entertainment data, traffic condition data, and status data of the vehicle.
18. The method according to claim 17, wherein if the data type of the sub-scene is entertainment data, the corresponding receiving object is a center console;

    If the data type of the sub-scene is traffic condition data, the corresponding receiving object is a rearview mirror;

    If the data type of the sub-scene is status data of the vehicle, the corresponding receiving object is a dashboard.
19. The method according to claim 5, wherein the data type of the sub-scene comprises at least two of the following:

    Driving assistance data, emergency data, full amount of information data, and driving necessary data.
20. The method according to claim 19, wherein the driving assistance data comprises at least one of traffic condition data and a remaining mileage overview map;

    The driving necessary data includes at least one of status data of the vehicle and a driving indication identifier;

    The full amount of information data includes at least one of a navigation overview map and entertainment data;

    The emergency data includes abnormal data of the vehicle.
21. The method according to claim 19 or 20, wherein if the data type of the sub-scene is driving assistance data or emergency data, the corresponding receiving object is a rear view mirror or a rear view mirror;

    If the data type of the sub-scene is full information data, the corresponding receiving object is a central control station;

    If the data type of the sub-scene is driving necessary data, the corresponding receiving object is a dashboard or a HUD.
22. The method according to any one of claims 1 to 21, wherein acquiring scene data comprises:

    Obtaining the scene data sent by at least one of a data collection device, a cloud server, and a smart home device having a communication connection with the vehicle.
23. The method according to any one of claims 1 to 21, wherein the receiving object comprises at least two of the following:

    A dashboard, a center console, a head-up display HUD, a rearview mirror, a mirror, and a smart terminal in communication with the vehicle.
24. A data pushing device, comprising:

    a data acquisition module, configured to acquire scene data;

    And a pushing module, configured to push at least part of the scene data to the plurality of receiving objects carried by the vehicle, where the scene data is used for display.
25. The apparatus according to claim 24, wherein there is a difference in scene data in which at least two of the received objects are pushed into the scene data pushed to the plurality of receiving objects.
26. The device according to claim 24, further comprising a processing module and an object acquisition module,

    The processing module is configured to process the scene data to obtain a plurality of sub-scene data;

    The object obtaining module is configured to acquire a receiving object corresponding to each of the sub-scene data;

    The pushing module is specifically configured to push each of the sub-scene data to a corresponding receiving object.
27. The device according to claim 26, wherein the processing module is configured to process the scene data according to a data type of the sub-scene to obtain a plurality of sub-scene data.
28. The device according to claim 27, further comprising: a type obtaining module, configured to determine a scene type according to the scene data, and obtain the information according to a correspondence between the scene type and a data type of the sub-scene The data type of the sub-scene corresponding to the scene type.
29. The device according to claim 26, wherein the object obtaining module is configured to determine, according to a data type of the sub-scene, a receiving object corresponding to each of the sub-scene data.
30. The device according to claim 29, wherein the object obtaining module is configured to determine a receiving object corresponding to each of the sub-scene data according to a pushing priority corresponding to a data type of each of the sub-scene.
31. The device according to claim 29, wherein the object obtaining module is configured to: obtain a preset correspondence between a data type of each of the sub-scene and each received object, and determine each according to the corresponding relationship The receiving object corresponding to the sub-scene data.
32. The device according to claim 31, further comprising: a relationship obtaining module, configured to output a data type of each of the sub-scene and each of the receiving objects to a user, and receive the corresponding relationship determined by the user .
33. The device according to any one of claims 24 to 32, wherein the data acquisition module is specifically configured to acquire a data collection device, a cloud server, and a communication connection with the vehicle in the vehicle. The scene data transmitted by at least one of the smart home devices.
34. A data pushing device, comprising:

    An input device, configured to acquire scene data;

    And a processor coupled to the output device and the input device, configured to control the output device to respectively push at least part of the scene data to a plurality of receiving objects carried by the vehicle, where the scene data is used for display.
35. The device according to claim 34, wherein the processor is further configured to process the scene data to obtain a plurality of sub-scene data, and acquire a receiving object corresponding to each of the sub-scene data;

    The processor is specifically configured to control the output device to push each of the sub-scene data to a corresponding receiving pair. Elephant.
36. The device according to claim 35, wherein the processor is specifically configured to process the scene data according to a data type of the sub-scene to obtain a plurality of sub-scene data.
37. The device according to claim 35, wherein the processor is further configured to determine, according to a data type of the sub-scene, a receiving object corresponding to each of the sub-scene data.
38. The device according to claim 37, wherein the processor is configured to determine a receiving object corresponding to each of the sub-scene data according to a pushing priority corresponding to a data type of each of the sub-scene.
39. The device according to claim 37, wherein the processor is configured to acquire a preset correspondence between a data type of each of the preset sub-scene and each received object, and determine each location according to the corresponding relationship. The receiving object corresponding to the sub-scene data.
40. The device according to any one of claims 34 to 39, wherein the input device is specifically configured to acquire a data collection device, a cloud server, and a communication connection with the vehicle in the vehicle. The scene data transmitted by at least one of the home devices.
41. A vehicle control device, comprising: an onboard output device, an onboard input device, and an onboard processor coupled to the onboard output device and the onboard input device;

    The onboard input device is configured to acquire scene data;

    The onboard processor is configured to control the onboard output device to push at least part of the scene data to a plurality of receiving objects carried by the vehicle, where the scene data is used for display.
42. The device according to claim 41, wherein said onboard input device comprises at least one of a programmable interface of software, a transceiver, and a device-oriented in-vehicle device interface;

    The onboard output device includes at least one of a software programmable interface, a transceiver, and a device oriented in-vehicle device interface.
43. The device according to claim 41 or 42, wherein the onboard processor is operative to perform the method of any of the preceding claims 2 to 23.
44. An in-vehicle internet operating system, comprising:

    Input control unit, controlling the vehicle input device to acquire scene data;

    And an output control unit that controls the vehicle-mounted output device to respectively push at least part of the scene data to the plurality of receiving objects carried by the vehicle, where the scene data is used for display.
45. The operating system according to claim 44, further comprising a push control unit

    The push control unit controls the data push system to process the scene data to obtain a plurality of sub-scene data;

    The push control unit further controls the data pushing system to acquire a receiving object corresponding to each of the sub-scene data;

    The output control unit further controls the vehicle-mounted output device to push each of the sub-scene data to a corresponding receiving object.
46. The operating system according to claim 45, wherein the push control unit further controls the data push system to process the scene data according to a data type of the sub-scene to obtain a plurality of sub-scene data.
47. The operating system according to claim 46, wherein the push control unit further controls the data push system to determine a scene type according to the scene data, according to a correspondence between the scene type and a data type of the sub-scene Relationship: The data type of the sub-scene corresponding to the scene type is obtained.
48. The operating system according to claim 45, wherein the push control unit further controls the data push system to determine a receiving object corresponding to each of the sub-scene data according to a data type of the sub-scene.
49. The operating system according to claim 48, wherein the push control unit further controls the data push system to determine, according to the push priority corresponding to the data type of each of the sub-scene, the sub-scene data corresponding to each of the sub-scene data Receive object.
50. The operating system according to claim 48, wherein the push control unit further controls the data push system to acquire a preset correspondence between a data type of each of the sub-scene and each received object, according to the Corresponding relationship, determining a receiving object corresponding to each of the sub-scene data.
51. The operating system according to any one of claims 44 to 50, wherein the input control unit further controls the in-vehicle input device to acquire the data collection device, the cloud server, and the vehicle in the vehicle. The scene data transmitted by at least one of the communication-connected smart home devices.

Images