The invention relates generally to the field of communication and relates specifically to targeted information exchange agreed upon by the parties involved.
When two parties interact to ready for a transaction, they are often required to provide information to the other party or a third party. In most cases it is done by direct exchange: a customer picks a coupon booklet at the store entrance. In some cases the information exchanged is sensitive. Quite often, however, such an approach is inconvenient (as in a large store, where coupons and promotions would better work if offered in right locations: at isles or sections) and insecure (as on websites, where a customer fills forms providing personal information). It would be much more secure and convenient to keep the data on a secure data server, and provide a method for users to authorize such an information exchange.
Such systems, indeed, already exist, but they mostly are limited to the web. PayPal, for instance, while confirming payment, provides a merchant with customer's shipping address, automatically pre-filling related forms with information stored on its servers. OpenID does similar job providing personal information stored on a trusted OpenID server. There is a need in a system that would dispatch information when all parties involved are not necessarily online and which would provide consistent experience for online and offline cases.
A system of token-based information exchange meets the need for a system described in the previous section. To perform information exchange a Publisher requests and Token Management Service creates a unique token, which is presented by the Publisher to a user and is scanned by the user PTD. Said PTD send it identifier and the token to the Token Management Service. The Token Management Service establishes the link between the request and the PTD identifier. Said link is user to exchange information between the user, the Publisher, the Token Management Service, and the parties authorized by the above three.
In this specific embodiment shown on
Publisher and the PTD
1. At a prior time a user logs into the Information Service and enters personal information (arrow 1).
2. For each web browsing session containing fillable forms a publisher (web server) sends a request for new token from Token Management Service wherein it specifies the information needed to fill the form (arrow 2).
3. Token Management Service issues a new token and sends it to the web server (arrow 3).
4. Web server inserts a graphical representation of the token as a two-dimensional barcode into the web page (arrow 4).
5. The token is scanned by a personal trusted device (arrow 5).
6. The PTD sends a message to the Token Management Service containing the scanned token and identifier of the PTD (arrow 6).
7. The Authentication subsystem authenticates the user by requesting, receiving, and verifying user credential from PTD (arrow 7 and 8).
8. The Token Management Service retrieves the requested information from the Information Service and passes it to the web server (arrow 9).
9. The web server updates the web page containing the form with information received at the previous step (arrow 10).
Number | Date | Country | |
---|---|---|---|
61298695 | Jan 2010 | US |