Vehicle management system and information processing device

Abstract

To provide a vehicle management system and an information processing device that enable a sales company to individually set dealer options and the like in a vehicle shipped from a vehicle manufacturer.SOLUTION: A vehicle management system according to the present invention includes: a vehicle that includes an electronic control device in which software common to multiple vehicles is stored, the electronic control device being set to vehicle-specific specifications by setting software parameters; a management server that manages the software parameters; and a dealer-side device that updates the parameters managed by the management server after the vehicle is shipped from a factory of a vehicle manufacturer. The parameters stored in the electronic control device of the vehicle are overwritten to the parameters updated by the dealer-side device.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a vehicle management system and an information processing device. [Background technology]

[0002] In recent years, advances have been made in technology that integrates the control of various vehicle components into a single electronic control unit (ECU), making it possible to control cockpit-related in-vehicle devices such as a standalone navigation system, display audio, and meters with a single ECU.

[0003] In existing systems, vehicle specifications vary depending on the user's wishes, so software is created at the vehicle manufacturer's factory according to the combination of vehicle specifications. Because the software created varies depending on the vehicle specifications desired by the user, software with matching combinations of vehicle specifications is managed with the same management number, and the same combination of software is stored in electronic control units with the same management number. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2007-11466 Summary of the Invention [Problem to be solved by the invention]

[0005] As described above, vehicle manufacturer factories manage electronic control units with different control numbers depending on the combination of software stored in the electronic control units. Therefore, if a vehicle manufacturer attempts to store software for different vehicle specifications in an electronic control unit at its factory, the number of control numbers for the electronic control units will increase, making management more complicated and requiring more space to store the electronic control units separated by control number.

[0006] Furthermore, when the control of cockpit-related in-vehicle equipment such as dealer options is integrated, software for dealer options and the like will also need to be stored in the electronic control unit, and as the number of software combinations increases, management will become more complicated and the storage space problems will become even greater.

[0007] An object of the present invention is to provide a vehicle management system and information processing device that allows a dealer to individually set dealer options and the like for a vehicle shipped from a vehicle manufacturer. [Means for solving the problem]

[0008] In order to achieve the above-mentioned object, the vehicle management system of the present invention includes a vehicle having an electronic control unit in which software common to multiple vehicles is stored and which is configured to vehicle-specific specifications by setting parameters of the software, a management server that manages the parameters of the software, and a sales company device that updates the parameters managed by the management server after the vehicle is shipped from the vehicle manufacturer's factory, and is characterized in that the parameters stored in the electronic control unit of the vehicle are rewritten with the parameters updated by the sales company device. [Effects of the Invention]

[0009] According to the present invention, the dealer can individually set dealer options and the like for vehicles shipped from the vehicle manufacturer. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram illustrating an outline of a vehicle management system according to an embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of the configuration of an electronic control device of a vehicle. [Figure 3] FIG. 3 is an explanatory diagram showing an example of the configuration of a parameter string. [Figure 4]FIG. 4 is a diagram showing an example of the configuration of write data to be written to an electronic control unit (ECU). [Figure 5] FIG. 5 is a diagram illustrating an example of the configuration of the specification storage table. [Figure 6] FIG. 6 is a diagram showing an example of a vehicle production flow. [Figure 7] FIG. 7 is a diagram showing an example of a dealer option purchase flow. [Figure 8] FIG. 8 is a schematic explanatory diagram for replacing an electronic control unit. [Figure 9] FIG. 9 is a diagram showing an example of a flow of attaching the supply items. [Figure 10] FIG. 10 is a diagram showing an example of an order table of the sales server. [Figure 11] FIG. 11 is a diagram showing the flow of management of electronic control units (ECUs) in a vehicle production factory. DETAILED DESCRIPTION OF THE INVENTION

[0011] DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS A vehicle management system and an information processing device according to an embodiment of the present invention will be described in detail below with reference to the accompanying drawings.

[0012] <Embodiment> In this embodiment, a method for setting vehicle specifications in an electronic control unit of a vehicle will be described. In this embodiment, setting vehicle specifications in an electronic control unit includes setting vehicle specifications in a vehicle production factory and updating vehicle specification settings performed on a vehicle after shipment by a vehicle sales company (equivalent to a sales company). In the following, the vehicle specifications set in the electronic control unit at the vehicle production factory will be referred to as first vehicle specifications, and the vehicle specifications updated on the electronic control unit at the vehicle sales company will be referred to as second vehicle specifications.

[0013] In this embodiment, vehicle specification settings in the electronic control unit are updated by writing parameter values ​​to the electronic control unit, such as enabling or disabling corresponding software. Therefore, the vehicle is shipped with software corresponding to the items whose settings will be updated later stored in the vehicle's electronic control unit. The parameter values ​​may be written not only as enabling or disabling, but also as yes or no. For example, the camera to be used to capture the vehicle's surroundings from at least one of the front camera, rear camera, left side camera, and right side camera that monitor the vehicle 4 may be set as "yes" or "no." In this case, possible combinations include using only the front camera, the front camera and rear camera, the front camera, rear camera, and left and right side cameras, or no camera. The captured images of the vehicle's surroundings may be recorded in a storage unit, such as an on-board drive recorder or a memory in the ECU, and the camera may be selected as the drive recorder target camera by setting "yes" or "no."

[0014] Furthermore, there is no particular limit to the number of pieces of software stored in the electronic control unit. It is possible to limit it to specific items, or it is possible to store software for all specifications, including all dealer options.

[0015] In the following description, the items for which settings are to be updated are assumed to be dealer option items, but other items may also be updated if they are items that are permitted to be changed later.

[0016] 1 is a diagram illustrating an outline of a vehicle management system according to an embodiment of the present invention, showing the main components related to the vehicle management systems of a vehicle production factory 1, a vehicle manufacturer 2, and a vehicle sales company 3.

[0017] The vehicle production factory 1 assembles parts and configures electronic control devices on a vehicle production line 10 before shipping vehicles 4. A factory server 11 shown in the vehicle production factory 1 is an information processing device that comprehensively manages the production of vehicles 4. The factory server 11 is connected to the vehicle production line 10 so as to be able to communicate with each other.

[0018] The first diagnostic device 12 shown in the vehicle production line 10 is an information processing device that diagnoses and configures the electronic control unit. The first diagnostic device 12 performs configuration by communicating with a communication unit for diagnosing the electronic control unit.

[0019] Vehicle manufacturer 2 has a sales server 21, a specification storage server 22, and a production instruction generation unit 23. The sales server 21, the specification storage server 22, and the production instruction generation unit 23 are constructed on an internal network of vehicle manufacturer 2. In addition to these, a traceability information management server that manages traceability information, a parts supply unit that supplies parts, and the like are also constructed on the internal network, but are not shown here.

[0020] The sales server 21 is an information processing device that manages order information such as the model of the vehicle 4 and dealer options. The sales server 21 may be installed outside the vehicle manufacturer 2, in which case it may communicate various information with the specification storage server 22 and the production instruction generation unit 23 via a network. The specification storage server 22 is an information processing device that changes the vehicle specification setting items 220 (see FIG. 3) based on the purchase information of the vehicle 4 and stores the latest setting information for the vehicle. The sales server 21 and the specification storage server 22 correspond to the "management server." The production instruction generation unit 23 is an information processing device that generates production instruction information for the vehicle. The production instruction information is instruction information required to produce the vehicle 4 according to the model of the vehicle 4. For example, in the case of a two-wheel drive vehicle, the information instructs the vehicle production factory 1 to assemble parts for the two-wheel drive vehicle.

[0021] A vehicle dealership 3 corresponds to any one of the stores that sell vehicles. Each vehicle dealership 3 has a vehicle dealership terminal 31, which corresponds to a "vehicle dealership device," and a second diagnostic device 32. The vehicle dealership terminal 31 is an information processing device that accepts vehicle purchases at the store.

[0022] The second diagnostic device 32 is an information processing device that diagnoses and configures the electronic control device of the vehicle 4 on the side of the vehicle dealership 3. The second diagnostic device 32 communicates with a communication unit for diagnosing the electronic control device of the vehicle 4 and configures the device.

[0023] The communication network N1 and the communication network N2 shown in FIG. 1 are the Internet, a dedicated line, or the like.

[0024] The information processing device applied to each device is, for example, a computer-configured information processing device in which a CPU (Central Processing Unit), a memory such as a ROM (Read Only Memory) or a RAM (Random Access Memory) or a storage unit, a communication unit, etc. are connected via a bus so that they can communicate with each other. Other information processing devices described later will also be described using a computer-configured information processing device as an example.

[0025] FIG. 2 is a diagram showing an example of the configuration of an electronic control unit of a vehicle 4. The electronic control unit (ECU) 41 shown in FIG. 2 is, for example, an electronic control unit called an HCU (HMI Control Unit) or an integrated ECU (Electronic Control Unit) that integrates the control of each part of the vehicle into a single electronic control unit. The electronic control unit (ECU) 41 can also integrate the control of cockpit-related on-board equipment of the vehicle 4, and can also control a standalone navigation system, display audio, meter, and other cockpit-related on-board equipment. If there are any changes to dealer options, these can be changed by setting parameters in the electronic control unit (also referred to as HCU) 41.

[0026] 2 stores a software group (software 1, software 2, ...) 40 for all specifications, including all dealer options. The electronic control unit (ECU) 41 is set to a predetermined vehicle specification by setting a parameter column 200 corresponding to the vehicle specification items. In addition, by switching the item corresponding to the dealer option in the parameter column 200 between enabled and disabled, the software corresponding to the dealer option in the software group 40 is enabled or disabled.

[0027] Each unit 42 shown in Fig. 2 is connected to an electronic control unit (ECU) 41 via a CGW (Central Gateway) 43. Each unit 42 is a vehicle control unit (VCU) that controls the brakes, an electronic fuel injection system (EFI) that controls devices related to the drive source such as the engine, etc. Each unit 42 and the CGW 43 are connected by a controller area network (CAN). The electronic control unit (ECU) 41 and the CGW 43 are connected by a CAN.

[0028] The CGW 43 is a control unit that controls multiple communication paths, and has a communication unit for diagnosing the first diagnostic device 12 and the second diagnostic device 32. The first diagnostic device 12 and the second diagnostic device 32 are connected to the communication unit for diagnosis of the CGW 43 via a CAN, and communicate with each unit 42 and the electronic control unit (ECU) 41.

[0029] In this embodiment, the diagnostic devices (first diagnostic device 12 and second diagnostic device 32) are mainly used to access electronic control unit (ECU) 41 and read and write predetermined information. Writing includes writing parameter values ​​to parameter column 200.

[0030] 3 is an explanatory diagram showing an example of the configuration of the parameter column 200. The parameter column 200 has a setting item 210 for a first vehicle specification and a setting item 220 for a second vehicle specification.

[0031] The setting items 210 for the first vehicle specifications include an item for setting the type relationship of the vehicle 4 and an item for setting manufacturer options. The items for setting the type relationship of the vehicle 4 are items related to regulations, such as OEM information 211 and tire diameter 212. For each parameter in the item for setting the type relationship of the vehicle 4 and the item for setting manufacturer options, a parameter value (A0, A1, etc.) corresponding to the first vehicle specification is selectively set.

[0032] The second vehicle specification setting items 220 are items including dealer options such as a navigation system 221 and a television 222. These items can be enabled / disabled later upon application. Each of these parameters is set with a parameter value (such as A0 (disabled) or A1 (enabled)) that switches the configuration between enabled and disabled based on the second vehicle specification.

[0033] Fig. 4 is a diagram showing an example of the configuration of write data to be written to the electronic control unit (ECU) 41. Fig. 4 shows the configuration of write data d3 for setting a first vehicle specification to be written to the electronic control unit (ECU) 41, and the configuration of write data d5 for setting a second vehicle specification to be written to the electronic control unit (ECU) 41.

[0034] As an example, the write data for setting the first vehicle specification and the write data for setting the second vehicle specification are both composed of data strings of parameter values ​​corresponding to the parameter strings. In Fig. 4, the parameter strings are shown next to the data strings, and each item is associated with each other, so that the correspondence between the parameter strings and the data strings can be seen.

[0035] The write data d3 for setting the first vehicle specifications is write data acquired at the vehicle production factory 1. For confirmation, an identification parameter value indicating that the data is write item information for the first vehicle specifications is set at the beginning of the data string.

[0036] Note that each parameter value corresponding to the first vehicle specification data sequence 110 is set based on the input method of the first vehicle specification setting item 210 (see FIG. 3). The parameter value of data 111 is set based on the input method of the first vehicle specification setting item 211 (see FIG. 3). The parameter value of data 112 is set based on the input method of the first vehicle specification setting item 212 (see FIG. 3). Each parameter value of data sequence 113 is set based on the input method of the first vehicle specification setting item 213 (see FIG. 3).

[0037] The write data d5 for setting the second vehicle specifications is data that is written and acquired by the vehicle production factory 1 and the vehicle sales company 3. For confirmation, an identification parameter value indicating that the data is write item information for the second vehicle specifications is set at the beginning of the data string.

[0038] Note that each parameter value corresponding to data sequence 120 of the second vehicle specification is set based on the input method of setting item 220 of the second vehicle specification (see FIG. 3). The parameter value of data 121 is set based on the input method of setting item 221 of the second vehicle specification (see FIG. 3). The parameter value of data 122 is set based on the input method of setting item 222 of the second vehicle specification (see FIG. 3).

[0039] Here, the configuration of the write data acquired at the vehicle production factory 1 and the configuration of the write data acquired at the vehicle sales company 3 have been explained separately, but the configuration may also include all of the items set at the vehicle production factory 1 and the items set at the vehicle sales company 3.

[0040] Therefore, the vehicle specification settings made to the electronic control unit 41 may have different items between the first vehicle specification and the second vehicle specification, or some or all of the items may overlap between the first vehicle specification and the second vehicle specification.

[0041] Any items that overlap between the first vehicle specification setting and the second vehicle specification setting are updated so that the second vehicle specification setting is the latest. If a new vehicle specification is set after the second vehicle specification setting, the new vehicle specification setting is always updated so that it is the latest.

[0042] The setting of the electronic control unit of the vehicle may be performed by collectively setting the corresponding items of the electronic control unit to enabled or disabled, or by individually setting the items.

[0043] By writing data strings as described above, it is possible to write data for each item all at once.

[0044] Fig. 5 is a diagram showing an example of the configuration of the specification storage table 100. As shown in Fig. 5, the specification storage table 100 has a table configuration in which "VIN information", "serial number", "specification information 1", and "specification information 2" are associated with each other. "Specification information 1" corresponds to the first specification information, and a parameter value is set for each item. "Specification information 2" corresponds to the second specification information, and a parameter value is set for each item.

[0045] FIG. 5 also shows the setting state after the setting has been updated using the second specification information, and the state before and after the update will be described later.

[0046] Next, the vehicle production flow shown in Fig. 6 and the dealer option purchase flow shown in Fig. 7 will be explained with reference to Fig. 1. The dotted arrows in Fig. 1 indicate the data flow when setting the first vehicle specification and the second vehicle specification at the time of vehicle purchase (order), and the solid arrows indicate the data flow when setting the second vehicle specification by purchasing a dealer option, etc. First, the vehicle production flow in Fig. 6 will be explained with reference to the dotted arrows in Fig. 1.

[0047] First, when a customer purchases a vehicle, the vehicle dealer terminal 31 transmits the vehicle specification information D1 to the sales server 21, and the sales server 21 receives the vehicle specification information D1 (step S1).

[0048] Next, the sales server 21 processes the order for the vehicle based on the received vehicle specification information D1, and instructs the production instruction generation unit 23 to generate production instruction information etc. for the vehicle specification information D1 (step S2).

[0049] The production instruction generation unit 23 generates converted data D2 by converting the vehicle purchase information into production instruction information, and transmits the converted data D2 to the factory server 11 (step S3). The converted data D2 is data that adds VIN (Vehicle Identification Number) information to generated information (called VLT) such as vehicle specifications and production schedules, including model and option information.

[0050] Upon receiving the converted data D2, the factory server 11 generates production instruction information D3 for the vehicle 4 from the converted data D2 and stores the information in the storage unit master 11-1. The factory server 11 also communicates with the vehicle production line 10 based on the production instruction information D3 stored in the master 11-1 to issue production instructions to the vehicle production line 10 (step S4).

[0051] Thereafter, the first diagnostic device 12 converts the production instruction information D3 into first write data D3-1, and writes the first write data D3-1 into the electronic control device 41 (see FIG. 2) of the vehicle 4 (step S5).

[0052] Here, the first write data D3-1 is write data converted from the production instruction information D3 and VIN information. The write data are write data d3 (see FIG. 4) for setting the first vehicle specifications and write data d5 (see FIG. 4) for setting the second vehicle specifications. By writing the first write data D3-1 to the electronic control unit 41, parameter values ​​for each item of the first vehicle specification setting items 210 (see FIG. 3) are set in the parameter column 200 (see FIG. 2). Furthermore, parameter values ​​for each item of the second vehicle specification setting items 220 (see FIG. 3) are set in the parameter column 200 (see FIG. 2). In this way, the first vehicle specification setting items 210 and the second vehicle specification setting items 220 are written by the first diagnostic device 12 of the vehicle production plant 1.

[0053] Next, after writing the first write data D3-1 to the electronic control device 41, the first diagnostic device 12 reads the management data D3-2 from the electronic control device 41 and transmits the management data D3-2 to the specification storage server 22 via the factory server 11 (step S6). The management data D3-2 includes the value of the parameter string 200 of the electronic control device 41, VIN information, and the serial number of the electronic control device 41.

[0054] Then, the specification storage server 22 stores the management data D3-2 in the specification storage table 100 in the storage unit (step S7).

[0055] A checksum is performed to check whether data is corrupted during communication. Although the explanation is omitted in the following flow chart 7, the same process is performed.

[0056] Next, the dealer option purchase flow shown in Fig. 7 will be explained with reference to the solid arrows shown in Fig. 1. First, when a customer purchases a dealer option, the vehicle dealer terminal 31 transmits dealer option purchase information D11 to the sales server 21 (step S11). The dealer option purchase information D11 includes information indicating the status of the dealer option setting items, such as whether they are enabled or disabled, and the VIN information of the vehicle 4. The VIN information is read from the vehicle 4 after it has been shipped.

[0057] The sales server 21 performs order processing based on the received dealer option purchase information D11 and transmits the dealer option purchase information D11 to the specification storage server 22 (step S12).

[0058] The specification storage server 22 stores the dealer option purchase information D11 in association with the management data D3-2 that matches the VIN information stored in the specification storage table 100 in the memory unit as update information (step S13), and updates the data (step S14).

[0059] Next, the second diagnostic device 32 reads the verification data D12 from the electronic control device 41 (see FIG. 2) of the vehicle 4 after shipment, and transmits the verification data D12 to the specification storage server 22 (step S15). The verification data D12 is the VIN information of the vehicle 4 and the serial number of the electronic control device 41 of the vehicle 4. The transmission to the specification storage server 22 is performed via the communication device (communication equipment) 30.

[0060] The specification storage server 22 collates the VIN information and serial number contained in the collation data D12 with the VIN information and serial number in the management data D3-2 stored in the specification storage table 100 (step S16).

[0061] When the VIN information and the serial number are found to be a perfect match, the specification storage server 22 transmits the update information associated with the perfectly matched VIN information, i.e., the latest dealer option write data D12-1, to the second diagnostic device 32 (step S17). The latest dealer option write data D12-1 is, for example, the write data d5 for the second vehicle specification setting (see FIG. 4). The latest dealer option write data D12-1 includes an activation parameter that activates the purchase item of the dealer option.

[0062] The second diagnostic device 32 writes the latest write data D12-1 for the dealer option to the electronic control device 41 of the vehicle 4, so that the second vehicle specification setting item 220 (see Figure 3) in the parameter column 200 (see Figure 2) becomes the latest value, and the dealer option purchase item becomes valid (step S18).

[0063] The specification storage server 22 updates the original settings stored therein to reflect the settings of the latest write data D12-1, and writes the latest dealer options to the electronic control device 41 (step S19). Specifically, the specification storage server 22 updates the data, and after the second diagnostic device 32 writes it to the electronic control device 41, it reads the data, and if the read content matches the latest written content of the dealer options, it notifies the specification storage server 22 that the writing was successful.

[0064] Here, the updating of data in the specification storage table 100 by the specification storage server 22 will be described with reference to FIG.

[0065] As shown in Fig. 5, the specification storage table 100 stores VIN information, serial numbers, and specification information data in association with each other. As shown in Fig. 5, "VIN information" is set to "XXXX" d2, which is the VIN information read from the vehicle 4. "Serial number" is set to "YYYY" d4, which is the serial number read from the electronic control unit 41. "XXXX" and "YYYY" are individual identification information that is a combination of letters and / or numbers.

[0066] In this example, no dealer options are set for "Specification Information 2" at the stage of setting the first specification information, but all items in "Specification Information 2" remain at their initial value of A0 (disabled) to match the current vehicle state. In other words, "Specification Information 2" is also written at the vehicle production factory 1 to match the current vehicle state. When the vehicle sales company sets the dealer options and the setting is completed successfully, the settings of the dealer option items in the specification storage table 100 are updated. In this example, a dealer option navigation system was purchased, so "Navigation" has been updated to A1 (enabled). Note that in this example, no dealer options were set for "Specification Information 2" at the stage of setting the first specification information, so all items in "Specification Information 2" were set to A0 (disabled), but the items in "Specification Information 2" may be set as manufacturer options, in which case the items in "Specification Information 2" may be enabled (A1) at the stage of setting the first specification information.

[0067] In this embodiment, as an example of updating the settings of the electronic control unit 41 performed by the vehicle dealership, an example is given in which the purchase of a dealer option is accepted at the vehicle dealership terminal 31 and the settings of the electronic control unit 41 are updated by the second diagnostic device 32, but the acceptance method and setting method may be performed by various means.

[0068] For example, a customer may access a predetermined website using a terminal such as a smartphone and apply to purchase a dealer option on the website. In this case, the website sends dealer option purchase information D11 to the sales server 21 instead of the vehicle dealer terminal 31. Other data flows are the same as those described above.

[0069] Furthermore, if the vehicle 4 is equipped with a wireless communication unit for wireless communication, it may communicate with the second diagnostic device 32 via the wireless communication unit. Furthermore, the vehicle 4 may connect to the communication device 30 via an access point from any area, not limited to within the vehicle dealership 3, and communicate with the second diagnostic device 32 to update the settings of the electronic control device of the vehicle 4. Furthermore, the vehicle 4 may be equipped with an in-vehicle communication device (e.g., a TCU [telematics control unit]) that communicates with the outside, and may access each server, such as the specification storage server 22, via the in-vehicle communication device to update various settings. This allows the settings of each server to be updated via the in-vehicle communication device in response to operations input to an operation unit, such as a display audio, of the vehicle 4.

[0070] Up to this point, we have explained the case where the electronic control unit does not need to be replaced. Next, we will explain the case where the electronic control unit needs to be replaced.

[0071] Fig. 8 is an explanatory diagram outlining the case where an electronic control device is replaced. Fig. 8 is a diagram showing the configuration of Fig. 1 when a supply item (electronic control device) is present. In Fig. 8, the same components as those in Fig. 1 are assigned the same numbers as those in Fig. 1. Note that, since the description of the same components as those in Fig. 1 would be repetitive, the following description of the same components will be omitted and only the different components will be described.

[0072] 8 differs from the configuration of vehicle manufacturer 2 in that traceability information management server 24 and parts supply unit 25 are clearly shown.

[0073] The traceability information management server 24 is an information processing device that manages version information of software stored in each electronic control device of each vehicle 4.

[0074] The parts supply unit 25 is an information processing device that receives a parts order when there is a hardware change. Upon receiving the parts order, the parts supply unit 25 ships the parts (supplies) to the vehicle dealership 3.

[0075] Next, the supply item attachment flow shown in FIG. 9 will be described with reference to the dotted and solid arrows shown in FIG.

[0076] First, the vehicle dealer terminal 31 transmits information D21 about the supply item (electronic control device) to the sales server 21 (step S21).

[0077] Next, the sales server 21 sends order information D22 for the supply item (electronic control device) to the parts supply unit 25 based on the information D21 of the supply item (electronic control device) to place an order (step S22). As a result, the parts supply unit 25 delivers the supply item (electronic control device) to the vehicle dealership 3.

[0078] Next, the vehicle dealer 3 installs the supply item (electronic control unit) in the vehicle 4 (step S23).

[0079] Next, the second diagnostic device 32 reads the verification data D23 (VIN information and serial number) from the electronic control device 41 (see FIG. 2) of the vehicle 4 and transmits it to the specification storage server 22 (step S24).

[0080] The specification storage server 22 acquires the latest written data linked to the VIN information in the traceability information management server 24 (step S25).

[0081] When the specification storage server 22 finds that the latest written data obtained from the traceability information management server 24 matches the written data stored in association with the VIN information, it changes the serial number associated with the VIN information to the serial number in the comparison data D23 (step S26).

[0082] Subsequently, the specification storage server 22 transmits the latest write data to the second diagnostic device 32 (step S27).

[0083] Next, the second diagnostic device 32 writes the parameter values ​​into the electronic control device 41 of the vehicle 4 (step S28).

[0084] After completion, the second diagnostic device 32 notifies the specification storage server 22 that the writing has been successful (step S29).

[0085] Next, license management in the sales server 21 will be described. In this embodiment, the electronic control unit enables / disables dealer options by setting the enable / disable. Therefore, payment for the dealer option is made as a license payment when the function is enabled. Since the sales server 21 stores the order details, a system for making license payments for products or services using this data will be described.

[0086] 10 is a diagram showing an example of an order table of the sales server 21. The order table 300 has data corresponding to the specification management table 200 (see FIG. 5), and stores the latest settings for each vehicle using VIN information and serial number.

[0087] The license management table 310 is a table that tally up the license fees for products or services for each payee based on the latest settings (parameter settings) for each vehicle in the order entry table 300.

[0088] The license management table 310 manages the number of dealer options used (n, m, ...) for each payee (Company B, Company C, ...) and calculates the payment amount based on the number of uses (n, m, ...) and each company's license fee (ZZZ, ZZ1, ...). The number of uses can be calculated by, for example, tallying up the valid settings of parameters. By providing such a license management table 310, the sales server 21 can pay the payment amount according to the number of uses for each payee via the settlement system.

[0089] (Variation) The sales server 21 may manage free trials of dealer options in a subscription table based on the order table 300.

[0090] For example, the sales server 21 sets the type of dealer option and the trial period in the subscription table, and when the trial period begins, notifies the specification storage server 22 and switches the corresponding item in "specification information 2" in the specification storage table 100 to enabled. When the trial period ends, the sales server 21 notifies the specification storage server 22 and switches the corresponding item in "specification information 2" in the specification storage table 100 to disabled. Note that the trial is not limited to being free, and may be at a special price.

[0091] For example, dealer option settings include settings for advanced functions, settings for special interior illumination colors, etc. After the trial period, the settings are restored to their original state, but if the customer purchases the option during the trial period, the dealer option setting will continue.

[0092] (Effects of the embodiment) In this embodiment, a vehicle is shipped from a vehicle production factory with software required for dealer options stored in the electronic control unit. The electronic control unit can then switch between enabling and disabling dealer options even after shipping by setting parameters. This allows the dealer to individually set dealer options for the vehicle after shipping.

[0093] Furthermore, electronic control units may have a large number of dealer options, and the combinations of these options can make management complicated. However, even in such cases, according to this embodiment, it is no longer necessary to manage electronic control units with individual control numbers according to the combination of vehicle model and dealer options. For example, it is possible to manage electronic control units with a single control number.

[0094] 11 is a diagram showing the management flow of electronic control units (ECUs) 41 within a vehicle production plant 1. As shown in FIG. 11, when electronic control units (ECUs) 41 are ordered, they are all assigned a common management number 1 and managed. The electronic control units (ECUs) 41 with management number 1 both store the same combination of software group 40, and software 1, software 2, etc. can be enabled / disabled later by rewriting parameter values, so they are all assigned the common management number 1 and managed until shipment.

[0095] This reduces the complexity of management due to the combination of vehicle models and dealer options. Furthermore, since there is no need to reserve separate spaces for the electronic control units (ECUs) 41 for different management numbers, the space required for placing the electronic control units (ECUs) 41 can also be reduced. Specifically, this reduces the amount of work required for internal and external management evaluation and the increase in factory space, and theoretically reduces the number of management numbers to one part number. It also reduces the cost of the hardware itself and the work required for hardware reassembly. Furthermore, the centralized management of vehicle specifications and dealer option purchase information makes it easy to analyze user preferences, leading to future sales promotions.

[0096] The present invention is not limited to the above-described embodiment, and various modifications other than those described above can be made without departing from the spirit of the present invention. [Explanation of symbols]

[0097] 1. Vehicle production plant 2. Vehicle manufacturers 3. Vehicle dealers 4 vehicles 10 Vehicle production lines 11 Factory Server 12 First diagnostic device 21 Sales Server 22 Specification storage server 23 Production Instruction Generation Department 31 Vehicle dealer terminal 32 Second diagnostic device 40 Software Group (Software 1, Software 2, ...) 41 Electronic Control Unit (ECU) 100 Specification Storage Table 200 Parameter Column N1 Communications Network N2 communication network

Claims

1. a vehicle having an electronic control unit in which software common to a plurality of vehicles is stored and which is configured to specifications for each vehicle by setting parameters of the software; a management server that manages parameters of the software; a sales company side device that updates the parameters managed by the management server after the vehicle is shipped from the vehicle manufacturer's factory; Including, The parameters stored in the electronic control unit of the vehicle are rewritten with the parameters updated by the dealer's device. Vehicle management system.

2. performing license management for a product or service based on the parameter information managed by the management server; The vehicle management system according to claim 1 .

3. a storage unit that stores vehicle identification information and parameter setting information corresponding to software stored in an electronic control unit of the vehicle in association with each other; a processing unit that, when receiving a change in the parameters of the vehicle from the sales company device, updates the setting information of the parameters stored in the storage unit to the setting of the parameters after the change in the vehicle; An information processing device having the above.

Images