Method, device and vehicle-mounted system for sharing vehicle-mounted terminal data

Abstract

The present invention discloses a method, device and vehicle-mounted system for sharing vehicle-mounted terminal data, the method comprising: when a login operation is detected on a target vehicle-mounted zero terminal, determining whether the account used for the login operation is a first account; when the account is the first account, controlling the target vehicle-mounted zero terminal to interact with a first virtual machine for data, wherein the first account is an account bound to the first virtual machine, and the first virtual machine is a virtual machine corresponding to the target vehicle-mounted zero terminal; when the account is a second account, controlling the target vehicle-mounted zero terminal to receive display interface data sent by the second virtual machine, the second account is a different account from the first account, and the second virtual machine is a virtual machine bound to the second account. The method solves the problem in the related art that the vehicle-mounted terminal runs locally, resulting in the inability to flexibly use the vehicle-mounted terminal data.

Description

Technical Field

[0001] The present invention relates to the field of vehicle-mounted terminal technology, and in particular to a method, device, vehicle-mounted system, computer-readable storage medium and processor for sharing vehicle-mounted terminal data. Background Art

[0002] The vehicle-mounted terminal is the front-end device of the vehicle monitoring and management system, and can also be called the vehicle dispatch monitoring terminal (TCU terminal).

[0003] Generally, the vehicle terminal integrates multiple functions such as positioning, communication, and vehicle driving recorder, and has powerful business dispatching functions and data processing capabilities. In addition, it also supports phone book calls, text message voice broadcasts, and has security alarms, wire cutting alarms, and remote safety oil and power off safety protection functions.

[0004] However, current in-vehicle terminals generally run locally, and the same in-vehicle terminal is generally bound to the car owner. If different people drive the same car, the data of the in-vehicle terminal cannot be switched in time because it is stored locally.

[0005] Currently, no effective solution has been proposed to address the problem in related technologies that the vehicle-mounted terminal runs locally, resulting in the inability to flexibly use the vehicle-mounted terminal data. Summary of the invention

[0006] The main purpose of the present invention is to provide a method, device, vehicle-mounted system, computer-readable storage medium and processor for sharing vehicle-mounted terminal data to solve the problem in the related art that the vehicle-mounted terminal runs locally, resulting in the inability to flexibly use the vehicle-mounted terminal data.

[0007] In order to achieve the above-mentioned purpose, according to one aspect of the present invention, a method for sharing vehicle-mounted terminal data is provided, including: when a login operation is detected on a target vehicle-mounted zero terminal, determining whether the account used for the login operation is a first account; when the account is the first account, controlling the target vehicle-mounted zero terminal to interact with a first virtual machine for data, wherein the first account is an account bound to the first virtual machine, and the first virtual machine is a virtual machine corresponding to the target vehicle-mounted zero terminal; when the account is a second account, controlling the target vehicle-mounted zero terminal to receive display interface data sent by the second virtual machine, the second account is a different account from the first account, and the second virtual machine is a virtual machine bound to the second account.

[0008] Optionally, the target vehicle-mounted zero terminal includes a decoder. When the account is a second account, after controlling the target vehicle-mounted zero terminal to receive the display interface data sent by the second virtual machine, the method further includes: controlling the decoder to decode the display interface data to obtain a target image, and the target image is an image of the display interface corresponding to the display interface data.

[0009] Optionally, after controlling the decoder to decode the display interface data to obtain a target image, the method further includes: controlling a target display to receive and display the target image, wherein the target display corresponds to the target vehicle-mounted zero terminal.

[0010] Optionally, before controlling the target display to receive and display the target image, the method further includes: controlling the target vehicle-mounted zero terminal to send the target image to the target display through a vGTP protocol.

[0011] Optionally, after controlling the target display to display the target image, the method further includes: controlling the target vehicle-mounted zero terminal to receive control instructions of the display, wherein the control instructions are generated based on the driver's operation on the display; controlling the target vehicle-mounted zero terminal to control the target vehicle according to the control instructions, wherein the target vehicle is a car equipped with the target vehicle-mounted zero terminal.

[0012] Optionally, when the account is a second account, the method further includes: controlling the target vehicle-mounted zero terminal to receive diagnostic data of the target vehicle fed back by the vehicle bus, and sending the diagnostic data to the first virtual machine, the target vehicle being a car equipped with the target vehicle-mounted zero terminal.

[0013] Optionally, when the account is a second account, the method further includes: terminating the first virtual machine from sending the display interface data; or when detecting that the target vehicle-mounted zero terminal has received the display interface data sent by the first virtual machine, controlling the target vehicle-mounted zero terminal not to decode the display interface data.

[0014] According to another aspect of the present invention, a device for sharing vehicle-mounted terminal data is provided, comprising: a determination unit, for determining whether the account used for the login operation is a first account when a login operation is detected on a target vehicle-mounted zero terminal; a first control unit, for controlling the target vehicle-mounted zero terminal to interact with a first virtual machine for data when the account is the first account, wherein the first account is an account bound to the first virtual machine, and the first virtual machine is a virtual machine corresponding to the target vehicle-mounted zero terminal; a second control unit, for controlling the target vehicle-mounted zero terminal to receive display interface data sent by a second virtual machine when the account is a second account, the second account is a different account from the first account, and the second virtual machine is a virtual machine bound to the second account.

[0015] According to another aspect of the present invention, a vehicle-mounted system is provided, comprising: a server, wherein a plurality of virtual machines are configured in the server, and the virtual machines are used to send display interface data; at least one vehicle-mounted zero terminal, used to determine a bound virtual machine to be determined for an account used for a login operation, the bound virtual machine being the virtual machine bound to the account, receiving the display interface data sent by the bound virtual machine and processing the display interface data to obtain a target image; and at least one display, communicatively connected to the corresponding vehicle-mounted zero terminal, and used to display the target image.

[0016] According to another aspect of the present invention, the vehicle-mounted zero terminal includes: a decoder for decoding the display interface data to obtain the target image.

[0017] According to another aspect of the present invention, the server further includes: a management unit, configured to manage and adjust the correspondence between the password of the account and the virtual machine.

[0018] According to another aspect of the present invention, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored program, wherein the program executes any one of the methods described.

[0019] According to still another aspect of the present invention, a processor is provided, wherein the processor is used to run a program, wherein the program executes any one of the methods when running.

[0020] Through the present invention, in the above-mentioned vehicle terminal data sharing method, first, when a login operation is detected on the target vehicle zero terminal, it is determined whether the account used for the above-mentioned login operation is the first account; then, when the above-mentioned account is the above-mentioned first account, the above-mentioned target vehicle zero terminal is controlled to interact with the first virtual machine for data, wherein the above-mentioned first account is an account bound to the first virtual machine, and the above-mentioned first virtual machine is a virtual machine corresponding to the above-mentioned target vehicle zero terminal; finally, when the above-mentioned account is a second account, the above-mentioned target vehicle zero terminal is controlled to receive display interface data sent by the second virtual machine, the above-mentioned second account is a different account from the above-mentioned first account, and the above-mentioned second virtual machine is a virtual machine bound to the above-mentioned second account. The sharing method determines whether the logged-in account is a bound account of the first virtual machine, that is, whether it is a bound account of the virtual machine corresponding to the target vehicle-mounted zero terminal, so that when the above account is the first account, the above first virtual machine is controlled to exchange data with the above target vehicle-mounted zero terminal, and when the above account is the second account, the above first virtual machine is controlled to receive display interface data sent by the second virtual machine, that is, receive display interface data sent by the virtual machine bound to the second account, thereby ensuring that no matter whether the logged-in account is a bound account of the virtual machine corresponding to the target vehicle-mounted zero terminal, the target vehicle-mounted zero terminal can log in to the virtual machine bound to the account to receive display interface data sent by the virtual machine bound to the account, thereby avoiding the problem that the vehicle-mounted data of the car where the target vehicle-mounted zero terminal is located cannot be shared due to local storage when driven by different drivers, and solves the problem in the related technology that the vehicle-mounted terminal runs locally, resulting in the inability to flexibly use the vehicle-mounted terminal data. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings constituting a part of the present invention are used to provide a further understanding of the present invention. The exemplary embodiments of the present invention and their descriptions are used to explain the present invention and do not constitute an improper limitation of the present invention. In the accompanying drawings:

[0022] Figure 1 is a flow chart of a method for sharing vehicle terminal data provided in an embodiment of the present invention;

[0023] Figure 2 is a schematic diagram of a vehicle terminal data sharing device provided according to an embodiment of the present invention;

[0024] Figure 3 is a schematic diagram of a vehicle-mounted system provided according to an embodiment of the present invention;

[0025] Figure 4 is a schematic diagram of a vehicle-mounted zero terminal provided according to an embodiment of the present invention;

[0026] Figure 5 It is a schematic diagram of the on-off of each path of the vehicle-mounted system provided according to an embodiment of the present invention. DETAILED DESCRIPTION

[0027] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments can be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0028] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so as to describe the embodiments of the present invention described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0030] According to an embodiment of the present invention, a method for sharing vehicle-mounted terminal data is provided.

[0031] Figure 1 FIG. 1 is a flow chart of a method for sharing vehicle terminal data according to an embodiment of the present invention. Figure 1 As shown, the invention comprises the following steps:

[0032] Step S101, when a login operation is detected on the target vehicle-mounted zero terminal, determining whether the account used for the login operation is a first account;

[0033] Step S102, when the account is the first account, controlling the target vehicle zero terminal to perform data interaction with the first virtual machine, wherein the first account is an account bound to the first virtual machine, and the first virtual machine is a virtual machine corresponding to the target vehicle zero terminal;

[0034] Step S103, when the above-mentioned account is a second account, control the above-mentioned target vehicle zero terminal to receive display interface data sent by the second virtual machine, the above-mentioned second account is a different account from the above-mentioned first account, and the above-mentioned second virtual machine is a virtual machine bound to the above-mentioned second account.

[0035] In the above-mentioned vehicle-mounted terminal data sharing method, first, when a login operation is detected on the target vehicle-mounted zero terminal, it is determined whether the account used for the above-mentioned login operation is the first account; then, when the above-mentioned account is the above-mentioned first account, the above-mentioned target vehicle-mounted zero terminal is controlled to interact with the first virtual machine for data, wherein the above-mentioned first account is an account bound to the first virtual machine, and the above-mentioned first virtual machine is a virtual machine corresponding to the above-mentioned target vehicle-mounted zero terminal; finally, when the above-mentioned account is a second account, the above-mentioned target vehicle-mounted zero terminal is controlled to receive display interface data sent by the second virtual machine, the above-mentioned second account is a different account from the above-mentioned first account, and the above-mentioned second virtual machine is a virtual machine bound to the above-mentioned second account. The sharing method determines whether the logged-in account is a bound account of the first virtual machine, that is, whether it is a bound account of the virtual machine corresponding to the target vehicle-mounted zero terminal, so that when the above account is the first account, the above first virtual machine is controlled to exchange data with the above target vehicle-mounted zero terminal, and when the above account is the second account, the above first virtual machine is controlled to receive display interface data sent by the second virtual machine, that is, receive display interface data sent by the virtual machine bound to the second account, thereby ensuring that no matter whether the logged-in account is a bound account of the virtual machine corresponding to the target vehicle-mounted zero terminal, the target vehicle-mounted zero terminal can log in to the virtual machine bound to the account to receive display interface data sent by the virtual machine bound to the account, thereby avoiding the problem that the vehicle-mounted data of the car where the target vehicle-mounted zero terminal is located cannot be shared due to local storage when driven by different drivers, and solves the problem in the related technology that the vehicle-mounted terminal runs locally, resulting in the inability to flexibly use the vehicle-mounted terminal data.

[0036] It should be noted that the steps shown in the flowcharts of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and that, although a logical order is shown in the flowcharts, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0037] In one embodiment of the present application, the target vehicle zero terminal includes a decoder, and when the account is the second account, after controlling the target vehicle zero terminal to receive the display interface data sent by the second virtual machine, the method further includes: controlling the decoder to decode the display interface data to obtain a target image, and the target image is an image of the display interface corresponding to the display interface data. Specifically, after the target vehicle zero terminal receives the display interface data, the decoder decodes the display interface data to obtain the target image for display.

[0038] In one embodiment of the present application, after controlling the decoder to decode the display interface data to obtain the target image, the method further includes: controlling the target display to receive and display the target image, wherein the target display corresponds to the target vehicle zero terminal. Specifically, the target display displays the target image, that is, displays the display interface of the logged-in virtual machine, so that the driver can operate it easily, wherein if the login account is the first account, the display interface of the first virtual machine is displayed, and if the login account is the second account, the display interface of the second virtual machine is displayed.

[0039] In one embodiment of the present application, before controlling the target display to receive and display the target image, the method further includes: controlling the target vehicle zero terminal to send the target image to the target display via the vGTP protocol. Specifically, by transmitting the target image via the vGTP protocol, lossless transmission of the image can be achieved, the display effect of the target image can be ensured, and the driver can operate the image easily.

[0040] In one embodiment of the present application, after controlling the target display to display the target image, the method further includes: controlling the target vehicle-mounted zero terminal to receive a control instruction of the display, the control instruction being generated according to the driver's operation on the display; controlling the target vehicle-mounted zero terminal to control the target vehicle according to the control instruction, the target vehicle being a car equipped with the target vehicle-mounted zero terminal. Specifically, the driver operates the display interface of the virtual machine so that the display generates a corresponding control instruction and sends it to the target vehicle-mounted zero terminal, so that the target vehicle-mounted zero terminal controls the target vehicle according to the control instruction, thereby improving the driving experience.

[0041] It should be noted that the above-mentioned sharing method allows a driver with an unbound account to log in to the virtual machine bound to the driver's account when driving the target vehicle, so that the virtual machine can share display interface data to the target vehicle-mounted zero terminal, and display the display interface of the virtual machine on the target display screen according to the display interface data, so that the driver can operate the display interface of the virtual machine to control the target vehicle, avoid the problem of inconvenience caused by the driver's unfamiliarity when operating the display interface of the virtual machine that is not bound to his own account, and improve the driving experience.

[0042] In one embodiment of the present application, when the above-mentioned account is a second account, the above-mentioned method further includes: controlling the above-mentioned target vehicle-mounted zero terminal to receive diagnostic data of the target vehicle fed back by the vehicle bus, and sending the above-mentioned diagnostic data to the above-mentioned first virtual machine, and the above-mentioned target vehicle is a car equipped with the above-mentioned target vehicle-mounted zero terminal. Specifically, the data collected by the target vehicle-mounted zero terminal is divided into sharable data and non-sharable data, and the non-sharable data includes the diagnostic data of the target vehicle. Since the first virtual machine is bound to the target vehicle-mounted zero terminal, the above-mentioned diagnostic data is sent to the above-mentioned first virtual machine for storage, and the first virtual machine can be logged in to query during maintenance. The target vehicle-mounted zero terminal and the first virtual machine interact with data, and non-sharable data can be transmitted to each other, saving storage resources and avoiding data leakage.

[0043] In one embodiment of the present application, when the above-mentioned account is a second account, the above-mentioned method further includes: terminating the above-mentioned first virtual machine from sending the above-mentioned display interface data; or when detecting that the above-mentioned target vehicle-mounted zero terminal has received the above-mentioned display interface data sent by the above-mentioned first virtual machine, controlling the above-mentioned target vehicle-mounted zero terminal not to decode the above-mentioned display interface data. Specifically, when the above-mentioned account is a second account, the target vehicle-mounted zero terminal has received the above-mentioned display interface data sent by the second virtual machine, therefore, terminating the first virtual machine from sending the display interface data, or even if the display interface data sent by the first virtual machine is received, decoding is not performed, so that the target display only displays the display interface of the second virtual machine, and does not display the display interface of the first virtual machine, to avoid cross-image or overlapping display.

[0044] The embodiment of the present application also provides a vehicle terminal data sharing device. It should be noted that the vehicle terminal data sharing device of the embodiment of the present application can be used to execute the vehicle terminal data sharing method provided by the embodiment of the present application. The vehicle terminal data sharing device provided by the embodiment of the present application is introduced below.

[0045] Figure 2 Schematic diagram of a device for sharing vehicle terminal data according to an embodiment of the present application. Figure 2 As shown, the device comprises:

[0046] The determination unit 10 is used to determine whether the account used for the login operation is the first account when a login operation is detected on the target vehicle-mounted zero terminal;

[0047] The first control unit 20 is used to control the target vehicle zero terminal to perform data interaction with the first virtual machine when the account is the first account, wherein the first account is an account bound to the first virtual machine, and the first virtual machine is a virtual machine corresponding to the target vehicle zero terminal;

[0048] The second control unit 30 is used to control the target vehicle-mounted zero terminal to receive display interface data sent by the second virtual machine when the above-mentioned account is a second account. The above-mentioned second account is a different account from the above-mentioned first account, and the above-mentioned second virtual machine is a virtual machine bound to the above-mentioned second account.

[0049] In the above-mentioned vehicle terminal data sharing device, when the determination unit detects a login operation on the target vehicle zero terminal, it determines whether the account used for the above-mentioned login operation is the first account; when the above-mentioned account is the above-mentioned first account, the first control unit controls the above-mentioned target vehicle zero terminal to interact with the first virtual machine for data, wherein the above-mentioned first account is an account bound to the first virtual machine, and the above-mentioned first virtual machine is a virtual machine corresponding to the above-mentioned target vehicle zero terminal; when the above-mentioned account is the second account, the second control unit controls the above-mentioned target vehicle zero terminal to receive display interface data sent by the second virtual machine, the above-mentioned second account is a different account from the above-mentioned first account, and the above-mentioned second virtual machine is a virtual machine bound to the above-mentioned second account. The sharing device determines whether the logged-in account is a bound account of the first virtual machine, that is, whether it is a bound account of the virtual machine corresponding to the target vehicle-mounted zero terminal, so that when the above account is the first account, the above first virtual machine is controlled to exchange data with the above target vehicle-mounted zero terminal, and when the above account is the second account, the above first virtual machine is controlled to receive display interface data sent by the second virtual machine, that is, receive display interface data sent by the virtual machine bound to the second account, thereby ensuring that no matter whether the logged-in account is a bound account of the virtual machine corresponding to the target vehicle-mounted zero terminal, the target vehicle-mounted zero terminal can log in to the virtual machine bound to the account to receive display interface data sent by the virtual machine bound to the account, thereby avoiding the problem that the vehicle-mounted data of the car where the target vehicle-mounted zero terminal is located cannot be shared due to local storage by different drivers, and solves the problem in the related technology that the vehicle-mounted terminal runs locally, resulting in the inability to flexibly use the vehicle-mounted terminal data.

[0050] In one embodiment of the present application, the target vehicle zero terminal includes a decoder, and the device further includes a third control unit, wherein the third control unit is used to control the target vehicle zero terminal to receive the display interface data sent by the second virtual machine, and then control the decoder to decode the display interface data to obtain a target image when the account is the second account. The target image is an image of the display interface corresponding to the display interface data. Specifically, after the target vehicle zero terminal receives the display interface data, the decoder decodes the display interface data to obtain the target image for display.

[0051] In one embodiment of the present application, the device further includes a fourth control unit, wherein the fourth control unit is used to control the target display to receive and display the target image after controlling the decoder to decode the display interface data to obtain the target image, wherein the target display corresponds to the target vehicle-mounted zero terminal. Specifically, the target display displays the target image, that is, displays the display interface of the logged-in virtual machine, so as to facilitate the driver to operate, wherein, if the login account is the first account, the display interface of the first virtual machine is displayed, and if the login account is the second account, the display interface of the second virtual machine is displayed.

[0052] In one embodiment of the present application, the device further includes a fifth control unit, wherein the fifth control unit is used to control the target vehicle zero terminal to send the target image to the target display through the vGTP protocol before the target display receives and displays the target image. Specifically, by transmitting the target image through the vGTP protocol, lossless transmission of the image can be achieved, the display effect of the target image is guaranteed, and the driver is convenient for operation.

[0053] In one embodiment of the present application, the device further includes a sixth control unit, and the sixth control unit includes a first control module and a second control module, wherein the first control module is used to control the target vehicle-mounted zero terminal to receive the control instruction of the above-mentioned display after controlling the above-mentioned target display to display the above-mentioned target image, and the above-mentioned control instruction is generated according to the driver's operation on the above-mentioned display; the second control module is used to control the above-mentioned target vehicle-mounted zero terminal to control the target vehicle according to the above-mentioned control instruction, and the above-mentioned target vehicle is a car equipped with the above-mentioned target vehicle-mounted zero terminal. Specifically, the driver operates the display interface of the virtual machine, so that the display generates corresponding control instructions and sends them to the target vehicle-mounted zero terminal, so that the target vehicle-mounted zero terminal controls the target vehicle according to the above-mentioned control instructions, thereby improving the driving experience.

[0054] It should be noted that the above-mentioned sharing method allows a driver with an unbound account to log in to the virtual machine bound to the driver's account when driving the target vehicle, so that the virtual machine can share display interface data to the target vehicle-mounted zero terminal, and display the display interface of the virtual machine on the target display screen according to the display interface data, so that the driver can operate the display interface of the virtual machine to control the target vehicle, avoid the problem of inconvenience caused by the driver's unfamiliarity when operating the display interface of the virtual machine that is not bound to his own account, and improve the driving experience.

[0055] In one embodiment of the present application, when the above-mentioned account is a second account, the above-mentioned device further includes a sending unit, and the above-mentioned sending unit is used to control the above-mentioned target vehicle-mounted zero terminal to receive the diagnostic data of the target vehicle fed back by the vehicle bus, and send the above-mentioned diagnostic data to the above-mentioned first virtual machine, and the above-mentioned target vehicle is a car equipped with the above-mentioned target vehicle-mounted zero terminal. Specifically, the data collected by the target vehicle-mounted zero terminal is divided into sharable data and non-sharable data, and the non-sharable data includes the diagnostic data of the target vehicle. Since the first virtual machine is bound to the target vehicle-mounted zero terminal, the above-mentioned diagnostic data is sent to the above-mentioned first virtual machine for storage, and the first virtual machine can be logged in to query during maintenance. The target vehicle-mounted zero terminal and the first virtual machine interact with data, and non-sharable data can be transmitted to each other, saving storage resources and avoiding data leakage.

[0056] In one embodiment of the present application, when the above-mentioned account is the second account, the above-mentioned device further includes a seventh control unit, and the above-mentioned seventh control unit includes a third control module and a fourth control module, wherein the above-mentioned third control module is used to stop the above-mentioned first virtual machine from sending the above-mentioned display interface data; or the above-mentioned fourth control module is used to control the above-mentioned target vehicle-mounted zero terminal not to decode the above-mentioned display interface data when it is detected that the above-mentioned target vehicle-mounted zero terminal has received the above-mentioned display interface data sent by the above-mentioned first virtual machine. Specifically, when the above-mentioned account is the second account, the target vehicle-mounted zero terminal has received the above-mentioned display interface data sent by the second virtual machine, and therefore, the first virtual machine is stopped from sending the display interface data, or even if the display interface data sent by the first virtual machine is received, decoding is not performed, so that the target display only displays the display interface of the second virtual machine, and does not display the display interface of the first virtual machine, so as to avoid cross-image or overlapping display.

[0057] The present application also provides a vehicle-mounted system, such as Figure 3 As shown, the vehicle-mounted system includes:

[0058] A server, wherein the server is configured with a plurality of virtual machines, and the virtual machines are used to send display interface data;

[0059] At least one vehicle-mounted zero terminal, used to determine the account used for the login operation to determine the bound virtual machine, the bound virtual machine is the virtual machine bound to the account, receive the display interface data sent by the bound virtual machine and process the display interface data to obtain a target image;

[0060] At least one display is communicatively connected to the corresponding vehicle-mounted zero terminal and is used to display the target image.

[0061] In the above-mentioned vehicle-mounted system, the above-mentioned server is configured with a plurality of virtual machines, and the above-mentioned virtual machines are used to send display interface data; at least one vehicle-mounted zero terminal is used to determine the account used for the login operation to determine the bound virtual machine, and the above-mentioned bound virtual machine is the above-mentioned virtual machine bound to the above-mentioned account, receives the above-mentioned display interface data sent by the above-mentioned bound virtual machine and processes the above-mentioned display interface data to obtain the target image; at least one display is connected to the corresponding vehicle-mounted zero terminal in communication, and is used to display the above-mentioned target image. In the vehicle-mounted zero terminal of the vehicle-mounted system, the vehicle-mounted zero terminal determines the bound virtual machine corresponding to the account used for the login operation to log in to the bound virtual machine corresponding to the account, thereby receiving the display interface data sent by the bound virtual machine and processing the display interface data to obtain the target image, and sending it to the corresponding display for display, thereby ensuring that regardless of whether the logged-in account is the bound account of the virtual machine corresponding to the vehicle-mounted zero terminal, the vehicle-mounted zero terminal can log in to the virtual machine bound to the account to receive the display interface data sent by the virtual machine bound to the account, thereby avoiding the problem that the vehicle-mounted data of the vehicle where the target vehicle-mounted zero terminal is located cannot be shared due to local storage when driven by different drivers, and solves the problem that the vehicle-mounted terminal in the related technology runs locally, resulting in the inability to flexibly use the vehicle-mounted terminal data.

[0062] In one embodiment of the present application, Figure 4 As shown, the vehicle-mounted zero terminal includes a decoder, and the decoder is used to decode the display interface data to obtain the target image. Specifically, after the target vehicle-mounted zero terminal receives the display interface data, the decoder decodes the display interface data to obtain the target image for display.

[0063] It should be noted that the above-mentioned vehicle-mounted zero terminal also includes multiple interfaces, such as FUSE interface, that is, device fuse interface; ANT1 and ANT2 interfaces, that is, wireless network antenna interface; GPS antenna interface; J1 interface, that is, power input, vehicle start signal input, video input and output and camera power interface; J2 interface, that is, driving signal input, switch quantity or dry node output, analog voltage signal input, RS232 bus interface, CAN bus interface, RS485 bus interface integrated port pin definition; SD memory card socket; LAN network cable socket; USB data cable interface; SIM / UIM card socket, etc.

[0064] In one embodiment of the present application, Figure 3 As shown, the server further includes a management unit, which is used to manage and adjust the correspondence between the password of the account and the virtual machine. Specifically, the management unit manages and adjusts the correspondence between the password of the account and the virtual machine, that is, the password of the account can be modified through the management unit to improve the user experience.

[0065] It should be noted that if Figure 5As shown, assuming there are three vehicle zero terminals, the car owners correspond to accounts USER1, USER2 and USER3 respectively, then the default binding is USER1 and virtual machine 1, virtual machine 1 corresponds to vehicle zero terminal 1, USER2 and virtual machine 2 are bound, virtual machine 2 corresponds to vehicle zero terminal 2, USER3 and virtual machine 3 are bound, virtual machine 3 is bound to vehicle zero terminal 3, the car owner USER2 logs in to virtual machine 2 through vehicle zero terminal 1, and the uplink path of vehicle zero terminal 1 is connected. Figure 3 The middle passage ① is represented by a solid line, and the downlink passage of the vehicle zero terminal 1 is connected. Figure 3 The middle passage ② is indicated by a dotted line.

[0066] It should also be noted that for a virtual machine, multiple vehicle zero terminals can log in to a virtual machine at the same time. For example, for virtual machine 2, the USER2 account logs in to virtual machine 2 through vehicle zero terminal 1 and vehicle zero terminal 2 at the same time. First, the vehicle zero terminal bound to USER2 needs to be identified, and the screen of virtual machine 2 is sent to another zero terminal. In addition, the server can set the same account to log in to the virtual machine bound to the account through at most two vehicle zero terminals at the same time.

[0067] The above-mentioned vehicle terminal data sharing device includes a processor and a memory. The above-mentioned determination unit, the first control unit, etc. and the second control unit are all stored in the memory as program units, and the processor executes the above-mentioned program units stored in the memory to realize corresponding functions.

[0068] The processor includes a kernel, which retrieves the corresponding program unit from the memory. One or more kernels can be set, and the kernel parameters can be adjusted to solve the problem in the related art that the vehicle terminal runs locally, resulting in the inability to flexibly use the vehicle terminal data.

[0069] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM, and the memory includes at least one memory chip.

[0070] An embodiment of the present invention provides a storage medium on which a program is stored. When the program is executed by a processor, the above method is implemented.

[0071] An embodiment of the present invention provides a processor, and the processor is used to run a program, wherein the method is executed when the program is run.

[0072] An embodiment of the present invention provides a device, the device including a processor, a memory, and a program stored in the memory and executable on the processor, and when the processor executes the program, the following steps are implemented:

[0073] Step S101, when a login operation is detected on the target vehicle-mounted zero terminal, determining whether the account used for the login operation is a first account;

[0074] Step S102, when the account is the first account, controlling the target vehicle zero terminal to perform data interaction with the first virtual machine, wherein the first account is an account bound to the first virtual machine, and the first virtual machine is a virtual machine corresponding to the target vehicle zero terminal;

[0075] Step S103, when the above-mentioned account is a second account, control the above-mentioned target vehicle zero terminal to receive display interface data sent by the second virtual machine, the above-mentioned second account is a different account from the above-mentioned first account, and the above-mentioned second virtual machine is a virtual machine bound to the above-mentioned second account.

[0076] The devices in this article can be servers, PCs, PADs, mobile phones, etc.

[0077] The present invention also provides a computer program product, which, when executed on a data processing device, is suitable for executing a program for initializing the following method steps:

[0078] Step S101, when a login operation is detected on the target vehicle-mounted zero terminal, determining whether the account used for the login operation is a first account;

[0079] Step S102, when the account is the first account, controlling the target vehicle zero terminal to perform data interaction with the first virtual machine, wherein the first account is an account bound to the first virtual machine, and the first virtual machine is a virtual machine corresponding to the target vehicle zero terminal;

[0080] Step S103, when the above-mentioned account is a second account, control the above-mentioned target vehicle zero terminal to receive display interface data sent by the second virtual machine, the above-mentioned second account is a different account from the above-mentioned first account, and the above-mentioned second virtual machine is a virtual machine bound to the above-mentioned second account.

[0081] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0082] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0083] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0084] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0085] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0086] The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0087] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0088] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0089] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, systems or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0090] The above are only embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent substitution, improvement, etc. made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.

Claims

1. A method for sharing vehicle terminal data, characterized in that: include: When a login operation is detected on the target vehicle-mounted zero terminal, determining whether the account used for the login operation is the first account; In the case where the account is the first account, controlling the target vehicle zero terminal to perform data interaction with the first virtual machine, wherein the first account is an account bound to the first virtual machine, and the first virtual machine is a virtual machine corresponding to the target vehicle zero terminal; In the case where the account is a second account, controlling the target vehicle zero terminal to receive display interface data sent by a second virtual machine, the second account is a different account from the first account, and the second virtual machine is a virtual machine bound to the second account; In the case where the account is a second account, the method further includes: controlling the target vehicle zero terminal to receive diagnostic data of the target vehicle fed back by the vehicle bus, and sending the diagnostic data to the first virtual machine, the target vehicle being a car provided with the target vehicle zero terminal; When the account is a second account, the method also includes: terminating the first virtual machine from sending the display interface data; or when detecting that the target vehicle-mounted zero terminal has received the display interface data sent by the first virtual machine, controlling the target vehicle-mounted zero terminal not to decode the display interface data.

2. The method according to claim 1, characterized in that The target vehicle zero terminal includes a decoder. When the account is the second account, after controlling the target vehicle zero terminal to receive display interface data sent by the second virtual machine, the method further includes: The decoder is controlled to decode the display interface data to obtain a target image, where the target image is an image of the display interface corresponding to the display interface data.

3. The method according to claim 2, characterized in that After controlling the decoder to decode the display interface data to obtain a target image, the method further includes: Control the target display to receive and display the target image, wherein the target display corresponds to the target vehicle-mounted zero terminal.

4. The method according to claim 3, characterized in that Before controlling the target display to receive and display the target image, the method further includes: The target vehicle-mounted zero terminal is controlled to send the target image to the target display through the vGTP protocol.

5. The method according to claim 3, characterized in that: After controlling the target display to display the target image, the method further includes: Controlling the target vehicle-mounted zero terminal to receive a control instruction of the display, wherein the control instruction is generated according to the driver's operation on the display; The target vehicle-mounted zero terminal is controlled to control the target vehicle according to the control instruction, and the target vehicle is a car equipped with the target vehicle-mounted zero terminal.

6. A vehicle terminal data sharing device, characterized in that: include: A determination unit, configured to, when a login operation is detected on the target vehicle-mounted zero terminal, determine whether the account used for the login operation is the first account; A first control unit, configured to control the target vehicle zero terminal to perform data interaction with a first virtual machine when the account is the first account, wherein the first account is an account bound to the first virtual machine, and the first virtual machine is a virtual machine corresponding to the target vehicle zero terminal; a second control unit, configured to control the target vehicle-mounted zero terminal to receive display interface data sent by a second virtual machine when the account is a second account, the second account is different from the first account, and the second virtual machine is a virtual machine bound to the second account; The device further includes a sending unit, which is used to control the target vehicle zero terminal to receive diagnostic data of the target vehicle fed back by the vehicle bus and send the diagnostic data to the first virtual machine when the account is the second account, and the target vehicle is a car equipped with the target vehicle zero terminal; The device also includes a seventh control unit, which includes a third control module and a fourth control module, wherein the third control module is used to stop the first virtual machine from sending the display interface data when the account is the second account; or the fourth control module is used to control the target vehicle-mounted zero terminal not to decode the display interface data when it is detected that the target vehicle-mounted zero terminal has received the display interface data sent by the first virtual machine when the account is the second account.

7. A vehicle-mounted system, characterized in that: include: A server, wherein a plurality of virtual machines are configured in the server, and the virtual machines are used to send display interface data; At least one vehicle-mounted zero terminal is used to determine the account used for the login operation to determine the bound virtual machine, the bound virtual machine is the virtual machine bound to the account, receives the display interface data sent by the bound virtual machine and processes the display interface data to obtain a target image, when the account is the second account, the vehicle-mounted zero terminal receives the diagnostic data of the target vehicle fed back by the vehicle bus, and sends the diagnostic data to the first virtual machine, the target vehicle is a car equipped with the vehicle-mounted zero terminal, the vehicle-mounted zero terminal stops receiving the display interface data sent by the first virtual machine; or when the vehicle-mounted zero terminal receives the display interface data sent by the first virtual machine, the vehicle-mounted zero terminal does not decode the display interface data, the first account is the account bound to the first virtual machine, the second account is a different account from the first account, and the first virtual machine is the virtual machine corresponding to the vehicle-mounted zero terminal; At least one display is communicatively connected to the corresponding vehicle-mounted zero terminal, and is used to display the target image.

8. The system according to claim 7, characterized in that The vehicle-mounted zero terminal includes: A decoder is used to decode the display interface data to obtain the target image.

9. The system according to claim 7, characterized in that The server also includes: The management unit is used to manage and adjust the corresponding relationship between the password of the account and the virtual machine.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium includes a stored program, wherein the program executes the method of any one of claims 1 to 5.

11. A processor, characterized in that: The processor is used to run a program, wherein the program executes the method according to any one of claims 1 to 5 when running.

Images