JP5477231B2 - Communication system including in-vehicle device and information center, and information center - Google Patents

Description

  The present invention relates to a communication system including an in-vehicle device and an information center, and an information center.

  Conventionally, a technique in which an in-vehicle device downloads and uses an application from an information center is known.

JP 2006-172501 A

  However, various resources (for example, CPU version, amount of memory, presence / absence of an external device, OS version, etc.) in a vehicle on which an in-vehicle device is mounted vary depending on the vehicle. Therefore, even if the same application is downloaded, it can be normally executed by one vehicle-mounted device and cannot be normally executed by another vehicle-mounted device.

  In such a case, if the in-vehicle device tries to download and execute an application that cannot be executed correctly by itself, it will give a message that it cannot be executed and notify the driver, or it will not respond or do something strange. It will be. When sending a message, the driver moves his / her line of sight to see the message once, which hinders driving. If nothing reacts, the driver feels strange, distracts from driving and still causes driving difficulties. If you do something strange, it will still interfere with your driving.

  In other words, downloading an application that cannot be executed normally hinders driver operation. Therefore, for an application that does not operate normally, it is desirable that an application that does not operate normally does not appear as an option when the driver selects and downloads the application.

  The present invention has been made in view of the above points, and it is an object of the present invention to provide a technique for preventing an application that does not operate normally from appearing as an option when a driver selects an application and downloads it from an information center to an in-vehicle device.

The invention described in claim 1 for achieving the above object is a communication system including an in-vehicle device (2) mounted on a vehicle and an information center (3) communicating with the in-vehicle device (2). The in-vehicle device (2) includes an in-vehicle device side data storage unit (25) for storing an owned resource list (25h) that is a list of resources provided in the in-vehicle device (2), and an in-vehicle device side control unit. (26), the information center (3) includes a center side data storage unit (32) and a center side control unit (33), and the center side data storage unit (32) includes a plurality of distribution applications (32c). 32e) for each of the plurality of distribution applications (32c, 32e), for each distribution application (32c, 32e) A storage unit for storing a necessary resource list (32d, 32f) that is a list of resources necessary for execution, and the in-vehicle device executes the distribution application for each of the plurality of distribution applications (32c, 32e). In this case, a list of resources that the information center (3) must provide is stored in the center side data storage unit (32), and the front in-vehicle device side control unit (26) The owned resource list (25h) is read from the in-vehicle device side data storage unit (25) and transmitted to the information center (3), and the center side control unit (33) transmits the transmitted owned resource list (25h). , The received owned resource list (25h) is used as the owned resource list (32a, 32b) for the in-vehicle device (2). The center side data storage unit (32) records the owned resource list (32a, 32b) for the in-vehicle device (2) from the center side data storage unit (32). Read, further read out the necessary resource list (32d, 32f) of each of the plurality of distribution applications (32c, 32e), and read out the owned resource list (32a, 32b) for the in-vehicle device (2) Compared with each of the necessary resource lists (32d, 32f), if the owned resource list (32a, 32b) for the in-vehicle device (2) satisfies a certain necessary resource list (32d, 32f) The distribution application (32c, 32e) corresponding to the resource list (32d, 32f) can be executed. Resources that can be provided by the information center (3) even if the owned resource list (32a, 32b) for the in-vehicle device (2) satisfies a certain required resource list (32d, 32f) However, if the information center (3) does not satisfy the list of resources that the information center (3) must provide when the in-vehicle device executes the distribution application corresponding to the certain required resource list, the distribution corresponding to the necessary resource list is performed. If the application is not included in the executable distribution application list and the owned resource list (32a, 32b) for the vehicle-mounted device (2) does not satisfy another certain required resource list (32d, 32f) Before the distribution application (32c, 32e) corresponding to the required resource list (32d, 32f) The executable distribution application list created in this way is not included in the executable distribution application list, and is transmitted to the vehicle-mounted device (2). The vehicle-mounted device side control unit (26) is connected to the center side control unit (33). ) Is transmitted, the distribution application included in the received executable distribution application list is displayed on the display (22), and the distribution application to be downloaded is displayed among the displayed distribution applications. The communication system is characterized by receiving a selection operation and requesting and downloading the distribution application selected by the selection operation to the information center (3).

  In the present invention, in order to grasp whether or not a distribution application can be executed by a specific in-vehicle device, it is only necessary to know the resources of the in-vehicle device necessary for executing each distribution application and the resources provided in the in-vehicle device. Pay attention.

  Therefore, as described above, the center-side data storage unit (32) stores the necessary resource list (32d, 32f), which is a list of resources necessary for normal execution, for each distribution application (32c, 32e). The side control unit (33) receives and records the owned resource list (25h), which is a list of resources included in the in-vehicle device (2).

  Then, the center side control unit (33) compares the owned resource list (32a, 32b) for the in-vehicle device (2) with each of the necessary resource list (32d, 32f), and owns the in-vehicle device (2). When the resource list (32a, 32b) satisfies a certain required resource list (32d, 32f), the distribution application (32c, 32e) corresponding to the required resource list (32d, 32f) is set as the executable distribution application list. If the owned resource list (32a, 32b) does not satisfy another required resource list (32d, 32f), the distribution application (32c, 32e) corresponding to the required resource list (32d, 32f) is displayed. Executables created in this way, not included in the executable distribution application list When the request for the distribution application selected from the executable distribution application list is received in the in-vehicle device (2), the requested distribution application is transmitted to the in-vehicle device (2). To do.

  By doing in this way, rather than determining whether the downloaded distribution application is operable on the in-vehicle device (2) side, this information is not transmitted on the in-vehicle device on the information center (3) side before downloading. The time when the driver selects an application and downloads it from the information center to the in-vehicle device by determining whether or not it can operate normally and making the in-vehicle device (2) unable to select what is determined to be inoperable Thus, it is possible to prevent an application that does not operate normally from appearing as an option.

  The invention according to claim 2 is the communication system according to claim 1, wherein the in-vehicle device side control unit (26) is owned by the in-vehicle device (2) at a predetermined timing. Based on the detection result, the content of the owned resource list (25h) in the in-vehicle device side data storage unit (25) is updated, and the updated latest owned property is updated at a predetermined timing. The resource list (25h) is transmitted to the information center (3).

  Thus, the content of the owned resource list (25h) is updated on the in-vehicle device (2) side, and the updated latest owned resource list (25h) is transmitted to the information center (3). Even if the resource configuration in (2) changes, the information center (3) can follow the change and create an appropriate executable distribution application list.

The invention according to claim 3 is an information center that communicates with the vehicle-mounted device (2) mounted on the vehicle, and includes a center-side data storage unit (32) and a center-side control unit (33), The center-side data storage unit (32) stores a plurality of distribution applications (32c, 32e) and distributes each of the plurality of distribution applications (32c, 32e) for each distribution application (32c, 32e). It is a storage unit for storing a necessary resource list (32d, 32f) that is a list of resources necessary for normal execution of the application, and for each of the plurality of distribution applications (32c, 32e), the distribution application is mounted on the vehicle. A list of resources that the information center (3) must provide when the machine executes The center side data storage unit (32) is configured to store the owned resource list (25h), which is a list of resources included in the in-vehicle device (2), The received resource list (25h) received from the in-vehicle device (2) is recorded in the center-side data storage unit (32) as the owned resource list (32a, 32b) for the in-vehicle device (2). The center-side control unit (33) reads the owned resource list (32a, 32b) for the in-vehicle device (2) from the center-side data storage unit (32), and further, the plurality of distribution applications (32c, 32e), each of the necessary resource lists (32d, 32f) is read, and the owned resource list (32a, 32b) for the vehicle-mounted device (2) is read. Is compared with each of the read required resource lists (32d, 32f), and the owned resource list (32a, 32b) for the in-vehicle device (2) satisfies a certain required resource list (32d, 32f). In this case, the distribution application (32c, 32e) corresponding to the necessary resource list (32d, 32f) is included in the executable distribution application list, provided that the owned resource list (32a, 32b) for the in-vehicle device (2) is included. Even if a certain required resource list (32d, 32f) is satisfied, the information that can be provided by the information center (3) when the vehicle-mounted device executes a distribution application corresponding to the certain required resource list. If the list of resources that the center (3) must provide is not met, The distribution application corresponding to the source list is not included in the executable distribution application list, and the necessary resource list (32d, 32f) different from the owned resource list (32a, 32b) for the in-vehicle device (2) is used. If not, the distribution application (32c, 32e) corresponding to the necessary resource list (32d, 32f) is not included in the executable distribution application list, and the executable distribution application list thus created is The center-side control unit (33) transmits the information to the vehicle-mounted device (2), and the center-side control unit (33) receives the executable distribution application list for each distribution application included in the executable distribution application list. Accepts user's selection and selected Based upon the request signal application is requested the distribution application information center and transmits the in-vehicle device (2).

Thus, the feature of the invention described in claim 1 can also be understood as an invention in an information center that communicates with an in-vehicle device (2) mounted on a vehicle .
According to a fourth aspect of the present invention, in the communication system according to the first or second aspect, when the in-vehicle device executes the distribution application stored in the center-side data storage unit (32), the information center The list of resources that (3) must provide includes a list of service functions that the information center (3) must provide.
According to a fifth aspect of the present invention, in the communication system according to any one of the first, second, and fourth aspects, the distribution application stored in the center-side data storage unit (32) is a vehicle-mounted device. The list of resources that must be provided by the information center (3) when the information center (3) is executed includes a list of data that must be provided by the information center (3).
The invention according to claim 6 provides the information center according to claim 3 when the in-vehicle device executes a distribution application stored in the center-side data storage unit (32). The list of resources that must be included includes a list of service functions that the information center must provide.
The invention according to claim 7 is the information center according to claim 3 or 6, when the in-vehicle device executes the distribution application stored in the center-side data storage unit (32). The list of resources that must be provided includes a list of data that the information center must provide.

  In addition, the code | symbol in the bracket | parenthesis in the said and the claim shows the correspondence of the term described in the claim, and the concrete thing etc. which illustrate the said term described in embodiment mentioned later. .

It is a figure which shows the structure of the communication system which concerns on embodiment of this invention. It is a block diagram of the vehicle equipment. 2 is a configuration diagram of an information center 3. FIG. It is a block diagram of the owned resource list 25h. It is a block diagram of the required resource lists 32d and 32f. It is a sequence diagram of operation | movement of a vehicle equipment and an information center. It is a flowchart which shows the content of the update process of an owned resource list. It is a list of distribution applications to be displayed on the display.

  Hereinafter, an embodiment of the present invention will be described. FIG. 1 shows a configuration of a communication system according to the present embodiment. This communication system includes an in-vehicle device 2 mounted on a vehicle 1 and an information center 3. The information center 3 also communicates with in-vehicle devices having the same configuration and function as the in-vehicle device 2 other than the in-vehicle device 2.

  The in-vehicle device 2 downloads a distribution application from the information center 3 by communicating with the information center 3 via the wireless base station 4 and a communication network (for example, a wide area network such as the Internet) 5. The in-vehicle device 2 may be, for example, a navigation device that calculates and guides a guidance route from the current position to the destination, or may be another device.

  FIG. 2 shows the configuration of the in-vehicle device 2. The in-vehicle device 2 includes an external device interface 21, a display 22, an operation unit 23, a communication unit 24, an in-vehicle device side data storage unit 25, and an in-vehicle device side control unit 26.

  The external device interface 21 is an interface for connecting various external devices to the in-vehicle device 2. Examples of external devices that can be connected include a head-up display, a GPS receiver, and a camera that captures the outside of the vehicle. The in-vehicle device side control unit 26 can determine what type of external device is connected to the external device interface 21 by exchanging signals with the external device connected to the external device interface 21. It is like that.

  The display 22 is a device that displays an image according to the control of the in-vehicle device side control unit 26. The operation unit 23 is a device that receives a user operation and outputs a signal corresponding to the received operation to the in-vehicle device side control unit 26.

  The communication unit 24 is a wireless communication interface for wirelessly connecting to the wireless base station 4 in the vicinity of the vehicle 1 and communicating with the information center 3 via the wireless base station 4 and the communication network 5. The in-vehicle device side data storage unit 25 can communicate with the information center 3 using the communication unit 24.

  The in-vehicle device side data storage unit 25 includes a writable non-volatile storage medium such as a magnetic storage medium, a flash memory, etc., and writes data to the storage medium according to the control of the in-vehicle device side control unit 26. Data is read from the medium and output to the in-vehicle device side control unit 26.

  The in-vehicle device side control unit 26 includes a CPU 26a, a RAM 26b, a ROM 26c, and the like, executes a program stored in the ROM 26c or the in-vehicle device side data storage unit 25, and operates the RAM 26b as necessary when executing the program. It is used as a memory area, controls external devices connected to the external device interface 21, receives data from the external devices, controls the display 22, receives signals from the operation unit 23, and uses the communication unit 24 to provide an information center 3, and performs data reading and writing processing to the in-vehicle device side data storage unit 25.

  Here, the detail of the data memorize | stored in the vehicle equipment side data storage part 25 is demonstrated. The in-vehicle device side data storage unit 25 stores an OS 25a, middleware 25b, an in-vehicle device embedded application 25c, data 25d, a distribution application software platform 25e, distribution applications 25f and 25g, and an owned resource list 25h.

  The OS 25a is an operating system program executed by the CPU 26a to perform basic input / output with various devices of the in-vehicle device 2. The middleware 25b is a program executed by the CPU 26a on the OS 25a in order to mediate exchange of request and response data between the OS 25a and the application between the OS 25a and the application.

  The in-vehicle device built-in application 25c is a program group recorded in the in-vehicle device side data storage unit 25 in advance (for example, when the in-vehicle device 2 is shipped). For example, when the in-vehicle device 2 is a navigation device, a destination search program, a map display program, a guidance route calculation program, a route guidance program along the guidance route, etc. It may be stored as 25c. These professional programs are also executed by the CPU 26a.

  The data 25d is data other than a program. For example, when the in-vehicle device 2 is a navigation device, map data for guidance route calculation and map display is stored in the in-vehicle device side data storage unit 25 as data 25d. It may be.

  The distribution application software platform 25e is a program group necessary for executing various applications (hereinafter referred to as distribution applications) that communicate with the information center 3 and download from the information center 3. For example, a program for starting a distribution application corresponds to the distribution application software platform 25e.

  The distribution applications 25 f and 25 g are application programs downloaded from the information center 3 by communicating with the information center 3. The downloaded distribution applications 25f and 25g are recorded in the in-vehicle device side data storage unit 25 as described above, and the in-vehicle device side control unit is executed on the OS 25a, the middleware 25b, and the distribution application software base 25e as necessary. 26. As will be described later, in the in-vehicle device 2 of the present embodiment, only an executable distribution application can be selected as a distribution application to be downloaded.

  The owned resource list 25h is a list of resources (hardware resources, software resources, external device resources, data resources, etc.) provided in the in-vehicle device 2. The contents of this owned resource list 25h will be described later.

  Next, the configuration of the information center 3 is shown in FIG. The information center 3 includes a communication unit 31, a center side data storage unit 32, and a center side control unit 33.

  The communication unit 31 is connected to the communication network 5 and communicates with the in-vehicle device 2 (and other in-vehicle devices having functions equivalent to the in-vehicle device 2) via the communication network 5 and the wireless base station 4. Interface. The center-side control unit 33 can communicate with the in-vehicle device 2 (and other in-vehicle devices having functions equivalent to the in-vehicle device 2) using the communication unit 31.

  The center-side data storage unit 32 includes a writable non-volatile storage medium such as a magnetic storage medium or a flash memory, and writes data to the storage medium according to the control of the center-side control unit 33. Data is read and output to the center side control unit 33.

  The center-side control unit 33 includes a CPU, a RAM, a ROM, and the like, executes a program stored in the ROM, and uses the RAM as a work memory area when necessary to execute a program. 31 is used to communicate with the in-vehicle device 2 (and a plurality of other in-vehicle devices having the same function as the in-vehicle device 2), and read and write data to the center side control unit 33.

  Here, the details of the data stored in the center-side data storage unit 32 will be described. The center-side data storage unit 32 includes owned resource lists 32a and 32b for each in-vehicle device and a plurality of distribution applications 32c and 32e.

  The owned resource lists 32a and 32b are data received and accumulated from the vehicle-mounted device 2 (and other vehicle-mounted devices having functions equivalent to the vehicle-mounted device 2). The process of receiving and storing the owned resource list will be described later.

  The plurality of distribution applications 32c and 32e are application programs for transmitting to the vehicle-mounted device 2 (and other vehicle-mounted devices having functions equivalent to the vehicle-mounted device 2), respectively. As the distribution application, for example, there is an application program that realizes a function of displaying various information in the host vehicle (engine speed, fuel consumption, estimated arrival time at the destination, etc.) on a head-up display.

  Further, in the plurality of distribution applications 32c and 32e, the required resource lists 32d and 32f of the distribution application are included in each distribution application 32c and 32e. The required resource list of a certain distribution application is a list of resources that the in-vehicle device must possess in order to execute the distribution application normally in the in-vehicle device.

  Here, the configurations of the owned resource list 25h recorded in the in-vehicle device side data storage unit 25 and the necessary resource lists 32d and 32f recorded in the center side data storage unit 32 will be described.

  First, FIG. 4 shows an example of the data configuration of the owned resource list 25h. As described above, the owned resource list 25h in the in-vehicle device side data storage unit 25 is a list of resources provided in the in-vehicle device 2, and includes a list of owned hardware resources, a list of owned software resources, and a list of owned external device resources. It is divided into a list and a list of owned data resources.

  The list of owned hardware resources includes information such as the version of the CPU 26a, the memory capacity of the RAM 26b, the display size (number of pixels, inches, etc.) of the display 22, for example.

  The list of owned software resources includes, for example, information such as the version of the OS 25a, the presence / absence of the middleware 25b, the version of the middleware 25b, the version of the distribution application software base 25e, and the list of the in-vehicle device embedded application 25c.

  The list of owned external device resources includes, for example, information on the types of external devices (for example, a head-up display, a GPS receiver, and a camera that captures images outside the vehicle) connected to the external device interface 21.

  The list of owned data resources includes, for example, information such as the version of specific data (for example, map data) in the data 25d of the in-vehicle device side data storage unit 25.

  For such an owned resource list 25h, the initial value of the resource list 25h is created so that the manufacturer of the in-vehicle device 2 reflects the actual resource of the in-vehicle device 2 at that time in advance (for example, when the in-vehicle device is manufactured). Then, the vehicle-mounted device 2 is shipped with the initial value of the resource list 25h written in the vehicle-mounted device-side data storage unit 25.

  Next, FIG. 5 shows an example of the configuration of the necessary resource lists 32d and 32f for a specific distribution application in the center-side data storage unit 32. The configuration of the required resource list is in a format corresponding to the owned resource list for the purpose of comparison with the owned resource list.

  Specifically, as described above, the required resource list of a certain distribution application is a list of resources necessary for the distribution application to be normally executed on the vehicle-mounted device, and includes a list of required hardware resources and a list of required software resources. The list is divided into a list, a list of necessary external device resources, and a list of necessary data resources.

  The list of necessary hardware resources includes, for example, information such as the CPU version, the memory capacity of the RAM, and the display size (number of pixels, inches, etc.). The list of necessary software resources includes, for example, information such as OS version, presence / absence of middleware, version of the middleware, version of software platform for distribution application, list of in-vehicle device embedded applications, and the like. The list of necessary external device resources includes, for example, information such as the type of external device. The list of necessary data resources includes information such as the version of specific data (for example, map data).

  The required resource list of a certain distribution application is included in the distribution application by the developer of the distribution application when the distribution application is developed. Therefore, the necessary resource list of the distribution application is recorded in the center side data storage unit 32 together with the distribution application.

  Hereinafter, the operation of the communication system configured as described above will be described. FIG. 6 shows a sequence diagram of operations of the in-vehicle device 2 and the information center 3 in this communication system.

  As shown in this figure, the in-vehicle device side control unit 26 of the in-vehicle device 2 updates the content of the owned resource list 25h at a predetermined timing after shipment (step 110). The predetermined update timing at which the owned resource list should be updated includes, for example, a timing when the device configuration of the in-vehicle device 2 is changed due to connection or removal of an external device, and a timing when the device is regularly visited.

  FIG. 7 shows details of the processing in step 110. As shown in this figure, the in-vehicle device side control unit 26 determines whether or not an external device is connected or disconnected in step 310, determines whether or not a regular update timing has come in step 320, and step Steps 310 and 320 are repeated until it is determined at 310 that the connection or disconnection has been made, or at step 320 that it has been visited, and it is determined at step 310 that there has been a connection or disconnection, or that it has been visited at step 320. If determined, the process proceeds to step 330. The connection and removal of the external device are detected by exchanging signals with the external device connected to the external device interface 21.

  In step 330, a resource owned by the in-vehicle device 2 at that time is detected. For example, the CPU 26a version and the memory capacity of the RAM 26b are detected by a known method, the display 22 is inquired, a response to the inquiry is received from the display 22, and the display size of the display 22 is detected based on the received response.

  Further, the version of the OS 25a is detected based on the version information in the OS 25a, and the presence / absence of the middleware 25b is detected based on whether the middleware 25b is recorded in the in-vehicle device side data storage unit 25, and there is the middleware 25b. In this case, the version is detected based on the version information in the middleware 25b, the version of the in-vehicle device embedded application 25c is detected based on the version information in the in-vehicle device embedded application 25c, and the detection result is stored in the owned resource list 25h. To reflect. Further, the in-vehicle device built-in application 25c recorded in the in-vehicle device side data storage unit 25 is searched for and found.

  Further, by communicating with the external device interface 21, the type of the external device connected to the external device interface 21 is specified. Based on the version information of the map data included in the data 25d, the version of the map data is detected, and the detection result is reflected in the owned resource list 25h.

  Then, the owned resource list 25h is updated in order to make the contents of the owned resource list 25h coincide with the current resource newly detected (or found) as described above. In this way, the owned resource list 25h is updated following the actual change in the resources of the vehicle-mounted device 2.

  In addition, the in-vehicle device side control unit 26 uses the updated latest owned resource list 25h as an ID on the in-vehicle device 2 side (for example, an ID for uniquely identifying the vehicle 1 and a unique identifier for identifying the in-vehicle device 2). ID) together with the information center 3 (step 120). The transmission of the owned resource list 25h may be performed immediately after the update in step 110, or may be performed periodically. Alternatively, it may be performed at the same timing as the request transmission in step 130 described later when the distribution application is downloaded from the information center 3 to the in-vehicle device 2.

  When the information center 3 receives the owned resource list 25h and the ID transmitted in this way, the data that associates the received owned resource list 25h with the ID is used as the owned resource list for the in-vehicle device 2 that is the transmission source. It records in the center side data storage part 32 (step 210). In this way, by receiving and recording the owned resource list and the in-vehicle device side ID from the in-vehicle device 2 or a plurality of other in-vehicle devices other than the in-vehicle device 2, as shown in FIG. The owned resource lists 32a and 32b for each of the plurality of in-vehicle devices are recorded in the unit 32. As for the owned resource list for the same vehicle-mounted device, only the last received (that is, latest) owned resource list is recorded, and the old owned resource list is deleted.

  Next, the operation of the in-vehicle device 2 and the information center 3 when the distribution application is downloaded from the information center 3 to the in-vehicle device 2 will be described.

  The in-vehicle device side control unit 26 transmits a download request including the ID on the in-vehicle device 2 side to the information center 3 based on the fact that the user has performed an operation for starting the download process with respect to the operation unit 23 (step 130). ).

  When the center-side control unit 33 of the information center 3 receives the download request transmitted in such a manner (step 220), the center-side data storage unit 32 stores the owned resource list associated with the ID included in the received download request. Read (step 230), and further read the necessary resource lists 32d and 32f of the plurality of distribution applications 32c and 32e (step 240).

  Further, the center side control unit 33 creates an executable distribution application list (step 250). Specifically, the read owned resource list is compared with each of the read required resource lists 32d and 32f. That is, it is determined whether or not the owned resource list satisfies each necessary resource list.

  If all the resources (hardware, software, external device, data presence / absence and version) described in a certain required resource list are included in the owned resource list, the owned resource list is included in the required resource list. If some of the resources listed in a required resource list are not included in the owned resource list, it is determined that the owned resource list does not satisfy the required resource list. The

  When a certain owned resource list (for example, the necessary resource list 32d) satisfies the necessary resource list when the owned resource list is compared with each necessary resource list, the resource list corresponds to the necessary resource list (the necessary resource list). A distribution application (including a distribution) (eg, distribution application 32c) is added to the executable distribution application list. When the owned resource list does not satisfy another certain required resource list (for example, the necessary resource list 32f), a distribution application (for example, the distribution application 32e) corresponding to the certain certain necessary resource list can be executed. Do not add to distribution application list.

  By doing in this way, only the delivery application corresponding to the required resource list which the said owned resource list satisfy | fills among the some delivery applications currently recorded on the vehicle equipment side data storage part 25 is executable executable application list. To be added.

  Further, the center side control unit 33 transmits the executable distribution application list created in this way to the in-vehicle device 2 (step 260).

  Then, the in-vehicle device side control unit 26 of the in-vehicle device 2 receives the executable distribution application list (step 140), and displays the distribution application included in the executable distribution application list on the display 22 (step 150). FIG. 8 shows a display example of the display 22 in step 150. Each of the displayed distribution applications can be selected by the user by operating the operation unit 23.

  At this time, the distribution application displayed on the screen has already been checked in the information center 3 whether or not it can be executed by the vehicle-mounted device 2 at that time, so the driver selects it and cannot execute it, and an error or warning is displayed on the screen. It is never displayed. Therefore, the driver can safely use the distribution application without being disturbed by driving.

  Subsequently, the in-vehicle device side control unit 26 receives an operation for selecting a distribution application to be downloaded from the displayed distribution applications (step 160). When the user performs a selection operation using the operation unit 23, the distribution application selected by the selection operation is requested to the information center 3 and downloaded (step 270).

  In step 170, the in-vehicle device side control unit 26 transmits distribution designation information indicating the distribution application selected by the selection operation to the information center 3, and the center side control unit 33 that has received the distribution designation information receives the distribution designation information. Is read from the center-side data storage unit 32 and transmitted to the in-vehicle device 2, and the in-vehicle device-side control unit 26 receives the distribution application transmitted in this manner and records it in the in-vehicle device side data storage unit 25. To do. And the vehicle equipment side control part 26 performs the downloaded delivery application based on execution start operation etc. with respect to the operation part 23 of a user.

  As described above, in this embodiment, in order to grasp whether or not a distribution application can be executed by a specific vehicle-mounted device, the resources of the vehicle-mounted device necessary for executing each distribution application and the resources provided by the vehicle-mounted device are included. We are paying attention to knowing.

  That is, as described above, the center side data storage unit 32 stores the necessary resource lists 32d and 32f that are lists of resources necessary for normal execution for each of the distribution applications 32c and 32e, and the center side control unit 33 The owned resource list 25h, which is a list of resources provided in the in-vehicle device 2, is received and recorded.

  When the download request is received from the in-vehicle device 2, the owned resource list for the in-vehicle device 2 is compared with each of the necessary resource lists 32 d and 32 f, and the owned resource list for the in-vehicle device 2 is determined as a specific necessary resource list ( For example, when the necessary resource list 32d) is satisfied, a distribution application (for example, the distribution application 32c) corresponding to the necessary resource list is included in the executable distribution application list, and the owned resource list is another specific necessary resource list (for example, If the required resource list 32f) is not satisfied, the distribution application corresponding to the necessary resource list (for example, the distribution application 32e) is not included in the executable distribution application list, and the executable distribution application created in this way Sends Activation list the in-vehicle device 2, and transmits upon receiving a request for delivery application selected from the possible distribution application list in the vehicle device 2, the requested distribution application in the vehicle-mounted device 2.

  In this way, whether or not the downloaded distribution application can be operated normally on the in-vehicle device 2 before the download on the information center 3 side, rather than determining whether or not the downloaded distribution application is operable. When the driver selects an application and downloads it from the information center to the in-vehicle device, the device does not operate normally. You can prevent applications from appearing in choices.

  In addition, the in-vehicle device side control unit 26 updates the content of the owned resource list 25h in the in-vehicle device side data storage unit 25 at a predetermined timing, and updates the updated owned resource list 25h at a predetermined timing. The data is transmitted to the information center 3.

  As described above, the content of the owned resource list 25h is updated on the in-vehicle device 2 side, and the updated latest owned resource list 25h is transmitted to the information center 3, so that the resource configuration of the in-vehicle device 2 changes. However, the information center 3 can follow this change and create an appropriate executable distribution application list.

(Other embodiments)
As mentioned above, although embodiment of this invention was described, the scope of the present invention is not limited only to the said embodiment, The various form which can implement | achieve the function of each invention specific matter of this invention is included. It is. For example, the following forms are also acceptable.

  (1) In the above embodiment, the owned resource list 25h of the in-vehicle device 2 is updated. However, for the in-vehicle device 2 with a low possibility of resource change, the owned source list in step 110 is not necessarily updated. do not have to.

  (2) In the above embodiment, the center-side control unit 33 creates the executable distribution application list of the in-vehicle device 2 when the download request is received from the in-vehicle device 2. Before receiving a download request from the machine 2, an executable distribution application list of each in-vehicle device (including the in-vehicle device 2) may be periodically created in advance. In this case, when a download request is received from the in-vehicle device 2, the executable distribution application list of the in-vehicle device 2 that is updated last (that is, the latest) may be transmitted to the in-vehicle device 2.

(3) In addition, in the required application list of each distribution application 32c, 32e stored in the center side data storage unit 32, a service that the information server 3 must provide when the vehicle-mounted device executes the distribution application. A list of functions (eg, POI data distribution function) and data (eg, POI data) may be included. In this case, the center-side control unit 33 can provide a service that can be provided by the information center 3 even if the owned resource list for the in-vehicle device 2 that is the transmission source of the download request satisfies a certain required resource list in step 250. If the functions and data do not satisfy the list of service functions and data that must be provided by the information server 3 included in the corresponding necessary application list, the distribution application corresponding to the necessary resource list can be executed. It may not be included in the list.

  (4) In the above-described embodiment, each function realized by the in-vehicle device side control unit 26 and the center side control unit 33 executing a program is hardware having those functions (for example, programming a circuit configuration). It may be realized using an FPGA capable of

DESCRIPTION OF SYMBOLS 1 Vehicle 2 Vehicle equipment 3 Information center 21 External device interface 22 Display 25 Vehicle equipment side data storage part 25a OS
25b Middleware 25c Onboard device embedded application 25d Data 25e Distribution application software base 25f, 25g Distribution application 25h Owned resource list 26 Onboard device side control unit 32 Center side data storage unit 32a, 32b Owned resource list 32c, 32e Distribution application 32d, 32f Necessary resource list 33 Center side controller

Claims (7)

A communication system comprising an in-vehicle device (2) mounted on a vehicle and an information center (3) communicating with the in-vehicle device (2),
The in-vehicle device (2) includes an in-vehicle device side data storage unit (25) for storing an owned resource list (25h) that is a list of resources provided in the in-vehicle device (2), and an in-vehicle device side control unit. (26)
The information center (3) includes a center side data storage unit (32) and a center side control unit (33).
The center-side data storage unit (32) stores a plurality of distribution applications (32c, 32e), and for each of the plurality of distribution applications (32c, 32e), for each distribution application (32c, 32e), A storage unit for storing a necessary resource list (32d, 32f) which is a list of resources necessary for normal execution of the distribution application;
For each of the plurality of distribution applications (32c, 32e), a list of resources that the information center (3) must provide when the vehicle-mounted device executes the distribution application is the center-side data storage unit (32 ) Is remembered,
The front vehicle-mounted device side control unit (26) reads the owned resource list (25h) from the vehicle-mounted device side data storage unit (25) and transmits it to the information center (3),
When the center-side control unit (33) receives the transmitted owned resource list (25h), the center-side control unit (33) converts the received owned resource list (25h) into the owned resource list (32a, 32b) for the in-vehicle device (2). ) In the center side data storage unit (32),
The center side control unit (33) reads the owned resource list (32a, 32b) for the in-vehicle device (2) from the center side data storage unit (32), and further, the plurality of distribution applications (32c, 32e). Each of the necessary resource lists (32d, 32f) is read, and the read owned resource list (32a, 32b) for the in-vehicle device (2) is compared with each of the read required resource lists (32d, 32f). When the owned resource list (32a, 32b) for the in-vehicle device (2) satisfies a certain required resource list (32d, 32f), the distribution application (32d, 32f) corresponding to the required resource list (32d, 32f) 32c, 32e) is included in the executable distribution application list, but for the in-vehicle device (2) Owned resource list (32a, 32 b) is one required resource list (32d, 32f) even meet, providing available resources of the information center (3), the distribution application corresponding to the one required resource list If the information center (3) does not satisfy the list of resources that the information center (3) must provide when the in-vehicle device executes, the distribution application corresponding to the necessary resource list is not included in the executable distribution application list, If the owned resource list (32a, 32b) for the in-vehicle device (2) does not satisfy another certain required resource list (32d, 32f), the distribution application (32d, 32f) corresponding to the necessary resource list (32d, 32f) 32c, 32e) are included in the executable distribution application list , And sends this manner the executable distribution application list created by the vehicle device (2),
The in-vehicle device side control unit (26) receives the executable distribution application list transmitted by the center side control unit (33), and displays the distribution application included in the received executable distribution application list (22). And receiving a selection operation of a distribution application to be downloaded from the displayed distribution applications, and requesting and downloading the distribution application selected by the selection operation to the information center (3). Communication system.   The vehicle-mounted device side control unit (26) detects a resource owned by the vehicle-mounted device (2) at a predetermined timing, and based on the detection result, the vehicle-mounted device side data storage unit (25) The content of the owned resource list (25h) is updated, and the updated latest owned resource list (25h) is transmitted to the information center (3) at a predetermined timing. Item 12. The communication system according to Item 1. An information center that communicates with an in-vehicle device (2) mounted on a vehicle,
A center side data storage unit (32) and a center side control unit (33);
The center-side data storage unit (32) stores a plurality of distribution applications (32c, 32e), and for each of the plurality of distribution applications (32c, 32e), for each distribution application (32c, 32e), A storage unit for storing a necessary resource list (32d, 32f) which is a list of resources necessary for normal execution of the distribution application;
For each of the plurality of distribution applications (32c, 32e), a list of resources that the information center must provide when the vehicle-mounted device executes the distribution application is stored in the center-side data storage unit (32). Is supposed to be
The center-side control unit (33) receives the owned resource list (25h), which is a list of resources included in the in-vehicle device (2), from the in-vehicle device (2), and receives the received owned resource list (25h). Is recorded in the center-side data storage unit (32) as the owned resource list (32a, 32b) for the in-vehicle device (2),
The center-side control unit (33) reads the owned resource list (32a, 32b) for the in-vehicle device (2) from the center-side data storage unit (32), and further, the plurality of distribution applications (32c, 32e). ) For each of the necessary resource lists (32d, 32f), the owned resource list (32a, 32b) for the in-vehicle device (2) read In comparison, if the owned resource list (32a, 32b) for the in-vehicle device (2) satisfies a certain required resource list (32d, 32f), the distribution corresponding to the required resource list (32d, 32f) Application (32c, 32e) is included in the executable distribution application list, provided that the in-vehicle device Distribution application 2) owning resource list for (32a, 32 b) is one required resource list (32d, even meet 32f), which can provide resources of the information center, corresponding to the one required resource list If the list does not satisfy the list of resources that the information center must provide when the in-vehicle device executes, the distribution application corresponding to the necessary resource list is not included in the executable distribution application list, When the owned resource list (32a, 32b) for the machine (2) does not satisfy another certain required resource list (32d, 32f), the distribution application (32c) corresponding to the necessary resource list (32d, 32f) 32e) is included in the executable distribution application list , And sends this manner the executable distribution application list created by the vehicle device (2),
The center-side control unit (33) receives the selection of the user for each of the distribution applications included in the executable distribution application list by the in-vehicle device (2) that has received the executable distribution application list. An information center, wherein the requested distribution application is transmitted to the in-vehicle device (2) based on the request for the distribution application. The information center (3) provides a list of resources that the information center (3) must provide when the vehicle-mounted device executes the distribution application stored in the center-side data storage unit (32). 3. A communication system according to claim 1 or 2, comprising a list of service functions that must be present. The information center (3) provides a list of resources that the information center (3) must provide when the vehicle-mounted device executes the distribution application stored in the center-side data storage unit (32). 5. A communication system according to claim 1, comprising a list of data that must be present. The list of resources that the information center must provide when the vehicle-mounted device executes the distribution application stored in the center-side data storage unit (32) is a list of service functions that the information center must provide. 4. The information center according to claim 3, further comprising a list. The list of resources that the information center must provide when the vehicle-mounted device executes the distribution application stored in the center-side data storage unit (32) is a list of data that the information center must provide. The information center according to claim 1, wherein the information center is included.

Images