center

Abstract

To provide a center capable of suppressing the occurrence of input omissions in information transmitted from a production system to the center.SOLUTION: A center capable of communicating with a production system and a communication module of a vehicle via a network includes: a receiving unit that receives time-of-shipping data including at least information identifying a production vehicle and software information of each electronic control unit installed in the vehicle from the production system; a storage unit that stores the time-of-shipping data; a receiving unit that receives first-time communication data after communication is established between the communication module of the vehicle and an external network, including at least vehicle identification information and vehicle type identification information; a determination unit that determines, when the first-time communication data is received from the vehicle, whether there is time-of-shipping data having vehicle identification information that matches the vehicle identification information included in the first-time communication data; and a transmitting unit that transmits a notification indicating that the time-of-shipping data does not exist if there is no time-of-shipping data that does not have the vehicle identification information that matches the vehicle identification information included in the first-time communication data.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a software update device for a vehicle that includes a production system and a communication module in a vehicle production factory, and a center that can communicate with the software update device via a network. [Background technology]

[0002] A vehicle is equipped with multiple on-board devices or electronic control units (ECUs) for executing control functions. The software of these electronic control units can be updated by wirelessly connecting a communication device provided in the on-board network to a communication network such as the Internet and using a program downloaded from a distribution server installed in an update center via wireless communication (over-the-air update). For example, see Patent Document 1.

[0003] Regarding such over-the-air updates, regulations require that production information, including version information for the software of the electronic control unit installed in each vehicle, be stored at the time of vehicle production (when the vehicle is shipped from the factory.) To comply with this requirement, the factory (production system) sends software information for the electronic control unit of each produced vehicle to a center, but currently this operation is performed manually. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Publication No. 2020-004245 Summary of the Invention [Problem to be solved by the invention]

[0005] The operation of inputting information such as software for electronic control units to be sent from the production system to the center is performed by humans, which means there is a risk of information being omitted.

[0006] The present disclosure has been made in consideration of the above-mentioned problems, and aims to provide a center that can prevent omissions in input of information sent from a production system to the center. [Means for solving the problem]

[0007] In order to solve the above problem, one aspect of the disclosed technology is a center that can communicate via a network with a production system at a vehicle production factory and a software update device for a vehicle equipped with a communication module, the center comprising: a shipment data receiving unit that receives shipment data from the production system, the shipment data including at least vehicle identification information that identifies the produced vehicle and version information of software related to each electronic control unit installed in the vehicle at the time of production of the vehicle; a shipment data storage unit that stores the shipment data in a predetermined storage unit; a first communication data receiving unit that receives first communication data that is data sent from the vehicle during first communication that takes place after communication between the vehicle's communication module and an external network is established, the first communication data including at least the vehicle identification information and vehicle model identification information for identifying the vehicle model; a determination unit that, when receiving first communication data from the predetermined vehicle, determines whether there is shipment data having vehicle identification information that matches the vehicle identification information included in the first communication data; and an omission notification sending unit that, if there is no shipment data having vehicle identification information that matches the vehicle identification information included in the first communication data, sends a notification to a predetermined destination indicating that the shipment data does not exist. [Effects of the Invention]

[0008] According to the center of the present disclosure, it is possible to prevent omission of input information from being sent from the production system to the center. [Brief explanation of the drawings]

[0009] [Figure 1] Overall configuration diagram of a network system including a center according to this embodiment. [Figure 2]A diagram showing an example of data used by the distribution gateway [Figure 3] FIG. 1 shows an example of data used at a center. [Figure 4] Flowchart of the control process executed by the in-vehicle authentication gateway [Figure 5] Flowchart of control processing executed by the distribution gateway [Figure 6] Flowchart of control process executed by the center DETAILED DESCRIPTION OF THE INVENTION

[0010] <Embodiment> [composition] 1 is a block diagram showing the overall configuration of a network system according to an embodiment of the present disclosure, which includes a plurality of vehicles 11 and 12, an in-vehicle authentication gateway 20, a distribution gateway 30, a plurality of centers 41 and 42, and a production factory 50.

[0011] A production factory (production system or manager) 50 transmits factory shipping data to multiple centers 41 and 42 when producing vehicles 11 and 12. The factory shipping data includes at least the VIN, which is vehicle identification information that identifies the vehicles 11 and 12, and information regarding the software versions of the electronic control units (ECUs) installed in the vehicles 11 and 12. Furthermore, the production factory 50 retransmits the factory shipping data as needed in response to VIN omission notifications transmitted from the multiple centers 41 and 42.

[0012] The plurality of vehicles 11 and 12 includes a data communication module (DCM) 101, one or more electronic control units (ECUs) 102, and an OTA master 103 that controls an over-the-air (OTA) update process for the software of the electronic control unit 102. The vehicles 11 and 12 can communicate with the plurality of centers 41 and 42 via the in-vehicle authentication gateway 20 and the distribution gateway 30. Specifically, when the data communication module 101 is activated, the vehicles 11 and 12 transmit a notification of initial communication data (ADF) to the in-vehicle authentication gateway 20 (ADF communication). The ADF notification includes at least the VIN, which is vehicle identification information, a DCM grade indicating the grade of the data communication module installed in the vehicle, and the serial ID of each electronic control unit installed in the vehicle. Note that the number of the plurality of vehicles 11 and 12 included in the network system is not limited to that shown in FIG. 1.

[0013] The in-vehicle authentication gateway (TSCPP) 20 is a device to which ADF notifications are sent from the multiple vehicles 11 and 12. The in-vehicle authentication gateway 20 sends the ADF notifications received from the vehicles 11 and 12 to the distribution gateway 30 every time an ADF notification is received.

[0014] The distribution gateway 30 distributes the ADF notification received from the in-vehicle authentication gateway 20 according to predetermined vehicle types (categories) based on predetermined filter rules. The distribution gateway 30 then determines a destination center 41 or 42 according to the vehicle type to which the ADF notification has been distributed, and distributes and transmits the ADF notification to the determined centers 41 and 42. Figure 2 shows an example of data used by the distribution gateway 30. In Figure 2, ADF data 201 is data included in the ADF notification received from the in-vehicle authentication gateway 20. Transmission data 202 is data required by the distribution gateway 30.

[0015] The centers 41 and 42 are configured to be able to communicate with the production factory 50 and the data communication modules (DCMs) 101 of the vehicles 11 and 12 via a network. A plurality of centers 41 and 42 are provided according to the vehicle type. In the example of FIG. 1, a center 41 for vehicle type A and a center 42 for vehicle type B are shown, but the number of centers may be three or more according to the vehicle type. Each center 41 and 42 receives factory shipping data from the production factory 50 (shipping data receiving unit). Each center 41 and 42 stores the factory shipping data received from the production factory 50 in a production management information database (not shown) (shipping data storage unit). Each center 41 and 42 also receives an ADF notification from the distribution gateway 30 (initial communication data receiving unit). Upon receiving the ADF notification from the distribution gateway 30, each center 41 and 42 compares the ADF notification with the factory shipping data using the VIN as a search key to determine whether they match (determination unit). In addition, if the result of the comparison shows that the VIN in the ADF notification does not exist in the factory shipping data, each center 41 and 42 will email a VIN omission notification to the production factory 50 and request that the shipping data be sent (omission notification sending unit).

[0016] FIG. 3 shows an example of data used by the centers 41 and 42. In FIG. 3, the production management information database 301 is a database (DB) that stores factory shipping data received from the production factory 50. The individual vehicle information database 302 is a database (DB) that stores information on vehicles under the control of the center (as OTA targets). Data is registered (added) when the center receives an ADF notification. Omission notification transmission data 303 is generated as appropriate when an omission is found, and is data for transmitting the omission to the production factory (manager) 50.

[0017] [control] Next, the control executed in the network system according to this embodiment will be described with further reference to Figures 4, 5, and 6. Figure 4 is a processing flowchart of the control executed by the in-vehicle authentication gateway (in-vehicle authentication GW) 20. Figure 5 is a processing flowchart of the control executed by the distribution gateway (distribution GW) 30. Figure 6 is a processing flowchart of the control executed by the centers 41 and 42.

[0018] (1) Control of the in-vehicle authentication gateway The process of FIG. 4 is started by the in-vehicle authentication gateway 20, for example, every time an ADF notification is transmitted from each of the vehicles 11 and 12.

[0019] (Step S401) The in-vehicle authentication gateway 20 receives the ADF notifications of the vehicles 11 and 12 at the timings at which they are transmitted from the vehicles 11 and 12. When the ADF notifications are received, the process proceeds to step S402.

[0020] (Step S402) The in-vehicle authentication gateway 20 creates transmission data 202 required for the destination, the distribution gateway 30. The transmission data 202 can be, for example, data including repro-related information. Once the transmission data 202 for the distribution gateway 30 is created as needed, the process proceeds to step S403.

[0021] (Step S403) The in-vehicle authentication gateway 20 transmits an ADF notification including the ADF data 201 and the necessary transmission data 202 to the distribution gateway 30. When the ADF notification is transmitted to the distribution gateway 30, the control of the in-vehicle authentication gateway 20 for this ADF notification ends.

[0022] (2) Control of the distribution gateway The process of FIG. 5 is started in the distribution gateway 30, for example, every time an ADF notification is received from the in-vehicle authentication gateway 20.

[0023] (Step S501) The distribution gateway 30 receives the ADF notification from the in-vehicle authentication gateway 20. When the ADF notification is received, the process proceeds to step S502.

[0024] (Step S502) The distribution gateway 30 determines the center 41 or 42 as a destination of the ADF notification received from the in-vehicle authentication gateway 20 based on a predefined filter rule. The filter rule is appropriately set based on the DCM grade based on the data communication module 101 mounted in the vehicles 11 and 12, the serial IDs of one or more electronic control units 102 mounted in the vehicles 11 and 12, and the like. The distribution gateway 30 then distributes the ADF notification to the center 41 or 42 in accordance with the determined content. For example, if the combination of the DCM grade and multiple serial IDs included in the ADF notification corresponds to the combination pattern of vehicle model A, the distribution gateway 30 determines that the destination of this ADF notification is the center 41 for vehicle model A, and distributes this ADF notification to the center 41. Once the destination of the ADF notification has been distributed to the center 41 or 42, the process proceeds to step S503.

[0025] (Step S503) The distribution gateway 30 transmits the distributed ADF notification to the corresponding center 41 or 42. When the distributed ADF notification is transmitted to the center 41 or 42, the control of the distribution gateway 30 for this ADF notification ends.

[0026] (3) Center control The process of FIG. 6 is started in the center 41 and / or 42, for example, every time an ADF notification is received from the distribution gateway 30.

[0027] (Step S601) The center 41 and / or 42 receives the ADF notification from the distribution gateway 30. When the ADF notification is received, the process proceeds to step S602.

[0028] (Step S602) Upon receiving the ADF notification, the center 41 and / or 42 refers to the production management information database (DB) to search for the VIN included in the ADF notification. That is, the center 41 and / or 42 performs a process of matching the ADF notification with the factory shipping data using the VIN. Once the VIN included in the ADF notification is found, the process proceeds to step S603.

[0029] (Step S603) The centers 41 and / or 42 that performed the VIN search each determine whether the VIN exists in the production management information database (DB) as a result of the search. That is, the centers 41 and / or 42 determine whether the VIN stored as factory default data matches the VIN in the ADF notification. If a matching VIN exists (step S603, Yes), the control of the centers 41 and / or 42 in response to this ADF notification ends. If a matching VIN does not exist (step S603, No), it is determined that the registration has been omitted, and the process proceeds to step S604.

[0030] (Step S604) If the center 41 and / or 42 determines that the registration is omitted, it generates a "VIN omitted notification email" indicating that the VIN stored as factory shipping data does not match the VIN in the ADF notification, and sends it to the production factory (production system or administrator) 50. This VIN omitted notification email also requests the re-send of the factory shipping data. Once the VIN omitted notification email is generated and sent, the control of the center 41 and / or 42 regarding this ADF notification ends.

[0031] <Effects> As described above, according to the centers 41 and 42 according to an embodiment of the present disclosure, upon receiving the initial communication data (ADF notification) in which the VIN is reliably transmitted from the vehicles 11 and 12, the centers 41 and 42 compare the VIN between this initial communication data and the factory shipping data transmitted from the production factory 50. This makes it possible to prevent omissions in the information transmitted from the production system to the centers.

[0032] Furthermore, according to the centers 41 and 42 according to an embodiment of the present disclosure, if the center has missed registering the factory shipping data, the center notifies the production system or the administrator of the fact and requests that the factory shipping data be resent, thereby making it possible to have the missed factory shipping data resent. [Industrial Applicability]

[0033] The disclosed technology can be used in a center that manages, via network communication, a network system for updating software in an electronic control unit mounted on a vehicle. [Explanation of symbols]

[0034] Cars 11 and 12 20 In-vehicle authentication gateway (TSCPP) 30 Distribution Gateway 41, 42 Center 50 production plants 101 Data Communication Module (DCM) 102 OTA Master 103 Electronic Control Unit (ECU) 201 ADF Data 202 Send Data 301 Production Management Information Database 302 vehicle information database 303 Data for sending leak notification

Claims

[Claim 1] A center capable of communicating via a network with a production system in a vehicle production factory and a vehicle software update device equipped with a communication module, a shipping data receiving unit that receives, from the production system, shipping data that includes at least vehicle identification information that identifies a produced vehicle and version information of software related to each electronic control unit installed in the vehicle at the time of production of the vehicle; a shipping data storage unit that stores the shipping data in a predetermined storage unit; an initial communication data receiving unit that receives initial communication data transmitted from the vehicle at the time of initial communication performed after communication between the communication module and the external network is established, the initial communication data including at least the vehicle identification information and vehicle type identification information for identifying the vehicle type; a determination unit that, when receiving the initial communication data from a predetermined vehicle, determines whether or not the shipping data having vehicle identification information that matches the vehicle identification information included in the initial communication data exists; The center is equipped with an omission notification sending unit that, if there is no shipping data having vehicle identification information that matches the vehicle identification information included in the initial communication data, sends a notification to the vehicle production plant indicating that the shipping data does not exist and requesting that the shipping data be resent.

Images