Card system

• US 20040139018A1
• Filed: 03/11/2004
• Published: 07/15/2004
• Est. Priority Date: 07/13/2000
• Status: Abandoned Application

• Current Assignee: VIX IP Pty Ltd. (Duncan Paul Saville,)
• Original Assignee: VIX IP Pty Ltd. (Duncan Paul Saville,)
• Inventors: Denison, Gyln G.H., Anderson, Ian R., Abotts, Michael E.
• Application Number:
  US10/332,611
• Publication Number:
  US 20040139018A1
• Time in Patent Office: Days
• US Class Current: 705/41
• CPC Class Codes: G06Q 20/105 involving programming of a portable memory device, e.g. IC cards, "electronic purses"
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system

Abstract

A card system including a plurality of component infrastructures, the component infrastructures each having core components of the system, the infrastructures having a hierarchal relationship such that one infrastructure is dependent on components of a lower infrastructure, and the core components being configurable for different card transaction applications.

Claims

1. A card system including a plurality of component infrastructures, said component infrastructures each having core components of said system, said infrastructures having a hierarchal relationship such that one infrastructure is dependent on components of a lower infrastructure, and said core components being configurable for different card transaction applications.

2. A card system as claimed in claim 1, wherein the components of an upper infrastructure are selectable for said applications and at least the components of a lower infrastructure are configured on the basis of configuration data.

3. A card system as claimed in claim 1, wherein an upper infrastructure includes management components to control data for cards, devices operable with the cards, participants, patrons and card purses.

4. A card system as claimed in claim 3, wherein a lower infrastructure has a component for managing configuration data for other components.

5. A card system as claimed in claim 3, wherein a lower infrastructure has a messaging component for handling message delivery between nodes of said system, and a publishing component for generating messages independent of said messaging component.

6. A card system as claimed in claim 5, wherein the messages received by a processor of a node are persisted in a data store of the node irrespective of whether the messages require further processing by other nodes of the system.

7. A card system as claimed in claim 6, wherein said nodes are communication network nodes and include components for a service provider, an acquirer, a clearing house and a card issuer, respectively.

8. A card system as claimed in claim 4, wherein the system includes nodes connected by a communications network, said nodes each having a transaction handler, said transaction handler including a unpacker to unpack transaction messages and route the messages to an instance of a transaction processor, said transaction processor controlling subsequent processing for said message.

9. A card system as claimed in claim 8, wherein said transaction processor initiates role processing of the message, based on a role for the message, such as purse or card management.

10. A card system as claimed in claim 9, wherein said processor initiates a validation process to validate the message.

11. A card system as claimed in claim 9, wherein said transaction processor initiates a process to determine the message is not a duplicate.

12. A card system as claimed in claim 2, wherein the upper infrastructure includes card management components for managing card issuance, maintenance of card data and hotlisting of cards.

13. A card system as claimed in claim 2, wherein said upper infrastructure includes components for managing devices of the system, including adding and removing devices, and remote configuration monitoring of devices, said devices being adapted to communicate with cards of the system.

14. A card system as claimed in claim 2, wherein the upper infrastructure includes components for managing financial services for participants, such as clearing and reconciliation of transactions between participants.

15. A card system as claimed in claim 2, wherein the upper infrastructure includes components for assigning roles and services to participants.

16. A card system as claimed in claim 2, wherein the upper infrastructure includes components for managing a purse on a card and for managing data associated with a patron using the card.

17. A card system as claimed in claim 1, wherein the components of a lower infrastructure include tools for graphical user application development to establish a framework for authentication of users.

18. A card system as claimed in claim 1, wherein components of a lower infrastructure include service components for handling transactions for components of an upper infrastructure at nodes of the system, and for maintaining and distributing action lists to a node.

19. A card system as claimed in claim 1, wherein the components of a lower infrastructure establish a messaging system for publishing messages to respective users of the system based on a topic of the message.

20. A card system as claimed in claim 1, wherein an upper infrastructure includes components for controlling the maintenance, distribution and access to configuration data for components of the system.

21. A card system as claimed in claim 1, wherein one of said infrastructures is a base services layer including core classes and an operating system interface having APIs for controlling, managing and providing access to OS resources.

22. A card system as claimed in claim 21, wherein said base service layer includes a serialisation component for converting objects into a stream for delivery.

23. A card system as claimed in claim 1, wherein an upper infrastructure has components adjusted by the components of a lower infrastructures.

24. A card system as claimed in claim 1, wherein the infrastructures include APIs and are platform independent.

25. A card system as claimed in claim 1, including managed objects having attributes to control the state of a resource of said system.

26. Software for a multiple application card system, stored on computer readable storage media, including a plurality of component infrastructures, said component infrastructures each having core components, said infrastructures having a hierarchal relationship such that one infrastructure is dependent on components of a lower infrastructure, and said core components being configurable for different card transaction applications.

27. Software as claimed in claim 26, wherein the components of an upper infrastructure are selectable for said applications and at least the components of a lower infrastructure are configured on the basis of configuration data.

28. Software as claimed in claim 26, wherein the upper infrastructure includes card management components for managing card issuance, maintenance of card data and hotlisting of cards.

29. Software as claimed in claim 27, wherein said upper infrastructure includes components for managing devices of the system, including adding and removing devices, and remote configuration monitoring of devices, said devices being adapted to communicate with cards of the system.

30. Software as claimed in claim 27, wherein the upper infrastructure includes components for managing financial services for participants, such as clearing and reconciliation of transactions between participants.

31. Software as claimed in claim 27, wherein the upper infrastructure includes components for assigning roles and services to participants.

32. Software as claimed in claim 27, wherein the upper infrastructure includes components for managing a purse on a card and for managing data associated with a patron using the card.

33. Software as claimed in claim 26, wherein the components of a lower infrastructure include tools for graphical user application development to establish a framework for authentication of users.

34. Software as claimed in claim 26, wherein components of a lower infrastructure include service components for handling transactions for components of an upper infrastructure at nodes of the system, and for maintaining and distributing action lists to a node.

35. Software as claimed in claim 26, wherein the components of a lower infrastructure publish messages to respective users of the system based on a topic of the message.

36. Software as claimed in claim 26, wherein an upper infrastructure includes components for controlling the maintenance, distribution and access to configuration data for components of the system.

37. Software as claimed in claim 26, wherein one of said infrastructures is a base services layer including core classes and an operating system interface having APIs for controlling, managing and providing access to OS resources.

38. Software as claimed in claim 37, wherein said base service layer includes a serialisation component for converting objects into a stream for delivery.

40. Software as claimed in claim 26, wherein the infrastructures include APis and are platform independent.

41. Software as claimed in claim 26, including managed objects having attributes to control the state of a resource of said system.

43. A transaction handler for a card system as claimed in claim 26, wherein said transaction processor maintains a cache for all messages received.

44. A transaction handler for a card system as claimed in claim 27, wherein said transaction handler initiates a plurality of threads of said unpacker and said transaction processor.

39. Software as claimed in claim 266, wherein an upper infrastructure has components adjusted by the components of a lower infrastructure.

42. A transaction handler for a card system, executed on a node of the system, having:

an unpacker for unpacking messages received by the node;

a router for routing unpacked messages to a transaction processor; and

a transaction processor for controlling validation, role processing and forwarding of said message.