Authenticating users during and after suspicious voice calls and browsing
US-2024364684-A1 · Oct 31, 2024 · US
US9769162B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9769162-B2 |
| Application number | US-201414330672-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jul 14, 2014 |
| Priority date | Mar 28, 2008 |
| Publication date | Sep 19, 2017 |
| Grant date | Sep 19, 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.
In a method for using and maintaining user data stored on a smart card, a smart card receives a user data request for the user data stored on the smart card. The smart card determines whether the user data request is a data maintenance request or a data use request. A data maintenance request is for modifying user data stored on the smart card. A data use request is for read only access to user data stored on the smart card. The smart card uses a first process to determine whether to allow the user data request when the user data request is determined to be a data maintenance request. The smart card uses a second process, different from the first method, to determine whether to allow the user data request when the user data request is determined to be a data use request.
Opening claim text (preview).
I claim: 1. A method for using and maintaining user data stored on a multi-application smart card comprising a memory, the method comprising: storing in the memory of said multi-application smart card a first application comprising first executable code, wherein said first application is associated with first user data and a first data use password and a first data maintenance password stored in the memory; storing in the memory of said multi-application smart card a second application comprising second executable code, wherein said second application is associated with second user data and a second data use password and a second data maintenance password stored in the memory; receiving, on said smart card, a user data request wherein said data request includes a received password; determining, on said smart card, whether said user data request is a data maintenance request or a data use request, wherein a data maintenance request is for modifying user data stored on said smart card, and a data use request is for read only access to user data stored on said smart card; comparing, on said smart card, the received password with the first data use password stored in the memory, and authorizing read only access to the first user data if the received password matches the first data use password; comparing, on said smart card, the received password with the second data use password stored in the memory, and authorizing read only access to the second user data if the received password matches the second data use password; comparing, on said smart card, the received password with the first data maintenance password stored in the memory, and authorizing read and write access to the first user data if the received password matches the first data maintenance password; and comparing, on said smart card, the received password with the second data maintenance password stored in the memory, and authorizing read and write access to the second user data if the received password matches the second data maintenance password. 2. The method of claim 1 wherein said first data maintenance password comprises a first stored passphrase and said second data maintenance password comprises a second stored passphrase. 3. The method of claim 1 wherein said first data maintenance password comprises a first stored personal identification number (PIN) and said second data maintenance password comprises a second stored PIN. 4. The method of claim 1 wherein said data request includes a received identifier wherein said received identifier comprises a static identifier associated with a home terminal and said static identifier does not change with each user data request received by said smart card from said home terminal, and further wherein, said method further comprises: comparing said received identifier with a static identifier stored in the memory on said smart card; and preventing write access to at least one of the first user data and second user data if the received identifier does not match the static identifier stored in the memory on said smart card. 5. The method of claim 4 wherein said static identifier stored in the memory on said smart card is stored in a list of static identifiers stored on said smart card. 6. The method of claim 1 wherein said user data request includes a received identifier wherein said received identifier comprises a dynamic identifier associated with a home terminal and said dynamic identifier is different in each data maintenance request received by said smart card from said home terminal, and further wherein, said first process further comprises: comparing said received identifier with a dynamic identifier stored on said smart card; and preventing write access to at least one of the first user data and second user data if the received identifier does not match the dynamic identifier stored on said smart card. 7. The method of claim 6 wherein said dynamic identifier comprises a next identifier generated using an end identifier and a last identifier in a one way function. 8. The method of claim 1 , wherein said first application is associated with a different commercial entity than said second application. 9. The method of claim 1 wherein said user data request comprises an authenticated data maintenance request including a received identifier wherein said received identifier comprises a static identifier associated with a home terminal and said static identifier does not change with each data maintenance request received by said smart card from said home terminal, and further wherein, said first process comprises: using a key stored on said smart card to verify said authenticated data maintenance request; comparing said received identifier with a stored static identifier stored on said smart card; and allowing said data maintenance request upon said authenticated data maintenance request being verified and said received identifier matching said stored static identifier. 10. The method of claim 9 wherein said stored static identifier is stored in a list of static identifiers stored on said smart card. 11. A non-transitory computer readable medium including instructions stored thereon for supporting using and maintaining user data stored on a multi-application smart card comprising a memory, which instructions, when executed, cause the multi-application smart card to perform steps comprising: storing in the memory of said multi-application smart card a first application comprising first executable code, and storing in said memory a first user data, a first data use password, and a first data maintenance password associated with said first application; storing in the memory of said multi-application smart card a second application comprising second executable code, and storing in said memory a second user data, a second data use password, and a second data maintenance password associated with said second application; receiving, on said smart card, a user data request wherein said data request includes a received password; determining, on said smart card, whether said user data request is a data maintenance request or a data use request, wherein a data maintenance request is for modifying user data stored on said smart card, and a data use request is for read only access to user data stored on said smart card; comparing, on said smart card, the received password with the first data use password stored in the memory, and authorizing read only access to the first user data if the received password matches the first data use password; comparing, on said smart card, the received password with the second data use password stored in the memory, and authorizing read only access to the second user data if the received password matches the second data use password; comparing, on said smart card, the received password with the first data maintenance password stored in the memory, and authorizing read and write access to the first user data if the received password matches the first data maintenance password; and comparing, on said smart card, the received password with the second data maintenance password stored in the memory, and authorizing read and write access to the second user data if the received password matches the second data maintenance password. 12. A multi-application smart card comprising: a processor and a memory; wherein the multi-application smart card is configured to perform steps comprising: storing in the memory of said multi-application smart card a first application comprising first executable code, and storing in said memory a first user data, a first data use password, and a first data maintenance password associated with said first app
Verifying personal identification numbers [PIN] · CPC title
involving programming of a portable memory device, e.g. IC cards, "electronic purses" · CPC title
Identification of user by a PIN code · CPC title
together with a coded signal {, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data} · CPC title
Access rights to memory zones · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.