IP Library › Granted Patent US 12,277,413
Granted Patent B2
US 12,277,413 · App. 17/572,798 · Granted Apr 15, 2025

Center, update control method, non-transitory storage medium, OTA master, and software update system

Inventor: Shoichi Nagamitsu (Toyota, JP)
Assignee: TOYOTA JIDOSHA KABUSHIKI KAISHA
G06F8/65G07C5/008G07C5/0808G07C5/0816B60Q11/00B60R16/0231B60W50/029H04L41/069
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,277,413
App. No.
17/572,798
Granted
Apr 15, 2025
Kind
B2
Abstract

A center configured to communicate with an OTA master and a malfunction management server includes a processor. The malfunction management server is configured to store malfunction occurrence information. The processor is configured to receive the malfunction occurrence information from the malfunction management server and an inquiry about presence or absence of an update of software of an electronic control device from the OTA master. The processor is configured to determine, when the inquiry is received, whether the vehicle that has transmitted the inquiry malfunctions based on the malfunction occurrence information. The processor is configured to restrict, when it is determined that the vehicle that has transmitted the inquiry malfunctions, execution of an update process for the software on the vehicle that has transmitted the inquiry.

Claims (50)

1. A center configured to communicate with an Over-The-Air (OTA) master and a malfunction management server via a network, the OTA master being mounted on a vehicle, the malfunction management server being configured to store malfunction occurrence information and malfunction resolution information based on information transmitted from the vehicle, the malfunction occurrence information including a malfunction information of the vehicle with a malfunction and identification information for identifying the vehicle with the malfunction, the malfunction resolution information indicating the malfunction occurring in the vehicle has been resolved, the center comprising a processor configured to:

receive the malfunction occurrence information and the malfunction resolution information that are transmitted by the malfunction management server;

in response to receiving the malfunction occurrence information from the malfunction management server, set a vehicle status record to a first status indicating that the vehicle with the identification information included in the received malfunction occurrence information is in a malfunctioning state;

in a case where the vehicle status record is the first status, in response to receiving the malfunction resolution information, change the vehicle status record to a second status indicating that the vehicle is in a normal state;

receive, from the OTA master, an inquiry about presence or absence of an update of software of an electronic control device;

determine, in response to receiving the inquiry, whether the vehicle status record corresponding to the vehicle that has transmitted the inquiry is the first status; and

in response to determining that the vehicle status record corresponding to the vehicle that has transmitted the inquiry is the first status,

determine whether execution of an update process for the software on the vehicle that has transmitted the inquiry is restricted, and

in response to determining that the execution is restricted, transmit a malfunction notification corresponding to the malfunction occurrence information, the malfunction notification notifying a user of predetermined first information related to the malfunction and predetermined second information to resolve the malfunction.

2. The center according to claim 1 , wherein the malfunction management server is configured to transmit the malfunction occurrence information to the center when the malfunction occurrence information is newly registered in the malfunction management server.

3. The center according to claim 1 , wherein the predetermined second information is contact information of a vehicle sales/maintenance company or navigation information to a shop of the company.

4. An update control method to be executed by a computer of a center including a processor, a memory, and a communication device that is configured to communicate with an Over-The-Air (OTA) master and a malfunction management server via a network, the OTA master being mounted on a vehicle, the malfunction management server being configured to store malfunction occurrence information and malfunction resolution information based on information transmitted from the vehicle, the malfunction occurrence information including a malfunction information of the vehicle with a malfunction and identification information for identifying the vehicle with the malfunction, the malfunction resolution information indicating the malfunction occurring in the vehicle has been resolved, the update control method comprising:

receiving the malfunction occurrence information and the malfunction resolution information that are transmitted by the malfunction management server;

in response to receiving the malfunction occurrence information from the malfunction management server, setting a vehicle status record to a first status indicating that the vehicle with the identification information included in the received malfunction occurrence information is in a malfunctioning state;

in a case where the vehicle status record is the first status, in response to receiving the malfunction resolution information, changing the vehicle status record to a second status indicating that the vehicle is in a normal state;

receiving, from the OTA master, an inquiry about presence or absence of an update of software of an electronic control device;

determining, in response to receiving the inquiry, whether the vehicle status record corresponding to the vehicle that has transmitted the inquiry is the first status; and

in response to determining that the vehicle status record corresponding to the vehicle that has transmitted the inquiry is the first status,

determine whether execution of an update process for the software on the vehicle that has transmitted the inquiry is restricted, and

in response to determining that the execution is restricted, transmitting a malfunction notification corresponding to the malfunction occurrence information, the malfunction notification being used to notify a user of predetermined first information related to the malfunction and predetermined second information to resolve the malfunction.

5. A non-transitory storage medium storing instructions that are executable by a computer of a center including a processor, a memory, and a communication device and that cause the computer to perform functions, the communication device being configured to communicate with an Over-The-Air (OTA) master and a malfunction management server via a network, the OTA master being mounted on a vehicle, the malfunction management server being configured to store malfunction occurrence information and malfunction resolution information based on information transmitted from the vehicle, the malfunction occurrence information including a malfunction information of the vehicle with a malfunction and identification information for identifying the vehicle with the malfunction, the malfunction resolution information indicating the malfunction occurring in the vehicle has been resolved, the functions comprising:

receiving the malfunction occurrence information and the malfunction resolution information that are transmitted by the malfunction management server;

in response to receiving the malfunction occurrence information from the malfunction management server, setting a vehicle status record to a first status indicating that the vehicle with the identification information included in the received malfunction occurrence information is in a malfunctioning state;

in a case where the vehicle status record is the first status, in response to receiving the malfunction resolution information, changing the vehicle status record to a second status indicating that the vehicle is in a normal state;

receiving, from the OTA master, an inquiry about presence or absence of an update of software of an electronic control device;

determining, in response to receiving the inquiry, whether the vehicle status record corresponding to the vehicle that has transmitted the inquiry is the first status; and

in response to determining that the vehicle status record corresponding to the vehicle that has transmitted the inquiry is the first status,

determining whether execution of an update process for the software on the vehicle that has transmitted the inquiry is restricted, and

in response to determining that the execution is restricted, transmitting a malfunction notification corresponding to the malfunction occurrence information, the malfunction notification being used to notify a user of predetermined first information related to the malfunction and predetermined second information to resolve the malfunction.

6. A software update system comprising:

a vehicle including an Over-The-Air (OTA) master;

a malfunction management server; and

a center, wherein:

the vehicle is configured to

detect malfunction occurring in the vehicle, and

transmit malfunction occurrence information to the malfunction management server, the malfunction occurrence information including information for identifying the vehicle and a malfunction information code related to the malfunction;

the malfunction management server being configured to store malfunction occurrence information and malfunction resolution information based on information transmitted from the vehicle, the malfunction occurrence information including a malfunction information of the vehicle with a malfunction and identification information for identifying the vehicle with the malfunction, the malfunction resolution information indicating the malfunction occurring in the vehicle has been resolved, is the malfunction management server being further configured to

communicate with the OTA master and the center via a network,

receive the malfunction occurrence information transmitted from the vehicle, and

transmit the malfunction occurrence information to the center;

the center is configured to

communicate with the OTA master and the malfunction management server via the network,

in response to receiving the malfunction occurrence information from the malfunction management server, set a vehicle status record to a first status indicating that the vehicle with the identification information included in the received malfunction occurrence information is in a malfunctioning state;

in a case where the vehicle status record is the first status, in response to receiving the malfunction resolution information, change the vehicle status record to a second status indicating that the vehicle is in a normal state;

receive, from the OTA master, an inquiry about presence or absence of an update of software,

determine, in response to receiving the inquiry, whether the vehicle status record corresponding to the vehicle that has transmitted the inquiry is the first status, and

in response to determination that the vehicle status record corresponding to the vehicle that has transmitted the inquiry is the first status,

determine whether execution of an update process for the software on the vehicle that has transmitted the inquiry is restricted, and

in response to determining that the execution is restricted, transmit a malfunction notification corresponding to the malfunction occurrence information, the malfunction notification being used to notify a user of predetermined information related to the malfunction; and

the vehicle is configured to notify, in response to receiving the malfunction notification transmitted from the center, a user of predetermined first information related to the malfunction and predetermined second information to resolve the malfunction.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 11, 2022
From: NAGAMITSU, SHOICHI
To: TOYOTA JIDOSHA KABUSHIKI KAISHA
Reel/Frame 058616/0106 →
Priority Claims (1)
JP 2021-035142 · Mar 5, 2021 · national
Continuity (1)
Related Publication 20220283797A1 · Sep 8, 2022
References Cited (17)
US 20140282470A1 · Buga · 2014 [cited by examiner]
US 20160294605A1 · Searle · 2016 [cited by examiner]
US 20190300008A1 · Ando · 2019 [cited by examiner]
US 20190391800A1 · Lin · 2019 [cited by examiner]
US 20200104113A1 · Grill · 2020 [cited by examiner]
US 20200398751A1 · Pampattiwar · 2020 [cited by examiner]
US 20210141631A1 · Harata · 2021 [cited by examiner]
US 20210157492A1 · Harata · 2021 [cited by examiner]
US 20210157529A1 · Sakurai et al. · 2021 [cited by applicant]
US 20210157571A1 · Ogawa · 2021 [cited by examiner]
US 20220197747A1 · Fuju et al. · 2022 [cited by applicant]
JP 2020004245A · 2020 [cited by applicant]
JP 2020027620A · 2020 [cited by applicant]
WO 2020162430A1 · 2020 [cited by applicant]
Aljanabi et al, DE 102019134131, (translation) Jul. 23, 2020, 11 pgs <DE_102019134131.pdf>. [cited by examiner]
Li et al, CN 105404273, (translation), Dec. 25, 2018, 14 pgs <CN_105404273.jpg>. [cited by examiner]
Kato et al, JP 2012101788 (translation), May 31, 2012, 15 pgs <JP_2012101788.jpg>. [cited by examiner]