On-vehicle apparatus and system

Abstract

To provide an on-vehicle apparatus and a system which can be configured at a low cost.SOLUTION: An on-vehicle apparatus according to the present disclosure comprises a first receiving unit, a first storage unit, a second receiving unit, and a controller. The first receiving unit receives first positional information. The first storage unit stores software. The software includes a first region and a second region. The first region is stored with common software. The second region is stored with first individual software and first vehicle parameters. The second receiving unit receives second individual software according to the first positional information and second vehicle parameters according to the first positional information. The controller substitutes the first individual software in the second region of the software with the second individual software. The controller substitutes the first vehicle parameters in the second region with the second vehicle parameters.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to an in-vehicle device and system. [Background technology]

[0002] The in-vehicle device storing the software can realize a plurality of vehicle functions according to the software, and it is desirable to configure the in-vehicle device at low cost. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2023-005670 Summary of the Invention [Problem to be solved by the invention]

[0004] The present disclosure provides an in-vehicle device and system that can be configured at low cost. [Means for solving the problem]

[0005] The in-vehicle device according to the present disclosure includes a first receiving unit, a first storage unit, a second receiving unit, and a controller. The first receiving unit receives first location information. The first storage unit stores software. The software includes a first area and a second area. Common software is stored in the first area. First individual software and first vehicle parameters are stored in the second area. The second receiving unit receives second individual software corresponding to the first location information and second vehicle parameters corresponding to the first location information. The controller replaces the first individual software in the second area of ​​the software with the second individual software. The controller replaces the first vehicle parameters in the second area with the second vehicle parameters. [Effects of the Invention]

[0006] The in-vehicle device according to the present disclosure can be configured at low cost. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is a diagram showing an outline of a system including an in-vehicle device according to an embodiment; [Figure 2] FIG. 1 is a diagram showing a hardware configuration of a system including an in-vehicle device according to an embodiment. [Figure 3] FIG. 2 is a diagram showing the configuration of software (before update) in the embodiment. [Figure 4] FIG. 2 is a diagram showing the configuration of an individual software database and a vehicle parameter database (for countries F, G, and H) in the embodiment. [Figure 5] FIG. 2 is a diagram showing the configuration of an individual software database and a vehicle parameter database (for countries J, K, and L) according to an embodiment. [Figure 6] FIG. 1 is a diagram showing the functional configuration of a system including an in-vehicle device according to an embodiment. [Figure 7] FIG. 2 is a diagram showing the configuration of software (after update) in the embodiment. [Figure 8] FIG. 2 is a diagram showing the configuration of software (after update) in the embodiment. [Figure 9] 3 is a flowchart showing the operation of a system including an in-vehicle device according to the embodiment. [Figure 10] 6 is a flowchart showing the operation of a system including an in-vehicle device according to a first modified example of the embodiment. [Figure 11] 10 is a flowchart showing the operation of a system including an in-vehicle device according to a second modification of the embodiment. [Figure 12] 10 is a flowchart showing the operation of a system including an in-vehicle device according to a third modified example of the embodiment. [Figure 13] FIG. 10 is a diagram showing a hardware configuration of a system including an in-vehicle device according to a fourth modified example of the embodiment. [Figure 14] FIG. 10 is a diagram showing the functional configuration of a system including an in-vehicle device according to a fourth modified example of the embodiment. [Figure 15]10 is a flowchart showing the operation of a system including an in-vehicle device according to a fourth modified example of the embodiment. [Figure 16] 10 is a flowchart showing the operation of a system including an in-vehicle device according to a fifth modified example of the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0008] Hereinafter, an embodiment of an in-vehicle device according to the present disclosure will be described with reference to the drawings.

[0009] (Embodiment) The in-vehicle device according to the embodiment can realize a plurality of vehicle functions according to software, and is designed to be configured at low cost.

[0010] A system 300 including the in-vehicle device 1 can be configured as shown in Fig. 1. Fig. 1 is a diagram showing an outline of the system 300 including the in-vehicle device 1.

[0011] The system 300 includes an in-vehicle device 1, a server 100, and a communication line 200.

[0012] The in-vehicle device 1 is mounted on a vehicle VH. The in-vehicle device 1 includes software 51 and type information 52. The software 51 is used to realize multiple functions of the vehicle VH. The in-vehicle device 1 is shipped to a predetermined country (e.g., country F). The left diagram of FIG. 1 shows the state before shipping, and the right diagram of FIG. 1 shows the state after shipping. The in-vehicle device 1 can be moved spatially via the vehicle VH in the destination country. The in-vehicle device 1 is communicatively connected to a server 100 via a communication line 200 in the destination country.

[0013] The communication line 200 includes at least a wireless communication line and may further include a wired communication line. The wireless communication line may be arranged on the vehicle VH side. The wired communication line may be arranged on the server 100 side. FIG. 1 illustrates a case where the server 100 is installed in country F, but the server 100 may also be installed outside country F.

[0014] Wireless communication lines include communication lines using radio access technologies (RATs) such as LTE (Long Term Evolution), NR (New Radio), Wi-Fi, etc. Wired communication lines include the Internet, telephone switching networks, etc.

[0015] In the country of destination, the in-vehicle device 1 can receive positioning signals distributed by a positioning system 600. The positioning system 600 has a plurality of positioning satellites 400a to 400c and a communication line 500. The communication line 500 includes a wireless communication line.

[0016] The positioning system 600 may be, for example, a satellite positioning system, such as a Global Navigation Satellite System (GNSS). The GNSS may be, for example, a Global Positioning System (GPS), a Global Navigation Satellite System (GLONASS), Galileo, a BeiDou Navigation Satellite System, or Michibiki. Each positioning satellite 400 may be, for example, a satellite of the GNSS. The positioning signal may be a signal measured by each positioning satellite 400.

[0017] For example, the multiple functions to be realized by the software 51 may differ depending on the language and hardware specification environment (such as the communication environment) of the shipping destination of the vehicle VH equipped with the in-vehicle device 1. When the vehicle VH equipped with the in-vehicle device 1 is shipped to multiple countries, if multiple pieces of software 51 corresponding to the number of countries are included in the in-vehicle device 1, a memory with an enormous capacity for storing the multiple pieces of software 51 will be provided in the in-vehicle device 1, which is likely to increase the cost of the in-vehicle device 1.

[0018] After further investigation, it was found that the functions to be realized by the software 51 are not all different among the multiple countries to which the vehicle VH is shipped, and some functions are common. The software 51 can be considered to include common software, individual software, and vehicle parameters. The common software realizes the common functions. The individual software realizes functions that differ from country to country and corresponds to the type of vehicle hardware. The vehicle parameters are parameters to be incorporated into the individual software and correspond to the type of vehicle hardware.

[0019] Therefore, in this embodiment, in the in-vehicle device 1, the temporary individual software 54a and temporary vehicle parameters 53a pre-stored in the software 51 can be replaced with the individual software 54 and vehicle parameters 53 corresponding to the country of shipment, thereby reducing the memory capacity for the software 51 and reducing the cost of the in-vehicle device 1.

[0020] For example, the software 51 includes an area 51a and an area 51b. The area 51a corresponds to common functions. The area 51b corresponds to functions that differ depending on the country. The area 51a stores common software 53. The area 51b stores temporary individual software 54a and temporary vehicle parameters 53a in advance before shipping. The in-vehicle device 1 includes type information 52. The type information 52 indicates the type of vehicle hardware.

[0021] After being shipped (for example, to country F), the vehicle-mounted device 1 receives positioning signals distributed by the positioning system 600. The vehicle-mounted device 1 receives a plurality of positioning signals from a plurality of positioning satellites 400a to 400c via the communication line 500, identifies its location based on the plurality of positioning signals, and generates position information 56 according to the identification result. The position information 56 includes global coordinates. The global coordinates include longitude and latitude.

[0022] The in-vehicle device 1 transmits the location information 56 and the type information 52 to the server 100 via the communication line 200. The server 100 identifies the individual software 54 corresponding to the location information 56 and the vehicle parameters 55 corresponding to the location information 56. The server 100 transmits the individual software 54 and the vehicle parameters 55 to the in-vehicle device 1 via the communication line 200. The in-vehicle device 1 receives the individual software 54 and the vehicle parameters 55. The in-vehicle device 1 can replace the temporary individual software 54a in the area 51b of the software 51 with the individual software 54, and can replace the temporary vehicle parameters 53a in the area 51b with the vehicle parameters 55.

[0023] This allows each in-vehicle device 1 to be shipped to multiple countries to include one piece of software 51. As a result, the memory capacity for the software 51 in the in-vehicle device 1 can be reduced compared to when multiple pieces of software corresponding to the number of countries are included in the in-vehicle device 1, and the cost of the in-vehicle device 1 can be reduced.

[0024] A system 300 including the in-vehicle device 1 can be configured in terms of hardware as shown in Fig. 2. Fig. 2 is a diagram showing the hardware configuration of the system 300 including the in-vehicle device 1.

[0025] In the system 300, the in-vehicle device 1 includes a controller 2, a communication device 3, a communication device 4, a non-volatile memory 5, a volatile memory 6, and a vehicle interface processor 7. The controller 2, the communication device 3, the communication device 4, the non-volatile memory 5, the volatile memory 6, and the vehicle interface processor 7 are communicatively connected to one another via a bus.

[0026] The controller 2 comprehensively controls each unit of the in-vehicle device 1. The controller 2 can be implemented as an SoC (System on Chip).

[0027] The communication device 3 is capable of receiving positioning signals. The positioning signals are distributed by a positioning system 600. The positioning system 600 may be a GNSS, and the communication device 3 may be a GNSS device. The communication device 3 has a receiver 3a. The receiver 3a is capable of receiving a plurality of positioning signals from a plurality of positioning satellites 400a to 400c via a communication line 500.

[0028] The communication device 4 can be connected to the server 100 via a communication line 200. The communication device 4 has a transmitting unit 4a and a receiving unit 4b. The transmitting unit 4a can transmit information to the server 100 via the communication line 200. The receiving unit 4b can receive information from the server 100 via the communication line 200.

[0029] The nonvolatile memory 5 stores information in a nonvolatile manner. The nonvolatile memory 5 may store software 51, type information 52, and programs 57 in a nonvolatile manner. The software 51 includes areas 51a and 51b. Area 51a corresponds to common functions. Area 51b corresponds to functions that differ from country to country. Common software 53 is stored in area 51a. The common software 53 realizes the common functions. Temporary individual software 54a and temporary vehicle parameters 53a are stored in area 51b before shipping.

[0030] For example, common software 53 shown in Fig. 3 may be stored in area 51a of software 51. Fig. 3 is a diagram showing the configuration of the software (before update).

[0031] The common software 53 includes at least one of an application program interface (API) 53c, an operating system (OS) 53b, and a hardware abstraction layer (HAL) 53a. Fig. 3 illustrates a configuration in which the common software 53 includes all of the API 53c, the OS 53b, and the HAL 53a.

[0032] The OS 53b is the core software of the common software 53. The API 53c functions as an interface between the application program and the OS 53b, concealing differences in the specifications of the application program and enabling the application program to access the OS 53b. The application program corresponds to the temporary individual software 54a or the individual software 54. The HAL 53a functions as an interface between the hardware and the OS 53b, concealing differences in the specifications of the hardware and enabling the hardware to access the OS 53b. The hardware corresponds to the peripheral PH.

[0033] Area 51b may store one or more temporary individual software 54a and one or more temporary vehicle parameters 55a shown in Fig. 3 before shipping. Area 51b may store a plurality of temporary individual software 54a_1 to 54a_n and a plurality of temporary vehicle parameters 55a_1 to 55a_m. n is any integer equal to or greater than 2. m is any integer equal to or greater than 2. n and m may be the same or different.

[0034] Each of the multiple temporary individual software programs 54a_1 to 54a_n has basically the same configuration as the individual software program 54 (see FIG. 1) to be replaced, but the functions to be realized are slightly different. The temporary individual software program 54a may be individual software program 54 corresponding to functions to be realized in a reference country (e.g., a country with a large number of shipments). Each individual software program 54a includes at least one of language support software, map software, radio software, and navigation software. Each temporary individual software program 54a includes identification information 541 indicating the type information to be supported.

[0035] The plurality of temporary vehicle parameters 55a_1 to 55a_m include at least one of a parameter related to a radio hardware specification, a parameter related to a steering specification, and a parameter related to wireless communication. Each temporary vehicle parameter 55a includes identification information 551 indicating the type information to which it corresponds and identification information 552 indicating the corresponding correspondence information to which it corresponds.

[0036] 2 indicates the type of hardware of the vehicle VH. The non-volatile memory 5 may be, for example, a flash memory. The program 57 may be used to control updates of the software 51.

[0037] The volatile memory 6 temporarily stores information and is also used as a working area for the controller 2. The volatile memory 6 may be, for example, a DRAM.

[0038] The vehicle interface processor 7 is connected to a plurality of peripherals PH and performs an interface operation between the controller 2 and the peripherals PH. Each peripheral PH corresponds to hardware indicated by type information corresponding to the temporary individual software 54a and / or the temporary vehicle parameters 55a.

[0039] The server 100 includes a processor 102, a communication device 104, a storage 105, and a memory 106. The processor 102, the communication device 104, the storage 105, and the memory 106 are communicatively connected to one another via a bus.

[0040] The processor 102 performs overall control of each unit of the server 100. The processor 102 may be implemented as an SoC.

[0041] The communication device 104 can be connected to the in-vehicle device 1 via a communication line 200. The communication device 104 has a receiving unit 104b and a transmitting unit 104a. The receiving unit 104b can receive information from the in-vehicle device 1 via the communication line 200. The transmitting unit 104a can transmit information to the in-vehicle device 1 via the communication line 200.

[0042] The storage 105 stores map information 1051, an individual software database 1052, a vehicle parameter database 1053, and a program 1054. The storage 105 may be, for example, a hard disk drive (HDD) or a solid state drive (SSD).

[0043] The map information 1051 associates a location with a country identifier. The location includes global coordinates. The global coordinates include longitude and latitude. The country identifier includes the country name.

[0044] The individual software database 1052 associates type information with a country identifier for a plurality of country identifiers. The type information indicates the type of vehicle hardware. The country identifier includes the country name. The individual software database 1052 can be used to manage one or more individual software that are candidates to be provided to the in-vehicle device 1.

[0045] For example, the individual software database 1052 may have a data structure as shown in the upper part of Fig. 4 for countries F, G, and H. Fig. 4 is a diagram showing the configuration of the individual software database and the vehicle parameter database (for countries F, G, and H).

[0046] The individual software database 1052 includes a type information column 1052a, a country F information column 1052f, a country G information column 1052g, and a country H information column 1052h. The type information column 1052a records type information indicating the hardware type. The country F information column 1052f records identification information for individual software for country F. The country G information column 1052g records identification information for individual software for country G. The country H information column 1052h records identification information for individual software for country H.

[0047] By referring to the individual software database 1052, it is possible to identify the identification information of the individual software corresponding to the type information for the countries F, G, and H.

[0048] In the example shown in Figure 4, for a hardware type of "European language support," if the country is F, individual software "F language" is identified, if the country is G, individual software "G language" is identified, and if the country is H, individual software "H language" is identified. Each of these individual software may include the corresponding language pack.

[0049] Corresponding to the hardware type "NAVI map," if the country is F, individual software "Around Country F" is specified, if the country is G, individual software "Around Country G" is specified, and if the country is H, individual software "Around Country H" is specified. Each of these individual software may include the corresponding map data.

[0050] Corresponding to the hardware type "compatible radio," if the country is country F, the individual software "AM / FM / DAB" is specified, if the country is country G, the individual software "AM / FM" is specified, and if the country is country H, the individual software "AM / FM / DAB" is specified. Each of these individual software may include an application program for the corresponding radio.

[0051] Corresponding to the hardware type "Wi-Fi communication," if the country is country F, the individual software "Wi-Fi app use" is identified, if the country is country G, the individual software "Wi-Fi app use" is identified, and if the country is country H, the individual software "Wi-Fi app use" is identified.

[0052] Corresponding to the hardware type "meter display", if the country is country F, individual software "meter app use" is identified, if the country is country G, individual software "meter app use" is identified, and if the country is country H, individual software "meter app use" is identified.

[0053] Corresponding to the hardware type "navigation," if the country is country F, individual software "navigation application use" is identified, if the country is country G, individual software "navigation application use" is identified, and if the country is country H, individual software "navigation application use" is identified. Each of these individual software may include a navigation application program.

[0054] Similarly, the individual software database 1052 may have a data structure as shown in the upper part of Fig. 5 for Country J, Country K, and Country M. Fig. 5 is a diagram showing the configuration of the individual software database and vehicle parameter database (for Country J, Country K, and Country M).

[0055] The individual software database 1052 includes a type information column 1052a, a country J information column 1052j, a country K information column 1052k, and a country M information column 1052m. The type information column 1052a records type information indicating the hardware type. The country J information column 1052j records identification information for individual software for country J. The country K information column 1052k records identification information for individual software for country K. The country M information column 1052m records identification information for individual software for country M.

[0056] By referring to the individual software database 1052, it is possible to identify the identification information of the individual software corresponding to the type information for countries J, K, and M.

[0057] In the example shown in Figure 5, for a hardware type of "European language support," if the country is J, individual software "J language" is identified, if the country is K, individual software "K language" is identified, and if the country is M, individual software "M language" is identified. Each of these individual software may include a corresponding language pack.

[0058] Corresponding to the hardware type "NAVI map," if the country is J, individual software "Around Country J" is specified, if the country is K, individual software "Around Country K" is specified, and if the country is M, individual software "Around Country M" is specified. Each of these individual software may include the corresponding map data.

[0059] Corresponding to the hardware type "compatible radio," if the country is country J, the individual software "AM / FM / HD" is specified, if the country is country K, the individual software "AM / FM" is specified, and if the country is country M, the individual software "AM / FM / HD" is specified. Each of these individual software may include an application program for the corresponding radio.

[0060] Corresponding to the hardware type "Wi-Fi communication," if the country is country J, individual software "Wi-Fi app use" is identified, if the country is country K, individual software "Wi-Fi app use" is identified, and if the country is country M, individual software "Wi-Fi app use" is identified.

[0061] Corresponding to the hardware type "meter display", if the country is country J, individual software "meter app use" is identified, if the country is country K, individual software "meter app use" is identified, and if the country is country M, individual software "meter app use" is identified.

[0062] Corresponding to the hardware type "navigation," if the country is country J, individual software "navigation application use" is identified, if the country is country K, individual software "navigation application use" is identified, and if the country is country M, individual software "navigation application use" is identified. Each of these individual software may include a navigation application program.

[0063] The vehicle parameter database 1053 shown in FIG. 2 associates type information, correspondence information, and country identifiers for a plurality of country identifiers. The type information indicates the type of vehicle hardware. The correspondence information indicates type information corresponding to individual software to be incorporated. The country identifier includes the country name. The vehicle parameter database 1053 can be used to manage one or more vehicle parameters that are candidates to be provided to the in-vehicle device 1.

[0064] For example, the vehicle parameter database 1053 may have a data structure for countries F, G, and H as shown in the lower part of FIG.

[0065] The vehicle parameter database 1053 includes a type information column 1053a, a country F information column 1053f, a country G information column 1053g, and a country H information column 1053h. The type information column 1053a records type information indicating the hardware type. The country F information column 1053f records identification information of vehicle parameters for country F. The country G information column 1053g records identification information of vehicle parameters for country G. The country H information column 1053h records identification information of vehicle parameters for country H.

[0066] By referring to the vehicle parameter database 1053, it is possible to identify the identification information of the vehicle parameters corresponding to the type information and the individual software into which the vehicle parameters are to be incorporated for countries F, G, and H.

[0067] In the example shown in Figure 4, corresponding to the hardware type "Radio AM frequency step," if the country is Country F, the vehicle parameter "D step" is identified, if the country is Country G, the vehicle parameter "E step" is identified, and if the country is Country H, the vehicle parameter "D step" is identified. It is also specified that these vehicle parameters should be incorporated into individual software corresponding to the hardware type "compatible radio."

[0068] It is determined that the vehicle parameters corresponding to the hardware type "Radio HD not installed" do not exist (indicated as "-" in Figure 4) regardless of whether the country is F, G, or H.

[0069] Corresponding to the hardware type "Radio DAB installed", if the country is country F, the vehicle parameter "enabled / operated" is identified, if the country is country G, the vehicle parameter "disabled / not operated" is identified, and if the country is country H, the vehicle parameter "enabled / operated" is identified.

[0070] It is determined that the vehicle parameters corresponding to the hardware type "Radio XM installed" do not exist (indicated as "-" in Figure 4) regardless of whether the country is F, G, or H.

[0071] Corresponding to the hardware type "Right or left handle OK", if the country is Country F, the vehicle parameter "Right" is specified, if the country is Country G, the vehicle parameter "Left" is specified, and if the country is Country H, the vehicle parameter "Left" is specified. In addition, it is specified that these vehicle parameters should be incorporated into individual software corresponding to the hardware type "Meter display".

[0072] Corresponding to the hardware type "Wi-Fi equipped / band," if the country is Country F, the vehicle parameter "A band" is identified, if the country is Country G, the vehicle parameter "B band" is identified, and if the country is Country H, the vehicle parameter "A band" is identified. In addition, it is identified that these vehicle parameters should be incorporated into individual software corresponding to the hardware type "Wi-Fi communication."

[0073] Similarly, the vehicle parameter database 1053 may have a data structure as shown in the lower part of FIG. 5 for Country J, Country K, and Country M.

[0074] The vehicle parameter database 1053 includes a type information column 1053a, a country J information column 1052j, a country K information column 1052k, and a country M information column 1052m. The type information column 1053a records type information indicating the hardware type. The country J information column 1052j records identification information of vehicle parameters for country J. The country K information column 1052k records identification information of vehicle parameters for country K. The country M information column 1052m records identification information of vehicle parameters for country M.

[0075] By referring to the vehicle parameter database 1053, it is possible to identify the identification information of the vehicle parameters corresponding to the type information and the individual software into which the vehicle parameters are to be incorporated for each of the countries J, K, and M.

[0076] In the example shown in Figure 5, corresponding to the hardware type "Radio AM frequency step," if the country is Country J, the vehicle parameter "D step" is identified, if the country is Country K, the vehicle parameter "E step" is identified, and if the country is Country M, the vehicle parameter "D step" is identified. It is also specified that these vehicle parameters should be incorporated into individual software corresponding to the hardware type "compatible radio."

[0077] Corresponding to the hardware type "Radio HD not installed," if the country is Country J, the vehicle parameter "enabled / enabled" is identified, if the country is Country K, the vehicle parameter "disabled / disabled," and if the country is Country M, the vehicle parameter "enabled / enabled." It is also identified that these vehicle parameters should be incorporated into individual software corresponding to the hardware type "compatible radio."

[0078] It is determined that the vehicle parameters corresponding to the hardware type "Radio DAB installed" do not exist (indicated as "-" in Figure 5) regardless of whether the country is Country J, Country K, or Country M.

[0079] Corresponding to the hardware type "Radio XM installed," if the country is Country J, the vehicle parameter "enabled / enabled" is identified, if the country is Country K, the vehicle parameter "disabled / disabled" is identified, and if the country is Country M, the vehicle parameter "disabled / disabled" is identified. It is also identified that these vehicle parameters should be incorporated into individual software corresponding to the hardware type "compatible radio."

[0080] Corresponding to the hardware type "Right or left handle OK", if the country is Country J, the vehicle parameter "left" is specified, if the country is Country K, the vehicle parameter "left" is specified, and if the country is Country M, the vehicle parameter "left" is specified. In addition, it is specified that these vehicle parameters should be incorporated into individual software corresponding to the hardware type "meter display".

[0081] Corresponding to the hardware type "Wi-Fi equipped / band," if the country is Country J, the vehicle parameter "A band" is identified, if the country is Country K, the vehicle parameter "B band" is identified, and if the country is Country M, the vehicle parameter "A band" is identified. In addition, it is identified that these vehicle parameters should be incorporated into individual software corresponding to the hardware type "Wi-Fi communication."

[0082] 2 is used to control the processing performed by the server 100. The memory 106 temporarily stores information. The memory 106 is also used as a working area for the processor 102. The memory 106 may be, for example, a DRAM.

[0083] A system 300 including the in-vehicle device 1 can be functionally configured as shown in Fig. 6. Fig. 6 is a diagram showing the functional configuration of the system 300 including the in-vehicle device 1.

[0084] In the system 300, the in-vehicle device 1 includes a control unit 11, a receiving unit 12, a transmitting unit 13, a receiving unit 14, a storage unit 15, a type information acquiring unit 16, an individual software updating unit 17, and a vehicle parameter updating unit 18.

[0085] The receiving unit 12 may be realized by the communication device 3 (see FIG. 2). The transmitting unit 13 and the receiving unit 14 may be realized by the communication device 4. The storage unit 15 may be realized by the non-volatile memory 5 and the volatile memory 6. The control unit 11, the type information acquiring unit 16, the individual software updating unit 17, and the vehicle parameter updating unit 18 may all be realized by hardware (e.g., as a circuit) within the controller 2. The control unit 11, the type information acquiring unit 16, the individual software updating unit 17, and the vehicle parameter updating unit 18 may all be realized by software within the controller 2. The control unit 11, the type information acquiring unit 16, the individual software updating unit 17, and the vehicle parameter updating unit 18 may be partially realized by hardware and partially realized by software. The units realized by software may be deployed as functional modules in the volatile memory 6 collectively at the time of compilation or sequentially as processing progresses by the controller 2 executing the program 57. This allows the units to be equivalently considered to be realized by software within the controller 2.

[0086] The server 100 includes a control unit 111 , a receiving unit 112 , a transmitting unit 113 , a storage unit 114 , a position information determining unit 115 , an individual software identifying unit 116 , and a vehicle parameter identifying unit 117 .

[0087] The receiving unit 112 and the transmitting unit 113 may be realized by the communication device 104 (see FIG. 2 ). The storage unit 114 may be realized by the storage 105 and the memory 106. The control unit 111, the position information determination unit 115, the individual software identification unit 116, and the vehicle parameter identification unit 117 may all be realized by hardware (e.g., as a circuit) within the processor 102. The control unit 111, the position information determination unit 115, the individual software identification unit 116, and the vehicle parameter identification unit 117 may all be realized by software within the processor 102. The control unit 111, the position information determination unit 115, the individual software identification unit 116, and the vehicle parameter identification unit 117 may be partially realized by hardware and partially realized by software. The units realized by software may be deployed as functional modules in the memory 106 collectively at the time of compilation or sequentially as processing progresses by the processor 102 executing the program 1054. This allows the relevant unit to be considered to be equivalently realized in software within the controller 2.

[0088] For example, before shipping, the storage unit 15 of the in-vehicle device 1 stores software 51 and type information 52. The storage unit 114 of the server 100 stores map information 1051, an individual software database 1052, and a vehicle parameter database 1053.

[0089] In the in-vehicle device 1, the receiver 12 receives positioning signals distributed by the positioning system 600 after shipping (for example, to country F). The receiver 12 receives a plurality of positioning signals from a plurality of positioning satellites 400a to 400c via a communication line 500. The controller 11 identifies a position based on the plurality of positioning signals and generates position information 56 according to the identification result. The position information 56 includes global coordinates. The global coordinates include longitude and latitude.

[0090] The type information acquisition unit 16 accesses the storage unit 15 via the control unit 11 and acquires the type information 52 .

[0091] The control unit 11 supplies the location information 56 to the transmission unit 13. The type information acquisition unit 16 supplies the type information 52 to the transmission unit 13 via the control unit 11. The transmission unit 13 transmits the location information 56 and the type information 52 to the server 100 via the communication line 200.

[0092] In the server 100 , the receiving unit 112 receives the location information 56 and the type information 52 from the in-vehicle device 1 via the communication line 200 and supplies them to the control unit 111 .

[0093] When the location information determination unit 115 receives the location information 56 from the control unit 111, it accesses the storage unit 114 via the control unit 111, refers to the map information 1051, and determines the country corresponding to the location information 56. The location information determination unit 115 notifies the determined country to each of the individual software identification unit 116 and the vehicle parameter identification unit 117 via the control unit 111. The control unit 111 supplies the type information 52 to each of the individual software identification unit 116 and the vehicle parameter identification unit 117.

[0094] The individual software identification unit 116 accesses the storage unit 114 via the control unit 111 , refers to the individual software database 1052 , and identifies the individual software 54 corresponding to the determined country and type information 52 .

[0095] For example, if the shipping destination country is Country F, the individual software identification unit 116 identifies the individual software "F language" in correspondence with the hardware type "European language compatible." The individual software identification unit 116 identifies the individual software "Around Country F" in correspondence with the hardware type "NAVI map." The individual software identification unit 116 identifies the individual software "AM / FM / DAB" in correspondence with the hardware type "Compatible radio." The individual software identification unit 116 identifies the individual software "Wi-Fi app used" in correspondence with the hardware type "Wi-Fi communication." The individual software identification unit 116 identifies the individual software "Meter app used" in correspondence with the hardware type "Meter display." The individual software identification unit 116 identifies the individual software "Navigation app used" in correspondence with the hardware type "Navigation."

[0096] The individual software identification unit 116 supplies the identified individual software 54 to the transmission unit 113 via the control unit 111. The individual software identification unit 116 supplies the individual software 54 to the transmission unit 113 in a form associated with type information.

[0097] The vehicle parameter identification unit 117 accesses the storage unit 114 via the control unit 111 , refers to the vehicle parameter database 1053 , and identifies the vehicle parameters 55 corresponding to the determined country and type information 52 .

[0098] For example, if the shipping destination country is Country F, the vehicle parameter identification unit 117 identifies the vehicle parameter "D Step" in correspondence with the hardware type "Radio AM Frequency Step". The vehicle parameter identification unit 117 identifies the vehicle parameter "Enabled / Operated" in correspondence with the hardware type "Radio DAB Equipped". The vehicle parameter identification unit 117 identifies both parameters "Right" in correspondence with the hardware type "Left and Right Handle OK". The vehicle parameter identification unit 117 identifies the vehicle parameter "A Band" in correspondence with the hardware type "Wi-Fi Equipped / Band".

[0099] The vehicle parameter identification unit 117 supplies the identified vehicle parameters 55 to the transmission unit 113 via the control unit 111. The vehicle parameter identification unit 117 supplies the vehicle parameters 55 to the transmission unit 113 in a form associated with the type information and the correspondence information.

[0100] The transmission unit 113 transmits the individual software 54 and the vehicle parameters 55 to the in-vehicle device 1 via the communication line 200. The transmission unit 113 transmits the individual software 54 to the in-vehicle device 1 in a form associated with type information. The transmission unit 113 transmits the vehicle parameters 55 to the in-vehicle device 1 in a form associated with type information and correspondence information.

[0101] In the in-vehicle device 1, the receiving unit 14 receives the individual software 54 and the vehicle parameters 55 from the server 100 via the communication line 200. The receiving unit 14 receives the individual software 54 in a form associated with type information. The receiving unit 14 receives the vehicle parameters 55 in a form associated with type information and correspondence information. The receiving unit 14 supplies the individual software 54 to the individual software update unit 17 via the control unit 11, and supplies the vehicle parameters 55 to the vehicle parameter update unit 18 via the control unit 11.

[0102] When the individual software update unit 17 receives the individual software 54, it identifies the provisional individual software 54a to be updated using the type information associated with the individual software 54 as a key.

[0103] For example, when the individual software update unit 17 receives the plurality of individual software programs 54_2 to 54_m, it uses type information associated with each of the individual software programs 54_2 to 54_m as a key to identify the plurality of temporary individual software programs 54a_2 to 54a_m having matching type information from among the plurality of temporary individual software programs 54a_1 to 54a_m shown in FIG. 3. The individual software update unit 17 overwrites and updates the plurality of temporary individual software programs 54a_2 to 54a_m with the plurality of individual software programs 54_2 to 54_m. As a result, as shown in FIG. 7, some of the individual software programs 54_2 to 54_m are updated, and the remaining temporary individual software program 54a_1 remains untouched. FIG. 7 is a diagram showing the configuration of the software (after update) 51, illustrating a state in which some of the individual software programs 54 have been updated and some of the vehicle parameters 55 have been updated.

[0104] Alternatively, when the individual software update unit 17 receives the plurality of individual software pieces 54_1 to 54_m, it uses type information associated with each of the individual software pieces 54_1 to 54_m as a key to identify the plurality of temporary individual software pieces 54a_1 to 54a_m having matching type information from among the plurality of temporary individual software pieces 54a_1 to 54a_m shown in FIG. 3. The individual software update unit 17 overwrites and updates the plurality of temporary individual software pieces 54a_1 to 54a_m with the plurality of individual software pieces 54_1 to 54_m. As a result, all of the individual software pieces 54_1 to 54_m are updated, as shown in FIG. 8. FIG. 8 is a diagram showing the configuration of the software (after update) 51, illustrating a state in which all of the individual software pieces 54 have been updated and all of the vehicle parameters 55 have been updated.

[0105] When the vehicle parameter update unit 18 receives the vehicle parameters 55, it identifies the temporary vehicle parameters 55a to be updated using the type information and correspondence information associated with the vehicle parameters 55 as keys.

[0106] For example, when vehicle parameter update unit 18 receives multiple vehicle parameters 55_2 to 55_n, it uses type information associated with each vehicle parameter 55_2 to 55_n as a key to identify multiple temporary vehicle parameters 55a_2 to 55a_n that have matching type information from among multiple temporary vehicle parameters 55a_1 to 55a_n shown in Fig. 3. Vehicle parameter update unit 18 overwrites and updates the multiple temporary vehicle parameters 55a_2 to 55a_n with the multiple vehicle parameters 55_2 to 55_n. As a result, as shown in Fig. 7, some vehicle parameters 55_2 to 55_n are updated, and the remaining temporary vehicle parameter 55a_1 remains unupdated.

[0107] Alternatively, when vehicle parameter update unit 18 receives multiple vehicle parameters 55_1 to 55_n, it uses type information associated with each vehicle parameter 55_1 to 55_n as a key to identify multiple temporary vehicle parameters 55a_1 to 55a_n having matching type information from among multiple temporary vehicle parameters 55a_1 to 55a_n shown in FIG. 3. Vehicle parameter update unit 18 overwrites and updates multiple temporary vehicle parameters 55a_1 to 54a_n with the multiple vehicle parameters 55_1 to 55_n. As a result, all vehicle parameters 55_1 to 55_n are updated as shown in FIG. 8.

[0108] This allows each in-vehicle device 1 to be shipped to multiple countries to include one piece of software 51. As a result, the memory capacity for the software 51 in the in-vehicle device 1 can be reduced compared to when multiple pieces of software corresponding to the number of countries are included in the in-vehicle device 1, and the cost of the in-vehicle device 1 can be reduced.

[0109] Next, the operation of the system 300 will be described with reference to Fig. 9. Fig. 9 is a flowchart showing the operation of the system 300 including the in-vehicle device 1.

[0110] In the system 300, after shipping, the in-vehicle device 1 starts up the software 51 in a setup mode (S1).

[0111] If it is the first time, the software 51 stores one or more pieces of temporary individual software 54a and one or more temporary vehicle parameters 55a in the area 51b.

[0112] If it is the second time or later, the software 51 stores one or more individual software 54 and one or more vehicle parameters 55 in the area 51b.

[0113] When the in-vehicle device 1 receives a plurality of positioning signals from a plurality of positioning satellites 400a to 400c via the communication line 500 (S2), it identifies its location based on the plurality of positioning signals and generates position information 56 according to the identification result. The position information 56 includes global coordinates. The global coordinates include longitude and latitude. The in-vehicle device 1 transmits the position information 56 and type information 52 to the server 100 via the communication line 200 (S3).

[0114] The server 100 waits until the information is received (No in S11), and when the information is received (Yes in S11), it determines whether or not the software 51 of the in-vehicle device 1 should be updated based on the received information (S12). The received information includes the location information 56 and the type information 52. Note that in S11, the received information may further include identification information of the in-vehicle device 1.

[0115] If it is the first time, the server 100 determines that the software 51 of the in-vehicle device 1 should be updated (Yes in S12), accesses the map information 1051 to identify the country corresponding to the location information 56, and accesses the individual software database 1052 and the vehicle parameter database 1053 (S13), and identifies and acquires update contents according to the identified country and type information 52 (S14). The update contents include individual software 54 corresponding to the location information 56 and type information 52, and vehicle parameters 55 corresponding to the location information 56 and type information 52. The server 100 transmits the update contents to the in-vehicle device 1 via the communication line 200 (S15).

[0116] If it is the second or subsequent time, the server 100 accesses the map information 1051 to identify the country corresponding to the location information 56 and determines whether the country has changed since the previous time. The server 100 may store country history information for each in-vehicle device 1, which indicates which country the in-vehicle device 1 has been in in the past. The country history information associates the identification information of the in-vehicle device 1 with the country in which the in-vehicle device 1 was previously located for multiple pieces of identification information of the in-vehicle device 1. If the identification information of the in-vehicle device 1 has been received in S11, the server 100 can determine whether the country has changed since the previous time based on the identification information of the in-vehicle device 1 and the country history information.

[0117] If the country has not changed since the previous time, the server 100 determines that an update is not necessary (No in S12), and transmits a notification of no update to the in-vehicle device 1 via the communication line 200 (S16).

[0118] If the country has changed since the previous time, the server 100 determines that an update is required (Yes in S12), and accesses the individual software database 1052 and the vehicle parameter database 1053 (S13), and identifies and acquires update contents according to the identified country and type information 52 (S14). The update contents include individual software 54 and vehicle parameters 55. The individual software 54 is associated with the type information. The vehicle parameters 55 are associated with the type information and the correspondence information. The server 100 transmits the update contents to the in-vehicle device 1 via the communication line 200 (S15).

[0119] The in-vehicle device 1 waits until information is received (No in S4), and when information is received (Yes in S4), it determines whether or not there is an update based on the received information (S5). If the received information is a notification that there is no update, the in-vehicle device 1 determines that there is no update (No in S5) and proceeds to S8. If the received information is an update, the in-vehicle device 1 determines that there is an update (Yes in S5) and performs update processing (S6).

[0120] If it is the first time, the in-vehicle device 1 identifies temporary individual software 54a whose type information matches, using type information associated with individual software 54 included in the update content as a key. The in-vehicle device 1 replaces the identified temporary individual software 54a with individual software 54. Similarly, the in-vehicle device 1 identifies vehicle parameters 55a whose type information and identification information match, using type information and identification information associated with vehicle parameters 55 included in the update content as a key. The in-vehicle device 1 replaces the identified vehicle parameters 55a with vehicle parameters 55.

[0121] If it is the second or subsequent time, the in-vehicle device 1 uses type information associated with the individual software 54 included in the update content as a key to identify the individual software 54 whose type information matches. The in-vehicle device 1 replaces the identified individual software 54 with the individual software 54 received in S4. Similarly, the in-vehicle device 1 uses type information associated with the vehicle parameters 55 included in the update content as a key to identify the vehicle parameters 55 whose type information matches. The in-vehicle device 1 replaces the identified vehicle parameters 55 with the vehicle parameters 55 received in S4.

[0122] The in-vehicle device 1 enables the update (S7), and when the setup is completed (S8), switches the software 51 from the setup mode to the normal mode (S9). After this, the in-vehicle device 1 can operate the software 51 in the normal mode.

[0123] As described above, in this embodiment, the temporary individual software 54a and the temporary vehicle parameters 53a stored in advance in the software 51 of the in-vehicle device 1 can be replaced with the individual software 54 and the vehicle parameters 53 corresponding to the country of destination. This allows one piece of software 51 to be included in each of the in-vehicle devices 1 to be shipped to multiple countries. As a result, the memory capacity for the software 51 in the in-vehicle device 1 can be reduced compared to when multiple pieces of software corresponding to the number of countries are included in the in-vehicle device 1, and the cost of the in-vehicle device 1 can be reduced.

[0124] As a first modification of the embodiment, the in-vehicle device 1 of the system 300 may be capable of holding the previous position information 57, as shown in Fig. 10. Fig. 10 is a flowchart showing the operation of the system 300 including the in-vehicle device according to the first modification of the embodiment.

[0125] After steps S1 and S2 are performed in the same manner as in the embodiment, the in-vehicle device 1 identifies a location based on a plurality of positioning signals and generates location information 56 according to the identification result. The in-vehicle device 1 stores the location information 56 therein (S21). The in-vehicle device 1 may store the location information 56 in the non-volatile memory 5 in association with the current time. The in-vehicle device 1 determines whether previous location information is available (S22). The in-vehicle device 1 searches the non-volatile memory 5 for location information 56 associated with the latest and older time. If the non-volatile memory 5 does not store location information 56 associated with the latest and older time, the in-vehicle device 1 determines that there is no previous location information (Yes in S22) and transmits the location information 56 and type information 52 to the server 100 via the communication line 200 (S3).

[0126] If location information 56 associated with an older time than the current time is stored in the non-volatile memory 5, the in-vehicle device 1 determines that there is previous location information (No in S22) and compares the previous location information 56 with the current location information 56. If there is no difference between the two (No in S23), the in-vehicle device 1 proceeds to S8. If there is a difference between the two (Yes in S23), the in-vehicle device 1 transmits the previous location information 56, the current location information 56, and the type information 52 to the server 100 via the communication line 200 (S24).

[0127] The server 100 waits until the information is received (No in S11), and when the information is received (Yes in S11), it determines whether or not the software 51 of the in-vehicle device 1 should be updated based on the received information (S25). If the information is received via S3 and S11, the received information includes the current location information 56 and type information 52. If the information is received via S24 and S11, the received information includes the previous location information 56, the current location information 56, and type information 52.

[0128] If it is the first time, the server 100 determines that the software 51 of the in-vehicle device 1 should be updated (Yes in S25), and performs S13 to S15, as in the embodiment.

[0129] If it is the second or subsequent time, this corresponds to the case where S24 and S11 are passed through, and the received content includes the previous location information 56, the current location information 56, and the type information 52. Therefore, the server 100 accesses the map information 1051, identifies the country corresponding to the previous location information 56 and the country corresponding to the current location information 56, and compares the two countries to determine whether the country has changed since the previous time. In this case, the server 100 does not need to store country history information.

[0130] If the country has not changed since the last time, the server 100 determines that an update is not necessary (No in S25) and performs S16; if the country has changed since the last time, the server 100 determines that an update is necessary (Yes in S25) and performs S13 to S15, which is the same as in the embodiment.

[0131] Thereafter, steps S4 to S9 are carried out in the same manner as in the embodiment.

[0132] In this way, according to the system 300 that can store the previous position information 57 in the vehicle-mounted device 1, the server 100 does not need to store country history information, so the amount of information that the server 100 needs to store can be reduced.

[0133] Alternatively, as a second modified example of the embodiment, the server 100 of the system 300 may be able to identify the update difference from the previous update of the software 51, as shown in Fig. 11. Fig. 11 is a flowchart showing the operation of the system 300 including the in-vehicle device according to the second modified example of the embodiment.

[0134] After steps S1 to S11 are performed in the same manner as in the first modified example of the embodiment, the server 100 determines whether or not the software 51 of the in-vehicle device 1 should be updated based on the received content (S25). If the received content goes through steps S3 and S11, the received content includes the current location information 56 and type information 52. If the received content goes through steps S24 and S11, the received content includes the previous location information 56, the current location information 56, and type information 52.

[0135] If it is the first time, the server 100 determines that the software 51 of the in-vehicle device 1 should be updated (Yes in S25), accesses the map information 1051 to identify the country corresponding to the location information 56, accesses the individual software database 1052 and the vehicle parameter database 1053 (S13), identifies the current update content based on the identified country and type information 52, and identifies and acquires the update difference based on the current update content (S31). The update difference is the difference between the previous update content and the current update content, but since this is the first time and the previous update content was zero, it is essentially the same as the current update content. The server 100 transmits the update difference to the in-vehicle device 1 via the communication line 200 (S32).

[0136] If it is the second or subsequent time, this corresponds to the case where S24 and S11 are passed through, and the received content includes the previous location information 56, the current location information 56, and the type information 52. Therefore, the server 100 accesses the map information 1051, identifies the country corresponding to the previous location information 56 (previous country) and the country corresponding to the current location information 56 (current country), and compares the two countries to determine whether the country has changed since the previous time. In this case, the server 100 does not need to store country history information.

[0137] If the country has not changed since the previous time, the server 100 determines that updating is not necessary (No in S25) and performs S16, which is the same as in the first modified example of the embodiment.

[0138] If the country has changed since the previous time, the server 100 determines that an update is required (Yes in S25), identifies the previous update content according to the previous country and type information 52, and identifies the current update content according to the current country and type information 52. The server 100 calculates the difference between the previous update content and the current update content, and identifies and acquires the update difference. The update difference includes an individual software difference and a vehicle parameter difference. The individual software difference is the difference between the previous individual software and the current individual software. The vehicle parameter difference is the difference between the previous vehicle parameters and the current vehicle parameters. The server 100 transmits the update difference to the in-vehicle device 1 via the communication line 200 (S32).

[0139] After that, steps S4 and S5 are performed in the same manner as in the first modified example of the embodiment, and then the in-vehicle device 1 performs update processing using the update difference (S41).

[0140] If it is the first time, the update difference is substantially the same as the update content of S6. The in-vehicle device 1 identifies temporary individual software 54a whose type information matches, using type information associated with individual software 54 included in the update difference as a key. The in-vehicle device 1 replaces the identified temporary individual software 54a with individual software 54. Similarly, the in-vehicle device 1 identifies vehicle parameters 55a whose type information and specification information match, using type information and specification information associated with vehicle parameters 55 included in the update difference as a key. The in-vehicle device 1 replaces the identified vehicle parameters 55a with vehicle parameters 55.

[0141] If it is the second or subsequent time, the in-vehicle device 1 identifies the individual software 54 with matching type information using type information associated with the individual software difference included in the update difference as a key. The in-vehicle device 1 updates the identified individual software 54 with the individual software difference. Similarly, the in-vehicle device 1 identifies the vehicle parameters 55 with matching type information using type information associated with the vehicle parameter difference included in the update content as a key. The in-vehicle device 1 updates the identified vehicle parameters 55 with the vehicle parameter difference.

[0142] Thereafter, steps S7 to S9 are carried out in the same manner as in the first modified example of the embodiment.

[0143] In this way, according to the system 300, in which the server 100 can identify the update difference from the previous time for the software 51, it is only necessary to transmit the update difference from the server 100 to the vehicle-mounted device 1, thereby reducing the amount of information to be transmitted from the server 100 to the vehicle-mounted device 1.

[0144] Alternatively, as a third modified example of the embodiment, the update content may be identified in two stages in the server 100 as shown in Fig. 12. Fig. 12 is a flowchart showing the operation of the system 300 including the in-vehicle device 1 according to the third modified example of the embodiment.

[0145] After steps S1 to S11 are performed in the same manner as in the embodiment, the server 100 determines whether or not the software 51 of the in-vehicle device 1 should be updated, depending on the received content (S12).

[0146] If it is the first time, the server 100 determines that the software 51 of the in-vehicle device 1 should be updated (Yes in S12), accesses the map information 1051 to identify the country corresponding to the location information 56, accesses the individual software database 1052 and the vehicle parameter database 1053 (S51), and identifies and acquires communication settings according to the identified country and type information 52 (S52). The communication settings include individual software 5 for communication corresponding to the location information 56 and type information 52, and vehicle parameters 55 for communication corresponding to the location information 56 and type information 52. The server 100 transmits the update contents to the in-vehicle device 1 via the communication line 200 (S53).

[0147] If it is the second or subsequent time, the server 100 accesses the map information 1051 to identify the country corresponding to the location information 56 and determines whether the country has changed since the previous time. The server 100 may store country history information for each in-vehicle device 1, which indicates which country the in-vehicle device 1 has been in in the past. The country history information associates the identification information of the in-vehicle device 1 with the country in which the in-vehicle device 1 was previously located for multiple pieces of identification information of the in-vehicle device 1. If the identification information of the in-vehicle device 1 has been received in S11, the server 100 can determine whether the country has changed since the previous time based on the identification information of the in-vehicle device 1 and the country history information.

[0148] If it is the second or subsequent time, the server 100 accesses the map information 1051 to identify the country corresponding to the location information 56 and determines whether the country has changed since the previous time. The server 100 may store country history information for each in-vehicle device 1, which indicates which countries the in-vehicle device 1 has been in in the past.

[0149] If the country has not changed since the previous time, the server 100 determines that an update is not necessary (No in S12), and transmits a notification of no update to the in-vehicle device 1 via the communication line 200 (S16).

[0150] If the country has changed since the previous time, the server 100 determines that an update is required (Yes in S12), and accesses the individual software database 1052 and the vehicle parameter database 1053 (S51), and identifies and acquires communication settings according to the identified country and type information 52 (S52). The communication settings include the individual software 5 for communication according to the location information 56 and the type information 52, and the vehicle parameters 55 for communication according to the location information 56 and the type information 52. The server 100 transmits the update contents to the in-vehicle device 1 via the communication line 200 (S53).

[0151] The in-vehicle device 1 waits until it receives information (No in S4), and when it receives information (Yes in S4), it determines whether or not there is an update based on the received information (S45). If the received information is a notification that there is no update, the in-vehicle device 1 determines that there is no update (No in S45) and proceeds to S8. If the received information is an update, the in-vehicle device 1 determines that there is an update (Yes in S45), and generates communication parameters for the in-vehicle device 1 based on the vehicle parameters included in the update (S61).

[0152] The vehicle-mounted device 1 transmits the communication parameters of the vehicle-mounted device 1 to the server 100 via the communication line 200 (S62).

[0153] When the server 100 receives the communication parameters of the in-vehicle device 1 from the in-vehicle device 1 via the communication line 200 (S54), the server 100 generates communication parameters of the server 100 accordingly and transmits them to the in-vehicle device 1 via the communication line 200 (S55). The server 100 establishes communication settings according to the communication parameters of the in-vehicle device 1 and the communication parameters of the server 100 (S56).

[0154] When the in-vehicle device 1 receives the communication parameters of the server 100 from the server 100 via the communication line 200 (S54), the in-vehicle device 1 establishes communication settings according to the communication parameters of the in-vehicle device 1 and the communication parameters of the server 100 (S64).

[0155] If it is the first time, the in-vehicle device 1 identifies temporary individual software for communication 54a having matching type information using type information associated with the individual software for communication 54 included in the communication settings as a key. The in-vehicle device 1 replaces the identified temporary individual software for communication 54a with the individual software for communication 54. Similarly, the in-vehicle device 1 identifies vehicle parameters for communication 55a having matching type information and specifying information using type information and specifying information associated with vehicle parameters for communication 55 included in the communication settings as a key. The in-vehicle device 1 replaces the identified vehicle parameters for communication 55a with vehicle parameters for communication 55.

[0156] If it is the second or subsequent time, the in-vehicle device 1 identifies the individual software for communication 54 having matching type information using type information associated with the individual software for communication 54 included in the communication settings as a key. The in-vehicle device 1 replaces the identified individual software for communication 54 with the individual software for communication 54 received in S4. Similarly, the in-vehicle device 1 identifies the vehicle parameters for communication 55 having matching type information using type information associated with the vehicle parameters for communication 55 included in the communication settings as a key. The in-vehicle device 1 replaces the identified vehicle parameters for communication 55 with the vehicle parameters for communication 55 received in S4.

[0157] That is, the in-vehicle device 1 performs the update process for communication and the validation of the update in advance.

[0158] On the other hand, after establishing the communication settings (S56), the server 100 accesses the individual software database 1052 and the vehicle parameter database 1053 (S57), and identifies and acquires other update contents according to the identified country and type information 52 (S58). The other update contents include individual software 54 other than for communication and vehicle parameters 55 other than for communication. The individual software 54 other than for communication is associated with the type information. The vehicle parameters 55 other than for communication are associated with the type information and the correspondence information. The server 100 transmits the other update contents to the in-vehicle device 1 via the communication line established by the communication settings (S59).

[0159] When the in-vehicle device 1 receives the other update content, it performs the other update process in accordance with the other update content (S65).

[0160] If it is the first time, the in-vehicle device 1 identifies temporary individual software 54a whose type information matches, using type information associated with individual software 54 included in the other update content as a key. The in-vehicle device 1 replaces the identified temporary individual software 54a with the individual software 54. Similarly, the in-vehicle device 1 identifies vehicle parameters 55a whose type information and identification information match, using type information and identification information associated with vehicle parameters 55 included in the other update content as a key. The in-vehicle device 1 replaces the identified vehicle parameters 55a with the vehicle parameters 55.

[0161] If it is the second or subsequent update, the in-vehicle device 1 identifies individual software 54 having matching type information using type information associated with the individual software 54 included in the other update content as a key. The in-vehicle device 1 replaces the identified individual software 54 with the individual software 54 received in S4. Similarly, the in-vehicle device 1 identifies vehicle parameters 55 having matching type information using type information associated with vehicle parameters 55 included in the other update content as a key. The in-vehicle device 1 replaces the identified vehicle parameters 55 with the vehicle parameters 55 received in S4.

[0162] The in-vehicle device 1 validates the other updates (S66), after which S8 and S9 are performed in the same manner as in the embodiment.

[0163] In this way, according to the system 300 in which the update contents in the server 100 are identified in two stages, communication can be performed using a communication line with a wide bandwidth secured in S59, for example, thereby making the transmission of information from the server 100 to the in-vehicle device 1 more efficient.

[0164] Alternatively, as a fourth modified example of the embodiment, the update contents may be specified on the in-vehicle device 1i side.

[0165] A system 300i including an in-vehicle device 1i can be configured in terms of hardware as shown in Fig. 13. Fig. 13 is a diagram showing the hardware configuration of a system 300i including an in-vehicle device 1i according to a fourth modified example of the embodiment.

[0166] In the system 300i, the nonvolatile memory 5i of the in-vehicle device 1i further stores map information 58i, an individual software database 59i, and a vehicle parameter database 60i. The map information 58i, the individual software database 59i, and the vehicle parameter database 60i are similar to the map information 1051, the individual software database 1052, and the vehicle parameter database 1053 in the embodiment, respectively.

[0167] The storage 105i of the server 100i stores an individual software library 1052i and a vehicle parameter library 1053i instead of the individual software database 1052 and the vehicle parameter database 1053 (see FIG. 2), but does not store the map information 1051. The individual software library 1052i includes identification information of individual software, as shown enclosed by dotted lines in FIGS. 4 and 5, but the association between the information and other information is omitted. The vehicle parameter library 1053i includes identification information of vehicle parameters, as shown enclosed by dotted lines in FIGS. 4 and 5, but the association between the information and other information is omitted.

[0168] A system 300i including an in-vehicle device 1i may be functionally configured as shown in Fig. 14. Fig. 14 is a diagram showing the functional configuration of a system 300i including an in-vehicle device 1i according to a fourth modified example of the embodiment.

[0169] In the system 300i, the in-vehicle device 1i further includes a position information determination unit 19i, an individual software identification unit 20i, and a vehicle parameter identification unit 21i. The functions of the position information determination unit 19i, the individual software identification unit 20i, and the vehicle parameter identification unit 21i are similar to the functions of the position information determination unit 115, the individual software identification unit 116, and the vehicle parameter identification unit 117 in the embodiment, respectively.

[0170] The server 100i does not include the location information determination unit 115, the individual software identification unit 116, and the vehicle parameter identification unit 117.

[0171] Furthermore, the operation of the system 300i differs from that of the embodiment in the following respects, as shown in Fig. 15. Fig. 15 is a flowchart showing the operation of the system 300i including the in-vehicle device 1i according to the fourth modification of the embodiment.

[0172] After steps S1 and S2 are performed in the same manner as in the embodiment, the in-vehicle device 1i identifies its location based on the plurality of positioning signals, and generates position information 56 according to the identification result. The in-vehicle device 1i determines whether or not the software 51 should be updated according to the position information 56 (S71).

[0173] If it is the first time, the in-vehicle device 1i determines that the software 51 should be updated (Yes in S71), accesses the map information 58i to identify the country corresponding to the location information 56, and accesses the individual software database 59i and the vehicle parameter database 60i (S72). Then, in accordance with the identified country and type information 52, the in-vehicle device 1i identifies and generates an update request (S73). The update request includes a request to acquire the individual software 54 corresponding to the location information 56 and the type information 52, and a request to acquire the vehicle parameters 55 corresponding to the location information 56 and the type information 52. The request to acquire the individual software 54 includes identification information of the individual software 54 to be acquired. The request to acquire the vehicle parameters 55 includes identification information of the vehicle parameters 55 to be acquired. The in-vehicle device 1i transmits the update request to the server 100i via the communication line 200 (S74).

[0174] If it is the second or subsequent time, the in-vehicle device 1i accesses the map information 58i to identify the country corresponding to the location information 56 and determines whether the country has changed since the previous time. The in-vehicle device 1i may store country history information indicating which countries the in-vehicle device 1i has been in in the past. The server 100i can determine whether the country has changed since the previous time based on the country history information.

[0175] The server 100i waits until an update request is received (No in S11), and when the update request is received (Yes in S11), the server 100i accesses the individual software library 1052i and the vehicle parameter library 1053i in response to the update request (S81) and acquires the update contents (S82). The update contents include the individual software 54 in response to the update request and the vehicle parameters 55 in response to the update request. The server 100i transmits the update contents to the in-vehicle device 1i via the communication line 200 (S15).

[0176] After this, steps S4 to S9 are performed in the in-vehicle device 1i in the same manner as in the embodiment.

[0177] In this way, according to the system 300i in which the update contents are specified on the vehicle-mounted device 1i side, the amount of information that needs to be held in the server 100i can be reduced.

[0178] Alternatively, as a fifth modified example of the embodiment, the second modified example of the embodiment and the fourth modified example of the embodiment may be combined as shown in Fig. 16. Fig. 16 is a flowchart showing the operation of a system 300i including an in-vehicle device 1i according to the fifth modified example of the embodiment.

[0179] After steps S1 to S21 are performed in the same manner as in the second modified example of the embodiment, the in-vehicle device 1i identifies its location based on the plurality of positioning signals, and generates position information 56 according to the identification result. The in-vehicle device 1i determines whether or not the software 51 should be updated according to the position information 56 (S71).

[0180] If it is the first time, the in-vehicle device 1i determines that the software 51 should be updated (Yes in S71), and determines whether previous position information is available (S22).

[0181] If there is no previous location information (Yes in S22), the in-vehicle device 1i accesses the map information 58i to identify the country corresponding to the location information 56, and accesses the individual software database 59i and the vehicle parameter database 60i (S72), and identifies and generates an update request according to the identified country and type information 52 (S73). The update request includes a request to acquire the individual software 54 corresponding to the location information 56 and the type information 52, and a request to acquire the vehicle parameters 55 corresponding to the location information 56 and the type information 52. The request to acquire the individual software 54 includes identification information of the individual software 54 to be acquired. The request to acquire the vehicle parameters 55 includes identification information of the vehicle parameters 55 to be acquired. The in-vehicle device 1i transmits the update request to the server 100i via the communication line 200 (S74).

[0182] If the in-vehicle device 1i has the previous location information (No in S22) and there is no difference between the previous location information 56 and the current location information 56 (No in S23), the process proceeds to S8. If there is a difference between the two (Yes in S23), the in-vehicle device 1i accesses the map information 58i to identify the country corresponding to the location information 56, accesses the individual software database 59i and the vehicle parameter database 60i (S91), and identifies and generates an update request according to the identified country and type information 52 (S92). The update request includes a request to acquire an individual software difference corresponding to the location information 56 and the type information 52, and a request to acquire a vehicle parameter difference corresponding to the location information 56 and the type information 52. The request to acquire the individual software difference includes identification information of the individual software 54 from which the difference is to be acquired. The request to acquire the vehicle parameter difference includes identification information of the vehicle parameters 55 from which the difference is to be acquired.

[0183] If it is the second or subsequent time, the in-vehicle device 1i accesses the map information 58i to identify the country corresponding to the location information 56 and determines whether the country has changed since the previous time. The in-vehicle device 1i may store country history information indicating which countries the in-vehicle device 1i has been in in the past. The server 100i can determine whether the country has changed since the previous time based on the country history information.

[0184] The server 100i waits until an update request is received (No in S11). When the update request is received (Yes in S11), the server 100i accesses the individual software library 1052i and the vehicle parameter library 1053i in response to the update request (S81) and acquires the update contents (S101). If the update request includes a request to acquire the individual software 54 and a request to acquire the vehicle parameters 55, the update contents include the individual software 54 in response to the request to acquire the individual software 54 and the vehicle parameters 55 in response to the request to acquire the vehicle parameters 55. If the update request includes a request to acquire the individual software difference and a request to acquire the vehicle parameter difference, the update contents include the individual software difference in response to the request to acquire the individual software difference and the vehicle parameter difference in response to the request to acquire the vehicle parameter difference. The server 100i transmits the update contents to the in-vehicle device 1i via the communication line 200 (S102).

[0185] After that, after steps S4 to S5 are performed in the same manner as in the second modified example of the embodiment, the in-vehicle device 1i performs an update process in accordance with the update contents (S111). If the update contents include the individual software 54 and the vehicle parameters 55, the in-vehicle device 1i replaces the temporary individual software 54a with the individual software 54 and replaces the temporary vehicle parameters 55a with the vehicle parameters 55. If the update contents include an individual software difference and a vehicle parameter difference, the in-vehicle device 1i updates the individual software 54 with the individual software difference and updates the vehicle parameters 55 with the vehicle parameter difference.

[0186] Thereafter, steps S7 to S9 are carried out in the same manner as in the second modified example of the embodiment.

[0187] In this way, according to the system 300i in which the update contents are specified on the vehicle-mounted device 1i side, the amount of information that needs to be held in the server 100i can be reduced.

[0188] Although several embodiments of the present invention have been described, these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included within the scope and spirit of the invention, as well as within the scope of the invention described in the claims and their equivalents. [Explanation of symbols]

[0189] 1,1i In-vehicle device 100,100i servers 300,300i system

Claims

1. a first receiving unit that receives a first positioning signal; a storage unit that stores software, the software including a first area and a second area, the first area storing common software, and the second area storing first individual software and first vehicle parameters; a second receiving unit that receives second individual software corresponding to first position information according to the first positioning signal and second vehicle parameters corresponding to the first position information; a controller capable of replacing the first individual software in the second area of ​​the software with the second individual software and replacing the first vehicle parameters in the second area with the second vehicle parameters; An in-vehicle device comprising:

2. a transmitting unit that transmits the first location information to a server; The second receiving unit receives the second individual software and the second vehicle parameters from the server. The in-vehicle device according to claim 1 .

3. the storage unit further stores the first position information; the first receiver further receives a second positioning signal; the transmitting unit transmits the first location information and second location information corresponding to the second positioning signal to the server; the second receiving unit receives, from the server, software difference information between the second individual software and third individual software corresponding to the second location information, and parameter difference information between the second vehicle parameters and third vehicle parameters corresponding to the second location information; The controller updates the second individual software in the second area to the third individual software in accordance with the software difference information, and updates the second vehicle parameters in the second area to the third vehicle parameters in accordance with the parameter difference information. The in-vehicle device according to claim 2 .

4. the first receiving unit further receives second location information; the transmitting unit transmits the first location information and the second location information to the server; the second receiving unit receives, from the server, third individual software corresponding to the second location information and third vehicle parameters corresponding to the second location information; The controller updates the second individual software in the second area to the third individual software, and updates the second vehicle parameters in the second area to the third vehicle parameters. The in-vehicle device according to claim 2 .

5. The common software includes: at least one of an application program interface, an operating system, and a hardware abstraction layer; The second individual software includes: at least one of language support software, map software, radio software, and navigation software; The second vehicle parameter is The parameter includes at least one of a parameter related to a radio frequency, a parameter related to a radio hardware specification, a parameter related to a handle specification, and a parameter related to wireless communication. The in-vehicle device according to claim 1 .

6. a first receiving unit that receives a first positioning signal; a first storage unit that stores software, first management information, and second management information, the software including a first area and a second area, the first area storing common software, the second area storing first individual software and first vehicle parameters, the first management information including correspondence between the individual software and regional information for a plurality of pieces of regional information, and the second management information including correspondence between vehicle parameters and regional information for a plurality of pieces of regional information; a transmitter that transmits to a server an update request including a request for second individual software corresponding to first position information according to the first positioning signal and second vehicle parameters corresponding to the first position information; a second receiving unit that receives the second individual software and the second vehicle parameters from the server; a controller that replaces the first individual software in the second area of ​​the software with the second individual software and replaces the first vehicle parameters in the second area with the second vehicle parameters; An in-vehicle device comprising:

7. An in-vehicle device according to any one of claims 1 to 6; a server capable of communicating with the in-vehicle device; A system with.

Images