Program, on-vehicle apparatus, and system

Abstract

A vehicle system (1) comprises a communication device (10) and an on-vehicle apparatus (20). An application program (100) is installed in the communication device (10). The application program (100) causes the communication device (10) to execute an operation for: receiving an input for configuring a layout of function buttons of the on-vehicle apparatus; and transmitting layout configuration information based on the input to the on-vehicle apparatus (20). When the on-vehicle apparatus (20) acquires, from the communication device (10) or another external device, generated in the communication device (10), the on-vehicle apparatus (20) arranges, on the basis of the layout configuration information, each of the function buttons in a first display region in which the plurality of function buttons are displayed.

Description

Programs, on-board devices, and systems

[0001] The present invention relates to a program, an in-vehicle device, and a system.

[0002] 2. Description of the Related Art Electronic devices that provide audio or video information for various purposes such as navigation and entertainment are used in vehicles.

[0003] For example, Patent Document 1 below discloses a technology for linking an information processing device used in a vehicle with a mobile terminal device carried by a person riding in the vehicle. In the technology described in Patent Document 1, when linking the information processing device with the mobile terminal device, the mobile terminal device generates display specifications including icons and their shapes to be displayed on a display unit of the information processing device in accordance with a change in operation mode, and transmits the display specifications to the information processing device. The information processing device displays the icons on the display unit based on the display specifications.

[0004] International Publication No. 2018 / 117085

[0005] The usability of electronic devices used in vehicles is an important factor for users of the electronic devices, and therefore, a technique for improving the usability of electronic devices used in vehicles is desired.

[0006] One example of a problem to be solved by the invention according to the present disclosure is to provide a technology for improving the usability of electronic devices used in vehicles.

[0007] A first invention in the present disclosure is a program that, when executed by a computer, causes the computer to perform operations including accepting input for setting the layout of function buttons of an in-vehicle device, and transmitting layout setting information based on the input to the in-vehicle device.

[0008] A second invention in the present disclosure is an in-vehicle device comprising: a layout setting information acquisition means for acquiring layout setting information for setting the layout of function buttons from an external computer; and a display control means for arranging each function button in a first display area in which a plurality of function buttons are displayed based on the layout setting information.

[0009] A third invention in the present disclosure is a system including: the above-described program; and the above-described vehicle-mounted device.

[0010] 1 is a block diagram illustrating an overview of a vehicle system according to the present disclosure. FIG. 2 is a block diagram illustrating a first example of the functional configuration of an application program according to the present disclosure. FIG. 3 is a diagram illustrating an example of the hardware configuration of a computer (communication device) on which an application program is installed. FIG. 4 is a flowchart illustrating an example of a layout setting operation performed by a communication device executing an application program. FIG. 5 is a diagram illustrating an example of a screen displayed on a display of a communication device by a communication device executing an application program. FIG. 6 is a diagram illustrating an example of a flow of an operation of adding a function button performed on an application program installed in a communication device. FIG. 7 is a diagram illustrating an example of an operation of deleting a function button performed on an application program installed in a communication device. FIG. 8 is a block diagram illustrating a second example of the functional configuration of an application program according to the present disclosure. FIG. 9 is a block diagram illustrating a first example of the functional configuration of an in-vehicle device according to the present disclosure. FIG. 10 is a diagram illustrating an example of the hardware configuration of a computer that realizes an in-vehicle device according to the present disclosure. FIG. 11 is a flowchart illustrating a first example of an operation performed by an in-vehicle device according to the present disclosure. FIG. 12 is a diagram illustrating an example of information displayed on a display of an in-vehicle device by a display control unit according to the present disclosure. FIG. 13 is a diagram illustrating another example of information displayed on a display of an in-vehicle device by a display control unit according to the present disclosure. FIG. 14 is a block diagram illustrating a third example of the functional configuration of an application program according to the present disclosure. 1 is a flowchart illustrating a control operation performed by a communication device executing an application program in the present disclosure; FIG. 2 is a block diagram illustrating a second example of a functional configuration of an in-vehicle device in the present disclosure; FIG. 3 is a flowchart illustrating a second example of an operation performed by an in-vehicle device in the present disclosure; FIG. 4 is a flowchart illustrating a deactivation control operation of a function button performed by a communication device executing an application program in the present disclosure; and FIG. 5 is a flowchart illustrating a deactivation control operation of a function button performed by an in-vehicle device in the present disclosure.

[0011] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. In all drawings, similar components are denoted by similar reference numerals, and descriptions thereof will be omitted as appropriate. In the following disclosure, the drawings relate to one or more embodiments.

[0012] In the following description, each component of each device represents a functional block rather than a hardware configuration. Each component of each device is realized by any combination of hardware and software, centered around the CPU of any computer, memory, a program loaded into the memory, a storage medium such as a hard disk that stores the program, and a network connection interface. There are many variations in the realization method and device.

[0013] Furthermore, when elements such as blocks in a diagram are linked by arrows, the direction of the arrows is merely to make the flow of information easier to understand. In this case, the direction of the arrows does not limit the direction of communication (one-way communication / two-way communication) unless otherwise specified.

[0014] 1 is a block diagram illustrating an example of an outline of a vehicle system according to the present disclosure. The vehicle system 1 illustrated in the drawing includes a communication device 10 and an in-vehicle device 20.

[0015] The communication device 10 is any device carried by a user who is in the vehicle V. For example, the communication device 10 is a portable device such as a smartphone or a tablet terminal. The in-vehicle device 20 is any electronic device used in the vehicle V to provide various information to the user. Note that the "in-vehicle device" in this disclosure is not limited to a so-called built-in type device. The "in-vehicle device" in this disclosure may also be a so-called on-dash type device.

[0016] A predetermined application program 100 for linking with the in-vehicle device 20 is installed in the communication device 10. After installing the application program 100 in the communication device 10, the user of the communication device 10 performs a predetermined initial connection procedure for linking the communication device 10 with the in-vehicle device 20. After the initial connection is completed, linking between the communication device 10 and the in-vehicle device 20 becomes possible. For example, when a user gets into a vehicle V while carrying the communication device 10, linking between the communication device 10 and the in-vehicle device 20 starts automatically or in response to a connection request operation by the user. The communication device 10 and the in-vehicle device 20 can link with each other by using any wireless communication standard (e.g., Bluetooth (registered trademark) or Wi-Fi (Wireless-Fidelity)) or by establishing a wired connection.

[0017] While the communication device 10 and the in-vehicle device 20 are linked, the user can control the communication device 10 by performing an operation on the in-vehicle device 20. As an example, the user can launch another application program installed in the communication device 10 separately from the application program 100 by performing an operation on the in-vehicle device 20. Furthermore, while the communication device 10 and the in-vehicle device 20 are linked, the user can control the in-vehicle device 20 by performing an operation on the communication device 10. As an example, the user can cause the in-vehicle device 20 to execute a function provided by the in-vehicle device 20 by performing an operation on the communication device 10. As another example, the user can set and edit the layout of multiple function buttons used on the in-vehicle device 20 by performing an operation on the communication device 10.

[0018] Here, the term "function button" in this disclosure refers to a button that serves as a so-called shortcut key for calling up a corresponding function of the in-vehicle device 20. Also, the term "function button" in this disclosure refers to a virtual button (so-called soft key) displayed on a display. By selecting a "function button," the function (process) corresponding to the button is executed. Although not particularly limited, the multiple function buttons used in the in-vehicle device 20 include buttons such as those exemplified in (1) to (4) below. (1) Buttons for performing audio operations on the in-vehicle device 20 (switching sources, setting the volume, play / stop, selecting songs, skipping songs, muting / unmuting, etc.) (2) Buttons for performing sound quality operations on the in-vehicle device 20 (switching equalization settings, turning the subwoofer on / off, turning the rear speakers on / off, etc.) (3) Buttons for controlling devices mounted on the vehicle V (for example, the cabin air conditioner, a camera that captures images around the vehicle, etc.) (4) Buttons for launching other applications installed in the communication device 10 (an external computer) that cooperates with the in-vehicle device 20

[0019] The function buttons exemplified in (1) to (3) above may include a button that transitions to one of multiple screens used in the in-vehicle device 20 in response to a selection operation. For example, a function button for switching the audio source to radio may be included in the multiple function buttons. In this case, a screen for selecting a radio station, tuning, etc., is displayed on the display of the in-vehicle device 20 in response to a selection operation of the button. On the other hand, the multiple function buttons used in the in-vehicle device 20 may also include buttons that do not result in a screen transition. For example, a function button for switching an equalizing setting or a function button for setting or canceling mute may not result in a screen transition. As a specific example, assume that a function button for switching an equalizing setting is selected. In this case, no screen transition occurs on the display of the in-vehicle device 20, and information related to the equalizing setting associated with the function button and stored in the in-vehicle device 20 is read and applied. In this case, a dialog box may be displayed to notify the user of changes to the equalizing setting, mute setting, etc.

[0020] A detailed example of a vehicle system according to the present disclosure will be described below.

[0021] First Embodiment <Example of Functional Configuration of Application Program> Fig. 2 is a block diagram showing a first example of the functional configuration of an application program according to the present disclosure. The application program 100 shown in the figure includes at least a layout setting input receiving module 110 and a layout setting information transmitting module 120.

[0022] The layout setting input receiving module 110 provides, on the communication device 10, a function for receiving input for setting the layout of function buttons that can be set on the in-vehicle device 20. The layout setting information transmission module 120 provides a function for transmitting, to the in-vehicle device 20, information indicating a layout setting (hereinafter also referred to as "layout setting information") generated based on the input received by the layout setting input receiving module 110. When the communication device 10 executes the application program 100, operations based on the functions provided by the layout setting input receiving module 110 and the layout setting information transmission module 120 are executed.

[0023] <Example of Hardware Configuration of Communication Device> FIG. 3 is a diagram illustrating an example of the hardware configuration of a computer (communication device) on which an application program is installed.

[0024] The computer 1000 includes a bus 1010 , a processor 1020 , a memory 1030 , a storage device 1040 , an input / output interface 1050 , and a network interface 1060 .

[0025] The bus 1010 is a data transmission path for transmitting and receiving data among the processor 1020, memory 1030, storage device 1040, input / output interface 1050, and network interface 1060. However, the method of connecting the processor 1020 and the like to each other is not limited to bus connection.

[0026] The processor 1020 is implemented as a central processing unit (CPU) or a graphics processing unit (GPU).

[0027] The memory 1030 is a main storage device realized by a random access memory (RAM) or the like.

[0028] The storage device 1040 is an auxiliary storage device realized by removable media such as a hard disk drive (HDD), a solid state drive (SSD), a memory card, or a read only memory (ROM), etc. The storage device 1040 stores at least program modules (the layout setting input receiving module 110 and the layout setting information transmitting module 120) that realize the functions of the application program 100 described above.

[0029] The processor 1020 loads a program module read from the storage device 1040 onto the memory 1030 and executes the program module, thereby realizing the function corresponding to the program module. For example, the processor 1020 reads the layout setting input receiving module 110 onto the memory 1030 and executes the module, thereby realizing the function of the layout setting input receiving module 110 described in the present disclosure. Similarly, the processor 1020 reads the layout setting information transmitting module 120 onto the memory 1030 and executes the module, thereby realizing the function of the layout setting information transmitting module 120 described in the present disclosure. The operation of the processor 1020 is common to each embodiment included in the present disclosure.

[0030] The above-described program modules may be recorded on a recording medium other than the storage device 1040. The recording medium on which the program modules are recorded may include any non-transitory, tangible medium usable by the computer 1000. The recording medium on which the program modules are recorded may have embedded therein program code that is readable by the computer 1000 (processor 1020).

[0031] The input / output interface 1050 is an interface for connecting the computer 1000 (communication device 10) to various input / output devices. The computer 1000 (communication device 10) is connected via the input / output interface 1050 to input devices such as operation buttons, a keyboard, a touch panel, and a microphone, and output devices such as a display and a speaker.

[0032] The network interface 1060 is an interface for connecting the computer 1000 (communication device 10) to a network. This network is, for example, a Controller Area Network (CAN) of the vehicle V. The network may also be, for example, a Local Area Network (LAN) or a Wide Area Network (WAN). The network interface 1060 may connect to the network wirelessly or via a wired connection. In the former case, the network interface 1060 supports various wireless communication standards. The computer 1000 (communication device 10) is connected to other devices, such as the in-vehicle device 20, via the network interface 1060.

[0033] <Example of Operation of Application Program> The following describes an example of an operation performed by the communication device 10 (computer 1000) executing the application program 100. Fig. 4 is a flowchart illustrating a layout setting operation performed by the communication device executing the application program.

[0034] First, the user operates the communication device 10 to start the application program 100 (step S102). For example, the user selects an icon corresponding to the application program 100 displayed on the desktop screen of the communication device 10. In response to this selection operation, the application program 100 starts.

[0035] When the layout setting input receiving module 110 is read in response to further operation by the user on the communication device 10, a layout setting editing screen is displayed on the display of the communication device 10 (step S104). When the layout setting input receiving module 110 receives input made by the user on the layout setting editing screen (step S106), it generates or updates layout setting information based on the input (step S108). The layout setting input receiving module 110 stores the layout setting information in, for example, the memory 1030 or the storage device 1040.

[0036] The layout setting input receiving module 110 monitors whether an operation indicating completion of layout setting editing (hereinafter referred to as "edit completion operation") has been performed by the user (step S110). The edit completion operation may be, for example, pressing a predetermined button displayed on a screen (not shown). If the edit completion operation is not detected (step S110: NO), steps S106 and S108 are repeatedly executed.

[0037] On the other hand, when an edit completion operation is detected (step S110: YES), the layout setting information transmission module 120 is read. In response to the edit completion operation, the layout setting information transmission module 120 transmits the layout setting information stored in the memory 1030 or the storage device 1040 to the in-vehicle device 20. Here, the layout setting information transmission module 120 may further execute a process of determining whether the communication device 10 and the in-vehicle device 20 are linked (step S112).

[0038] If the communication device 10 and the in-vehicle device 20 are currently linked (step S112: YES), the layout setting information transmission module 120 transmits layout setting information to the in-vehicle device 20 (step S114). In this case, the in-vehicle device 20 determines the layout of multiple function buttons on the screen displayed on the in-vehicle device 20 based on the layout setting information acquired from the communication device 10. On the other hand, if the communication device 10 and the in-vehicle device 20 are not linked (step S112: NO), the layout setting information transmission module 120 stores the layout setting information in the memory 1030 and the storage device 1040 (step S116). In this case, the layout setting information is transmitted to the in-vehicle device 20 when the communication device 10 and the in-vehicle device 20 subsequently start linking with each other.

[0039] An example of the layout setting operation by the application program 100 will be described in more detail with reference to the drawings. FIG. 5 is a diagram showing an example of a screen displayed on the display of the communication device 10 as a result of the communication device 10 executing the application program 100. When the application program 100 is started on the communication device 10, the application program 100 causes a screen such as that shown in this figure to be displayed on the display of the communication device 10. By checking the screen such as that shown in this figure, the user can confirm the current layout setting for the user in the in-vehicle device 20. Note that when the user performs a predetermined operation (e.g., a flick operation or a swipe operation) on the screen displayed on the display of the communication device 10, the screen displayed on the display of the communication device 10 transitions. For example, suppose that the user performs a flick operation or swipe operation to the left while the screen of FIG. 5(B) is displayed. In this case, a screen transition event occurs, and the screen of FIG. 5(C) is displayed on the display of the communication device 10. Similarly, suppose that the user performs a flick operation or swipe operation to the right while the screen of FIG. 5(B) is displayed. In this case, a screen transition event occurs, and the screen of Fig. 5(A) is displayed on the display of the communication device 10. Note that the screen (the screen illustrated in Fig. 5) displayed on the display of the communication device 10 by starting the application program 100 may not be the same as the screen displayed on the display of the in-vehicle device 20. For example, if the in-vehicle device 20 is linked to another communication device (not shown) owned by another user, layout information related to the other user that is set in an application program started on the other communication device (not shown) may be displayed on the display of the in-vehicle device 20.

[0040] The screen illustrated in this figure is the same as the screen for the function buttons displayed on the display of the in-vehicle device 20. For example, as shown in FIGS. 5A to 5C, assume that three screens (pages) can be transitioned to on the display of the communication device 10. In this case, screens similar to those shown in FIGS. 5A to 5C are displayed in the area where the function buttons of the in-vehicle device 20 are arranged. In the in-vehicle device 20, screens (pages) are preferably switched by pressing a screen switching button (software button or hardware button). However, the in-vehicle device 20 may also switch screens (pages) by a predetermined screen switching operation (flick operation or swipe operation) similar to the communication device 10.

[0041] Although details will be described in other embodiments, when the communication device 10 and the in-vehicle device 20 are linked, the screen displays related to the function buttons may or may not be synchronized between the communication device 10 and the in-vehicle device 20. In the latter case, it is possible to display one of a plurality of screens related to the function buttons on the display of the communication device 10, and another of the plurality of screens on the display of the in-vehicle device 20. In this case, the display of the communication device 10 virtually expands the entire display area of ​​the in-vehicle device 20. This allows more function buttons to be displayed, which is expected to have the effect of improving the usability of the in-vehicle device 20 (electronic device used in a vehicle).

[0042] 6A to 6C are diagrams illustrating an example of a flow of an operation for adding a function button executed on the application program 100 installed in the communication device 10. The hand symbols in these diagrams simulate operations by a user. Note that the flow of operations shown in these diagrams is merely an example, and the operation of the invention according to the present disclosure is not limited to the example shown in these diagrams.

[0043] First, the user selects a button to start editing the layout, as shown in FIG. 6A . This triggers a screen transition event, and a layout setting editing screen is displayed on the display of the communication device 10, as shown in FIG. 6B . In the example of FIG. 6B , the user selects a menu item corresponding to “Add Function Button” on an interface showing a menu related to editing layout settings. This causes a list to be displayed, as shown in FIG. 6C , for selecting the type of function button to be added. In the example of FIG. 6C , the user selects audio and video sources on the list. This causes icons of function buttons related to audio and video sources to be displayed, as shown in FIG. 6D . In the example of FIG. 6D , the user selects a function button for activating the radio as a source for the in-vehicle device 20. After selecting the function button to be added, the user performs a predetermined operation (e.g., a drag-and-drop operation), as shown in FIG. 6E . As a result, the function button selected in FIG. 6D is added to the screen, as shown in FIG. 6F . The layout setting input receiving module 110 generates or updates layout setting information based on the input as shown in this figure. Thereafter, when a predetermined operation (editing completion operation) is performed to complete the layout editing, the layout setting information transmission module 120 transmits the layout setting information generated or updated in accordance with the operations up to that point to the vehicle-mounted device 20.

[0044] 7A to 7C are diagrams illustrating an example of a flow of a function button deletion operation executed on the application program 100 installed in the communication device 10. The hand symbols in these diagrams simulate user operations. Note that the flow of operations shown in these diagrams is merely an example, and the operation of the present disclosure is not limited to the example shown in these diagrams.

[0045] First, the user selects a button to start layout editing, as shown in FIG. 7A . This triggers a screen transition event, and a layout setting editing screen is displayed on the display of the communication device 10, as shown in FIG. 7B . In the example of FIG. 7B , the user selects a menu item corresponding to “Delete Function Button” on an interface displaying a menu related to layout setting editing. Then, as shown in FIG. 7C , the user selects a function button to be deleted. As shown in FIG. 7D , a deletion confirmation dialog box is displayed. When an operation to approve the deletion (e.g., pressing the Delete button) is performed, as shown in FIG. 7D , the selected function button is deleted from the screen, as shown in FIG. 7E . The layout setting input receiving module 110 generates or updates layout setting information based on the input as shown in FIG. 7A . Then, when an operation to complete the layout editing (editing completion operation) is performed, the layout setting information transmission module 120 transmits the layout setting information generated or updated in accordance with the previous operations to the in-vehicle device 20.

[0046] 8A to 8C are diagrams illustrating an example of the flow of a function button rearrangement operation executed on the application program 100 installed in the communication device 10. The hand symbols in these diagrams simulate user operations. Note that the flow of operations shown in these diagrams is merely an example, and the operation of the present disclosure is not limited to the example shown in these diagrams.

[0047] First, the user selects a button to start layout editing, as shown in FIG. 8A . This triggers a screen transition event, and a layout setting editing screen is displayed on the display of the communication device 10, as shown in FIG. 8B . In the example of FIG. 8B , the user selects a function button to be rearranged on the screen. After selecting the target function button, the user performs a predetermined operation (e.g., a drag-and-drop operation), as shown in FIG. 8C . In response to this operation, the selected function button is swapped with another function button, as shown in FIG. 8D . Finally, the rearrangement of the function buttons is completed, as shown in FIG. 8E . After that, when an operation to complete the layout editing (editing completion operation) is performed, the layout setting information transmission module 120 transmits the layout setting information generated or updated in response to the previous operations to the in-vehicle device 20.

[0048] As described above, according to the application program 100 of the present embodiment, a function for editing the layout settings of multiple function buttons used in the in-vehicle device 20 is implemented in the communication device 10 in which the application program 100 is installed. The driver of the vehicle V can start the application program 100 and edit the display layout of the multiple function buttons of the in-vehicle device 20 when not driving the vehicle V. A passenger in the vehicle V can also start the application program 100 and edit the display layout of the multiple function buttons of the in-vehicle device 20. In this way, the user of the communication device 10 can use the application program 100 to edit the layout of the multiple function buttons displayed on the in-vehicle device 20 to suit the user's preferences. When the communication device 10 and the in-vehicle device 20 cooperate with each other, information indicating the layout settings of the multiple function buttons edited on the application program 100 is transmitted to the in-vehicle device 20. As a result, the edited layout settings of the multiple function buttons are reflected on the display of the in-vehicle device 20. In this way, by making it possible to easily change the layout of the function buttons on the vehicle-mounted device 20 to suit the preferences of the driver or passengers of the vehicle V, it is expected that the usability of the electronic device (vehicle-mounted device 20) used in the vehicle will be improved.

[0049] <Modification of Functional Configuration of Application Program> Generally, preferred layout settings for multiple function buttons used in the vehicle-mounted device 20 differ from user to user. Therefore, the application program 100 installed in the communication device 10 may have functions such as those illustrated in Fig. 9. Fig. 9 is a block diagram showing a second example of the functional configuration of an application program in the present disclosure.

[0050] In the example shown in this figure, the application program 100 includes an identification information acquisition module 130 in addition to the configuration illustrated in FIG. 2 . The identification information acquisition module 130 provides a function for acquiring information identifying the communication device 10 (computer) or the user of the communication device 10 (computer) (hereinafter also referred to as “identification information”). The information identifying the communication device 10 (computer) is, for example, information indicating a unique terminal identification number, such as an International Mobile Equipment Identity (IMEI). The information identifying the user is, for example, user-specific information, such as a user identifier assigned to the user when the application program 100 is installed or account information entered by the user when the application program 100 is installed. In this modification, the layout setting information transmission module 120 transmits layout setting information to the in-vehicle device 20, linking it to the identification information acquired by the identification information acquisition module 130. As a result, layout setting information capable of identifying the user (i.e., layout setting information for each user) is transmitted to the in-vehicle device 20.

[0051] Here, the layout setting information for each user is stored in at least one of the communication device 10 and the in-vehicle device 20. By storing the layout setting information for each user in at least one of the communication device 10 and the in-vehicle device 20, further improvement in usability can be expected. For example, when the communication device 10 stores the layout setting information for each user, the layout setting of function buttons for the in-vehicle device of the vehicle that the user normally uses can be easily reflected in the in-vehicle device of another vehicle. Specifically, when the user enters a second vehicle different from the first vehicle that the user normally uses and links the communication device 10 with the in-vehicle device of the second vehicle, the layout setting information for each user stored in the storage area of ​​the communication device 10 is transmitted to the in-vehicle device of the second vehicle. Then, a screen for arranging function buttons based on the layout setting information is displayed on the display of the in-vehicle device of the second vehicle. That is, in a case where a user can use multiple in-vehicle devices (e.g., a case where the user owns multiple vehicles), a function button layout tailored to the user's preferences is automatically applied to the target in-vehicle device without requiring configuration operations for each in-vehicle device. This is expected to improve the user experience when the user uses multiple in-vehicle devices. For example, if the in-vehicle device 20 stores layout setting information for each user, and multiple users (e.g., family members or friends) share a single vehicle, each user's layout setting can be recalled and reflected in the in-vehicle device 20 without the need for layout editing operations. Specifically, when collaboration between the communication device 10 and the in-vehicle device 20 is disclosed, identification information acquired by the identification information acquisition module 130 is transmitted from the communication device 10 to the in-vehicle device 20. Based on the identification information transmitted from the communication device 10, the in-vehicle device 20 identifies layout setting information corresponding to the identification information from the layout setting information for each user stored in its storage area. Then, the in-vehicle device 20 displays a screen on the display on which function buttons are arranged based on the identified layout setting information. In other words, in a case where multiple users share one vehicle (one onboard device), the layout of function buttons tailored to each user's preferences is automatically applied to the onboard device without the need for each user to perform setting operations each time they get in the vehicle.This is expected to improve the user experience for each user when multiple users share a single in-vehicle device.

[0052] Alternatively, the layout information for each user may be stored in a so-called cloud server. In this case, the layout setting information transmission module 120 associates the identification information acquired by the identification information acquisition module 130 with the layout setting information and transmits them to the cloud server (not shown). After that, when cooperation between the communication device 10 and the in-vehicle device 20 is initiated, either the communication device 10 or the in-vehicle device 20 communicates with the cloud server (not shown) and acquires the layout setting information for each user stored in the cloud server. A screen based on the acquired layout setting information is then displayed on the display of the in-vehicle device 20.

[0053] 10 is a block diagram showing a first example of the functional configuration of an in-vehicle device according to the present disclosure. The in-vehicle device 20 shown in the figure includes at least a layout setting information acquisition unit 210 and a display control unit 220.

[0054] The layout setting information acquisition unit 210 acquires information (layout setting information) for setting the layout of function buttons available on the vehicle-mounted device 20 from an external computer (e.g., the communication device 10). The display control unit 220 arranges each function button in an area (hereinafter also referred to as a "first display area") where multiple function buttons are displayed on the display of the vehicle-mounted device 20, based on the acquired layout setting information.

[0055] <Example of Hardware Configuration of Vehicle-Mounted Device> FIG. 11 is a diagram illustrating an example of the hardware configuration of a computer that realizes the vehicle-mounted device according to the present disclosure.

[0056] The computer 2000 illustrated in this figure includes a bus 2010 , a processor 2020 , a memory 2030 , a storage device 2040 , an input / output interface 2050 , and a network interface 2060 .

[0057] The bus 2010 is a data transmission path for transmitting and receiving data among the processor 2020, memory 2030, storage device 2040, input / output interface 2050, and network interface 2060. However, the method of connecting the processor 2020 and the like to each other is not limited to bus connection.

[0058] The processor 2020 is implemented as a central processing unit (CPU) or a graphics processing unit (GPU).

[0059] The memory 2030 is a main storage device realized by a random access memory (RAM) or the like.

[0060] The storage device 2040 is an auxiliary storage device realized by removable media such as a hard disk drive (HDD), a solid state drive (SSD), a memory card, or a read only memory (ROM), etc. The storage device 2040 stores at least program modules that realize the functions of the above-described in-vehicle device 20 (the layout setting information acquisition unit 210 and the display control unit 220).

[0061] The processor 2020 loads a program module read from the storage device 2040 onto the memory 2030 and executes the program module, thereby realizing a function corresponding to the program module. For example, the processor 2020 reads a program module corresponding to the layout setting information acquisition unit 210 onto the memory 2030 and executes the program module, thereby realizing the function of the layout setting information acquisition unit 210 described in the present disclosure. Similarly, the processor 2020 reads a program module corresponding to the display control unit 220 onto the memory 2030 and executes the program module, thereby realizing the function of the display control unit 220 described in the present disclosure. The operation of the processor 2020 is common to each embodiment included in the present disclosure.

[0062] The above-described program modules may be recorded on a recording medium other than the storage device 2040. The recording medium on which the program modules are recorded includes any non-transitory, tangible medium usable by the computer 2000. The recording medium on which the program modules are recorded may have embedded therein program code that is readable by the computer 2000 (processor 2020).

[0063] The input / output interface 2050 is an interface for connecting the computer 2000 (the in-vehicle device 20) to various input / output devices. The computer 2000 (the in-vehicle device 20) is connected via the input / output interface 2050 to input devices such as operation buttons, a keyboard, a touch panel, and a microphone, and output devices such as a display and a speaker.

[0064] The network interface 2060 is an interface for connecting the computer 2000 (on-board device 20) to a network. This network is, for example, a Controller Area Network (CAN) of the vehicle V. The network may also be, for example, a Local Area Network (LAN) or a Wide Area Network (WAN). The network interface 2060 may connect to the network via a wireless connection or a wired connection. In the former case, the network interface 2060 supports various wireless communication standards. The computer 2000 (on-board device 20) is connected to other devices such as the communication device 10 via the network interface 2060.

[0065] <Example of Operation of Vehicle-Mounted Device> An example of operation executed by the vehicle-mounted device 20 (computer 2000) will be described below. Fig. 12 is a flowchart showing a first example of operation executed by the vehicle-mounted device in the present disclosure.

[0066] First, the layout setting information acquisition unit 210 acquires layout setting information (step S202). As an example, when linking with the communication device 10, the layout setting information acquisition unit 210 acquires layout information stored in the communication device 10 from the communication device 10. As another example, the layout setting information generated or updated by the application program 100 of the communication device 10 may be stored in a storage area (e.g., the memory 2030 or the storage device 2040) of the in-vehicle device 20 when the communication device 10 and the in-vehicle device 20 link. In this case, the layout setting information acquisition unit 210 reads the layout setting information stored in the storage area of ​​the in-vehicle device 20 in response to the start of linking between the in-vehicle device 20 and the communication device 10. As yet another example, the layout setting information may be stored in a cloud server (not shown). In this case, in response to the start of linking between the communication device 10 and the in-vehicle device 20, the communication device 10 or the in-vehicle device 20 communicates with the cloud server (not shown) and acquires the layout setting information stored on the cloud server.

[0067] The display control unit 220 generates screen data for arranging the function buttons in an area (first display area) for arranging the function buttons based on the layout setting information acquired in step S202 (step S204).Then, the display control unit 220 displays a screen based on the screen data on the display of the in-vehicle device 20 (step S206).

[0068] <Display Example of the In-Vehicle Device Display> FIG. 13 is a diagram illustrating an example of information displayed on the display of the in-vehicle device by the display control unit in the present disclosure. As illustrated in FIG. 13 , the display control unit 220 displays multiple function buttons in a portion (first display area A1) of the display area of ​​the in-vehicle device. Here, the display control unit 220 determines the multiple function buttons to be arranged in the first display area A1 and their display positions based on layout setting information. The display control unit 220 also displays information different from the multiple function buttons in an area A2 (hereinafter also referred to as the "second display area") of the display area of ​​the in-vehicle device that is different from the first display area. Here, "information different from the multiple function buttons" includes, for example, information about various screens used by the in-vehicle device 20. For example, as illustrated in FIG. 13 , the home screen of the in-vehicle device 20 is displayed in the second display area A2. Furthermore, when multiple function buttons displayed in the first display area A1 (or multiple function buttons displayed on the display of the communication device 10 by the application program 100) are selected, a screen to be launched in response to the selection may be displayed in the second display area A2. For example, the function button located at the top of the first display area A1 is a button for calling up a song selection function. When this function button is pressed, a screen for selecting an artist, album, song track, etc. is displayed in the second display area A2.

[0069] Furthermore, the display control unit 220 can switch the screen displayed in the first display area A1 in response to detecting a predetermined screen switching operation by the user. For example, the display control unit 220 can switch the screen displayed in the first display area A1, as shown in FIG. 14 , in response to detecting an operation on a screen switching button B1 displayed in the first display area A1. In this case, by configuring the screen switching to be performed using the screen switching button B1, it is possible to prevent erroneous operations due to touch operations on A2, etc. FIG. 14 is a diagram showing another example of information displayed on the display of the in-vehicle device by the display control unit of the present disclosure. In FIG. 14 , the display control unit 220 displays another screen based on layout setting information in the first display area A1. Note that in this figure, the function button B2 is a function button for outputting video from an in-vehicle camera capturing images of the vehicle's surroundings. In this case, the display control unit 220 may display video captured by the in-vehicle camera in real time in the area of ​​the function button B2, as shown in the figure. When the function button B2 is selected, the display control unit 220 may enlarge and display the camera image displayed on the button in the second display area A2, for example.

[0070] In this way, a screen based on the layout setting information edited using the application program 100 installed in the communication device 10 exemplified in this embodiment is displayed on the display of the in-vehicle device 20. That is, a screen configured to be easy for the user to use is displayed on the display of the in-vehicle device 20. This is expected to have the effect of improving the usability of the electronic device (in-vehicle device 20) used in the vehicle.

[0071] Second Embodiment This embodiment is similar to the first embodiment except for the points described below.

[0072] <Example of Functional Configuration of Application Program> The application program 100 installed in the communication device 10 further includes a program module that realizes a function as a remote controller for the vehicle-mounted device 20, as shown in FIG. 14, for example.

[0073] FIG. 15 is a block diagram showing a third example of the functional configuration of an application program according to the present disclosure. The application program 100 illustrated in this figure further includes a display control module 140 and a control instruction transmission module 150. The display control module 140 provides a function for displaying a screen based on the layout setting information obtained through the above-described processing on the display of the communication device 10 (computer). Here, the screen displayed on the display of the communication device 10 by the display control module 140 is the same as the screen displayed in the first display area A1 of the vehicle-mounted device 20. In other words, the screen displayed on the display of the communication device 10 by the display control module 140 is a screen on which multiple function buttons used by the vehicle-mounted device 20 are arranged according to the layout setting information. The control instruction transmission module 150 provides a function for transmitting control instructions to the communication device 10 in response to operation inputs on the screen displayed on the display of the communication device 10 (computer).

[0074] Although not shown in this figure, the application program 100 may further include an identification information acquisition module 130 exemplified in FIG.

[0075] <Example of Operation of Application Program> FIG. 16 is a flowchart illustrating an example of a control operation performed by a communication device according to the present disclosure by executing an application program.

[0076] In response to the start of cooperation between the communication device 10 and the in-vehicle device 20, the display control module 140 acquires layout setting information (step S302). The display control module 140 can acquire the layout setting information to be used from, for example, a storage area of ​​the communication device 10 or another external device (the in-vehicle device 20 or a cloud server not shown).

[0077] Then, the display control module 140 displays a screen based on the acquired layout setting information on the display of the communication device 10 (step S304). For example, the display control module 140 displays a screen such as that shown in Fig. 5A on the display of the communication device 10. As described above, the user can transition the screen displayed on the display of the communication device 10 by performing a predetermined operation (e.g., a flick operation or a swipe operation) on the screen displayed on the display of the communication device 10.

[0078] The control instruction transmission module 150 also accepts a user's selection of a function button on the screen displayed on the display of the communication device 10 (step S306). When the user arbitrarily selects a function button, the control instruction transmission module 150 acquires information indicating the selected function button (hereinafter also referred to as "button selection information"). The button generation information includes, for example, information equivalent to the control information generated when a function button is selected on the in-vehicle device 20. The control instruction transmission module 150 then executes a process to call the function corresponding to the selected function button (step S308).

[0079] <Example of Functional Configuration of In-Vehicle Device> FIG. 17 is a block diagram showing a second example of the functional configuration of an in-vehicle device according to the present disclosure. The in-vehicle device 20 illustrated in this figure further includes a button selection information acquisition unit 230. The button selection information acquisition unit 230 acquires information (hereinafter also referred to as "button selection information") generated in response to the selection of a function button on at least one of an external computer (e.g., the communication device 10) and the first display area of ​​the in-vehicle device 20. Furthermore, a function (process) corresponding to the function button indicated by the button selection information is executed. For example, the display control unit 220 executes a process to display, in the second display area, a screen corresponding to the function button indicated by the button selection information, among various screens used by the in-vehicle device 20.

[0080] FIG. 18 is a flowchart showing a second example of the operation executed by the vehicle-mounted device according to the present disclosure.

[0081] First, the button selection information acquisition unit 230 acquires button selection information generated by selecting a function button on a screen displayed on the display of the communication device 10 (step S402). The in-vehicle device 20 executes processing corresponding to the function button indicated by the button selection information acquired in step S402 (step S404). For example, assume that the button selection information acquired in step S402 indicates a function button for calling up one of the screens used by the in-vehicle device. In this case, the display control unit 220 reads screen data corresponding to the function button indicated by the button selection information and executes processing to display the screen data in the second display area (area A2 in FIGS. 13 and 14 ).

[0082] <Specific Example of Operation> A specific example of operation will be described with reference to Fig. 5. For example, as shown by diagonal hatching in Fig. 5A, assume that a button for muting (or canceling) the audio is selected. In this case, the control instruction transmission module 150 generates information indicating the selected function button as button selection information and transmits the button selection information to the in-vehicle device 20. Based on the transmitted button selection information, the in-vehicle device 20 identifies the selected function button as a "button for setting mute (or canceling mute)." Then, based on the identification result of the selected function button, the in-vehicle device 20 controls ON / OFF of audio output from the speaker provided in the vehicle.

[0083] 5B, assume that a button to which a preset equalization setting is applied is selected. In this case, the control instruction transmission module 150 generates information indicating the selected function button as button selection information and transmits the button selection information to the in-vehicle device 20. Based on the generated button selection information, the in-vehicle device 20 identifies the selected function button as a "button to which a preset equalization setting is applied." Based on the result of identifying the selected function button, the in-vehicle device 20 then reads out the equalization preset information associated with the selected function button and applies it to the audio output of the in-vehicle device 20.

[0084] For example, suppose a button for switching the FM radio frequency to a specific frequency is selected, as indicated by diagonal hatching in Figure 5C. In this case, the control instruction transmission module 150 generates information indicating the selected function button as button selection information and transmits the button selection information to the in-vehicle device 20. Based on the generated button selection information, the in-vehicle device 20 identifies the selected function button as a "button for switching the FM radio frequency." Based on the identification result of the selected function button, the in-vehicle device 20 then reads information about the FM radio frequency associated with the function button and controls the antenna provided in the vehicle to receive radio waves of that frequency.

[0085] 14 is displayed on the in-vehicle device 20 as a screen based on the layout setting information, a screen similar to the screen displayed in the first display area A1 in FIG. 14 is also displayed on the display of the communication device 10 linked to the in-vehicle device 20. Assume that function button B2 is selected on the screen displayed on the display of the communication device 10. In this case, the control instruction transmission module 150 transmits information indicating that function button B2 has been selected as button selection information to the in-vehicle device 20. Based on the selected function button, the in-vehicle device 20 executes a process of displaying the video from the in-vehicle camera corresponding to function button B2 in the second display area (area A2 in FIGS. 13 and 14 ).

[0086] In addition, the screen may include a function button for launching another application program that is installed in the communication device 10 separately from the application program 100. For example, in the screen of Fig. 5C, the function button located in the second column from the top on the right side is given a predetermined mark indicating that it is a button for launching an application program installed in the communication device 10. When such a function button is selected on the screen displayed on the display of the communication device 10, the application program 100 controls the communication device 10 to launch the application program corresponding to that function button.

[0087] In the above example, when the in-vehicle device 20 and the communication device 10 (external computer) are linked, the selection states of multiple function buttons may be synchronized between the screen displayed on the display of the communication device 10 and the screen displayed on the display of the in-vehicle device 20. For example, when the communication device 10 and the in-vehicle device 20 are linked, assume that one of multiple function buttons is selected on a screen displayed on the display of either the communication device 10 or the in-vehicle device 20. In this case, information indicating the selection state is transmitted to the other of the communication device 10 and the in-vehicle device 20. The other of the communication device 10 and the in-vehicle device 20 changes the selection state on the display based on the acquired information indicating the selection state. As a result, the selection states of multiple function buttons on the communication device 10 and the in-vehicle device 20 are synchronized.

[0088] As described above, according to this embodiment, it is possible to accept a user's operation input on the screen related to the function buttons displayed on the display of the communication device 10 based on the layout setting information, and to call up a function of the in-vehicle device 20 corresponding to the operation input. It is also possible to accept an operation input related to the function buttons displayed on the display of the in-vehicle device 20 based on the layout setting information, and to launch an application installed on the communication device 10 in response to the operation input. It is also possible to virtually expand the entire display area of ​​the in-vehicle device 20 using the display of the communication device 10. This allows more function buttons to be displayed, which is expected to have the effect of improving the usability of the in-vehicle device 20 (electronic device used in a vehicle).

[0089] Third Embodiment When there are multiple grades of the in-vehicle device 20, the supported functions may differ depending on the grade. For example, it is possible that a lower-grade, less expensive in-vehicle device 20 does not support some functions that a higher-grade in-vehicle device 20 supports. The vehicle system 1 described in this embodiment further has a configuration to solve this problem. Note that this embodiment has the same configuration as the other embodiments, except for the points described below.

[0090] In the vehicle system 1 of this embodiment, a function button that is not supported by the target vehicle-mounted device 20 is preferably controlled to be in an inactive state in the communication device 10 (computer) and the vehicle-mounted device 20 .

[0091] 19 is a flowchart illustrating a function button deactivation control operation performed by a communication device according to the present disclosure when the communication device executes an application program. For example, when the communication device 10 and the in-vehicle device 20 start linking with each other, the application program 100 acquires information for identifying functions supported by the in-vehicle device 20 (step S502). For example, in response to the start of linking between the communication device 10 and the in-vehicle device 20, the application program 100 can acquire information indicating the model number of the in-vehicle device 20 from the in-vehicle device 20.

[0092] The application program 100 then identifies functions that are not supported by the in-vehicle device 20 based on the information acquired from the in-vehicle device 20 (step S504).The application program 100 then executes a control process to display the function buttons corresponding to the identified functions in an inactive state using the results of the identification of the functions that are not supported by the in-vehicle device 20 (step S506).

[0093] As one example, the layout setting input receiving module 110 controls a function button identified as a "function button not supported by the in-vehicle device 20" in a list of multiple function buttons displayed, for example, in FIG. 6D to be inactive. This prevents the communication device 10 from accidentally setting a function button that is not supported by the in-vehicle device 20 linked to the communication device 10, which could result in a decrease in usability. As another example, the display control module 140 controls a function button identified as a "function button not supported by the in-vehicle device 20" in a screen based on the acquired layout setting information, for example, in FIGS. 5A to 5C, to be inactive. This allows the user to easily identify function buttons that are not supported by the in-vehicle device 20 linked to the communication device 10. As a result, improved usability can be expected.

[0094] FIG. 20 is a flowchart illustrating a function button deactivation control operation executed by the in-vehicle device according to the present disclosure. First, when displaying a screen based on layout setting information, the display control unit 220 acquires information stored in a predetermined storage area of ​​the in-vehicle device 20 for identifying functions supported by the in-vehicle device 20 (step S602). For example, the display control unit 220 acquires information indicating a model number stored in the storage area of ​​the in-vehicle device 20. Based on the information acquired in step S602, the display control unit 220 then identifies function buttons not supported by the in-vehicle device 20 from among the multiple function buttons arranged on the screen based on the layout setting information (step S604). When displaying a screen based on the acquired layout setting information, the display control unit 220 then deactivates the function buttons identified as "function buttons not supported by the in-vehicle device 20" (step S606). This allows the user to easily identify function buttons not supported by the in-vehicle device 20 when operating the in-vehicle device 20. As a result, improved usability can be expected.

[0095] Although the present disclosure has been described above with reference to the embodiments, the present disclosure is not limited to the above-described embodiments. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present disclosure within the scope of the present disclosure. Furthermore, each embodiment can be combined with other embodiments as appropriate.

[0096] In addition, although the flowcharts used in the above description show a sequence of steps (processes), the order of steps executed in each embodiment is not limited to the sequence shown in the flowcharts. In each embodiment, the order of steps shown in the diagrams can be changed as long as it does not cause any problems in terms of the content.

[0097] Examples of reference forms are given below. 1. A program that, when executed by a computer, causes the computer to perform operations including: accepting input for setting a layout of function buttons of an in-vehicle device; and transmitting layout setting information based on the input to the in-vehicle device. 2. The program described in 1., wherein the operations further include: acquiring identification information for identifying the computer or a user of the computer; and transmitting the layout setting information linked to the identification information. 3. The program described in 1. or 2., wherein the operations further include displaying a screen based on the layout setting information on a display of the computer; and transmitting to the in-vehicle device a control instruction corresponding to an operation input on the screen displayed on the display of the computer. 4. An in-vehicle device comprising: layout setting information acquisition means for acquiring layout setting information for setting a layout of function buttons from an external computer; and display control means for arranging each function button in a first display area in which a plurality of function buttons are displayed, based on the layout setting information. 5. The in-vehicle device according to 4., wherein the display control means displays the plurality of function buttons in the first display area, and displays information different from the plurality of function buttons in a second display area different from the first display area. 6. The in-vehicle device according to 5., further comprising button selection information acquisition means for acquiring button selection information generated in response to a selection of a function button on either the external computer or the first display area, wherein the display control means displays a screen corresponding to a function button indicated by the button selection information in the second display area. 7. A system comprising: a program according to any one of 1. to 3.; and an in-vehicle device according to any one of 4. to 6.. 8. The system according to 7., wherein at least one of the computer and the in-vehicle device holds the layout setting information for each user. 9. The system according to 7. or 8., wherein the function buttons that are not supported in the in-vehicle device are controlled to an inactive state in the computer and the in-vehicle device.10. The system described in any one of 7. to 9., wherein the computer transmits the layout setting information to the in-vehicle device in response to an operation indicating completion of editing of the layout setting information. 11. The system described in any one of 7. to 10., wherein the plurality of function buttons includes a button for transitioning to one of a plurality of screens used on the in-vehicle device. 12. The system described in any one of 7. to 11., wherein the plurality of function buttons includes a button for launching an application installed on the computer. 13. The system described in any one of 7. to 12., wherein when the computer and the in-vehicle device are linked, the selection states of the plurality of function buttons on the computer and the in-vehicle device are synchronized.

[0098] REFERENCE SIGNS LIST 1 Vehicle system 10 Communication device 1000 Computer 1010 Bus 1020 Processor 1030 Memory 1040 Storage device 1050 Input / output interface 1060 Network interface 100 Application program 110 Layout setting input reception module 120 Layout setting information transmission module 130 Identification information acquisition module 140 Display control module 150 Control instruction transmission module 20 Vehicle-mounted device 2000 Computer 2010 Bus 2020 Processor 2030 Memory 2040 Storage device 2050 Input / output interface 2060 Network interface 210 Layout setting information acquisition unit 220 Display control unit 230 Button selection information acquisition unit

Claims

1. A program that, when executed by a computer, causes the computer to receive an input for setting the layout of function buttons of an in-vehicle device and transmit layout setting information based on the input to the in-vehicle device.

2. The program according to claim 1, wherein the operation further includes obtaining identification information for identifying the computer or a user of the computer and transmitting the layout setting information in association with the identification information.

3. The program according to claim 1 or 2, wherein the operation further includes causing a screen based on the layout setting information to be displayed on a display of the computer and transmitting a control instruction corresponding to an operation input on the screen displayed on the display of the computer to the in-vehicle device.

4. An in-vehicle device comprising: layout setting information acquisition means for acquiring layout setting information for setting the layout of function buttons from an external computer; and display control means for arranging each function button in a first display area where a plurality of function buttons are displayed based on the layout setting information.

5. The in-vehicle device according to claim 4, wherein the display control means causes the plurality of function buttons to be displayed in the first display area and causes information different from the plurality of function buttons to be displayed in a second display area different from the first display area.

6. The in-vehicle device according to claim 5, further comprising button selection information acquisition means for acquiring button selection information generated in response to a function button being selected on either the external computer or the first display area, wherein the display control means causes a screen corresponding to the function button indicated by the button selection information to be displayed in the second display area.

7. A system comprising: the program according to any one of claims 1 to 3; and the in-vehicle device according to any one of claims 4 to 6.

8. The system according to claim 7, wherein at least one of the computer and the in-vehicle device holds the layout setting information for each user.

9. The system according to claim 7 or 8, wherein the function buttons not supported by the in-vehicle device are controlled to be in an inactive state in the computer and the in-vehicle device.

10. The system according to any one of claims 7 to 9, wherein the computer transmits the layout setting information to the in-vehicle device in response to an operation indicating completion of editing of the layout setting information.

11. The system according to any one of claims 7 to 10, wherein the plurality of function buttons include buttons for transitioning to any one of a plurality of screens used in the in-vehicle device.

12. The system according to any one of claims 7 to 11, wherein the plurality of function buttons include buttons for starting an application installed in the computer.

13. The system according to any one of claims 7 to 12, wherein when the computer and the in-vehicle device are in cooperation, selection states of the plurality of function buttons in the computer and the in-vehicle device are synchronized.

Images