ON-LINE GENERATION AND AUTHENTICATION OF ITEMS

• US 20090293112A1
• Filed: 12/02/2004
• Published: 11/26/2009
• Est. Priority Date: 12/03/2004
• Status: Abandoned Application

• Current Assignee: First Ondemand Limited
• Original Assignee: First Ondemand Limited
• Inventors: Fox, Francis Kirkman, Moore, Stephen James, Smith, Neil Richard Bradley, Lawson, Marcus Maxwell
• Application Number:
  US11/720,752
• Publication Number:
  US 20090293112A1
• Time in Patent Office: Days
• US Class Current: 726/9
• CPC Class Codes: G06Q 20/042 characterized in that the payment protocol involves at least one cheque
• CPC Class Codes: G06Q 20/06 Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 9/3234 involving additional secure or trusted devices, e.g. TPM, smartcard, USB or software token network architectures or network communication protocols for supporting authentication of entities using an additional device in a packet data network H04L63/0853

Abstract

Value based tokens are generated for inclusion on a data carrier which may be applied to a media such as a coupon, bank note etc. The tokens are generated by a core system which communicates with application specific wrappers. The wrappers supply token parameters to the core that are specific to the application and the core generates the tokens, and stores them for later authentication. The core then encodes the tokens onto a data carrier under the control of the wrapper and distributes the tokens under the control of the wrapper. When a token is presented for validation, for example by a customer in a shop, the encoded data carrier is scanned and the token retrieved. It is passed back to the core by the wrapper for validation of its identification number and other parameters.

Claims

1. A system for generating and authenticating tokens representing value, comprising:

a core system for generating and authenticating tokens; and

a plurality of application specific wrappers communicating with the core system each for providing the core system with application specific data relating to tokens generated by the core, whereby the core produces tokens which have a content controlled by the wrapper; and

wherein the core comprises;

a token generator responsive to one of the wrappers for generating value based tokens having parameters at least partially determined by the wrapper;

a store for storing the value based tokens;

an encoder for encoding the value based tokens onto a data carrier, the encoder being responsive to the wrapper to determine the encoding applied by the encoder; and

a token deliverer for delivering the generated tokens electronically to third parties via a delivery channel.

2. A system according to claim 1, wherein the delivery channel is selected by a wrapper.

3. A system according to claim 1, wherein the token generator creates a token in response to a request from the wrapper.

4. A system according to claim 1, wherein the token generator modifies a token in response to a request from the wrapper and stores the modified token in the store.

5. A system according to claim 1 wherein the encoder retrieves a token from the store for encoding according to a format specified by the wrapper.

6. A system according to claim 1, wherein the data carrier is a 2-dimensional bar code.

9. A system according to claim 1, wherein the toke generator comprises a token manager which receives a token type from the wrapper, generates a token identification number, and creates the token in the store.

10. A system according to claim 9, wherein the token manager receives further token attributes from the wrapper.

11. A system according to claim 10, wherein the further token attributes are at least one of a PIN code, data to be carried with the token, token start date, token end date, token status, and the number of times the token can be redeemed.

12. A system according to claim 9, wherein the token manager generates an internal token key for each token, the internal token key being used to reference the token identification number (TIN) when the TIN is received from a remote location for authentication.

13. A system according to claim 9, wherein the token manager retrieves a security function for the token type and applies the security function to the token prior to storage.

15. A system according to claim 1, wherein the encoder receives a request from the wrapper including the token identification number and the type of data carrier, and wherein the encoder returns the data carrier encoded with the token to the wrapper.

17. A system according to claim 1, wherein the core comprise a token authenticator for authenticating the validity of tokens received from the wrapper.

18. A system according to claim 17, wherein the authenticator receives the token TIN, confirms that the token exists in the store and authenticates the token if the token is stored as valid.

19. A system according to claim 18, wherein the token has a start and end date and authenticator further validates start and end dates.

20. A system according to claim 19, wherein the token has a redemption count indicating the number of times it can be redeemed and the authenticator validates the token only if the redemption count has not been exceeded.

21. A system according to claim 17, wherein the authenticator retrieves the security profile for the token and validates the security content of the token.

22. A system according to claim 17, wherein, the core further comprises a redemption component for redeeming authenticated tokens, the redemption component changing the status of a token in the store to indicate that it has been redeemed.

23. A system according to claim 22, wherein the redemption status is changed by incrementing a redemption count.

24. A system according to claim 1, wherein the token is a value based token having a header including a token identification number, a payload and a security section.

25. A system according to claim 24, wherein the payload includes an additional payload comprising a reference to data stored in the store which is provided on authentication of the token,

26. A system according to claim 25, wherein the payload and additional payload are data sets that are readable independently of each other.

27. A system according to claim 1, wherein each token has a non-repudiable time stamp associated with it on creation.

7. (canceled)

8. (canceled)

14. (canceled)

16. (canceled)