US2024177546A1PendingUtilityA1
Vehicle sensor tracking for customized vehicle profile
Assignee: TOYOTA MOTOR NORTH AMERICA INCPriority: May 9, 2019Filed: Feb 7, 2024Published: May 30, 2024
Est. expiryMay 9, 2039(~12.8 yrs left)· nominal 20-yr term from priority
G07C 5/085G06F 16/27G07C 5/0808G07C 5/008G06F 16/9035
70
PatentIndex Score
0
Cited by
0
References
0
Claims
Abstract
An example operation may include one or more of initiating a vehicle event, retrieving a user profile associated with a user participating in the vehicle event, applying a vehicle status, based on the user profile, to the vehicle event, permitting access to a first set of vehicle features based on the vehicle status, collecting vehicle actions performed during the vehicle event for a period of time, and determining whether to increase or decrease a vehicle status based on the collected vehicle actions.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method, comprising:
receiving, by a first hardware-implemented server, information related to an event associated with an operation of a vehicle from a device of a user; retrieving, by the first hardware-implemented server, a user profile of the user, wherein the user profile is linked to a second hardware-implemented server that is different than the first hardware-implemented server; sending, by the second hardware-implemented server, a status of the user based on the user profile to the vehicle to permit access by a user to a first set of vehicle features; receiving, by the first hardware-implemented server and the second hardware-implemented server, a value associated with information regarding actions performed by the vehicle for a certain period of time during the event; and determining, by the first hardware-implemented server and the second hardware-implemented server, whether to increase or decrease the status by increasing or decreasing a number of features that can be operated by the user based on the value being within or below a first threshold range associated with the first hardware-implemented server and the value being within or below a second threshold range associated with the second hardware-implemented server, wherein the second threshold range is greater than the first threshold range.
2 . The method of claim 1 , wherein the information regarding actions performed by the vehicle is collected by one or more sensors associated with the vehicle.
3 . The method of claim 1 , wherein the determining whether to increase or decrease the status further comprises:
comparing the information regarding actions performed by the vehicle to a set of predetermined vehicle actions; identifying that the information regarding the actions performed by the vehicle is within the threshold range; and increasing the status to an increased status in response to the identifying.
4 . The method of claim 3 , further comprising:
sending the increased status to the vehicle to permit access to a second set of vehicle features comprising one or more vehicle features that were not accessible to the status.
5 . The method of claim 1 , further comprising:
retrieving, by the hardware-implemented server, a smart contract from the blockchain, wherein the smart contract specifies a plurality of vehicle statuses associated with corresponding sets of vehicle features.
6 . The method of claim 3 , further comprising:
updating the user profile in the blockchain with the increased status.
7 . The method of claim 1 , further comprising:
creating a blockchain transaction comprising the increased or decreased status; and storing the blockchain transaction in the blockchain.
8 . A system, comprising:
a first hardware-implemented server the first hardware-implemented server comprising:
a processor that, when executing one or more instructions stored in an associated memory, is configured to:
receive information related to an event associated with an operation of a vehicle from a device of a user;
retrieve a user profile of the user, wherein the user profile is linked to a second hardware-implemented server that is different than the first hardware-implemented server; and
the second hardware-implemented server is different than the first hardware-implemented server, wherein the second hardware-implemented server is configured to:
send a status of the user based on the user profile to the vehicle to permit access by a user to a first set of vehicle features;
wherein both the first hardware-implemented server and the second hardware-implemented server are configured to:
receive a value associated with information in regards to actions performed by the vehicle for a certain period of time while the event is in process; and
determine whether to increase or decrease the status by the increase or the decrease of a number of features that can be operated by the user based on the value that is within or below a first threshold range associated with the first hardware-implemented server and the value that is within or below a second threshold range associated with the second hardware-implemented server, wherein the second threshold range is greater than the first threshold range.
9 . The server of claim 8 , wherein the information regarding actions performed by the vehicle is collected by one or more sensors associated with the vehicle.
10 . The server of claim 8 , wherein, when the processor is configured to determine whether to increase or decrease the status, the processor is further configured to:
compare the information regarding actions performed by the vehicle to a set of predetermined vehicle actions; identify that the information regarding the actions performed by the vehicle is within the threshold range; and increase the status to an increased status in response to the identifying.
11 . The server of claim 10 , wherein the processor is further configured to:
send the increased status to the vehicle to control the vehicle to permit access to a second set of vehicle features comprising one or more vehicle features that were not accessible to the status.
12 . The server of claim 8 , wherein the processor is further configured to:
retrieve a smart contract from the blockchain,
wherein the smart contract specifies a plurality of vehicle statuses associated with related sets of vehicle features.
13 . The server of claim 10 , wherein the server is further configured to:
update the user profile in the blockchain with the increased status.
14 . The server of claim 8 , wherein the server is further configured to:
create a blockchain transaction comprising the increased or decreased status based on the user profile; and store the blockchain transaction in the blockchain.
15 . A non-transitory computer readable medium comprising one or more instructions that when executed by a processor, cause the processor to perform:
receiving, by a first hardware-implemented server, information related to an event associated with an operation of a vehicle from a device of a user; retrieving, by the first hardware-implemented server, a user profile of the user, wherein the user profile is linked to a second hardware-implemented server that is different than the first hardware-implemented server; sending, by the second hardware-implemented server, a status of the user based on the user profile to the vehicle to permit access by a user to a first set of vehicle features; receiving, by the first hardware-implemented server and the second hardware-implemented server, a value associated with information regarding actions performed by the vehicle for a certain period of time during the event; and determining, by the first hardware-implemented server and the second hardware-implemented server, whether to increase or decrease the status by increasing or decreasing a number of features that can be operated by the user based on the value being within or below a first threshold range associated with the first hardware-implemented server and the value being within or below a second threshold range associated with the second hardware-implemented server, wherein the second threshold range is greater than the first threshold range.
16 . The non-transitory computer readable medium of claim 15 , wherein the information regarding actions performed by the vehicle is collected by one or more sensors associated with the vehicle.
17 . The non-transitory computer readable medium of claim 15 , wherein the determining whether to increase or decrease the status further comprises:
comparing the information regarding actions performed by the vehicle to a set of predetermined vehicle actions; identifying that the information regarding the actions performed by the vehicle is within the threshold range; and increasing the status to an increased status in response to the identifying.
18 . The non-transitory computer readable medium of claim 17 , wherein the one or more instructions further cause the processor to perform:
sending the increased status to the vehicle to control the vehicle to permit access to a second set of vehicle features comprising one or more vehicle features that were not accessible to the status.
19 . The non-transitory computer readable medium of claim 15 , wherein the one or more instructions further cause the processor to perform:
retrieving a smart contract from the blockchain, wherein the smart contract specifies a plurality of statuses associated with corresponding sets of vehicle features.
20 . The non-transitory computer readable medium of claim 17 , wherein the one or more instructions further cause the processor to perform:
updating the user profile in the blockchain with the increased status.Join the waitlist — get patent alerts
Track US2024177546A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.