DE112020002009T5 - VEHICLE DEVICE AND CONTROL METHOD FOR VEHICLE DEVICE - Google Patents

Abstract

A vehicle device (1) according to an embodiment can provide multiple contents (M1, M2, M3, M4, M5, M6, M7, M8) with a user interface (23) and includes a synchronization unit (21a, 21b, 21c, 21d, 21e, 21f) configured to synchronize multiple surfaces drawn on multiple physical surfaces (30) different from each other. The synchronization unit loads the surface drawn on a different physical surface that differs from the physical surface associated with the synchronization unit and synchronizes the surface drawn by the synchronization unit and the surface drawn on the different physical surface is drawn by processing the loaded surface as the surface drawn by the synchronization unit.

Description

CROSS REFERENCE TO RELATED APPLICATION

This application is based on Japanese patent application no 2019-077775 , filed April 16, 2019, the specification of which is incorporated herein by reference.

TECHNICAL AREA

The present disclosure relates to an in-vehicle device and a control method for an in-vehicle device.

STATE OF THE ART

In recent vehicle devices, multiple content can be provided with a single user interface. At this time, the contents provided may be generated by different application programs, different plural operating systems, or different units as in Patent Document 1, for example.

PRIOR ART LITERATURE

PATENT LITERATURE

Patent Document 1: JP 2016 - 097 928 A

OVERVIEW

In general, displayed content is displayed by drawing surfaces on physical surfaces, such as storage, and compositing the drawn surfaces in hardware. It should be noted that, in short, the surface is the image data that is a source for a content image that is being displayed at a given moment. An object that draws the surfaces is hereinafter referred to as a drawing unit. A physical surface is individually associated with the drawing unit.

However, in the conventional method of combining surfaces drawn on different physical surfaces, there is a possibility of missynchronization of the displayed contents. For example, in a user interface in which a frame image and a menu image are displayed, it is assumed that the surfaces of the frame image and the menu image are drawn by different drawing units. In this case, even if the frame image is moved horizontally, for example, the menu image may be displayed without changing its position or move later than the frame image.

This is because the drawing unit that draws the surface of the frame picture notifies that the surface of the frame picture is to be moved, and the drawing unit that draws the surface of the menu picture draws a new surface according to the notification, but each surface separately is drawn even if the drawing of the surface of the frame image is completed and the display of the frame image is updated, if the drawing of the surface of the menu image is not completed, the display of the menu image is not updated and the original menu image can be displayed as it is is.

An object of the present disclosure is to provide an in-vehicle device and a method for controlling an in-vehicle device that can synchronize surfaces drawn on different physical surfaces.

In order to achieve the above objects, the present disclosure provides an in-vehicle device that can provide multiple contents with a user interface, and includes a synchronization unit that synchronizes surfaces drawn on different physical surfaces. The sync unit loads the surface drawn on a different physical surface that differs from the physical surface associated with the sync unit and synchronizes the surface drawn by the sync unit and the surface drawn on the different physical surface surface is drawn by processing the loaded surface as the surface drawn by the synchronization unit. As a result, the surfaces drawn on the different physical surface can be synchronized.

character list

• 1 ein Diagramm, das ein Konfigurationsbeispiel eines Cockpitsystems in einer ersten Ausführungsform zeigt;
• 2 ein Diagramm, das ein Beispiel einer elektrischen Konfiguration einer Fahrzeugvorrichtung zeigt;
• 3 ein Diagramm, das ein Beispiel einer Softwarekonfiguration der Fahrzeugvorrichtung zeigt;
• 4 ein Diagramm, das ein Beispiel eines Anzeigemodus einer Instrumentenanzeige zeigt;
• 5 ein Diagramm, das ein Beispiel eines Anzeigemodus einer Mittelanzeige zeigt;
• 6 ein Diagramm, das ein Beispiel eines Anzeigemodus einer Blickfeldanzeige zeigt;
• 7 ein Diagramm, das ein Beispiel physischer Oberflächen zeigt, die jeweiligen Anwendungen zugeordnet sind;
• 8 ein Diagramm, das ein Beispiel eines Anzeigemodus durch ein herkömmliches Verfahren als ein Vergleichsbeispiel zeigt;
• 9 ein Diagramm, das einen Ablauf einer Synchronisierungsverarbeitung zeigt;
• 10 ein Diagramm, das ein Beispiel eines Modus eines Ladens einer Oberfläche zeigt;
• 11 ein Diagramm, das einen Anzeigemodus der Fahrzeugvorrichtung zeigt;
• 12 ein Diagramm, das ein Konfigurationsbeispiel einer Fahrzeugvorrichtung gemäß einer zweiten Ausführungsform zeigt;
• 13 ein Diagramm, das ein anderes Konfigurationsbeispiel einer Fahrzeugvorrichtung zeigt;
• 14 ein erstes Diagramm, das ein Beispiel zeigt, wie Oberflächen in einer dritten Ausführungsform zu laden sind; und
• 15 ein zweites Diagramm, das ein Beispiel zeigt, wie Oberflächen zu laden sind.

The above and other objects, features, and advantages of the present disclosure will become more apparent from the following detailed description when read in conjunction with the drawings. Show it:

• 1 12 is a diagram showing a configuration example of a cockpit system in a first embodiment;
• 2 12 is a diagram showing an example of an electrical configuration of an in-vehicle device;
• 3 12 is a diagram showing an example of a software configuration of the in-vehicle device;
• 4 Fig. 14 is a diagram showing an example of a display mode of an instrument panel;
• 5 12 is a diagram showing an example of a display mode of a center display;
• 6 Fig. 14 is a diagram showing an example of a display mode of a head-up display;
• 7 a diagram showing an example of physical surfaces associated with respective applications;
• 8th a diagram showing an example of a display mode by a conventional method as a comparative example;
• 9 a diagram showing a flow of synchronization processing;
• 10 Fig. 14 is a diagram showing an example of a surface loading mode;
• 11 a diagram showing a display mode of the vehicle device;
• 12 12 is a diagram showing a configuration example of an in-vehicle device according to a second embodiment;
• 13 12 is a diagram showing another configuration example of an in-vehicle device;
• 14 Fig. 14 is a first diagram showing an example of how to load surfaces in a third embodiment; and
• 15 a second diagram showing an example of how to load surfaces.

DESCRIPTION OF EMBODIMENTS

Several exemplary embodiments according to the drawings are described below. Furthermore, the configurations that are substantially the same in each embodiment will be described with the same reference numerals.

(First embodiment)

A first embodiment will be described below. As in 1 is shown, a vehicle device 1 forms a cockpit system 5 with three displays such as an instrument display 2, a center display 3 and a head-up display 4.

The meter display 2 includes, for example, a liquid crystal display or an OLED display, and is assumed to be installed on a portion of an instrument panel near a driver's front side. The center display 3 is, for example, a liquid crystal display or an OLED display, and is assumed to be provided in the vicinity of a center console.

The head-up display 4 is, for example, a liquid crystal display, an OLED display, or a projector that projects an image onto a windshield, and is assumed to be provided near the front of the driver on the dashboard. However, the number, arrangement, or configuration of the display devices are just an example, and the present disclosure is not limited to these examples.

Even though 1 Fig. 1 shows an example of the in-vehicle device 1 connected to multiple displays, as will be described below, the in-vehicle device 1 of the present embodiment is intended to synchronize surfaces in a user interface. Accordingly, only one or more displays need to be connected to the vehicle device 1 .

The vehicle device 1 is communicably connected to a plurality of electronic control units 6 (hereinafter referred to as ECUs 6) installed in a vehicle. Although the vehicle device 1 can be regarded as one of the ECUs 6, for easier understanding, the vehicle device 1 and the ECUs 6 are separated in the present disclosure.

As in 2 As shown, the vehicle device 1 includes a CPU 10, a bus master 11, a main memory 12, a graphic processing unit 13 (hereinafter referred to as a GPU 13), an image processing unit 14 (hereinafter referred to as an IPU 14), a communication unit 15, and the like.

The GPU 13 is a functional unit that actually draws a surface instructed by an application program, as described below. It should be noted that, in short, the surface is image data that is a source for a content image displayed at a particular moment. The IPU 14 is a functional unit that outputs the drawn surface as a video signal to each display.

The CPU 10 includes several, for example eight, cores 10a. These eight cores 10a are grouped into four cores each and are assigned to two CPU modules 16A and 16B. In other words, a plurality of CPU modules 16 that can operate functionally independently are provided in the vehicle device 1 .

CPU module 16A is associated with an application set 22A that requires relative real-time capability, and CPU module 16B is associated with an application set 22B that does not require relative real-time capability. Hereinafter, when explanations are given that are common to CPU modules 16, they are simply referred to as the CPU modules 16 without adding A or B.

Each of the CPU modules 16 and the GPU 13 has a dedicated cache memory 17. Hereinafter, the cache memory dedicated to the CPU module 16A will be referred to as a cache 17A for convenience, the cache memory dedicated to the CPU module 16B provided is referred to as a cache 17B for convenience, and the cache memory provided for the GPU 13 is referred to as a cache 17G for convenience. Each of the cache memories 17 is connected to the main memory 12 and the IPU 14 via a bus 11a and the bus master 11, and is configured to be able to transmit and receive data mutually.

The communication unit 15 performs communication with other ECUs 6 . The communication unit 15 contains, for example, a controller area network interface. Depending on the type of the ECUs 6, a radio communication method such as WiFi or a wired communication method such as USB can be used.

As in 3 1, in the in-vehicle device 1, an operating system 20 (hereinafter referred to as “OS 20”) is executed on the CPU 10, and a plurality of application programs 21 (hereinafter referred to as “applications 21”) are executed on the OS 20. The applications 21 running on the OS 20 include an instrument application 21a, a navigation application 21b, a security application 21c, a video application 21d, and a HUD application 21e. HUD is an abbreviation for head-up display. Each application 21 is an example, and the applications 21 running on the OS 20 are not limited to these examples.

The instrument application 21a informs the user of, for example, a vehicle's speed, revolutions per minute, or warnings, and also draws surfaces mainly displayed on the instrument display 2 . For example, the instrument application 21a draws a surface for displaying content such as a speedometer M1, a tachometer M2, or a warning light M3, as in a 4 shown user interface 23 as a normal display mode.

However, the surfaces drawn by the instrument application 21a can be displayed on the center display 3 or the head-up display 4 as well. The surface drawn by the instrument application 21a shall have relative real-time characteristics compared to the surface drawn by the other exemplary applications 21a. Although the instrument application 21a instructs the GPU 13 to draw the surface in practice, here it is expressed for the sake of simplicity that the instrument application 21 should draw the surface. Here, a similar explanation can be applied to the other applications 21 .

The navigation application 21b implements a navigation function and draws surfaces displayed on the center display 3 mainly. For example, as in 5 As shown, the navigation application 21b draws an interface for displaying a content such as a navigation screen M4 including a map, a current position of the vehicle, and the like. However, the surface drawn by the navigation application 21b, for example, on the instrument panel 2 as a navigation display mode described in 4 shown can be displayed and may be displayed on the head-up display 4 as well.

The security application 21c implements various functions for displaying a menu and driving assistance, and draws surfaces that are displayed on the center display 3 mainly. For example, as in 5 As shown, the security application 21c draws an interface for displaying content such as multiple items or icons M5 for selecting a target function or content. However, the surfaces drawn by the security application 21c, for example, on the instrument display 2 as a menu display mode described in 4 as shown are displayed and may be displayed on the head-up display 4 as well.

The HUD application 21e notifies the user of, for example, a speed, a future course, and the like, and draws surfaces that are displayed on the head-up display 4 mainly. For example, as in 6 As shown, the HUD application 21e draws a surface for displaying current speed information M6, time information M7, or course information M8 indicating a distance to a corner, a turning direction, and the like. However, the surfaces drawn by the HUD application 21e net can also be displayed on the instrument display 2 or the center display 3.

As in 7 As shown, a physical surface 30 is individually associated with each of the applications 21 for drawing the surface. That is, each of the applications 21 functions as a drawing unit that draws a surface that is a content holding unit on the physical surface 30 associated with each of the applications 21 . Although details will be described later, each of the applications 21 corresponds to a synchronization unit that loads a surface that is a content holding unit into the physical surface 30 associated with each of the applications 21 and that synchronizes the surface.

The physical surfaces 30 are secured in such a size that required surfaces can be drawn, that is, provided on the cache memory 17 or the main memory 12. A size of the physical surface 30 need not equal the number of pixels of the display device. This is because a required surface is selected from surfaces drawn on the physical surface 30 and displayed on the display device.

In the present embodiment, physical surface 30A is associated with instrument application 21a, physical surface 30B is associated with navigation application 21b, physical surface 30C is associated with security application 21C, physical surface 30D is associated with video application 21d, and physical surface 30E is the Associated with HUD application 21e. Then one or more surfaces on each of the physical surfaces 30 are drawn by each of the applications 21 .

For example, surfaces SA1 through SA3 on physical surface 30A are drawn by instrument application 21a. Similarly, a surface SB1 is drawn on physical surface 30B by navigation application 21b. Surfaces SC1 and SC2 are drawn on physical surface 30C by security application 21c. In 7 For convenience of description, a plurality of surfaces drawn by the security application 21c are collectively referred to as the surface SC1. A surface SD1 is drawn by the video application 21 on the physical surface 30D. Surfaces SE1 through SE3 are drawn on physical surface 30E by HUD application 21e. The above surfaces are examples.

At least one of the contents displayed on the display devices undergoes an animation operation. Here, the animation operation is a display mode in which a position and a size of an image indicating the content change gradually, the image rotates, the user interface 23 moves along a wiping operation as a whole, the image fades in or out gradually, itself the color of the image changes and the like.

For example, as in 4 As shown, the speedometer M1, the tachometer M2, a map, a menu, or the like are content whose size and position change depending on a display mode or the display device at a display target. However, the animation operation is not limited to this, and any animation operation in which the display mode changes continuously or intermittently from a certain point in time is included.

Next, the effects of the configuration described above will be explained.
As described above, the physical surfaces 30 are individually assigned to the applications 21, and the applications 21 individually draw a surface on the physical surfaces 30. At this time, when display is performed by a prior art method in which the IPU 14 combines the surfaces drawn on the physical surfaces 30, there may be some out-of-sync of the displayed content.

This is because a point in time when drawing of the surface is completed may be different for each of the applications 21 . Here, using a method of the prior art in a comparative example given in 8th is shown, in the navigation display mode of a screen transition, assuming that the animation operation for displaying the speedometer M1 and the tachometer M2 in an enlarged manner is performed. In 8th the reference numbers of the contents are omitted.

In this case, since it is necessary to zoom out the map relatively, calculated in the in 8th 1, as shown in the sequence, the instrument application 21a first determines the size and position of the surface to be updated, notifies the navigation application 21b of a calculation result, and draws the surface according to the size and position after the update. On the other hand, when the navigation application 21b receives a notification from the instrument application 21a, the navigation application 21b specifies the size and the position of the surface after the update based on the notification and draws the new surface, that is, performs the update such that the new surface has the specified size and position.

At that time, when the drawing of the surface has been completed first by the instrument application 21a, the IPU 14 combines and displays the surface at that time. However, since drawing of the surface by the navigation application 21b is not completed, an original surface is displayed as it is. Accordingly, as an out-of-sync condition occurring in 8th As shown, the speedometer M1 and the tachometer M2 overlap the navigation screen M4.

Thereafter, when the drawing of the surface is completed in the navigation application 21b, each surface is displayed in an intended state as a synchronous state shown in 8th is shown. The synchronization deviation that 8th Fig. 1 is an example and, for example, when a menu is displayed in a frame, a synchronization deviation in which the menu does not move even if the frame is moved may occur.

As described above, when the prior art method is used, surfaces drawn on different physical surfaces 30 cannot be synchronized and, for example, display deviation occurs. Since the synchronization deviates at the time of displaying on the display device, the user can visually recognize the synchronization deviation and may have a sense of error.

Thus, in the in-vehicle device 1, the surfaces drawn on the different physical surfaces 30 are synchronized in the following manner. Although the following processing can be executed by any application 21, here is a case where the surface of the speedometer M1 or the like drawn by the instrument application 21a and the surface of the navigation screen M4 drawn by the navigation application 21b be synchronized, as an example, in comparison with the example of FIG 8th described.

The instrument application 21a executes the synchronization processing specified in 9 is shown and draws the surfaces SA1 to SA3 on the physical surface 30A associated with the instrument application 21a at step S1 as in FIG 7 is shown. For example, the instrument application 21a draws the surface SA1 for displaying the speedometer M1, the surface SA2 for displaying the tachometer M2, and the surface SA3 for displaying the warning light M3.

Then, at step S2 in the synchronization processing, the instrument application 21a loads the surface drawn on the different physical surface 30 . In this case, as in 10 As shown, instrument application 21a loads surface SB1 drawn on different physical surface 30B by navigation application 21b into physical surface 30A on which surfaces SA1 through SA3 are drawn. At the time of loading, the surface SB1 has a size and a shape when drawn by the navigation application 21b.

Subsequently, at step S3 in the synchronization processing, the tool application 21a calculates a position, a size, a deformation amount, or the like of the surfaces including the surfaces SA1 to SA3 drawn by the tool application 21a and the loaded surface SB1. That is, the tool application 21a treats the loaded surface SB1 as a texture, and calculates the position, the size, or the deformation amount of the texture, pseudo-processing the surface SB1 as a surface drawn by the tool application 21a.

When the calculation is completed, the instrument application 21a draws each surface on the physical surface 30A of the instrument application 21a according to a calculation result at step S4 in the synchronization processing. Consequently, as in 10 As shown, the surfaces SA1 to SA3 drawn by the instrument application 21a and the surface SB1 drawn by the navigation application 21b are drawn on the physical surface 30A according to the calculated size and position. That is, each surface is redrawn or rearranged according to the calculation result.

At this time, the surface SB1 on the different physical surface 30B is separated from the physical surface 30B at a time when the surface SB1 is loaded into the physical surface 30A. Therefore, regardless of the drawing operation of the navigation application 21b, the surface SB1 can be displayed on the instrument application 21a with an appropriate size, position, or amount of deformation.

Thus, at step S5 in the synchronization processing, the instrument application 21a can display each surface in an appropriate state by instructing display of each surface for which repainting or rearranging has been completed. This means that when an animation operation is performed, the navigation screen M4 is reduced when the speedometer M1 and tachometer M2 are enlarged, and a display can be changed seamlessly without overlapping the speedometer M1, tachometer M2 and navigation screen M4 .

Specifically, in the vehicle device 1, as a sequence according to the embodiment shown in FIG 11 shown, each application 21 is a surface. Then the application 21 that requires the surface drawn on the different physical surface 30, here the instrument application 21a, loads the surface drawn by navigation application 21b into the physical surface 30 of the instrument application 21a, calculates the position, size and the like of the loaded surface and redraws the surface.

Accordingly, for example, when the instrument application 21a performs an animation operation in which the speedometer M1 or the tachometer M2 is displayed in an enlarged manner, the instrument application 21a can control the size, position, and the like of the surface displayed on the different physical Surface 30 is drawn to correspond to the animation operation. Accordingly, as shown in the embodiment, the speedometer M1 and the tachometer M2 are prevented from overlapping the navigation screen M4 in the screen transition. That is, it is possible to synchronize the surfaces drawn on the different physical surfaces 30. In 11 the reference numbers of the contents are omitted.

According to the embodiment described above, the following effects can be obtained. The vehicle device 1 can provide multiple contents through a user interface 23 and includes a synchronization unit that synchronizes the surfaces that are content holding units. Then, the synchronization unit loads a surface drawn on a different physical surface 30 that differs from the physical surface 30 associated with the synchronization unit and treats the loaded surface as the surface drawn by the synchronization unit , wherein the surface drawn by the synchronization unit is synchronized with the surface drawn on the different physical surface 30 .

Accordingly, even if the surface is drawn on the different physical surface 30 when the surface is displayed on the user interface 23, the synchronization unit can control the timing at which the display is updated. That is, it is possible to share the surface drawn on the different physical surface 30 . As a result, the surfaces drawn on the different physical surfaces 30 can be synchronized. Specifically, the surface drawn by the synchronizing unit and the surface drawn on the different physical surface 30 can be synchronized and a state where the user can visually recognize an error, the display deviation or the like is can be avoided.

The control method of the in-vehicle device 1 includes, when a plurality of contents are provided through a user interface 23, a step of drawing the surface that is the content holding unit on the physical surface 30 associated with a synchronization unit, a step of loading a surface that is on of the different physical surface 30 that is different from the physical surface 30 associated with the synchronizing entity, and a step of synchronizing the surface that is drawn by the synchronizing entity with the surface that is on the different or different physical surface 30 another physical surface 30, by processing the loaded surface, than the surface drawn by the synchronization unit.

Also, according to such a control method of the vehicle device 1, the surfaces drawn on the different surfaces 30 can be synchronized with each other, and the surface drawn by the synchronizing unit and the surface drawn on the different physical Surface 30 is drawn can be synchronized with each other.

In the in-vehicle device 1, at least one of the contents is subjected to the animation operation. In a case where the animation operation for the content is performed when the original surfaces are not synchronized with each other, the display of the content may deviate, overlap, or the like, causing an error chen, which the user can recognize visually. Therefore, by synchronizing the original surfaces even if the position and size of the content are changed, the above error can be prevented from occurring.

Multiple applications 21 are executed in the vehicle device 1 and the synchronizing unit is implemented as the application 21 and synchronizes a surface drawn by the synchronizing unit with a surface drawn on the different physical surface 30 by the other application 21 will. Accordingly, it is possible to prevent an excessive load from being applied to each of the applications 21 .

Thus, as in the instrument application 21a according to the embodiment, the application 21 that draws a surface that requires the relative real-time property compared to the surface that is drawn on the different physical surface 30, the surface that relatively requires the real-time property, synchronize with the surface drawn on the different physical surface 30 without delaying the display of the speedometer M1, tachometer M2, or hazard light M3 that is required.

The vehicle device 1 includes multiple CPU modules 16 , and the synchronizing unit synchronizes a surface drawn by the synchronizing unit with a surface drawn on the different physical surface 30 provided for another CPU module 16 . In this case, since the physical surface 30 is managed for each CPU module 16, the physical surface 30A on which the instrument application 21a draws the surface and the physical surface 30B on which the navigation application 21b draws the surface over which CPU modules 16 shared across. With such a configuration, by employing the control method described above, the surfaces drawn on the different physical surface 30 can be synchronized.

(Second embodiment)

Next, a second embodiment will be described. In the second embodiment, a configuration example of an in-vehicle device 1 different from that according to the first embodiment will be described. In order to simplify the description, the in-vehicle device 1, an OS 20, or an application 21 are described with common reference numerals. A method of synchronization control and the like are common to those according to the first embodiment.

<First configuration example>

In a first configuration example, as in 12 1, in the in-vehicle device 1, a hypervisor 40 is executed on the CPU 10, and a plurality of, for example, two operating systems (OS) 20A and 20B are executed on the hypervisor 40. FIG. At this time, an OS 20A is assigned to the CPU module 16A and an OS 20B is assigned to the CPU module 16B. In the present embodiment, it is assumed that the OS 20A is in charge of relatively high real-time property processing and the OS 20B is in charge of relatively low real-time property processing.

Thus, in the OS 20A, for example, an instrument application 21a that requires real-time property is executed, and in the OS 20B, a navigation application 21b, a security application 21c, a HUD application 21e, a video application 21, and the like that do not require real-time property so much as that OS 20A running. The type of the OS 20 and the arrangement of the applications 21 are only examples, and the present disclosure is not limited to these examples.

In this case, since each physical surface 30 is managed for each OS 20, a physical surface 30A on which the instrument application 21a draws a surface and a physical surface 30B on which the navigation application 21b draws a surface reside via CPU module 16 and the OS 20 across. In other words, a synchronization unit must share the surfaces across the CPU modules 16 and the OS 20. Even in such a case, by employing the control method described in the first embodiment, the surfaces drawn on the different physical surfaces 30, here the physical surfaces 30 of the different OS 20 of the different CPU modules 16 , shared and synchronized.

Although in the first embodiment the configuration in which each surface is used as the synchronizing unit by the application 21 that draws the surface by the synchronizing unit, that is, the application 21 has been exemplified, a configuration in which a synchronization application 21f dedicated to synchronization is implemented and the drawing of the surface and the sharing of the surface are processed separately. In other words, a synchronizing entity that draws the surface that is a content holding entity on the physical surface 30 associated with the synchronizing entity, and a synchronizing application 21f that serves as a synchronizing entity that is drawn in the physical surface 30 that is associated with the application 21f, loads a surface drawn on a different physical surface 30, and calculates a position, a size, or a deformation amount of the loaded surface. Even with such a configuration, the surfaces drawn on the different physical surfaces 30 can be synchronized by loading the surfaces drawn by the synchronization unit by the synchronization unit. The synchronization application 21f can be applied to all the display devices and can be provided individually in each of the display devices.

Hypervisor 40 may be configured to run as a function of OS 20A. That is, OS 20A may execute on CPU 10, hypervisor 40 may operate as a function of OS 20, and OS 20B may execute on hypervisor 40.

<Second configuration example>

In a second configuration example, as in 13 As shown, the in-vehicle device 1 includes a plurality of CPUs 10 and each of the OS 20A and the OS 20B is executed on a respective one of the CPUs 10 . In this case, since the physical surface 30 is managed for each CPU 10, the physical surface 30A on which the instrument application 21a draws the surface and the physical surface 30B on which the navigation application 21b draws the surface reside above the CPU -modules 10 across.

In other words, the synchronization unit must share the surface across the CPU 10. Even in such a case, by employing the control method described in the first embodiment, the surfaces drawn on the different physical surfaces 30, here the physical surfaces 30 on the different CPU modules 16 side, can be shared and synchronized will.

(Third embodiment)

Next, a third embodiment will be described. In the third embodiment, an example in which surfaces are synchronized between an in-vehicle device 1 and an ECU 6 will be described. In order to simplify the description, the in-vehicle device 1, an OS 20, or an application 21 are described with common reference numerals. The configuration of the in-vehicle device 1 is similar to the configuration of the in-vehicle device 1 according to the first embodiment or the second embodiment, and a synchronization control method similar to the synchronization control method according to the first embodiment can be employed.

In the third embodiment, as in 14 As shown, the in-vehicle device 1 is communicably connected to another ECU 6 and, using a control method similar to the control method according to the first embodiment, synchronizes a surface drawn on the physical surface 30 by the synchronizing unit of the in-vehicle device 1 and the surface drawn on a different physical surface 30 of the ECU 6 .

Specifically, in the case of the instrument application 21a, for example, the in-vehicle device 1 loads the surface drawn on the physical surface 30F into the physical surface 30A of the in-vehicle device 1, calculates a position, a size, or a deformation amount, draws each surface based on a calculation result and then displays the surface, thereby synchronizing the surface drawn on the physical surface 30A by the vehicle device 1 with the surface drawn on the different physical surface 30F.

At this time, the in-vehicle device 1 can individually attach a connection to load the surface drawn on the physical surface 30F of the ECU 6 . Accordingly, the required surfaces can be loaded individually and the surfaces drawn on different physical surfaces 30 can be synchronized.

Alternatively, as in 15 For example, as shown in FIG the loaded surface group SG to the physical ober distributed over area 30A associated with instrument application 21a.

Accordingly, the surfaces drawn on the different physical surfaces 30 can be synchronized while simplifying processing for loading the surface and reducing a communication amount between the in-vehicle device 1 and the ECU 6 . The distribution unit 21g can be implemented by hardware.

Although the present disclosure has been described according to the examples, it should be understood that the present disclosure is not limited to the examples or structures. The present disclosure also includes various modifications and modifications within an equivalent range. Furthermore, different combinations and configurations, as well as other combinations and configurations, including only one element or more or less than those elements, also fall within the spirit and scope of the present disclosure.

The controller and method described in the present disclosure may be implemented by a dedicated computer configured with a memory and a processor programmed to perform one or more specific functions embodied in computer programs of the memory are. Alternatively, the controller and method according to the present disclosure may be achieved by a dedicated computer configured with a processor having one or more dedicated hardware logic circuits. Alternatively, the controller and method according to the present disclosure may be implemented using one or more dedicated computers configured by a combination of a processor and memory programmed to perform one or more functions and a processor having one or more hardware logic circuits be reached. Further, the computer program may store a computer-readable non-transitory tangible recording medium as an instruction to be executed by the computer.

QUOTES INCLUDED IN DESCRIPTION

This list of documents cited by the applicant was generated automatically and is included solely for the better information of the reader. The list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions.

Patent Literature Cited

• JP 2019077775 [0001]
• JP 2016097928 A [0004]

Claims (10)

Vehicle device (1) that can provide multiple content (M1, M2, M3, M4, M5, M6, M7, M8) with a user interface, comprising: a synchronization unit (21a, 21b, 21c, 21d, 21e, 21f) configured to synchronize multiple surfaces drawn on multiple physical surfaces different from each other, wherein the synchronization unit is configured to load one of the plurality of surfaces drawn on a different physical surface that is one of the plurality of physical surfaces and different from one of the plurality of physical surfaces associated with the synchronization unit and the surface that is drawn by the synchronizing unit and to synchronize the surface drawn on the different physical surface by processing the loaded surface as the surface drawn by the synchronizing unit. Vehicle device according to claim 1 wherein a plurality of application programs (21a, 21b, 21c, 21d, 21e) for drawing the plurality of surfaces are executed in the vehicle device, and the synchronizing unit is implemented as one of the plurality of application programs and the surface drawn by the synchronizing unit is associated with the surface synchronized drawn on the different physical surface by a different one of the multiple application programs. Vehicle device according to claim 1 or 2 , wherein at least one of the plurality of contents is subjected to an animation operation. Vehicle device according to one of Claims 1 until 3 wherein multiple operating systems (30) are executed in the vehicle device, and the synchronizing unit is configured to synchronize the surface drawn by the synchronizing unit and the surface drawn on the different physical surface for a different one of the multiple operating systems intended to be synchronized. Vehicle device according to one of Claims 1 until 4 , further comprising a plurality of CPU (central processing unit) modules (16), wherein the synchronization unit is configured to synchronize the surface drawn by the synchronization unit and the surface drawn on the different physical surface used for a different one of the multiple CPU modules is provided to synchronize. Vehicle device according to one of Claims 1 until 5 , wherein the vehicle device is communicably connected to an external device, and the synchronization unit is configured to display the surface drawn by the synchronization unit and the surface drawn on the different physical surface provided for the external device, to sync. Vehicle device according to one of Claims 1 until 6 , wherein the synchronization unit is configured to draw the surface requiring relatively real-time properties compared to the surface drawn on the different physical surface. Vehicle device according to one of Claims 1 until 7 , wherein the synchronization unit is configured to load the multiple surfaces drawn on the different physical surface. Vehicle device according to one of Claims 1 until 7 , further comprising a distribution unit (21f) configured to collectively load the multiple surfaces drawn on the different physical surface as a surface group (SG) and the multiple surfaces included in the surface group individually distribute surfaces. A control method for an in-vehicle device (1) for providing a plurality of contents (M1, M2, M3, M4, M5, M6, M7, M8) through a user interface, comprising: loading a surface drawn on a different physical surface than a physical surface associated with the synchronization entity; and synchronizing a surface drawn by the synchronization unit and the surface drawn on the different physical surface by processing the loaded surface as the surface drawn by the synchronization unit.

Images