Information processing device

Abstract

The objective is to provide an information processing device that allows sales companies to configure individual settings, such as dealer options, for vehicles shipped from the vehicle manufacturer. [Solution] The information processing device according to the present invention is characterized by comprising: a storage unit that stores vehicle identification information and parameter setting information corresponding to software stored in the vehicle's electronic control unit in association with each other; and a processing unit that, upon receiving a change in vehicle parameters from a sales company's device, updates the parameter setting information associated with the storage unit to the parameter settings after the change in the vehicle.

Description

Technical Field

[0001] The present invention relates to an information processing apparatus.

Background Art

[0002] In recent years, technology has advanced to integrate the control of each part of a vehicle into a single electronic control unit (ECU). With this technology, it becomes possible to control, with a single electronic control unit, a single navigation system, a display audio, a meter, etc., which are in-vehicle devices related to the cockpit.

[0003] In an existing system, since vehicle specifications vary according to user preferences, software is created at the factory of a vehicle manufacturer according to combinations of vehicle specifications. Since the software to be created varies according to the vehicle specifications desired by the user, combinations of vehicle specifications that match are managed with the same management number, and software of the same combination is stored in electronic control units with the same management number.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] As described above, the factory of a vehicle manufacturer manages electronic control units with different management numbers according to combinations of software to be stored in the electronic control units. For this reason, when attempting to store software of different vehicle specifications in an electronic control unit at the factory of a vehicle manufacturer, the management number of the electronic control unit increases, management becomes complicated, and further space is required to store the electronic control units separately for each management number.

[0006] Furthermore, as the control of cockpit-related in-vehicle equipment, such as dealer options, becomes integrated, the software for these dealer options also needs to be stored in the electronic control unit. This further increases the number of software combinations, leading to greater management complexity and storage space issues.

[0007] The objective of the present invention is to provide an information processing device that enables sales companies to perform individual settings, such as dealer options, on vehicles shipped from the vehicle manufacturer. [Means for solving the problem]

[0008] To achieve the above objective, the information processing device according to the present invention is characterized by comprising: a storage unit that stores vehicle identification information and parameter setting information corresponding to software stored in the vehicle's electronic control unit in association with each other; and a processing unit that, upon receiving a change in the vehicle's parameters from a sales company's device, updates the parameter setting information associated with the storage unit to the changed parameter settings of the vehicle. [Effects of the Invention]

[0009] According to the present invention, individual settings such as dealer options can be made by the sales company in vehicles shipped from the vehicle manufacturer. [Brief explanation of the drawing]

[0010] [Figure 1] Figure 1 is a schematic diagram illustrating the vehicle management system according to an embodiment. [Figure 2] Figure 2 shows an example of the configuration of a vehicle's electronic control unit. [Figure 3] Figure 3 is an explanatory diagram showing an example of the configuration of the parameter sequence. [Figure 4] Figure 4 shows an example of the structure of the data to be written to an electronic control unit (ECU). [Figure 5] Figure 5 shows an example of the configuration of a specifications storage table. [Figure 6] Figure 6 shows an example of a vehicle production flow. [Figure 7] Figure 7 shows an example of the purchase flow for dealer options. [Figure 8] Figure 8 is a schematic diagram illustrating the process of replacing an electronic control unit. [Figure 9] Figure 9 shows an example of the supply installation flow. [Figure 10] Figure 10 shows an example of an order table for a sales server. [Figure 11] Figure 11 shows the flow of management of electronic control units (ECUs) within a vehicle production plant. [Modes for carrying out the invention]

[0011] In the following, with reference to the attached drawings, a vehicle management system and an information processing device, which are embodiments of the present invention, will be described in detail.

[0012] <Embodiment> In this embodiment, a method for setting vehicle specifications to the vehicle's electronic control unit will be described. In this embodiment, setting vehicle specifications to the electronic control unit includes setting vehicle specifications within the vehicle production plant and updating the vehicle specifications for vehicles after shipment by the vehicle sales company (equivalent to a sales company). In the following, the vehicle specifications set to the electronic control unit at the vehicle production plant will be referred to as the first vehicle specifications, and the vehicle specifications updated to the electronic control unit by the vehicle sales company will be referred to as the second vehicle specifications, and these will be explained separately.

[0013] In this embodiment, the update of the vehicle specifications in the electronic control unit is performed by writing parameter values such as enabling or disabling the corresponding software to the electronic control unit. Therefore, the vehicle is shipped with the software corresponding to the items whose settings are to be updated later stored in the electronic control unit of the vehicle. Note that the parameter values may be written not only for enabling or disabling but also for values such as presence or absence. For example, the cameras used for imaging the situation around the vehicle among at least any one of the front camera, rear camera, left side camera, and right side camera for monitoring the surroundings of vehicle 4 may be set by writing values such as "present" or "absent". In this case, for example, combinations such as only the front camera, the front camera and the rear camera, the front camera, the rear camera, and the left and right side cameras, and no camera are conceivable. Then, the imaged situation around the vehicle may be recorded in a storage unit such as an in-vehicle drive recorder or a memory in the ECU, and may be selected as a drive recorder target camera according to the setting of "present" or "absent".

[0014] Also, the number of software stored in the electronic control unit is not particularly limited. It may be restricted to specific ones, or the software for all specifications including all dealer options may be stored.

[0015] Also, in the following, the items for which the settings are updated are described assuming dealer option items, but if there are other items for which later changes are permitted, the update may be enabled.

[0016] Figure 1 is a schematic explanatory diagram of a vehicle management system according to an embodiment. Figure 1 shows the main components related to the vehicle management systems of vehicle production factory 1, vehicle manufacturer 2, and vehicle sales company 3.

[0017] Vehicle production factory 1 assembles parts and sets electronic control devices on vehicle production line 10 to ship vehicle 4. Factory server 11 shown in vehicle production factory 1 is an information processing device that comprehensively manages the production of vehicle 4. Factory server 11 is connected to vehicle production line 10 so as to be capable of mutual communication.

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

[0019] Vehicle manufacturer 2 has a sales server 21, a specification storage server 22, and a production instruction generation unit 23. Sales server 21, specification storage server 22, and production instruction generation unit 23 are constructed in the in-house network of vehicle manufacturer 2 or the like. In addition to these, a traceability information management server that manages traceability information, a parts supply unit that supplies parts, etc. are constructed in the in-house network, but illustration thereof is omitted here.

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

[0021] Vehicle sales company 3 is any one of the stores that sells vehicles. Each vehicle sales company 3 has a vehicle sales company terminal 31 and a second diagnostic device 32, which are considered "vehicle sales company side equipment". The vehicle sales company 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 used by the vehicle sales company 3 to diagnose and configure the electronic control unit of the vehicle 4. The second diagnostic device 32 communicates with the communication unit for diagnosing the electronic control unit of the vehicle 4 and configures it.

[0023] The communication networks N1 and N2 shown in Figure 1 are the internet, dedicated lines, etc.

[0024] The information processing devices used in each device are, for example, computer-configured information processing devices in which a CPU (Central Processing Unit), memory or storage such as ROM (Read Only Memory) or RAM (Random Access Memory), and a communication unit are interconnected via a bus. Other information processing devices described later will also be explained using computer-configured information processing devices as examples.

[0025] Figure 2 shows an example of the configuration of the electronic control unit of vehicle 4. The electronic control unit (ECU) 41 shown in Figure 2 is an electronic control unit called an HCU (HMI Control Unit) or integrated ECU (Electronic Control Unit) that integrates the control of various parts of the vehicle into a single electronic control unit. The electronic control unit (ECU) 41 can also integrate the control of cockpit-related in-vehicle equipment of vehicle 4, and can control individual in-vehicle equipment such as a navigation system, display audio, and meters. If there are changes to dealer options, these can be changed by setting the parameters of the electronic control unit (also called HCU) 41.

[0026] The electronic control unit (ECU) 41 shown in Figure 2 stores a set of software (Software 1, Software 2, ...) 40 for all specifications, including all dealer options. The electronic control unit (ECU) 41 is set to the predetermined vehicle specifications by setting the parameter column 200 corresponding to the vehicle specification items. In addition, by switching the items in the parameter column 200 that correspond to dealer options to enable or disable, the software in the software group 40 that corresponds to the dealer options is enabled or disabled.

[0027] Each unit 42 shown in Figure 2 is connected to the Electronic Control Unit (ECU) 41 via the Central Gateway (CGW) 43. These units include a Vehicle Control Unit (VCU) that controls the brakes, and an Electronic Fuel Injector (EFI) that controls devices related to the engine and other power sources. Each unit 42 and the CGW 43 are connected via a Controller Area Network (CAN). The Electronic Control Unit (ECU) 41 and the CGW 43 are also connected via CAN.

[0028] CGW43 is a control unit that controls multiple communication paths and has a diagnostic communication section for the first diagnostic device 12 and the second diagnostic device 32. The first diagnostic device 12 and the second diagnostic device 32 communicate with each unit 42 and the electronic control unit (ECU) 41 via CAN connection to the diagnostic communication section of CGW43.

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

[0030] Figure 3 is an explanatory diagram showing an example of the configuration of parameter column 200. Parameter column 200 includes setting items 210 for the first vehicle specification and setting items 220 for the second vehicle specification.

[0031] The first vehicle specification setting item 210 includes items for setting the vehicle type relationship of vehicle 4 and items for setting manufacturer options. The items for setting the vehicle type relationship of vehicle 4 are regulatory items such as OEM information 211 and tire diameter 212. Each parameter in the items for setting the vehicle type relationship of vehicle 4 and the items for setting manufacturer options is selectively set to a parameter value (such as A0 or A1) that corresponds to the first vehicle specification.

[0032] The second set of vehicle specifications, item 220, includes items related to dealer options such as the navigation system 221 and television 222. These items can be switched on or off later upon request. Each of these parameters is set with a parameter value (such as A0 (disabled) or A1 (enabled)) that switches the configuration on or off based on the second set of vehicle specifications.

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

[0034] As an example, both the write data for setting the first vehicle specifications and the write data for setting the second vehicle specifications consist of a data column of parameter values ​​corresponding to a sequence of parameter columns. Figure 4 shows the parameter columns alongside the data columns to illustrate the correspondence between the parameter columns and the data columns, with each item being associated with the others.

[0035] The write data d3 for the first vehicle specification setting is the write data acquired at vehicle production plant 1. For confirmation, an identification parameter value is set at the beginning of the data column to indicate that it is the write item information for the first vehicle specification.

[0036] The parameter values ​​corresponding to the data column 110 of the first vehicle specification are set based on the input method of setting item 210 (see Figure 3) of the first vehicle specification. The parameter values ​​of data 111 are set based on the input method of setting item 211 (see Figure 3) of the first vehicle specification. The parameter values ​​of data 112 are set based on the input method of setting item 212 (see Figure 3) of the first vehicle specification. The parameter values ​​of data column 113 are set based on the input method of setting item 213 (see Figure 3) of the first vehicle specification.

[0037] The second vehicle specification setting write data d5 is data written and retrieved at vehicle production plant 1 and vehicle sales company 3. For confirmation, an identification parameter value is set at the beginning of the data column to indicate that it is information for the second vehicle specification write item.

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

[0039] Here, the structure of the write data acquired at vehicle production plant 1 and the structure of the write data acquired at vehicle sales company 3 have been explained separately. However, it is also possible to have a structure that includes all the items set at vehicle production plant 1 and all the items set at vehicle sales company 3.

[0040] Therefore, the vehicle specifications set for the electronic control unit 41 may differ between the first vehicle specifications and the second vehicle specifications, and some or all of the items may overlap between the first and second vehicle specifications.

[0041] Any overlapping items between the first and second vehicle specification settings will be updated so that the second vehicle specification setting is the most up-to-date. If new vehicle specifications are set after the second vehicle specification setting, the settings will always be updated to reflect the new vehicle specification setting.

[0042] The settings for the vehicle's electronic control unit may be configured by enabling or disabling the relevant items in the electronic control unit all at once, or by configuring them individually.

[0043] As described above, by writing data in a column format, it is possible to write item by item in a batch.

[0044] Figure 5 shows an example of the configuration of the specification storage table 100. As shown in Figure 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. "Specification information 1" corresponds to the first specification information, and parameter values ​​are set for each item. "Specification information 2" corresponds to the second specification information, and parameter values ​​are set for each item.

[0045] Figure 5 also shows the configuration state after the settings have been updated according to the second specification information, but the explanation of the state before and after the update will be described later.

[0046] Next, we will explain the vehicle production flow shown in Figure 6 and the dealer option purchase flow shown in Figure 7, referring to Figure 1. The dotted arrows in Figure 1 represent the data flow when setting the first and second vehicle specifications at the time of vehicle purchase (ordering), and the solid arrows represent the data flow when setting the second vehicle specifications, such as when purchasing dealer options. First, we will explain the vehicle production flow in Figure 6, referring to the dotted arrows in Figure 1.

[0047] First, when a customer purchases a vehicle, the vehicle sales company terminal 31 sends 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 vehicle order 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 conversion data D2 by converting vehicle purchase information into production instruction information and sends the conversion data D2 to the factory server 11 (step S3). The conversion data D2 is data that adds VIN (Vehicle Identification Number) information to generated information (called VLT) such as vehicle specifications and production schedule, including model and option information.

[0050] When the factory server 11 receives the conversion data D2, it generates production instruction information D3 for the vehicle 4 from the conversion data D2 and stores it in the master 11-1 of the storage unit. 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 and issues production instructions to the vehicle production line 10 (step S4).

[0051] Subsequently, 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 to the electronic control unit 41 (see Figure 2) of the vehicle 4 (step S5).

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

[0053] Next, the first diagnostic device 12 writes the first write data D3-1 to the electronic control unit 41, then reads the management data D3-2 from the electronic control unit 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 consists of the values ​​of the parameter column 200 of the electronic control unit 41, the VIN information, and the serial number of the electronic control unit 41.

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

[0055] Furthermore, a checksum is performed to verify that there is no data corruption during communication. Although the explanation is omitted in Flowchart 7 below, the same procedure should be followed.

[0056] Next, we will explain the dealer option purchase flow shown in Figure 7, referring to the solid arrows shown in Figure 1. First, when a customer purchases a dealer option, the vehicle sales company terminal 31 sends dealer option purchase information D11 to the sales server 21 (step S11). The dealer option purchase information D11 consists of information indicating the status of the dealer option settings, 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 shipment.

[0057] The sales server 21 processes the order based on the received dealer option purchase information D11 and sends 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 as update information in the management data D3-2 which matches the VIN information stored in the specification storage table 100 of the storage unit (step S13), and updates the data (step S14).

[0059] Next, the second diagnostic device 32 reads the verification data D12 from the electronic control unit 41 (see Figure 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 consists of the VIN information of the vehicle 4 and the serial number of the electronic control unit 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 compares the VIN information and serial number contained in the matching 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 specification storage server 22 finds a perfect match between the VIN information and the serial number, it sends the update information associated with the perfectly matched VIN information, i.e., the latest write data D12-1 for dealer options, to the second diagnostic device 32 (step S17). The latest write data D12-1 for dealer options is, as an example, the write data d5 for the setting of the second vehicle specification (see Figure 4). The latest write data D12-1 for dealer options includes activation parameters to enable the purchased items of the dealer options.

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

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

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

[0065] As shown in Figure 5, the specification storage table 100 stores VIN information, serial number, and specification information data linked together. As shown in Figure 5, the "VIN information" is set to "XXXX" d2, which is the Vin information read from vehicle 4. The "serial number" is set to "YYYY" d4, which is the serial number read from electronic control unit 41. Note that "XXXX" and "YYYY" are individual identification information that is a combination of letters or numbers.

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

[0067] In this embodiment, as an example of updating the settings of the electronic control unit 41 performed by the vehicle sales company, the purchase of a dealer option is accepted at the vehicle sales company terminal 31, and the settings of the electronic control unit 41 are updated by the second diagnostic device 32. However, the acceptance method and setting method can be carried out by various means.

[0068] For example, a customer may access a designated website using a smartphone or other device and apply to purchase dealer options through the website. In this case, the website transmits the dealer option purchase information D11 to the sales server 21 on behalf of the vehicle sales company terminal 31. The rest of the data flow is the same as described above.

[0069] Furthermore, if vehicle 4 is equipped with a wireless communication unit, it may communicate with the second diagnostic device 32 via the wireless communication unit. Also, vehicle 4 may connect to the communication device 30 via an access point from any area, not limited to within the vehicle sales company 3, and communicate with the second diagnostic device 32 to update the settings of the vehicle 4's electronic control unit. In addition, vehicle 4 may be equipped with an in-vehicle communication device (for example, a TCU [Telematics Control Unit]) that communicates with the outside world, and may be able to access various servers such as the specification storage server 22 via the in-vehicle communication device to update various settings. This makes it possible to update the settings of each server via the in-vehicle communication device in response to operations input into the vehicle's control unit, such as a display audio system.

[0070] So far, we have explained the cases where there is no need to replace the electronic control unit. Next, we will explain the cases where the electronic control unit needs to be replaced.

[0071] Figure 8 is a schematic diagram illustrating the process of replacing an electronic control unit. Figure 8 shows the configuration when a replacement part (electronic control unit) is available, as in the configuration shown in Figure 1. In Figure 8, components identical to those in Figure 1 are given the same numbers. Since explaining the same components as in Figure 1 would be repetitive, the explanation of identical components will be omitted below, and different components will be described instead.

[0072] Figure 8 shows a different configuration for vehicle manufacturer 2, in that it clearly indicates the traceability information management server 24 and the parts supply unit 25.

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

[0074] The parts supply unit 25 is an information processing device that receives parts orders when there are hardware changes. When the parts supply unit 25 receives a parts order, it ships the relevant parts (replacement parts) to the vehicle sales company 3.

[0075] Next, we will explain the supply installation flow shown in Figure 9, referring to the dotted and solid arrows shown in Figure 8.

[0076] First, the vehicle sales company terminal 31 transmits information D21 about the replacement parts (electronic control unit) to the sales server 21 (step S21).

[0077] Next, the sales server 21 sends order information D22 for the replacement part (electronic control unit) to the parts supply unit 25 based on the replacement part (electronic control unit) information D21, and places an order (step S22). As a result, the replacement part (electronic control unit) is delivered from the parts supply unit 25 to the vehicle sales company 3.

[0078] Next, vehicle sales company 3 installs the replacement parts (electronic control unit) into vehicle 4 (step S23).

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

[0080] The specification storage server 22 retrieves the latest write data associated with the VIN information from the traceability information management server 24 (step S25).

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

[0082] Next, the specification storage server 22 sends the latest written data to the second diagnostic device 32 (step S27).

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

[0084] Upon completion, the second diagnostic device 32 notifies the specification storage server 22 of the success of the write operation (step S29).

[0085] Next, we will explain license management in the sales server 21. In this embodiment, the electronic control unit enables / disables the dealer option by setting it to enable / disable. Therefore, payment for the dealer option is incurred when the function is enabled. Since the sales server 21 stores order details, we will now explain the mechanism for making license payments related to goods or services using that data.

[0086] Figure 10 shows an example of an order table on the sales server 21. The order table 300 contains data corresponding to the specification management table 200 (see Figure 5), and stores the latest settings for each vehicle using VIN information and serial numbers.

[0087] The license management table 310 is a table that aggregates license usage fees for goods or services for each payee, based on the latest settings (parameter settings) for each vehicle in the order 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 usage fee (ZZZ, ZZ1, ...). The number of uses can be calculated by aggregating the enabled settings of parameters, etc. By setting up such a license management table 310, the sales server 21 can pay the payment amount to each payee according to the number of uses via the payment system.

[0089] (modified version) The sales server 21 may manage the free trial of the dealer option in the 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, it 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 expires, 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 free; it may also be offered at a special price.

[0091] For example, dealer options include settings to upgrade features or to change the interior illumination to a special color. After the trial period, the settings revert to their original state, but if the customer purchases the vehicle during the trial period, the dealer option can be retained.

[0092] (Effects of the embodiment) In this embodiment, the vehicle is shipped from the production plant with the necessary software for dealer options stored in the electronic control unit. Furthermore, the electronic control unit can enable / disable dealer options even after shipment by setting parameters. Therefore, dealerships can individually configure dealer options on vehicles after shipment.

[0093] Furthermore, while electronic control devices often have numerous dealer options, and their combinations can make management complicated, this embodiment eliminates the need to manage each electronic control device with a separate management number based on the vehicle model and dealer option combination. For example, it becomes possible to manage them using just one management number.

[0094] Figure 11 shows the management flow of electronic control units (ECUs) 41 within the vehicle production plant 1. As shown in Figure 11, when an electronic control unit (ECU) 41 is ordered, it is managed with a common management number 1. Both electronic control units (ECUs) 41 with management number 1 store the same combination of software groups 40, and since the activation / deactivation of software 1, software 2, etc. can be performed later by rewriting the parameter values, they are managed with a common management number 1 until shipment.

[0095] Therefore, the complexity of management due to combinations of vehicle models and dealer options can be reduced. Furthermore, since the electronic control units (ECUs) 41 do not need to be placed in separate locations, each with a different management number, the expansion of the space required for the ECUs 41 can also be reduced. Specifically, it reduces the amount of internal and external management and evaluation man-hours, the increase in factory space, and theoretically limits the number of management numbers to one part number. In addition, the cost of the hardware itself and the man-hours for hardware reconfiguration can be reduced. Moreover, centralized management of vehicle specifications and dealer option purchase information allows for easy analysis of user preferences, which can lead to future sales promotions.

[0096] It should be noted that the present invention is not limited to the embodiments described above, and various modifications other than those described above can be made without departing from the spirit of the invention. [Explanation of Symbols]

[0097] 1. Vehicle production plant 2. Vehicle manufacturers 3. Vehicle sales companies 4 vehicles 10 Vehicle production lines 11 Factory Server 12. First diagnostic device 21 Business Server 22. Specification storage server 23 Production Instruction Generation Unit 31. Vehicle sales company terminal 32 Second diagnostic device 40 Software Groups (Software 1, Software 2, ...) 41 Electronic Control Unit (ECU) 100 Specification Storage Table 200 parameter list N1 Communication Network N2 Communication Network

Claims

1. A storage unit that stores vehicle identification information and parameter setting information corresponding to the software stored in the vehicle's electronic control unit in association with each other, When the sales company's device receives a change in the vehicle's parameters, the processing unit updates the parameter setting information associated with the storage unit to reflect the changed parameter settings for the vehicle. An information processing device having

2. The aforementioned software is software that supports multiple vehicle specifications, The parameter corresponding to the aforementioned software is the parameter for enabling or disabling the software. The information processing apparatus according to claim 1.

Images