Electronic device and method for establishing conference call
US-2016088033-A1 · Mar 24, 2016 · US
US10601796B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10601796-B2 |
| Application number | US-201715462301-A |
| Country | US |
| Kind code | B2 |
| Filing date | Mar 17, 2017 |
| Priority date | Mar 17, 2016 |
| Publication date | Mar 24, 2020 |
| Grant date | Mar 24, 2020 |
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.
Systems, methods, and computer-readable media for personalizing program credentials are provided. For example, a program credential (e.g., loyalty pass) associated with a program provider (e.g., an issuer) subsystem may be customized using personal data. The personal data can be collected from an electronic device before provisioning the customized program credential on the electronic device for use in a suitable transaction. However, such personal data may not be collected unless an administration entity subsystem is first able to validate the program provider subsystem. The administration entity subsystem can generate tracking data that may be used during the validation and/or provisioning in order to track when program credentials are personalized.
Opening claim text (preview).
What is claimed is: 1. A method comprising: at an administration entity subsystem: receiving first data from an electronic device, wherein the first data comprises program provider information indicative of a program provider subsystem; determining that the program provider subsystem is valid based on the program provider information; in response to determining that the program provider subsystem is valid, associating tracking data with the program provider information in a data structure; transmitting second data to the electronic device, wherein the second data comprises the tracking data; receiving third data from the electronic device, wherein the third data comprises program provider data; determining that the program provider data is in the data structure; and in response to determining that the program provider data is in the data structure, enabling personalization of a program provider credential on the electronic device. 2. The method of claim 1 , wherein: prior to determining that the program provider data is in the data structure, the method further comprises, at the administration entity subsystem, identifying a program provider key; prior to determining that the program provider data is in the data structure, the method further comprises, at the administration entity subsystem, unsigning the program provider data with the identified program provider key; determining that the program provider data is in the data structure comprises determining that the unsigned program provider data is in the data structure; and the enabling comprises enabling the personalization of the program provider credential on the electronic device. 3. The method of claim 2 , wherein the identifying the program provider key comprises identifying the program provider key based on the program provider information. 4. The method of claim 2 , wherein: the third data further comprises other program provider information indicative of the program provider subsystem; and the identifying the program provider key comprises identifying the program provider key based on the other program provider information. 5. The method of claim 2 , further comprising, at the administration entity subsystem, prior to receiving the first data from the electronic device, sharing the program provider key with the program provider subsystem. 6. The method of claim 2 , wherein the program provider key is not accessible by the electronic device. 7. The method of claim 2 , wherein the determining that the unsigned program provider data is in the data structure comprises determining that the unsigned program provider data is associated with the program provider information in the data structure. 8. The method of claim 7 , wherein the unsigned program provider data is the tracking data. 9. The method of claim 2 , wherein: a signature of the program provider data comprises a certificate; and the method further comprises, prior to the enabling personalization of the program provider credential, at the administration entity subsystem, validating the signature of the program provider data using the certificate. 10. The method of claim 1 , wherein: prior to transmitting the second data, the method further comprises, at the administration entity subsystem, identifying a program provider key; and the second data comprises the tracking data signed with the identified program provider key as signed tracking data. 11. The method of claim 10 , wherein the identifying the program provider key comprises identifying a merchant key based on merchant information. 12. The method of claim 10 , wherein: the third data further comprises the program provider information indicative of the program provider subsystem; and the determining that the program provider data is in the data structure comprises determining that the program provider data of the third data is associated in the data structure with the program provider information of the third data. 13. The method of claim 10 , further comprising, at the administration entity subsystem, prior to receiving the first data from the electronic device, sharing the program provider key with the program provider subsystem. 14. The method of claim 10 , wherein the program provider key is not accessible by the electronic device. 15. The method of claim 10 , wherein the determining that the program provider data is in the data structure comprises determining that the program provider data is associated with the program provider information in the data structure. 16. The method of claim 15 , wherein the program provider data is the tracking data. 17. The method of claim 1 , wherein the enabling comprises transmitting fourth data to the electronic device, wherein the fourth data is operative to complete provisioning of the program provider credential on the electronic device. 18. The method of claim 1 , further comprising, based on the enabling, charging the program provider subsystem a fee at the administration entity subsystem. 19. A device comprising: a memory; and at least one processor configured to: receive first data from an electronic device, wherein the first data comprises program provider information indicative of a program provider subsystem; determine that the program provider subsystem is valid based on the program provider information; in response to a determination that the program provider subsystem is valid, associate tracking data with the program provider information in a data structure; transmit second data to the electronic device, wherein the second data comprises the tracking data; after transmission of the second data, receive third data from the electronic device, wherein the third data comprises signed program provider data; identify a program provider key; unsign the program provider data with the identified program provider key; determine that the unsigned program provider data is associated with the program provider information in the data structure; and in response to a determination that the unsigned program provider data is associated with the program provider information in the data structure, confirm personalization of a program provider credential on the electronic device. 20. The device of claim 19 , wherein the at least one processor is configured to identify the program provider key based on the program provider information. 21. The device of claim 19 , wherein: the third data further comprises other program provider information indicative of the program provider subsystem; and the at least one processor is configured to identify the program provider key based on the other program provider information. 22. The method of claim 19 , wherein the at least one processor is further configured to transmit fourth data to the electronic device, wherein the fourth data is operative to complete provisioning of the program provider credential on the electronic device. 23. The method of claim 19 , wherein the at least one processor is further configured to: prior to receipt of the first data from the electronic device, share the program provider key with the program provider subsystem. 24. The device of claim 19 , wherein the program provider key is not accessible by the electronic device. 25. A non-transitory machine-readable medium comprising code that, when executed by one or more processors, causes the one or more processors to perform operations, the code comprisi
Incentive systems for frequent usage, e.g. frequent flyer miles programs or point systems · CPC title
using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263) · CPC title
Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication · CPC title
Subscription-based services using application servers or record carriers, e.g. SIM application toolkits · CPC title
Authentication · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.