JP2013126802A - Method for downloading application software to on-board device, and the on-board device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a method for downloading application software which prevents the occurrence of a useless "down load of application software" to an on-board device from a center.SOLUTION: In the download method, when the on-board device 11 is used by a user A in a vehicle 10, the on-board device 11 transfers an authentication request together with the "user ID of the user A, a password inputted by the user A, a model number of the on-board device 11 and an identification number of the vehicle 10" to the center 40. Upon the confirmation of a membership of the user A and the validity of the password, the center 40 extracts "application software that is under a license agreement with the user A, operable on the on-board device 11 and suitable to the sort of the vehicle 10" from a data table on the basis of "the user ID of the user A, the model number of the on-board device 11 and the identification number of the vehicle 10", and transmits an application software list representing the result to the on-board device 11.

Description

  The present invention relates to a method for downloading an application to an in-vehicle device mounted on a vehicle and configured to be communicable with a center, and the in-vehicle device.

  A vehicle (automobile) in recent years is equipped with an in-vehicle device that implements a number of functions such as a navigation system, a music playback system, a video playback system, and an e-mail system by applications. Some in-vehicle devices are fixed to the vehicle body, or some are portable and can be carried into the vehicle by the user.

  On the other hand, a user may drive a family or acquaintance's vehicle or rent a vehicle through a rental service. Furthermore, recently, an attempt of car sharing that promotes environmental protection by using one vehicle by a plurality of users has been started. As a result, cases where a plurality of users use an in-vehicle device fixed to the same vehicle or a portable in-vehicle device are increasing.

  On the other hand, the types of applications that can be used in in-vehicle devices are rapidly increasing. Furthermore, the user may make a use contract with the application provider and download the application to the in-vehicle device for use.

  By the way, when a plurality of users use an in-vehicle device fixed to the same vehicle or a portable in-vehicle device, it is necessary to restrict the use of an application for which a contract (a license agreement) is not concluded. One of the prior arts is that information related to a contract that a user has entered into with an administrator is transmitted from the center to the vehicle-mounted device, and the same information is transmitted based on the transmitted information when a specific user uses the vehicle-mounted device. The in-vehicle device is configured so that only an application contracted by a specific user can be used (see, for example, Patent Document 1).

JP 2004-238941 A

  However, when an application can be used in the in-vehicle device by downloading the application from the center to the in-vehicle device, even if the application has a contract with the user, the application cannot be operated on the in-vehicle device that the user is actually trying to use. There are also applications. In this case, communication related to downloading of the application is useless, and there is a problem that an unnecessary communication fee is generated in some cases.

  The present invention has been made to address the above problems. That is, an object of the present invention is to provide an application download method and an in-vehicle device that do not cause useless “downloading of applications” from the center to the in-vehicle device.

  The application download method of the present invention (hereinafter also simply referred to as “the present download method”) downloads an application from the center to the vehicle-mounted device using communication between the vehicle-mounted device and the center.

The download method further includes first to third steps.
The first step is a step of transmitting user-related information including at least user-related information for identifying a user who uses the vehicle-mounted device from the vehicle-mounted device to the center and vehicle-related information related to the vehicle-mounted device.
The second step is a step executed by the computer of the center, and the application contracted by the user based on the user related information and the in-vehicle device related information included in the transmitted user side information And obtaining an application operable on the vehicle-mounted device.
The third step is a step of downloading the acquired application from the center to the in-vehicle device.

  According to this, when the user uses any on-vehicle device, only “an application that the user has a contract and can operate on the on-vehicle device” is downloaded to the on-vehicle device. Therefore, applications that are not contracted by the user and applications that cannot be operated in the in-vehicle device that the user intends to use are not downloaded. As a result, it is possible to avoid occurrence of communication related to useless download.

in this case,
The first step is a step of further including vehicle information related to a vehicle on which the in-vehicle device is mounted in the user side information,
The second step includes a step of narrowing down the acquired application by excluding applications that are not suitable for the vehicle from the acquired applications based on the vehicle information included in the user side information. Yes,
The third step is preferably a step of downloading the narrowed application from the center to the in-vehicle device.

  According to this, an application inappropriate for the vehicle on which the vehicle-mounted device to be used is mounted is not downloaded to the vehicle-mounted device. For example, when an application is an application dedicated to a normal gasoline engine vehicle, if the vehicle on which the vehicle-mounted device to be used is mounted is a hybrid vehicle, it is useless to download the application. Therefore, according to the said structure, the application which is unsuitable for a vehicle is not downloaded vainly. Therefore, it is possible to avoid occurrence of useless communication.

Furthermore, the third step includes
Before executing the download, check whether there is an application already held in association with the user by the in-vehicle device among the acquired applications, and download the already held application. It is preferred to include exclusion from the application.

  According to this, it is possible to avoid downloading an application already downloaded or installed in the in-vehicle device as an application of the user who intends to use the in-vehicle device. As a result, it is possible to avoid occurrence of communication related to useless download.

  The present invention naturally extends to “an in-vehicle device, a center, and a system including the in-vehicle device and the center” that realize such a download method. Other objects, other features, and attendant advantages of the present invention will be readily understood from the description of each embodiment of the present invention described with reference to the following drawings.

1 is a schematic diagram of a system using a download method according to an embodiment of the present invention. It is a block diagram of the vehicle equipment shown in FIG. It is a block diagram of the vehicle related information management machine shown in FIG. It is a block diagram of the center shown in FIG. It is the flowchart which showed the routine which CPU of the vehicle equipment shown in FIG. 2 performs. FIG. 5 is a flowchart showing a routine executed by the computer at the center shown in FIG. 4. FIG. FIG. 5 is an example of an application list created by a computer at the center shown in FIG. 4. FIG. FIG. 5 is an example of an application list created by a computer at the center shown in FIG. 4. FIG. FIG. 5 is an example of an application list created by a computer at the center shown in FIG. 4. FIG. FIG. 5 is an example of an application list created by a computer at the center shown in FIG. 4. FIG. It is the flowchart which showed the routine which CPU of the vehicle equipment shown in FIG. 2 performs. FIG. 5 is a flowchart showing a routine executed by the computer at the center shown in FIG. 4. FIG. 5 is a flowchart showing a routine executed by the CPU of the in-vehicle device shown in FIG. 2 and the computer at the center shown in FIG.

  Hereinafter, a method for downloading an application according to an embodiment of the present invention will be described. This download method is implemented by a system including a vehicle, an in-vehicle device, and a center (a center including an application server and can also be referred to as an information providing center and an information management center).

<System configuration>
As shown in FIG. 1, the download method according to the embodiment of the present invention is performed between a plurality of vehicles (three vehicles in the example shown in FIG. 1) 10, 20, 30 and the center 40. Implemented using communication. However, there are no restrictions on the number of in-vehicle devices, the number of vehicles, and the number of users.

The vehicle 10 includes an in-vehicle device 11 and a vehicle-related information management device 12. The vehicle 10 is a hybrid vehicle in this example, and is equipped with an electric motor and a gasoline engine as drive sources. The in-vehicle device 11 and the vehicle-related information management device 12 are fixed to the main body of the vehicle 10.
The vehicle 20 includes an in-vehicle device 21 and a vehicle-related information management device 22. The vehicle 20 is a gasoline engine vehicle in this example, and is mounted with a gasoline engine as a drive source. The in-vehicle device 21 and the vehicle-related information management device 22 are fixed to the main body of the vehicle 20.
The vehicle 30 includes an in-vehicle device 31 and a vehicle-related information management device 32. The vehicle 30 is an electric vehicle in this example and is equipped with an electric motor as a drive source. The in-vehicle device 31 and the vehicle-related information management device 32 are fixed to the main body of the vehicle 30.

  However, each of the in-vehicle device 11, the in-vehicle device 21, and the in-vehicle device 31 may be configured to be portable, and even if one of these in-vehicle devices is brought into the vehicle on which the user A is boarded and installed in the vehicle. Good. Therefore, for example, as indicated by a two-dot chain line arrow in FIG. 1, the user A takes the vehicle-mounted device 11 out of the vehicle 10 and uses the vehicle-mounted device 11 as “the vehicle-mounted device 31 of the vehicle 30 to be boarded”. You can also

  The in-vehicle device 11, the in-vehicle device 21, and the in-vehicle device 31 have substantially the same configuration. Therefore, the configuration of the in-vehicle device 11 will be described below. However, the in-vehicle device 11, the in-vehicle device 21, and the in-vehicle device 31 are different from each other in performance and / or function. For example, the in-vehicle device 11 can receive and reproduce a terrestrial digital video broadcast for a mobile terminal, but the other in-vehicle devices 21 and 31 do not have such a function. Or although the vehicle equipment 11 and the vehicle equipment 21 respond | correspond to the newest version of a specific application, the vehicle equipment 31 respond | corresponds only to the old version of the specific application.

  As shown in FIG. 2, the in-vehicle device 11 has a microcomputer 111 as a main configuration. The microcomputer 111 includes a CPU 11a, a ROM 11b, a RAM 11c, an input / output interface 11d and the like connected to each other by a bus. The CPU 11a executes a program (routine), which will be described later, stored in the ROM 11b while utilizing the data storage function of the RAM 11c. The ROM 11b stores “information for identifying the type of the vehicle-mounted device 11 including the model number (vehicle-mounted device model number) of the vehicle-mounted device 11, that is, vehicle-related information”.

  The in-vehicle device 11 includes a GPS device 112, a terrestrial communication device 113, a display device 114, a sound generator 115, a short-range communication device 116, and an external memory 117. These devices are connected to the input / output interface 11d and configured to exchange signals with the microcomputer 111.

The GPS device 112 receives a GPS signal from a GPS satellite (not shown), and generates a signal for specifying a position where the vehicle 10 exists based on the GPS signal.
The terrestrial communication device 113 is configured to be capable of wireless communication with the center 40 shown in FIG.
The display device 114 includes a display (not shown) and displays necessary information in the form of a map, a still image, a moving image, character information, and the like in accordance with an instruction signal from the microcomputer 111. Further, the display device 114 also has a data input / output function. That is, the display device 114 is also a touch panel.

The sound producing device 115 includes a speaker (not shown) and generates necessary sounds or sounds according to instructions from the microcomputer 111.
The short-range communication device 116 is configured to be able to exchange information with the vehicle-related information management machine 12 illustrated in FIG. 1 by wired communication or wireless communication. The short-range communication device 116 is configured to support general communication standards so that information can be exchanged with vehicle-related information management machines (for example, the vehicle-related information management machines 22 and 32) of other vehicles. Has been.

  The external memory 117 is a storage device such as a hard disk. The external memory 117 specifies the user of the application program (including data for installation) downloaded for use in the vehicle-mounted device 11. It is stored in association with the information to be processed. Furthermore, the external memory 117 may store the above-described in-vehicle device related information. The external memory 117 supplies these pieces of information to the microcomputer 111 and stores necessary information according to instructions from the microcomputer 111.

  The vehicle-related information manager 12, the vehicle-related information manager 22, and the vehicle-related information manager 32 have substantially the same configuration. Therefore, the configuration of the vehicle-related information management machine 12 will be described below with reference to FIG.

The vehicle-related information management machine 12 includes a nonvolatile memory 121, a short-range communication device 122, and an electronic control device 123.
The nonvolatile memory 121 stores information (hereinafter referred to as “vehicle-related information”) that identifies the vehicle 10 such as a vehicle body number of the vehicle 10.
The near field communication device 122 is configured to be able to exchange information with the vehicle-mounted device 11 (the near field communication device 116) by wired communication or wireless communication. The short-range communication device 122 is configured to correspond to a general communication standard so that information can be exchanged with other in-vehicle devices (for example, the in-vehicle devices 21 and 31).
The electronic control device 123 is an electronic control circuit mainly composed of a microcomputer, for example, and is connected to the nonvolatile memory 121 and the short-range communication device 122. When the electronic control device 123 receives a signal for requesting vehicle-related information from the vehicle-mounted device 11 through the short-range communication device 122, the electronic control device 123 reads the vehicle-related information from the non-volatile memory 121 and transmits the vehicle-related information via the short-range communication device 122. Thus, the information is transmitted to the short-range communication device 116 of the in-vehicle device 11.

  As shown in FIG. 4, the center 40 includes a computer 41, an input / output device 42, and an external storage device (database) 43.

  The computer 41 is a server that includes well-known components for configuring the computer, in addition to the CPU 41a and the terrestrial communication device 41b. The terrestrial communication device 41b is configured to be able to communicate with the in-vehicle device of each vehicle via the terrestrial communication device of the in-vehicle device of each vehicle (the in-vehicle devices 11, 21, and 31 in the example shown in FIG. 1). . The CPU 41a can use information acquired by this communication. The input / output device includes a keyboard, a display device, and the like, and can input given data and display the given data.

  The external storage device 43 is a known information storage device that holds a large amount of data so that it can be read and written. The external storage device 43 stores a user information data table DB1 storing information related to users (user information), a contract information data table DB2 storing information related to contracts (contract information), and information related to in-vehicle devices (in-vehicle device information). In-vehicle device information data table DB3, application information data table DB4 storing information related to applications (application information), vehicle information data table DB5 storing information related to vehicles (vehicle information), and application data storing data of the application main body A table DB 6 and the like are provided, and various information is stored while being associated with each other.

The user information data table DB1 stores a user ID (user authentication number), a password, a user operation (setting) history of an application, and the like while being associated with each other.
The contract information data table DB2 stores each user (each user ID), an application with which each user has a contract (use license agreement), and the like in association with each other.
The in-vehicle device information data table DB3 stores a model number of each in-vehicle device, detailed information of the in-vehicle device such as the type / version of each in-vehicle device, and the like while being associated with each other.
The application information data table DB4 stores each application, the type and version of the in-vehicle device on which each application can operate, the vehicle type to which each application is compatible, and the like while being associated with each other.
The vehicle information data table DB5 stores the vehicle number and the vehicle type (information specifying the vehicle characteristics / specifications such as the drive type and body shape of the vehicle) while associating with each other.
The application data table DB 6 stores program data of applications to be downloaded in a predetermined format.

<Operation>
Next, an application download method implemented in the system configured as described above will be described.

  When the user A gets on the vehicle 10 and changes an accessory switch (start switch) (not shown) of the vehicle 10 to the on state, the CPU 11a of the vehicle-mounted device 11 proceeds from step 500 to step 510 of the routine shown in FIG. A “user authentication data input screen” is displayed on the display device 114. The user authentication data input screen includes a blank for entering a user ID and a blank for entering a password. Next, the CPU 11a proceeds to step 520 and monitors whether the input of the user ID and the password is completed. The user ID and password are collectively referred to as “user related information”.

  When the user A inputs his / her user ID and password by a predetermined touch panel operation, the CPU 11a determines “Yes” in step 520, proceeds to step 530, and uses the short-range communication device 116 to manage the vehicle-related information management machine. The vehicle related information including the vehicle body number is acquired from 12.

  Next, the CPU 11a proceeds to step 540, and acquires in-vehicle device related information including the model number of the in-vehicle device 11 from the ROM 11b. Next, the CPU 11a proceeds to step 550, and transmits an “authentication request (user authentication request)” to the center 40 together with the “user-side information including user-related information, vehicle-related information, and vehicle-mounted device-related information” acquired so far. Thereafter, the CPU 11a proceeds to step 560 and monitors whether or not the result from the center 40 has been received.

  On the other hand, the center (actually, the CPU 41a of the computer 41) 40 executes the routine shown by the flowchart in FIG. 6, and monitors whether or not an authentication request has arrived from any onboard device in step 605. ing.

  Therefore, when an authentication request is transmitted from the vehicle-mounted device 11 to the center 40, the center 40 determines “Yes” in step 605 and proceeds to step 610. “User side information received together with the authentication request in step 605” The user information data table DB1 is searched using the “user related information included in” as a key, and the data and password corresponding to the user A are extracted. Next, the center 40 proceeds to step 615, and determines whether or not data indicating the user A exists in the user information data table DB1 based on the search result.

  At this time, if the data indicating the user A does not exist in the user information data table DB1, it is determined that the user A does not have any application license agreement for using this system. Therefore, the center 40 determines “No” in step 615 and proceeds to step 655 to transmit a result indicating that “user authentication has failed” to the in-vehicle device 11.

  In this case, the CPU 11a of the in-vehicle device 11 determines “Yes” in Step 560 of FIG. 5 and determines “No” in “Step 565 to determine whether the user authentication is successful”. Return to.

  On the other hand, if the data indicating the user A exists in the user information data table DB1 at the time when the center executes the process of step 615 in FIG. 6, it is determined as “Yes” in the step 615. Proceeding to step 620, based on the search result at step 610, "password included in user-related information of user side information received together with authentication request" matches user A's password extracted from user information data table DB1. Determine whether.

  If the passwords do not match at this time, the center makes a “No” determination at step 620 to proceed to step 665 and transmits a result indicating that “user authentication has failed” to the in-vehicle device 11. As a result, the CPU 11a of the in-vehicle device 11 returns from step 565 to step 510 in FIG.

  On the other hand, if the “password included in the user related information of the user side information received together with the authentication request” matches the password of the user A extracted from the user information data table DB1, the center 40 proceeds to step 620 in FIG. In step 625 to step 665 described below are sequentially performed, and then the processing associated with the authentication request is terminated.

  Step 625: The center 40 searches the contract information data table DB2 using the user ID of the user A as a key, thereby creating a list of applications for which the user A has a contract (contracting a license agreement). To do. An example of this list is shown in FIG. In the example of FIG. 7, the user A has a license agreement for a total of five applications V to Z.

  Step 630: The center 40 searches the in-vehicle device information data table DB3 by using “the model number of the in-vehicle device 11 included in the in-vehicle device related information of the user side information received together with the authentication request” as a key. Get type and version. The type and version of the in-vehicle device are hereinafter referred to as “in-vehicle device detailed information”.

  Step 635: The center 40 searches the application information data table DB4 by using the application included in the list created in step 625 as a key, thereby searching for in-vehicle device detailed information on which these applications can operate.

  Step 640: The center 40 collates the in-vehicle device detailed information of the in-vehicle device 11 acquired in Step 630 with the in-vehicle device detailed information acquired in Step 635, so that the list of applications created in Step 625 is obtained. By deleting “an application that cannot be operated by the in-vehicle device 11” from the list, only “an application that can be operated by the in-vehicle device 11” is left in the list of the applications. For example, if the application W is inoperable in the in-vehicle device 11 among the applications V to Z, a list of applications shown in FIG. 8 is created as a result of the processing in step 640.

  Step 645: The center 40 searches the vehicle information data table DB5 using “the vehicle body number of the vehicle 10 included in the vehicle-related information of the user-side information received together with the authentication request” as a key, thereby determining the vehicle type of the vehicle 10 (the vehicle 10 (Characteristics / Specifications) is acquired as “Vehicle Type Identification Information”.

  Step 650: The center 40 searches the application information data table DB4 using the vehicle type identification information acquired in step 645 as a key, thereby acquiring an application (vehicle type compatible application) that matches the vehicle 10. For example, if the application is an application dedicated to a hybrid vehicle, the application is compatible with the vehicle 10 that is a hybrid vehicle, but is not compatible with the vehicle 20 that is a gasoline engine vehicle and the vehicle 30 that is an electric vehicle. Conversely, if the application is an application dedicated to an electric vehicle, the application is not compatible with the vehicle 10 that is a hybrid vehicle and the vehicle 20 that is a gasoline engine vehicle, but is compatible with the vehicle 30 that is an electric vehicle.

  Step 655: Based on the application adapted to the vehicle 10 acquired in Step 650, the center 40 selects “application not suitable for the vehicle 10 (unsuitable for the vehicle 10) from the list of applications modified in Step 640. "Is deleted. As a result, only the “application suitable for the vehicle 10” remains in the application list. For example, if the Y application is not compatible with the vehicle 10, a list of applications shown in FIG. 9 is created as a result of the process of step 655. Hereinafter, the list of applications modified in step 655 is also referred to as “transmission application list”.

  Step 660: The center 40 searches the user information data table DB1 using each application remaining in the list of transmission applications as a key, thereby acquiring a user operation history for each application remaining in the transmission application list. . The user operation history includes whether or not the application has been downloaded to the in-vehicle device 11, whether or not the application has been installed in the in-vehicle device 11, what settings the user A has already applied to the application, etc. Information.

  Step 665: The center 40 indicates information indicating that the user authentication of the user A has been successful, a list of applications that are information for identifying applications remaining in the transmission application list, and indicates that these applications are the applications of the user A. The “search result” consisting of the information shown and the information related to the user operation history of the user A for each of these applications is transmitted to the vehicle-mounted device 11 (see FIG. 10).

  By the way, CPU11a of the vehicle equipment 11 is monitoring whether the result from the center was received in step 560 of FIG. Therefore, when the search result is transmitted from the center 40 to the vehicle-mounted device 11, the CPU 11a determines “Yes” in step 560 and proceeds to step 565. In this case, the user authentication is successful, Even if “Yes” is determined, the process proceeds to step 570 to store (save) the search result including the received application list. Next, the CPU 11a proceeds to step 1110 in FIG. 11 (see symbol A in a circle).

  In step 1110, the CPU 11 a selects a specific application from a list of applications included in the search result transmitted from the center 40 (hereinafter referred to as “reception application list”). Next, the CPU 11a proceeds to step 1115, and determines whether or not the application selected in step 1110 has already been downloaded to the in-vehicle device 11 as the user A application.

  Now, it is assumed that “V application” included in the received application list is selected in step 1110 and that “V application” has already been downloaded as the application of user A as shown in FIG. In this case, the CPU makes a “Yes” determination at step 1115 to directly proceed to step 1120 to determine whether or not all the applications included in the received application list have been selected.

  In this case, since “X application and Z application” has not yet been selected, the CPU 11a determines “No” in step 1120 and proceeds to step 1125 to select “X application” as another application that has not been selected. To do. Thereafter, the CPU returns to step 1115.

  As shown in FIG. 10, the X application has not yet been downloaded to the in-vehicle device 11 as the user A application. Accordingly, the CPU makes a “No” determination at step 1115 to proceed to step 1130, and “download request (application acquisition request) together with“ information specifying the application, user related information, vehicle related information, and vehicle equipment related information ”. Is transmitted to the center 40. That is, in this case, the CPU 11a requests the center 40 to download the X application. Then, the CPU 11a proceeds to step 1135 and monitors whether or not the X application has been downloaded from the center 40.

  On the other hand, the center 40 repeatedly executes the routine shown by the flowchart in FIG. Therefore, the center 40 monitors whether or not there is a download request from the in-vehicle device in step 1210. Accordingly, when a download request is transmitted from the in-vehicle device 11 in step 1130 of FIG. 11, the center 40 determines “Yes” in step 1210 and proceeds to step 1220, and the application for which the download request has been made is the user A It is determined (confirmed) whether it exists in the transmission application list (application list modified in step 655 of FIG. 6).

  In this case, since the X application exists in the user A's transmission application list, the center 40 determines “Yes” in step 1220 and proceeds to step 1230 to store the data body of the application requested to be downloaded. The location is acquired by searching the application information data table DB4. Next, the center 40 proceeds to step 1240, reads the application stored in the storage location of the acquired data body of the application from the application data table DB6, and transmits (downloads) it to the in-vehicle device 11.

  If the application requested to be downloaded when the center 40 performs the processing of step 1220 does not exist in the transmission application list, the center 40 proceeds to step 1250 and sends information indicating that the download is rejected. Send to.

  When the application is downloaded to the in-vehicle device 11 by the processing in step 1240, the in-vehicle device 11 determines “Yes” in step 1135 of FIG. 11 and proceeds to step 1120, and all the applications included in the list of received applications It is determined whether or not has been selected. In this case, since the Z application has not yet been selected, the CPU 11a determines “No” in step 1120, proceeds to step 1125, and selects “Z application” as another application that has not been selected. Thereafter, the CPU returns to step 1115.

  The Z application has already been downloaded to the in-vehicle device 11 as shown in FIG. Therefore, the CPU 11a directly proceeds from step 1115 to step 1120. At this stage, all applications included in the list of received applications are already selected. Therefore, the CPU 11a determines “Yes” in step 1120, and proceeds to step 1140 to install an application that is not installed in the in-vehicle device 11 among the applications included in the received application list as the application of the user A. In the example shown in FIG. 10, since the V application and the X application are not installed, the CPU 11a installs the V application and the X application.

  Next, the CPU 11a proceeds to step 1145 to expand the installed application, and proceeds to step 1150 to execute the expanded application. At this time, the CPU 11a has already been installed according to the application settings included in the information received in step 560 in FIG. 5 which is the operation history of user A acquired in step 660 in FIG. The settings of the application (Z application) and the currently installed application (V application and X application) are changed. As a result, an application execution environment is provided. The above is a series of operations executed when the accessory switch (start switch) of the vehicle is changed to the ON state (that is, at the time of logon).

  Next, an operation when an accessory switch (not shown) of the vehicle is changed to an off state in order to log off the vehicle-mounted device 11 when the user A gets off the vehicle 10 will be described. In this case, the CPU 11a of the in-vehicle device 11 proceeds from step 1300 to step 1310 of the routine shown in FIG. 13 and acquires the user operation history. Next, the CPU 11a proceeds to step 1320, and transmits the user operation history to the center 40 together with “information specifying each application and user related information”.

  On the other hand, the center monitors whether or not a user operation history is received from the in-vehicle device in step 1410 of FIG. Therefore, when the user operation history is transmitted from the vehicle-mounted device 11, the center 40 determines “Yes” in step 1410, proceeds to step 1420, and stores the user operation history in the user information data table DB1 while associating the user operation history with the user A. To do. Next, the center 40 proceeds to step 1430, and transmits the result (processing result) stored in step 1420 to the in-vehicle device 11.

  The CPU 11a of the in-vehicle device 11 monitors whether or not the processing result has been transmitted from the center 40 in step 1330. Accordingly, when the processing result is transmitted, the CPU 11a determines “Yes” in step 1330, proceeds to step 1340, terminates the application, and stops the operation of the in-vehicle device 11.

  The case where the user A uses the in-vehicle device 11 in the vehicle 10 has been described above. As is clear from this description, for example, when the user A uses the vehicle-mounted device 21 in the gasoline engine vehicle 20, the vehicle-mounted device 21 is a model that cannot operate the Y application, and the Z application is an application dedicated to the hybrid vehicle. If the X application is an application dedicated to an electric vehicle, the applications included in the transmission application list and the reception application list are the V application and the W application. That is, applications other than the V application and the W application are not downloaded to the in-vehicle device 21. Further, when the V application is already downloaded to the in-vehicle device 21 as the user A application, only the W application is downloaded from the center 40 to the in-vehicle device 21.

  Further, in this case, when the user A uses the vehicle-mounted device 31 in the vehicle 30 that is an electric vehicle, the vehicle-mounted device 31 is included in the transmission application list and the reception application list if the vehicle-mounted device 31 cannot operate the V application. The application is a W application and an X application. Furthermore, when the W application is already downloaded to the in-vehicle device 31 as the user A application, only the X application is downloaded from the center 40 to the in-vehicle device 31.

  When the in-vehicle device 11 is portable and the user A brings the in-vehicle device 11 into the vehicle 30 for use, the W application is inoperable on the in-vehicle device 11 and the Y application is dedicated to the gasoline engine vehicle. In addition, since the Z application is dedicated to the hybrid vehicle, the applications included in the transmission application list and the reception application list are the V application and the X application.

As described above, the application download method according to the embodiment of the present invention is a method of downloading an application from the center to the vehicle-mounted device using communication between the vehicle-mounted device and the center,
A first step of transmitting user-related information including at least user-related information for identifying a user who uses the vehicle-mounted device from the vehicle-mounted device to the center and vehicle-related information related to the vehicle-mounted device (steps 510 to 5 in FIG. 5). See step 550);
A step executed by the computer of the center, the application being contracted by the user based on the user-related information and the vehicle-mounted device-related information included in the transmitted user-side information, and the vehicle-mounted device A second step (step 625, step 630 to step 640 in FIG. 6) of acquiring an application operable in
A third step of downloading the acquired application from the center to the in-vehicle device (see steps 660 and 665 in FIG. 6, steps 1110 to 1135 in FIG. 11, and FIG. 12);
including.

Furthermore,
The first step is a step of further including vehicle information relating to a vehicle on which the vehicle-mounted device is mounted in the user side information (see Step 530 and Step 550 in FIG. 6).
The second step includes a step of narrowing down the acquired application by excluding applications that are not suitable for the vehicle from the acquired applications based on the vehicle information included in the user side information. Yes (see step 645 to step 655 in FIG. 6),
The third step is a step of downloading the narrowed-down application from the center to the vehicle-mounted device (see Steps 660 and 665 in FIG. 6, Steps 1110 to 1135 in FIG. 11, and FIG. 12). is there.

  Furthermore, the third step confirms whether or not there is an application already held in association with the user by the in-vehicle device among the acquired applications before executing the download. Including the application being downloaded from the application to be downloaded (refer to the determination of “Yes” in step 1115 in FIG. 11).

Furthermore, the in-vehicle device used in the download method according to the present embodiment is
An in-vehicle device configured to be able to communicate with a center,
First means for transmitting user-related information including at least user-related information for identifying a user who uses the vehicle-mounted device from the vehicle-mounted device to the center and vehicle-related information related to the vehicle-mounted device (step 510 in FIG. 5). See step 520, step 540 and step 550);
An application that is acquired based on the user-related information and the vehicle-mounted device-related information included in the transmitted user-side information at the center and that is contracted by the user and that can be operated on the vehicle-mounted device 2 from the center (see Steps 560 to 570 in FIG. 5, Steps 1115 to 1135 in FIG. 6, FIG. 11, and Steps 1230 and 1240 in FIG. 12).

Further, the first means is configured to generate the user side information so that vehicle information related to a vehicle on which the vehicle-mounted device is mounted is included as the user side information (steps 530 and 550 in FIG. 5). ),
The second means is configured to receive only applications that are determined to be suitable for the vehicle based on the vehicle information at the center (steps 645 to 665 in FIG. 6 and steps 1110 to 11 in FIG. 11). (See step 1135).

  In addition, the second means is configured to receive only applications from the center that are applications of a user who intends to use the vehicle-mounted device, except for applications already downloaded to the vehicle-mounted device ( (Refer to “Yes” at step 1115 in FIG. 11).

  Therefore, according to the download method according to the present embodiment, it is meaningless for an application that the user has not contracted, an application that cannot be operated on the in-vehicle device to be used, and a vehicle in which the in-vehicle device to be used is mounted. Applications are not downloaded from the center 40 to the in-vehicle device. Therefore, it is possible to avoid occurrence of useless communication.

  The present invention is not limited to the above embodiment, and various modifications can be employed within the scope of the present invention. For example, the data tables DB1 to DB6 may be combined into one. In addition, the vehicle-related information management machine 12 may be configured to be able to communicate with the center 40, and an authentication request, a download request, and reception of the downloaded application may be performed through the vehicle-related information management machine 12. Furthermore, the vehicle-mounted device related information transmitted from the vehicle-mounted device 11 to the center 40 may include the vehicle-mounted device detailed information regarding the vehicle-mounted device 11. In addition, the vehicle related information transmitted from the in-vehicle device 11 to the center 40 may include vehicle type specifying information.

  DESCRIPTION OF SYMBOLS 10, 20, 30 ... Vehicle, 11, 21, 31 ... In-vehicle machine, 12, 22, 32 ... Vehicle related information management machine, 40 ... Center, 41 ... Computer (server), 43 ... External storage device, 111 ... Microcomputer .

Claims (6)

An application download method for downloading an application from the center to the in-vehicle device using communication between the in-vehicle device and the center,
A first step of transmitting user-related information including at least user-related information for identifying a user who uses the in-vehicle device from the in-vehicle device to the center and in-vehicle device-related information regarding the in-vehicle device;
A step executed by the computer of the center, the application being contracted by the user based on the user-related information and the vehicle-mounted device-related information included in the transmitted user-side information, and the vehicle-mounted device A second step of acquiring an application operable with
A third step of downloading the acquired application from the center to the in-vehicle device;
Including download method. The application download method according to claim 1,
The first step is a step of further including vehicle information related to a vehicle on which the in-vehicle device is mounted in the user side information,
The second step includes a step of narrowing down the acquired application by excluding applications that are not suitable for the vehicle from the acquired applications based on the vehicle information included in the user side information. Yes,
The third step is a step of downloading the narrowed application from the center to the in-vehicle device.
How to download. In the application download method according to claim 1 or 2,
The third step confirms whether there is an application already held in association with the user by the in-vehicle device among the acquired applications before executing the download. A download method comprising excluding an existing application from the downloaded application. An in-vehicle device configured to be able to communicate with a center,
First means for transmitting user-related information including at least user-related information for identifying a user who uses the vehicle-mounted device from the vehicle-mounted device to the center and vehicle-vehicle related information related to the vehicle-mounted device;
An application that is acquired based on the user-related information and the vehicle-mounted device-related information included in the transmitted user-side information at the center and that is contracted by the user and that can be operated on the vehicle-mounted device A second means for receiving from the center;
In-vehicle device including The in-vehicle device according to claim 4,
The first means is configured to generate the user side information so that vehicle information related to a vehicle on which the in-vehicle device is mounted is included as the user side information.
The second means is configured to receive only an application determined to be suitable for the vehicle based on the vehicle information at the center.
In-vehicle device. The in-vehicle device according to claim 5,
The second means is a vehicle-mounted device configured to receive from the center only applications that are applications of a user who intends to use the vehicle-mounted device and that are not already downloaded to the vehicle-mounted device.

Images