Fuel dispenser user interface system architecture
US-9268930-B2 · Feb 23, 2016 · US
US9715600B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9715600-B2 |
| Application number | US-201615049750-A |
| Country | US |
| Kind code | B2 |
| Filing date | Feb 22, 2016 |
| Priority date | Nov 29, 2012 |
| Publication date | Jul 25, 2017 |
| Grant date | Jul 25, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A vending machine can include a touch display and a touch controller operatively connected to the touch display and configured to transmit display data to the touch display and receive input data from a touchscreen function of the touch display. The vending machine also includes a secure device operatively connected to the touch display for securing the display by managing touch input information provided to one or more applications based on the input data received from the touchscreen functionality. The vending machine has a processor operatively connected to the secure device for communicating access requests for the touch display to the secure device from the one or more applications along with an indication of whether the one or more applications are signed by an authorized entity. The secure device manages the touch input information provided to the one or more applications further based at least in part on the indication.
Opening claim text (preview).
What is claimed is: 1. A method for controlling access to a touch display, comprising: receiving input data from a touch display, wherein the input data is associated with an application accessing the touch display; determining whether the application is signed by an authorized entity based at least in part on determining whether a secure channel is established with the application via an encryption key pair wherein the application has one key of the encryption key pair and another key of the encryption key pair is stored at a secure device that controls the touch display, wherein the one key is previously provided as part of an application verification process; and providing touch input information correlating to the input data to the application based at least in part on whether the application is signed by the authorized entity. 2. The method of claim 1 , further comprising generating the touch input information by restricting the input data where the application is not signed by an authorized entity. 3. The method of claim 2 , wherein the generating the touch input information comprises determining one of a fixed number of regions on the touch display correlating to the input data as the touch input information. 4. The method of claim 2 , wherein the generating the touch input information comprises determining coordinate information correlating to the input data as the touch input information. 5. The method of claim 1 , wherein the secure channel communicates the input data to a processor. 6. The method of claim 5 , further comprising maintaining the secure channel at least in part by determining whether a consistent ping message is received from the processor. 7. The method of claim 6 , further comprising disabling the touch display based at least in part on determining that the consistent ping message is not received from the processor over a period of time. 8. The method of claim 6 , further comprising erasing at least a portion of a memory upon detecting removal of at least one cable to the processor or to the touch display. 9. The method of claim 1 , further comprising encrypting a portion of the touch input information for communicating to the application over the secure channel.
during program execution, e.g. stack integrity {; Preventing unwanted data erasure; Buffer overflow} · CPC title
Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities · CPC title
output devices, e.g. displays or monitors · CPC title
Program or device authentication · CPC title
by graphic or iconic representation · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.