US2022138667A1PendingUtilityA1

Managing transport data expiration

Assignee: TOYOTA MOTOR NORTH AMERICA INCPriority: Nov 3, 2020Filed: Nov 3, 2020Published: May 5, 2022
Est. expiryNov 3, 2040(~14.3 yrs left)· nominal 20-yr term from priority
G06F 21/6245G06Q 10/02H04W 4/48G06F 21/6218G06F 2221/2143G06F 2221/2137G06Q 10/083G06F 16/2379G06F 16/2365G06Q 10/0283
59
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

An example operation includes one or more of utilizing data, by a transport, for a period of time according to a license file, removing a first type of the data, by the transport, while the transport is operating, removing a second type of the data, by the transport when the transport ceases operating, and retaining a third type of data in memory after the transport ceases operating.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
         1 . A method, comprising:
 utilizing data, by a transport, for a period of time according to a license file;   removing a first type of the data, by the transport, while the transport is operating;   removing a second type of the data, by the transport when the transport ceases operating; and   retaining a third type of data in memory after the transport ceases operating.   
     
     
         2 . The method of  claim 1 , comprising
 applying one or more of the first type of data and the second type of data to a device associated with one or more occupants; and   modifying one or more transport controls based on the third type of data.   
     
     
         3 . The method of  claim 1 , comprising
 accessing the third type of data by one or more first devices operating inside the transport when the transport begins operating; and   accessing one or more of the first type of data and the second type of data by one or more second devices inside the transport prior to the transport ceasing operation.   
     
     
         4 . The method of  claim 1 , comprising
 identifying a data use time rule from the license file;   accessing the first type of data at a particular time during the period of time based on the data use time rule; and   removing the first type of data after the accessing.   
     
     
         5 . The method of  claim 1 , comprising
 identifying one or more transport occupants associated with the data;   retrieving data use consent information from the license file associated with the one or more occupants;   accessing one or more of the first, second and third data; and   updating the license file to identify the accessed data.   
     
     
         6 . The method of  claim 1 , comprising receiving, by the transport, a validation of the data utilization from at least one component, wherein the validation comprises a blockchain consensus between a peer group consisting of the transport and the at least one component. 
     
     
         7 . The method of  claim 6 , comprising executing a smart contract, by the transport, to record the validation and the at least one component on a blockchain based on the blockchain consensus. 
     
     
         8 . A transport, comprising:
 a processor configured to
 utilize data for a period of time according to a license file; 
 remove a first type of the data while the transport is operating; 
 remove a second type of the data when the transport ceases operating; and 
 retain a third type of data in memory after the transport ceases operating. 
   
     
     
         9 . The transport of  claim 8 , wherein the processor is further configured to
 apply one or more of the first type of data and the second type of data to a device associated with one or more occupants; and   modify one or more transport controls based on the third type of data.   
     
     
         10 . The transport of  claim 8 , wherein the processor is further configured to
 access the third type of data by one or more first devices operating inside the transport when the transport begins operating; and   access one or more of the first type of data and the second type of data by one or more second devices inside the transport prior to the transport ceasing operation.   
     
     
         11 . The transport of  claim 8 , wherein the processor is further configured to
 identify a data use time rule from the license file;   access the first type of data at a particular time during the period of time based on the data use time rule; and   remove the first type of data after the accessing.   
     
     
         12 . The transport of  claim 8 , wherein the processor is further configured to
 identify one or more transport occupants associated with the data;   retrieve data use consent information from the license file associated with the one or more occupants;   access one or more of the first, second and third data; and   update the license file to identify the accessed data.   
     
     
         13 . The transport of  claim 8 , wherein the processor is further configured to
 receive a validation of the data utilization from at least one component, wherein the validation comprises a blockchain consensus between a peer group consisting of the transport and the at least one component.   
     
     
         14 . The transport of  claim 13 , wherein the processor is further configured to
 execute a smart contract, by the transport, to record the validation and the at least one component on a blockchain based on the blockchain consensus.   
     
     
         15 . A non-transitory computer readable storage medium configured to store instructions that when executed cause a processor to perform:
 utilizing data, by a transport, for a period of time according to a license file;   removing a first type of the data, by the transport, while the transport is operating;   removing a second type of the data, by the transport when the transport ceases operating; and   retaining a third type of data in memory after the transport ceases operating.   
     
     
         16 . The non-transitory computer readable storage medium of  claim 15 , wherein the processor is further configured to perform:
 applying one or more of the first type of data and the second type of data to a device associated with one or more occupants; and   modifying one or more transport controls based on the third type of data.   
     
     
         17 . The non-transitory computer readable storage medium of  claim 15 , wherein the processor is further configured to perform:
 accessing the third type of data by one or more first devices operating inside the transport when the transport begins operating; and   accessing one or more of the first type of data and the second type of data by one or more second devices inside the transport prior to the transport ceasing operation.   
     
     
         18 . The non-transitory computer readable storage medium of  claim 15 , wherein the processor is further configured to perform:
 identifying a data use time rule from the license file;   accessing the first type of data at a particular time during the period of time based on the data use time rule; and   removing the first type of data after the accessing.   
     
     
         19 . The non-transitory computer readable storage medium of  claim 15 , wherein the processor is further configured to perform:
 identifying one or more transport occupants associated with the data;   retrieving data use consent information from the license file associated with the one or more occupants;   accessing one or more of the first, second and third data; and   updating the license file to identify the accessed data.   
     
     
         20 . The non-transitory computer readable storage medium of  claim 15 , wherein the processor is further configured to perform:
 receiving, by the transport, a validation of the data utilization from at least one component, wherein the validation comprises a blockchain consensus between a peer group consisting of the transport and the at least one component.

Join the waitlist — get patent alerts

Track US2022138667A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.