JP2019191835A - On-vehicle device, and cooperation method - Google Patents

Abstract

To provide an on-vehicle device capable of improving safety when used with a portable terminal, and a cooperation method.SOLUTION: An on-vehicle device communicable with a portable terminal by respectively using a first communication channel and a second communication channel includes: a reception unit for receiving installed notification that an application for cooperation which operates in cooperation with the on-vehicle device is installed in the portable terminal through the first communication channel; and an on-vehicle cooperation unit for determining the presence/absence of reception of installed notification when establishment of the second communication channel is detected, transmitting a signal to start the cooperation between the on-vehicle device and the portable terminal by using the second communication channel in the case of determining that the installed notification is received, and not transmitting the signal to start the cooperation in the case of determining that the installed notification is not received.SELECTED DRAWING: Figure 2

Description

  The present invention relates to an in-vehicle device and a cooperation method.

  The in-vehicle device can be used alone, but convenience is improved by linking with a mobile terminal owned by the user. In recent years, in-vehicle devices that can be connected to portable terminals are widely known. Patent Document 1 discloses an electronic device that can be connected to an information terminal device, using a connection unit that enables USB connection with the information terminal device, and a device class prepared in advance in the information terminal device. To the first communication mode means for communicating with the information terminal device, to request means for requesting the information terminal device to switch to the second communication mode means different from the first communication mode means, and to the second communication mode means Based on the search result of the search means and the search result of the search means, it is determined whether or not an adverse change has occurred in the first communication mode means. An electronic device is disclosed that includes a determination unit and a reset unit that allows the connection unit to be reset when it is determined that an adverse change has occurred by the determination unit.

JP 2014-85857 A

  In the invention described in Patent Document 1, there is room for improvement in safety.

The vehicle-mounted device according to the first aspect of the present invention is a vehicle-mounted device that can communicate with a mobile terminal using each of the first communication path and the second communication path, and operates in cooperation with the vehicle-mounted apparatus. An acquisition unit that receives an installed notification that the application for the application is installed in the mobile terminal from the mobile terminal using the first communication path, and detects the establishment of the second communication path, the installation A signal for starting cooperation between the in-vehicle device and the portable terminal is transmitted using the second communication path when it is determined whether or not the received notification has been received. And a vehicle-mounted cooperation unit that does not transmit a signal for starting the cooperation when it is determined that the installed notification has not been received.
The cooperation method according to the second aspect of the present invention is a cooperation method between an in-vehicle device and a mobile terminal capable of communicating using each of the first communication path and the second communication path, and the mobile terminal is connected to the in-vehicle Transmitting a notification indicating whether or not a cooperation application operating in cooperation with the device is installed to the in-vehicle device using the first communication path; and When establishment is detected, the presence / absence of installation of the application for cooperation in the mobile terminal is determined based on the received notification, and when it is determined that the application is installed, cooperation between the in-vehicle device and the mobile terminal is determined. A signal to be started is transmitted using the second communication path, and the cooperation is started when it is determined that the application is not installed. And a not transmitting a signal.

  ADVANTAGE OF THE INVENTION According to this invention, the safety | security at the time of using with a portable terminal can be improved.

Hardware configuration diagram of linkage system S Functional configuration diagram of in-vehicle device 1 and portable terminal 2 The figure which shows an example of the application table | surface 263 Sequence diagram showing the operation of the cooperation system S when the cooperation application 262 is stored in the flash memory 26 The sequence diagram which shows operation | movement of the cooperation system S when the cooperation application 262 is not stored in the flash memory 26 The flowchart showing the operation of the in-vehicle cooperation unit 113 in the first embodiment. The flowchart showing the operation of the wireless processing unit 211 in the first embodiment. The flowchart showing the operation of the companion application 261 in the first embodiment The flowchart showing operation | movement of the wired cooperation part 212 in 1st Embodiment. The figure which shows an example of the screen display which prompts the installation displayed in S437 of FIG. Sequence diagram in comparative example The figure which shows an example of OS application table | surface 263A in 2nd Embodiment The flowchart showing the operation of the companion application 261 in the second embodiment The flowchart showing the operation of the in-vehicle cooperation unit 113 in the second embodiment Flowchart representing the operation of the wire link unit 212 in the second embodiment The figure which shows an example of the code | correspondence table | surface 264 in the modification 1 of 2nd Embodiment. The flowchart showing operation | movement of the vehicle-mounted cooperation part 113 in the modification 1 of 2nd Embodiment. Functional configuration diagram of the cooperation system S in the third embodiment The flowchart showing operation | movement of the companion application 261 in 3rd Embodiment The flowchart showing the operation of the in-vehicle cooperation unit 113 in the third embodiment

-First embodiment-
Hereinafter, with reference to FIGS. 1-11, 1st Embodiment of the vehicle-mounted apparatus 1 which concerns on this invention is described.

(Hardware configuration)
FIG. 1 is a diagram showing a hardware configuration of a cooperation system S according to the present invention. The linkage system S includes an in-vehicle device 1 and a mobile terminal 2 mounted on the vehicle 5. However, the in-vehicle device 1 and the mobile terminal 2 can be used outside the vehicle 5 and merely show the vehicle 5 as an example of a usage scene. The in-vehicle device 1 and the portable terminal 2 can communicate with each other through two communication paths as will be described later. In the present embodiment, a person who uses the cooperation system S is called a “user”.

  The in-vehicle device 1 includes a CPU 11, a ROM 12, a RAM 13, a wireless communication module 14, a wired communication module 15, a flash memory 16, a display unit 17, and an input unit 18. The CPU 11 is a central processing unit, and realizes functions to be described later by developing a program stored in the ROM 12 in the RAM 13 and executing it. The RAM 13 is a volatile storage device, and the RAM 13 also stores information necessary for program operation. The wireless communication module 14 is a communication module that exchanges information by wireless signals, and corresponds to, for example, Bluetooth (registered trademark) or IEEE 802.11 communication standards.

  The wired communication module 15 is a communication module that exchanges information via a USB cable or the like, and corresponds to, for example, a USB communication standard. The flash memory 16 is a non-volatile storage device. The display unit 17 is a liquid crystal display, for example, and presents image information to the user based on an operation command from the CPU 11. The input unit 18 is, for example, a plurality of buttons, and receives a user input and transmits it to the CPU 11.

  The portable terminal 2 includes a CPU 21, a ROM 22, a RAM 23, a wireless communication module 24, a wired communication module 25, a flash memory 26, a display unit 27, and an input unit 28. The CPU 21 is a central processing unit, and realizes functions to be described later by developing a program stored in the ROM 22 in the RAM 23 and executing it. The RAM 23 is a volatile storage device, and the RAM 23 also stores information necessary for program operation. The wireless communication module 24 is a communication module that transmits and receives information by wireless signals, and corresponds to, for example, Bluetooth and IEEE 802.11 communication standards.

  The wired communication module 25 is a communication module that exchanges information via a USB cable, and corresponds to, for example, the USB communication standard. The flash memory 26 is a non-volatile storage device that stores information to be described later. The display unit 27 is a liquid crystal display, for example, and presents image information to the user based on an operation command from the CPU 21. The input unit 28 is, for example, a plurality of buttons, and receives a user input and transmits it to the CPU 21.

  In the following, it is assumed that the wireless communication module 14 of the in-vehicle device 1 and the wireless communication module 24 of the mobile terminal 2 can exchange information through a predetermined connection procedure, for example, pass code matching confirmation. "Establishment of". The fact that the wired communication module 15 of the in-vehicle device 1 and the wired communication module 25 of the portable terminal 2 are connected by a USB cable and can exchange information is called “establishment of wired communication”. In the present embodiment, a wireless communication channel is also referred to as a “first communication channel”, and a wired communication channel is also referred to as a “second communication channel”.

(Functional configuration)
FIG. 2 is a diagram illustrating a functional configuration of the in-vehicle device 1 and the mobile terminal 2. However, information stored in the flash memory 26 is also shown in FIG.

  The in-vehicle device 1 includes a response unit 111, an acquisition unit 112, and an in-vehicle cooperation unit 113 as functions obtained by executing a program stored in the ROM 12. The response unit 111 responds to the inquiry from the mobile terminal 2 with the name of the manufacturer of the in-vehicle device 1 and the model name of the in-vehicle device 1. Note that the operation of the response unit 111, that is, reception of an inquiry and transmission of a response are performed using the wireless communication module 14. The acquisition unit 112 receives a notification from the mobile terminal 2 via the wireless communication module 14. This notification is a notification indicating whether or not an application operable in cooperation with the in-vehicle device 1, that is, a cooperative app described later is installed.

  The in-vehicle cooperation unit 113 starts operation when the wired communication is established, and determines whether to transmit a connection command. The in-vehicle cooperation unit 113 transmits the connection command to the mobile terminal 2 only when it is determined to transmit the connection command. This connection command includes the name of the manufacturer of the in-vehicle device 1, the model name of the in-vehicle device 1, a description, and a related URL. That is, the manufacturer name of the in-vehicle device 1 and the model name of the in-vehicle device 1 output by the response unit 111 and the in-vehicle cooperation unit 113 are the same.

  The portable terminal 2 includes a wireless processing unit 211 and a wired link unit 212 as functions obtained by executing a program stored in the ROM 22. The flash memory 16 of the mobile terminal 2 stores a companion application 261, a cooperative application 262, and an application table 263.

  When wireless communication is established, the wireless processing unit 211 activates a companion application 261 that is a pre-registered application. A method for realizing the operation of the wireless processing unit 211 is not particularly limited, and can be realized as follows, for example. That is, first, a setting file that defines the operation for each application, such as a manifest file, is prepared. Then, the wireless processing unit 211 reads the manifest file of each application, and activates an application having a manifest in which ACL_CONNECT indicating an activation request when establishing wireless communication is described.

  The wired cooperation unit 212 activates the cooperation application 262 when receiving a connection command from the in-vehicle device 1 via the wired communication module 25. However, when the cooperative application 262 is not stored in the flash memory 26, a display that prompts the user to install the cooperative application 262 is displayed on the display unit 27. This display will be described later with reference to the drawings.

  The companion application 261 notifies the in-vehicle device 1 of the installation status of the cooperation application 262 using the wireless communication module 14. The cooperative application 262 is a general term for one or a plurality of applications (hereinafter referred to as “applications”) that operate in cooperation with the in-vehicle cooperation unit 113 of the in-vehicle device 1, and the cooperative application 262 may not be stored in the flash memory 26. . In the present embodiment, when an application is stored in the flash memory 26, the application is also referred to as “installed” in the mobile terminal 2. For example, the cooperation application 262 shares calculation processing with the in-vehicle cooperation unit 113 and displays the calculation results on the display unit 17 of the in-vehicle device 1.

  The application table 263 is a list of applications that can operate in cooperation with the in-vehicle device 1 (hereinafter referred to as “cooperative apps”). In the application table 263, an application capable of cooperative operation is described for each manufacturer and model of the in-vehicle device 1. Within the mobile terminal 2, each application is managed using a package name. The package name is also referred to as an application identifier, and is, for example, a concatenation of a character string indicating a manufacturing company and the name of the application.

(App table 263)
FIG. 3 is a diagram illustrating an example of the application table 263. The application table 263 includes a plurality of records, and each record has fields of a manufacturing company, a model, and a cooperative application package name. The name of the manufacturer of the in-vehicle device 1 is stored in the manufacturing company field, and the model name of the in-vehicle device 1 is stored in the model field. In the cooperative application package name field, the package name of the cooperative application is stored. That is, the in-vehicle device is specified from the values stored in the manufacturing company and model fields, and the app is specified from the values stored in the cooperative application package name field.

(Sequence diagram | With linked application 262)
FIG. 4 is a sequence diagram showing the operation of the cooperation system S. However, since the operation varies greatly depending on whether or not the cooperative application 262 is stored in the flash memory 26 in the mobile terminal 2, the operation when the cooperative application 262 is stored will be described here, and FIG. The operation when 262 is not stored will be described.

  First, when the wireless connection between the in-vehicle device 1 and the mobile terminal 2 is established (S500), the mobile terminal 2 outputs an activation command to the companion application 261 to activate the companion application 261 (S501). The activated companion application 261 acquires information on the in-vehicle device 1, that is, the manufacturer and model name (S502). Next, the companion application 261 determines that the cooperation application 262 corresponding to the in-vehicle device 1 is stored in the flash memory 26 with reference to the application table 263 (S503).

  The processing of S503 will be described using the application table 263 illustrated in FIG. 3. When the manufacturing company acquired in S502 is “AAA” and the model is “AM1”, the package name “aaa.app1” is stored in the flash memory 26. The presence or absence of the cooperative application 262 is determined. Here, since the companion application 261 determines that the cooperation application 262 exists, the companion application 261 transmits a notification that the cooperation application 262 is installed in the in-vehicle device 1 (S504). Receiving this notification, the acquisition unit 112 of the in-vehicle device 1 records the received notification in the RAM 13 (S505).

  Next, when the wired connection between the in-vehicle device 1 and the portable terminal 2 is established (S506), the in-vehicle cooperation unit 113 of the in-vehicle device 1 records the notification that the cooperation application 262 is installed in the RAM 13, so the connection command Is to be output (S507). And the vehicle-mounted apparatus 1 outputs a connection command to the portable terminal 2 (S508). The wired link unit 212 of the mobile terminal 2 that has received this connection command specifies the link app 262 with reference to the app table 263 (S509), and outputs a start command to the specified app (S510). Thereby, the cooperation operation | movement of the cooperation application 262 and the vehicle-mounted apparatus 1 is started (S511).

(Sequence diagram | No linked app)
FIG. 5 is a sequence diagram illustrating the operation of the cooperation system S when the cooperation application 262 is not stored in the flash memory 26. That is, FIG. 5 and FIG. 4 are the same operations up to S502. After S502, the companion application 261 determines that the cooperation application 262 is not installed (S503A), and transmits a notification that the cooperation application 262 is not installed in the in-vehicle device 1 (S504A). Receiving this notification, the acquisition unit 112 of the in-vehicle device 1 records the received notification in the RAM 13 (S505A).

  Next, when the wired connection between the in-vehicle device 1 and the portable terminal 2 is established (S506), the in-vehicle cooperation unit 113 of the in-vehicle device 1 records the notification that the cooperation application 262 is not installed in the RAM 13, so the connection command Is determined not to be output, and the operation is terminated (S507).

(Flowchart of in-vehicle cooperation unit 113)
FIG. 6 is a flowchart showing the operation of the in-vehicle cooperation unit 113 of the in-vehicle device 1. The execution subject of each step described below is the CPU 11 of the in-vehicle device 1. The in-vehicle cooperation unit 113 always executes the process shown in FIG. 6 at predetermined time intervals, for example, every 100 ms.

  First, in S311, the in-vehicle cooperation unit 113 determines whether or not the wired connection has been established. If it is determined that the wired connection has been established, the process proceeds to S312. If it is determined that the wired connection has not been established, FIG. The process ends. In S <b> 312, the in-vehicle cooperation unit 113 determines whether or not a notification that the cooperation application 262 received from the mobile terminal 2 is installed is recorded in the RAM 13. When the cooperative application 262 determines that this is recorded, the process proceeds to S313. When the cooperative application 262 determines that this is not recorded, the process of FIG. 6 ends. In S313, the in-vehicle cooperation unit 113 outputs a connection command to the mobile terminal 2 via a wired connection, and the process of FIG.

  As described above, the in-vehicle cooperation unit 113 outputs a connection command only when a notification that the cooperation application 262 is installed is received from the mobile terminal 2. Moreover, the vehicle-mounted cooperation part 113 does not output a connection command, when the notification that the cooperation application 262 is not installed is received, or when no notification is received.

(Flowchart of wireless processing unit 211)
FIG. 7 is a flowchart showing the operation of the wireless processing unit 211 of the mobile terminal 2. The execution subject of each step described below is the CPU 21 of the mobile terminal 2. The wireless processing unit 211 always executes the processing shown in FIG. 7 at predetermined time intervals, for example, every 100 ms.

  First, in step S411, the wireless processing unit 211 determines whether a wireless connection has been newly established. If the wireless processing unit 211 determines that the wireless connection has been newly established, the wireless processing unit 211 proceeds to step S412 and determines that the wireless connection has not been newly established. Ends the process shown in FIG. In step S412, the wireless processing unit 211 outputs a start command to the companion application 261 and ends the process illustrated in FIG. However, in S412, if there are other applications that should be activated when the wireless connection is established, the wireless processing unit 211 similarly outputs an activation instruction to the application.

(Flow chart of companion application 261)
FIG. 8 is a flowchart showing the operation of the companion application 261 of the mobile terminal 2. The execution subject of each step described below is the CPU 21 of the mobile terminal 2. The companion application 261 is activated when an activation instruction is received from the wireless processing unit 211, and executes the processing illustrated in FIG.

  First, in step S421, the companion application 261 inquires the in-vehicle device 1 and acquires the manufacturer name and model name of the in-vehicle device 1. In addition, the response part 111 of the vehicle-mounted apparatus 1 responds to this inquiry. In subsequent S422, the companion application 261 identifies the linked application 262 corresponding to the manufacturer name and model name acquired in S421 with reference to the application table 263, and searches the flash memory 26 for the identified linked application 262.

  In subsequent S423, the companion application 261 determines whether or not the cooperative application 262 specified in S422 is stored in the flash memory 26, that is, whether or not it is installed. If it is determined that the companion application 261 is installed, the process proceeds to S424. If it is determined that the companion application 261 is not installed, the process proceeds to S425. In S424, the companion application 261 transmits a notification that the cooperation application 262 is installed in the in-vehicle device 1. In S425, the companion application 261 transmits a notification that the cooperation application 262 is not installed in the in-vehicle device 1.

  When S424 or S425 is executed, the companion application 261 ends the process shown in FIG. Note that the communication in S421, S424, and S425 is performed using the wireless communication module 24.

(Flowchart of wired cooperation unit 212)
FIG. 9 is a flowchart showing the operation of the wired link unit 212 of the mobile terminal 2. The execution subject of each step described below is the CPU 21 of the mobile terminal 2. The wired link unit 212 always executes the process shown in FIG. 9 at predetermined time intervals, for example, every 100 ms.

  First, in step S431, the wired cooperation unit 212 determines whether a connection command has been received from the in-vehicle device 1. When determining that the connection command has been received, the wired cooperation unit 212 proceeds to S432, and when determining that the connection command has not been received, the processing illustrated in FIG. 9 ends. In S432, the wired cooperation unit 212 extracts the manufacturer name and the model name from the connection command, specifies the corresponding cooperative application 262 with reference to the application table 263, and identifies the specified cooperative application 262 from the flash memory 26. Search for.

  In subsequent S433, the wired link unit 212 determines whether the link application 262 specified in S432 is stored in the flash memory 26, that is, whether it is installed. The companion application 261 proceeds to S435 when determining that it is installed, and proceeds to S437 when determining that it is not installed.

  In S435, the wired cooperation unit 212 determines whether there is only one cooperation application 262 corresponding to the installed in-vehicle device 1 that is the cooperation application 262 installed. If it is determined that there is only one wired link unit 212, the process proceeds to S436, and if it is determined that a plurality of wired cooperation units 212 are installed, the process proceeds to S441. In S436, the wired cooperation unit 212 activates the cooperation application 262 corresponding to the connected in-vehicle device 1 and ends the process illustrated in FIG.

  In step S <b> 441, the wired cooperation unit 212 determines whether the user's answer is recorded in the flash memory 26. This answer recording is performed in S443 described later, and a negative determination is always made when S441 is executed for the first time. When the wired cooperation unit 212 determines that the user's answer has been recorded, the process proceeds to S444, and when it determines that the user's answer is not recorded, the process proceeds to S442. In S442, the wired cooperation unit 212 inquires which one of the plurality of cooperation applications 262 installed in the user is to be activated. The display unit 27 is used for this inquiry. In subsequent S443, the wired link unit 212 acquires the user's answer using the input unit 28, records it in the flash memory 26, and proceeds to S444.

  In S444, the wired cooperation unit 212 activates the cooperation application 262 based on the user's answer recorded in the flash memory 26, and ends the processing illustrated in FIG. In S437, which is executed when a negative determination is made in S433, the wired cooperation unit 212 outputs a screen display prompting installation using the information included in the received connection command to the display unit 27, and ends the processing illustrated in FIG. . In S437, of the information included in the connection command, the description of the cooperation function and the associated URL are used.

(Screen display prompting installation)
FIG. 10 is a diagram illustrating an example of a screen display prompting the installation displayed in S437 of FIG. The upper half of FIG. 10, that is, the character string described in the upper part of the URL starting with “http ··” is “description”, and the URL is “related URL”. A button for opening the URL with a Web browser is arranged below the URL. The screen display for prompting installation as shown in FIG. 10 is useful for function cooperation with the connected device, but if the user is driving the vehicle 5, the user should be distracted from driving. It is not desirable.

(Sequence diagram | Comparative example)
FIG. 11 is a sequence diagram in the comparative example. In this comparative example, the mobile terminal 2 does not include the companion application 261, and the in-vehicle device 1 does not include the response unit 111 and the acquisition unit 112. In this comparative example, the in-vehicle cooperation unit 113 of the in-vehicle device 1 outputs a connection command as soon as a wired connection is established. Further, in this comparative example, the operation will be described assuming that the cooperative application 262 is not installed in the mobile terminal 2.

  First, when a wired connection is established (S591), the in-vehicle cooperation unit 113 of the in-vehicle device 1 outputs a connection command (S592). The wired cooperation unit 212 of the mobile terminal 2 specifies the corresponding cooperative application 262 using the manufacturer name and model name included in the connection command and searches the flash memory 26, but determines that the cooperative application is not installed ( S593). Therefore, the wired link unit 212 of the portable terminal 2 outputs a display command (S594), and displays a screen for prompting installation on the display unit 27 (S595).

According to the first embodiment described above, the following operational effects are obtained.
(1) The in-vehicle device 1 can communicate with the mobile terminal 2 using wireless communication and wired communication. When the in-vehicle device 1 detects the establishment of the wired communication and the acquisition unit 112 that receives the notification that the cooperation application 262 corresponding to the in-vehicle device 1 connected from the mobile terminal 2 using the wireless communication is installed. Then, it is determined whether or not a notification that the corresponding cooperative application 262 is installed is received (S312 in FIG. 6), and when it is determined that a notification that it is installed is received (S312 in FIG. 6). YES), a connection command is transmitted using wired communication, and when it is determined that the installation completion notification has not been received, the in-vehicle cooperation unit 113 that does not transmit the connection command is provided.

  That is, the in-vehicle device 1 does not transmit a connection command when the cooperation application 262 corresponding to the in-vehicle device 1 is not installed in the connected mobile terminal 2. Therefore, operations other than the operation of the cooperative application 262 by the mobile terminal 2, for example, the image display operation as shown in FIG. 10 can be suppressed, and the user's attention can be prevented from deviating from driving. In other words, the in-vehicle device 1 can improve safety when used with the mobile terminal 2.

  When the cooperation application 262 corresponding to the connected in-vehicle device 1 is not installed in the mobile terminal 2, the cooperation function cannot be used at least immediately. In such a case, installation of the cooperation application 262 is promoted by performing the screen display shown in FIG. 10 and the cooperation function is validated, which generally leads to improvement of user convenience. However, safety should be given priority over convenience in the vehicle, and it is not desirable to distract the user's attention.

  Note that the screen display shown in FIG. 10 can also be suppressed by changing the operation of the wired link unit 212 of the mobile terminal 2, but the behavior when the mobile terminal 2 is connected to another device is also changed. Therefore, it is not preferable.

(2) The cooperation method of the vehicle-mounted device 1 and the portable terminal 2 that can communicate using the wireless communication path and the wired communication path is as follows. That is, when the portable terminal 2 transmits a notification indicating whether or not the cooperation application 262 is installed using the wireless communication path to the in-vehicle device 1 and when the in-vehicle device 1 detects the establishment of the wired communication path, the mobile terminal 2 receives the notification. Based on the notification, it is determined whether or not the cooperation application 262 is installed in the mobile terminal 2, and when it is determined that the cooperation application 262 is installed, a connection command is transmitted using the wireless communication path, and the cooperation application 262 is installed. If it is determined that there is no connection command, the connection command is not transmitted. Therefore, when the cooperation application 262 corresponding to the in-vehicle device 1 is not installed in the mobile terminal 2, the in-vehicle device 1 does not transmit a connection command, so the mobile terminal 2 performs an operation unintended by the user, and the user's attention starts from driving. This can be prevented.

(Modification 1)
In the first embodiment described above, the wireless communication module 14 and the wireless communication module 24 use Bluetooth or IEEE 802.11 that requires a certain procedure before data transmission. However, the wireless communication module 14 and the wireless communication module 24 may use a communication standard that does not require a procedure before data transmission, for example, Bluetooth Low Energy (registered trademark) (hereinafter referred to as “BLE”).

  In this case, as a first method, the companion application 261 may transmit a signal indicating that information is requested every predetermined time period, for example, every 10 seconds, 1 minute, or 5 minutes. And when the vehicle-mounted apparatus 1 exists in the range which this signal reaches, you may perform the operation | movement similar to 1st Embodiment by transmitting a manufacture company name etc. to the portable terminal 2. FIG. That is, in the first method, the process of S502 of FIG. 4 is repeatedly attempted from the mobile terminal 2 side.

  As a second method, instead of the companion application 261 transmitting a signal at a predetermined time cycle, the in-vehicle device 1 may transmit a manufacturing company name or the like to the surroundings at a predetermined time cycle. In this case, when the mobile terminal 2 receives the manufacturer name or the like from the in-vehicle device 1, the companion application 261 is activated to perform processing using the received information. That is, in the second method, the process of S502 of FIG. 4 is repeatedly attempted from the in-vehicle device 1 side.

(Modification 2)
An introduction assistance application that assists the installation of the cooperation application 262 may be installed in the mobile terminal 2. This introduction assistance application may list all the cooperative applications 262 that can be used in the vehicle-mounted device 1 connected in the past, or may list only those that have a large number of downloads. Further, only those that are not installed in the mobile terminal 2 may be listed, or the cooperation applications 262 that have been installed may be listed after being distinguished by whether or not they are installed.

(Modification 3)
In the first embodiment described above, the wired communication module 15 is assumed to exchange information via a wire, that is, some cable for convenience of explanation. However, the wired communication module 15 may exchange information by wireless communication. In this case, the name of the wired communication module 15 may be changed to, for example, the “second wireless communication module” 15 in order to resolve the name conflict.

-Second embodiment-
A second embodiment of the linkage system S will be described with reference to FIGS. In the following description, the same components as those in the first embodiment are denoted by the same reference numerals, and different points will be mainly described. Points that are not particularly described are the same as those in the first embodiment. The present embodiment is different from the first embodiment mainly in that the connection command transmitted from the in-vehicle device 1 to the mobile terminal 2 includes information for specifying an application to be activated.

(Differences from the first embodiment)
In the first embodiment described above, the connection command does not include information for specifying the cooperative application 262 to be activated. Therefore, when there are a plurality of cooperative applications 262 that can be activated in the mobile terminal 2, the cooperative application 262 that is activated is identified by the operation of the wired cooperation unit 212, specifically, the operations of S441 to S444 in FIG. However, in the present embodiment, the companion application 261 identifies the cooperation application 262 to be activated in advance, and transmits the application identifier of the cooperation application 262 to be activated to the in-vehicle device 1.

  The in-vehicle device 1 creates and transmits a connection command using the received application identifier as a model name. The wired cooperation unit 212 of the mobile terminal 2 activates the cooperation application 262 that is uniquely specified by the combination of the manufacturer name and the model name included in the connection command. In the present embodiment, the application table 263 referred to by the cooperative application 262 is the same as that in the first embodiment. However, the application table referred to by the wired link unit 212 is different from that of the first embodiment, and is referred to as an “OS application table 263A” for distinction. In the OS application table 263A, the mobile application package name is uniquely specified by the manufacturer and model.

(OS application table 263A)
FIG. 12 is a diagram illustrating an example of the OS application table 263A stored in the mobile terminal 2 according to the second embodiment. As shown in FIG. 12, in the OS application table 263A, a combination of a manufacturer and a model always corresponds to one linked application package name. In the example shown in FIG. 12, the model name and the application identifier are the same.

(Flow chart of companion application 261)
FIG. 13 is a flowchart showing the operation of the companion application 261 in the second embodiment. Since the processing up to S423 is the same as that of the first embodiment, the description thereof is omitted. The companion application 261 proceeds to S451 if an affirmative determination is made in S423, and proceeds to S453 if a negative determination is made.

  In S451, the companion application 261 determines whether there is only one cooperation application 262 corresponding to the connected in-vehicle device 1 that is the cooperation application 262 installed. If it is determined that there is only one companion application 261, the process proceeds to S452, and if it is determined that a plurality of companion applications 261 are installed, the process proceeds to S454. In S452, the companion application 261 transmits the app identifier of the cooperative app 262 corresponding to the connected in-vehicle device 1 as a notification to the in-vehicle device 1 via the wireless communication module 24, and ends the process illustrated in FIG.

  In S454, the companion application 261 determines whether the user's answer is recorded in the flash memory 26 or not. The recording of the answer is performed in S456 described later, and a negative determination is always made when S454 is executed for the first time. If the companion application 261 determines that the user's answer has been recorded, the process proceeds to S457. If the companion application 261 determines that the user's answer has not been recorded, the process proceeds to S455. In S455, the companion application 261 inquires which one of the plurality of cooperative applications 262 installed in the user is to be activated. The display unit 27 is used for this inquiry. In subsequent S456, the companion application 261 acquires the user's answer using the input unit 28, records it in the flash memory 26, and proceeds to S457.

  In S457, the companion application 261 specifies the cooperation application 262 based on the user's answer recorded in the flash memory 26, and transmits the application identifier of the specified cooperation application 262 to the in-vehicle device 1 via the wireless communication module 24. The process shown in FIG. In S453, which is executed when a negative determination is made in S423, the companion application 261 transmits zero indicating that the corresponding application is not installed as a notification to the in-vehicle device 1 via the wireless communication module 24, and is shown in FIG. The process ends.

(Flowchart of in-vehicle cooperation unit 113)
FIG. 14 is a flowchart showing the operation of the in-vehicle cooperation unit 113 in the second embodiment. In S <b> 312 </ b> A that is executed when an affirmative determination is made in S <b> 311, the in-vehicle cooperation unit 113 determines whether a notification other than zero has been received from the mobile terminal 2. The in-vehicle cooperation unit 113 proceeds to S313A when determining that a notification other than zero has been received, and ends the process illustrated in FIG. 14 when determining that zero has been received.

  In S313A, the in-vehicle cooperation unit 113 outputs a connection command through a wired connection and ends the process illustrated in FIG. However, as described above, the connection command in the second embodiment includes an application identifier for designating the cooperative application that the mobile terminal 2 starts in addition to the connection command in the first embodiment. The application identifier included in this connection command is output by the companion application 261 of the mobile terminal 2.

(Flowchart of in-vehicle cooperation unit 113)
FIG. 15 is a flowchart illustrating the operation of the wired cooperation unit 212 according to the second embodiment. In S431, the wired link unit 212 determines whether a connection command has been received from the in-vehicle device 1. The wired cooperation unit 212 proceeds to S432A when determining that the connection command has been received, and ends the process illustrated in FIG. 15 when determining that the connection command has not been received. In S432A, the wired cooperation unit 212 refers to the OS application table 263A, activates the cooperation application 262 specified by the manufacturer and the model name, and ends the processing illustrated in FIG.

According to the second embodiment described above, the following operational effects can be obtained.
(3) The connection command includes information for specifying the cooperative application 262 to be activated on the mobile terminal 2. Therefore, when a plurality of cooperation applications 262 are installed in the mobile terminal 2, the specific cooperation application 262 can be activated in the mobile terminal 2 without making an inquiry to the user. That is, when the mobile terminal 2 can start a plurality of cooperative applications 262, the mobile terminal 2 is prevented from making an inquiry to the user and distracting the user's attention.

(4) The notification transmitted by the mobile terminal 2 includes an application identifier that identifies the cooperative application 262. The in-vehicle cooperation unit 113 creates a connection command including the received application identifier as it is. Since the companion application 261 of the portable terminal 2 determines the cooperation application 262 to be activated in advance and transmits it to the in-vehicle device 1 as a notification, the processing of the in-vehicle device 1 is simple.

(Modification 1 of the second embodiment)
In the second embodiment described above, the companion application 261 transmits the application identifier to the in-vehicle device 1. However, the companion application 261 may transmit the code corresponding to the predetermined application identifier to the in-vehicle device 1 without transmitting the application identifier itself. In this case, the in-vehicle device 1 and the portable terminal 2 have a code correspondence table that is a correspondence table between application identifiers and codes in advance, identify the application identifier with reference to the code correspondence table, and perform the second embodiment. Information similar to the form is output to the mobile terminal 2.

(Code correspondence table 264)
FIG. 16 is a diagram illustrating an example of the code correspondence table 264 stored in the flash memory 16 of the in-vehicle device 1 and the flash memory 26 of the mobile terminal 2 in the first modification of the second embodiment. The code correspondence table 264 shows correspondence between codes that are integers of “1” or more and application identifiers. The reason why the code is “1” or more is that zero is used to indicate that the cooperative application 262 corresponding to the connected in-vehicle device 1 is not installed.

(Operation of the in-vehicle cooperation unit 113)
FIG. 17 is a flowchart showing the operation of the in-vehicle cooperation unit 113 in Modification 1 of the second embodiment. Here, differences from the operation of the in-vehicle cooperation unit 113 in the second embodiment shown in FIG. 13 will be described. Since the processing up to S312A is the same as in the second embodiment, the description thereof is omitted. The in-vehicle cooperation unit 113 proceeds to S312B if an affirmative determination is made in S312A, and ends the process shown in FIG. 17 if a negative determination is made in S312A.

  In S <b> 312 </ b> B, the in-vehicle cooperation unit 113 identifies the application identifier corresponding to the code received from the mobile terminal 2 with reference to the code correspondence table 264. For example, when the code “2” is received from the mobile terminal, “aaa.app2” is specified as the application identifier. In subsequent S313A, the in-vehicle cooperation unit 113 creates a connection command using the application identifier specified in S312B, outputs the connection command to the mobile terminal 2, and ends the processing illustrated in FIG.

(Modification 2 of the second embodiment)
In the second embodiment, the application identifier itself is used as the model name in the OS application table 263. However, the application identifier itself is not limited as long as it is an identifiable code (hereinafter referred to as “alternative code”). However, when using an alternative code instead of an application identifier as a model name, a correspondence table between the alternative code and the application identifier is created in advance and stored in an area that can be referred to by the companion application 261. Then, in S452 and S457 of FIG. 13, the companion application 261 specifies an alternative code by referring to the above-described correspondence table instead of the application identifier itself, and transmits the alternative code.

-Third embodiment-
With reference to FIGS. 18-20, 3rd Embodiment of the vehicle-mounted apparatus 1 which concerns on this invention is described. In the following description, the same components as those in the first embodiment are denoted by the same reference numerals, and different points will be mainly described. Points that are not particularly described are the same as those in the first embodiment. The present embodiment is different from the second embodiment mainly in that when the mobile terminal 2 has a plurality of cooperative applications 262 that can be activated, the cooperative application 262 that is activated by the processing of the in-vehicle device 1 is determined.

(Differences from the second embodiment)
In the present embodiment, the companion application 261 of the mobile terminal 2 has the application identifiers or codes of the plurality of cooperative apps 262 in the in-vehicle device 1 when there are a plurality of cooperative apps 262 corresponding to the connected in-vehicle device 1. Send. When the in-vehicle cooperation unit 113 of the in-vehicle device 1 receives a plurality of application identifiers or codes, the in-vehicle cooperation unit 113 inquires the user about which cooperation application 262 is to be activated, generates a connection command based on a response to the inquiry, and generates a mobile terminal. 2 to send. Note that the connection command output by the in-vehicle device 1 in the third embodiment is the same as that in the second embodiment. The operation of the wired link unit 212 of the mobile terminal 2 is the same as that of the second embodiment.

(Functional configuration)
FIG. 18 is a functional configuration diagram of the cooperation system S according to the third embodiment. The difference from the first embodiment is that the in-vehicle device 1 further includes an inquiry unit 114 and an answer acquisition unit 115. The inquiry unit 114 uses the display unit 17 to inquire which of the cooperative applications 262 is to be activated by the user. The response acquisition unit 115 acquires the response of the inquiry made by the inquiry unit 114 using the input unit 18.

(Flow chart of companion application 261)
FIG. 19 is a flowchart showing the operation of the companion application 261 in the third embodiment. Since the operation up to S423 is the same as that of the second embodiment, the description thereof is omitted. The companion application 261 proceeds to S461 when making an affirmative determination in S423, and proceeds to S453 when making a negative determination, and transmits zero to the in-vehicle device 1 as in the second embodiment. In S451, the companion application 261 transmits the application identifiers of all the installed cooperative applications 262 corresponding to the connected in-vehicle device 1 as notifications to the in-vehicle device 1, and ends the process illustrated in FIG. For example, when there are a plurality of installed linked apps 262 corresponding to the connected in-vehicle device 1, the application identifiers of all the linked apps 262 are transmitted to the in-vehicle device 1.

(Flowchart of in-vehicle cooperation unit 113)
FIG. 20 is a flowchart showing the operation of the in-vehicle cooperation unit 113 in the third embodiment. Since the operations up to S312A are the same as those in the second embodiment, a description thereof will be omitted. In S312A, the in-vehicle cooperation unit 113 proceeds to S321 if an affirmative determination is made, and ends the process illustrated in FIG. 20 if a negative determination is made. In S321, the in-vehicle cooperation unit 113 determines whether there is only one application identifier included in the notification received from the mobile terminal 2. If it is determined that there is only one in-vehicle cooperation unit 113, the process proceeds to S322. If it is determined that two or more in-vehicle cooperation units 113 are included, the process proceeds to S323. In S322, the in-vehicle cooperation unit 113 generates a connection command including the application identifier included in the notification as a model name, transmits the connection command to the mobile terminal 2, and ends the process illustrated in FIG.

  In S323, the in-vehicle cooperation unit 113 determines whether the user's answer is recorded in the flash memory 16. The recording of the answer is performed in S325 described later, and a negative determination is always made when S323 is executed for the first time. The in-vehicle cooperation unit 113 proceeds to S326 when determining that the user's answer has been recorded, and proceeds to S324 when determining that the user's answer is not recorded. In S324, the in-vehicle cooperation unit 113 uses the inquiry unit 114 to inquire which of the plurality of cooperation applications 262 is activated to the user. For this inquiry, the display unit 17 is used. For example, the display unit 17 displays a plurality of received application identifiers. In subsequent S325, the in-vehicle cooperation unit 113 acquires the user's answer using the input unit 18, records it in the flash memory 16, and proceeds to S326.

  In S326, the in-vehicle cooperation unit 113 generates a connection command including the application identifier of the cooperation application 262 specified from the user's answer recorded in the flash memory 16 as a model name. And the vehicle-mounted cooperation part 113 transmits the produced | generated connection command to the portable terminal 2 via the wired communication module 15, and complete | finishes the process shown in FIG.

According to the third embodiment described above, the following operational effects can be obtained.
(5) The notification includes application identifiers of a plurality of cooperative applications 262 installed in the mobile terminal 2. The in-vehicle device 1 includes an inquiry unit 114 that inquires which one of the cooperative applications 262 is activated by the user, and an answer acquisition unit 115 that acquires an answer to the inquiry. The in-vehicle cooperation unit 113 creates a connection command based on the answer acquired by the answer acquisition unit 115. Therefore, an inquiry to the user of the cooperation application 262 that is activated using the in-vehicle device 1 and an activation instruction to the portable terminal 2 based on the user's answer can be performed.

(Modification of the third embodiment)
The in-vehicle device 1 and the mobile terminal 2 may include the code correspondence table 264 illustrated in FIG. 16, and an application identifier included in a notification output by the companion application 261 may be used as a code. In this case, the inquiry unit 114 of the in-vehicle device 1 provides the user with an application identifier as an option with reference to the code correspondence table 264 when making an inquiry to the user. In this case, the in-vehicle cooperation unit 113 may include an application identifier or a code in the connection command. When a code is included in the connection command, the wired cooperation unit 212 determines the cooperation application 262 to be activated with reference to the code correspondence table 264.

  The above-described embodiments and modifications may be combined. Although various embodiments and modifications have been described above, the present invention is not limited to these contents. Other embodiments conceivable within the scope of the technical idea of the present invention are also included in the scope of the present invention.

DESCRIPTION OF SYMBOLS 1 ... In-vehicle apparatus 2 ... Portable terminal 111 ... Response part 112 ... Acquisition part 113 ... In-vehicle cooperation part 114 ... Inquiry part 115 ... Answer acquisition part 211 ... Wireless processing part 212 ... Wired cooperation part 261 ... Companion application 262 ... Cooperation application 263 ... Application table 264 ... Code correspondence table

Claims (5)

An in-vehicle device capable of communicating with a mobile terminal using each of the first communication path and the second communication path,
An acquisition unit that receives an installed notification that a cooperation application that operates in cooperation with the in-vehicle device is installed in the portable terminal from the portable terminal using the first communication path;
When the establishment of the second communication path is detected, it is determined whether or not the installed notification has been received, and when it is determined that the installed notification has been received, cooperation between the in-vehicle device and the portable terminal is started. An in-vehicle device comprising: an in-vehicle cooperation unit that transmits a signal using the second communication path and does not transmit a signal for starting the cooperation when it is determined that the installation notification has not been received. The in-vehicle device according to claim 1,
The in-vehicle device that includes information for specifying the cooperation application to be activated by the mobile terminal in the signal for starting the cooperation. The in-vehicle device according to claim 2,
The installed notification includes application specifying information for specifying the cooperation application,
The in-vehicle cooperation unit is an in-vehicle device that creates a signal for starting the cooperation based on the application specifying information. The in-vehicle device according to claim 2,
The installed notification includes information on a plurality of cooperation applications installed on the mobile terminal,
An inquiry unit that inquires which of the plurality of cooperation applications is to be activated to the user;
An answer obtaining unit for obtaining an answer to the inquiry,
The in-vehicle cooperation unit is an in-vehicle device that creates a signal for starting the cooperation based on the answer acquired by the answer acquisition unit. A method of linking an in-vehicle device and a mobile terminal that can communicate using each of a first communication path and a second communication path,
The mobile terminal transmits a notification indicating whether or not a cooperation application operating in cooperation with the in-vehicle device is installed in the mobile terminal to the in-vehicle device using the first communication path;
When the in-vehicle device detects the establishment of the second communication path, it determines whether or not the cooperation application is installed in the mobile terminal based on the received notification, and determines that the cooperation application is installed. A signal for starting cooperation between the in-vehicle device and the portable terminal when using the second communication path and determining that the cooperation application is not installed. A method of cooperation including not transmitting.

Images