Vehicle smart connection

US10939296B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10939296-B2
Application numberUS-201816105181-A
CountryUS
Kind codeB2
Filing dateAug 20, 2018
Priority dateAug 20, 2018
Publication dateMar 2, 2021
Grant dateMar 2, 2021

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

A vehicle includes a controller, programmed to responsive to wirelessly connecting to a mobile device using a mobile credential issued from a server within a time frame specified in the mobile credential, issue an access token to the mobile device, and responsive to receiving a command authorized by the access token from the mobile device, route the command to a vehicle subsystem for execution.

First claim

Opening claim text (preview).

What is claimed is: 1. A vehicle, comprising a controller, programmed to receive a vehicle credential from a server, wherein the vehicle credential is associated with a mobile credential, responsive to detecting a connecting attempt from a mobile device with the mobile credential, verify the mobile credential using the vehicle credential, responsive to a successful verification and wirelessly connecting to a mobile device with the mobile credential issued from a server within a time frame specified in the mobile credential, issue an access token to the mobile device using the vehicle credential, wherein the access token specifies an access authority to a plurality of vehicle subsystems, responsive to receiving a command from the mobile device verify if the command is authorized by the access token, and responsive to a successful verification, route the command to a vehicle subsystem for execution. 2. The vehicle of claim 1 , wherein the controller is further programmed to, responsive to receiving a delete instruction from the server, delete the vehicle credential. 3. The vehicle of claim 1 , wherein the controller is further programmed to, responsive to detecting a predefined threat initiated from the mobile device, disconnect from the mobile device and delete the vehicle credential. 4. The vehicle of claim 1 , wherein the controller is further programmed to: responsive to detecting a disconnection of the controller from the mobile device, start a timer for a predefined time period, and responsive to detecting an expiration of the timer and a failure to reconnect by the mobile device, delete the vehicle credential. 5. The vehicle of claim 1 , wherein the controller is further programmed to, responsive to detecting an expiration of the mobile credential defined by the time frame, disconnect from the mobile device. 6. The vehicle of claim 1 , wherein the controller is further programmed to, responsive to receiving a response signal from the vehicle subsystem, send the response signal to the mobile device. 7. The vehicle of claim 1 , wherein the mobile device is wirelessly connected to the controller using at least one of the following technologies: WiFi, near-field communication (NFC), or radio-frequency identification (RFID). 8. A method for a vehicle, comprising: receiving a vehicle credential from a server, wherein the vehicle credential is associated with a mobile credential; responsive to receiving a connection request from a mobile device using a mobile credential, verifying the mobile credential with the vehicle credential; responsive to a successful verification and connecting with the mobile device, issuing an access token to the mobile device based on the vehicle credential, wherein the access token specifies an access authority to perform a remote procedure call (RPC) to a vehicle subsystem; and responsive to receiving an verifying a RPC from the mobile device, perform the RPC via the vehicle subsystem, wherein at least one of the vehicle credential or the mobile credential is time-based by specifying a time frame defining a validity of the credential. 9. The method of claim 8 , further comprising: responsive to detecting an expiration of the time frame, disconnecting the mobile device and delete the vehicle credential. 10. The method of claim 8 , further comprising: responsive to detecting the RPC is not authorized by the access token, declining to perform the RPC. 11. The method of claim 8 , further comprising: responsive to detecting a current time beyond the time frame, declining to the connection request from the mobile device. 12. The method of claim 8 , further comprising: responsive to detecting a disconnection from the mobile device, starting a timer for a predefined time period, and responsive to detecting an expiration of the timer and a failure to reconnect by the mobile device, deleting the vehicle credential. 13. A mobile device, comprising: a processor, programmed to send a request for vehicle including a time condition and location condition to a server; responsive to receiving a mobile credential from the server specifying a time frame defining a validity of the mobile credential and a current time being within the time frame, connect to a vehicle specified in the mobile credential; responsive to receiving an access token from the vehicle, send a remote procedure call (RPC) to the vehicle; and receive a response from the vehicle. 14. The mobile device of claim 13 , wherein the processor is further programmed to, responsive to detecting an expiration of the time frame, disconnect from the vehicle and delete the mobile credential. 15. The mobile device of claim 13 , wherein the processor is further programmed to, responsive to detecting a second mobile device connected to the vehicle, communicate with a second mobile device using the access token via the vehicle. 16. The mobile device of claim 13 , wherein the processor is further programmed to, responsive to detecting a distance between the mobile device and the vehicle extending beyond a predefined threshold, delete the mobile credential and send an alert to the server. 17. The mobile device of claim 13 , wherein the processor is further programmed to, responsive to detecting a disconnection of the mobile device from the vehicle for long than a predefined time period and a failure to reconnect by to the vehicle, delete the mobile credential and send an alert to the server.

Assignees

Inventors

Classifications

  • Protocols for remote procedure calls [RPC] · CPC title

  • Location-dependent; Proximity-dependent · CPC title

  • Security of mobile devices; Security of mobile applications · CPC title

  • Remote procedure calls [RPC]; Web services · CPC title

  • H04W12/08Primary

    Access security · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10939296B2 cover?
A vehicle includes a controller, programmed to responsive to wirelessly connecting to a mobile device using a mobile credential issued from a server within a time frame specified in the mobile credential, issue an access token to the mobile device, and responsive to receiving a command authorized by the access token from the mobile device, route the command to a vehicle subsystem for execution.
Who is the assignee on this patent?
Ford Global Tech Llc
What technology area does this patent fall under?
Primary CPC classification H04W12/08. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Mar 02 2021 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).