Generating event messages corresponding to event indicators

• US 20070265947A1
• Filed: 05/10/2006
• Published: 11/15/2007
• Est. Priority Date: 05/10/2006
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Weir, Robert, Stern, Edith, Willner, Barry, Schimpf, Brian
• Granted Patent: US 7,958,032 B2
• Time in Patent Office: Days
• US Class Current: 705/35
• CPC Class Codes: G06Q 20/102 Bill distribution or payments
• CPC Class Codes: G06Q 20/40 Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
• CPC Class Codes: G06Q 20/4014 Identity check for transactions
• CPC Class Codes: G06Q 20/4016 involving fraud or risk level assessment in transaction processing
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

A transaction entity handles event messages associated with events of interest. At least one type of event is identified that is of interest to a user. Each type of event further corresponds to an event type that is to be repeated by a transaction entity to an aggregating entity. Further, a description is associated with each identified type of event. The transaction entity identifies an occurrence of an event that is an identified type of event and generates an event message comprising a token that associates the user with an account maintained by the aggregating and the description that is associated with the identified type of event corresponding to the identified occurrence of the event. The event message is transmitted to the aggregating entity.

Claims

1. A computer implemented method for handling an event message associated with an event of interest comprising:

identifying at least one type of event that is of interest to a user and that corresponds to an event type that is to be reported by a transaction entity to an aggregating entity;

associating a description with each identified type of event;

detecting an occurrence of an event that is an identified type of event;

generating an event message comprising;

a token that associates said user with an account maintained by said aggregating entity; and

said description that is associated with said identified type of event corresponding to said identified occurrence of said event; and

transmitting said event message to said aggregating entity.

2. The method according to claim 1, wherein said identifying at least one type of event that is of interest to a user and that corresponds to an event type that is to be reported by a transaction entity to an aggregating entity comprises:

providing said user with a list of event types; and

identifying at least one type of event that is selected by said user from said list of event types.

3. The method according to claim 2, wherein:

said list of event types further comprises a default description for at least one listed event type; and

said associating a description with each identified type of event comprises;

associating a description identified by said user as either accepting said default description or providing a personalized description for at least one type of event from said list of event types provided to said user.

4. The method according to claim 1, wherein said associating a description with each identified type of event comprises:

associating, for at least one type of event, at least one description that acknowledges said occurrence of said event without describing the nature of said event.

5. The method according to claim 1, wherein said associating a description with each identified type of event comprises:

associating, for at least one type of event, a contextually meaningless personalized reference defined by said user.

6. The method according to claim 1, wherein said associating a description with each identified type of event comprises:

associating, for at least one type of event, a reference defined by said aggregating entity.

7. The method according to claim 1, wherein said associating a description with each identified type of event comprises:

associating, for at least one type of event, a reference defined by said transaction entity.

8. The method according to claim 1, wherein said generating an event message comprises:

dynamically generating at least part of at least one description based on at least one of a predetermined preference, a rule and an expression.

9. The method according to claim 1, wherein said generating an event message comprises:

retrieving at least one description from a static list of descriptions associated with identified types of events.

10. The method according to claim 1, wherein:

said associating a description with each identified type of event comprises;

associating a plurality of different descriptions for a select one type of event in a many to one relationship; and

said generating an event message further comprises;

selecting one of said plurality of different descriptions to include in said event message if said occurrence of said event is of said select one type of event.

11. The method according to claim 1, wherein:

said associating a description with each identified type of event comprises associating a same description with a plurality of types of events in a one to many relationship; and

said generating an event message further comprises selecting said same description to include in said event message if said occurrence of said event is of any one of said plurality of types of events.

12. The method according to claim 1, further comprising characterizing at least one type of event based upon at least one of a rule, an expression and an exception corresponding to a preference identified by said user.

13. A computer system to handle an event message associated with an event of interest comprising:

a module to identify at least one type of event that is of interest to a user and that corresponds to an event type that is to be reported by a transaction entity to an aggregating entity;

a module to associate a description with each identified type of event;

a module to detect an occurrence of an event that is an identified type of event;

a module to generate an event message comprising;

a token that associates said user with an account maintained by said aggregating entity; and

said description that is associated with said identified type of event corresponding to said identified occurrence of said event; and

a module to transmit said event message to said aggregating entity.

14. The system according to claim 13, wherein said module to identify at least one type of event that is of interest to a user and that corresponds to an event type that is to be reported by a transaction entity to an aggregating entity:

identifies at least one type of event that is selected by said user from a list of event types that was provided to said user.

15. The system according to claim 14, wherein:

said list of event types further comprises a default description for at least one listed event type; and

said module to associate a description with each identified type of event associates a description identified by said user as either accepting said default description or providing a personalized description for at least one type of event from said list of event types provided to said user.

16. The system according to claim 13, wherein said module to associate a description with each identified type of event associates, for at least one type of event, at least one description that acknowledges said occurrence of said event without describing the nature of said event.

17. The system according to claim 13, wherein said module to associate a description with each identified type of event associates, for at least one type of event, a contextually meaningless personalized reference defined by said user.

18. The system according to claim 13, wherein said module to associate a description with each identified type of event associates, for at least one type of event, a reference defined by said aggregating entity.

19. The system according to claim 13, wherein said module to associate a description with each identified type of event associates, for at least one type of event, a reference defined by said transaction entity.

20. The system according to claim 13, wherein said module to generate an event message dynamically generating at least part of at least one description based on at least one of a predetermined preference, a rule and an expression.

21. The system according to claim 13, wherein said module to generate an event message retrieves at least one description from a static list of descriptions associated with identified types of events.

22. The system according to claim 13, wherein:

said module to associate a description with each identified type of event associates a plurality of different descriptions for a select one type of event in a many to one relationship; and

said module to generate an event message selects one of said plurality of descriptions to include in a corresponding event message if said occurrence of said event is of said select one type of event.

23. The system according to claim 13, wherein:

said module to associate a description with each identified type of event associates a same description with a plurality of types of events in a one to many relationship; and

said module to generate an event message selects said same description to include in a corresponding event message if said occurrence of said event is of any one of said plurality of types of events.

24. The system according to claim 13, wherein said module to identify at least one type of event that is of interest to a user and that corresponds to a type of event that is to be reported by a transaction entity to an aggregating entity characterizes at least one type of event based upon at least one of a rule, an expression and an exception corresponding to a preference identified by said user.

25. A computer program product to handle an event message associated with an event of interest comprising:

a computer usable medium having computer usable program code embodied therewith, the computer usable program code comprising;

computer usable program code configured to identify at least one type of event that is of interest to a user and that corresponds to an event type that is to be reported by a transaction entity to an aggregating entity;

computer usable program code configured to associate a description with each identified type of event;

computer usable program code configured to detect an occurrence of an event that is an identified type of event;

computer usable program code configured to generate an event message comprising;

a token that associates said user with an account maintained by said aggregating entity; and

said description that is associated with said identified type of event corresponding to said identified occurrence of said event; and

computer usable program code configured to transmit said event message to said aggregating entity.

26. The computer program product according to claim 25, wherein said computer usable program code configured to identify at least one type of event that is of interest to a user and that corresponds to an event type that is to be reported by a transaction entity to an aggregating entity:

identifies at least one type of event that is selected by said user from a list of event types that was provided to said user.

27. The computer program product according to claim 26, wherein:

said list of event types further comprises a default description for at least one listed event type; and

said computer usable program code configured to associate a description with each identified type of event associates a description identified by said user as either accepting said default description or providing a personalized description for at least one type of event from said list of event types provided to said user.

28. The computer program product according to claim 25, wherein said computer usable program code configured to associate a description with each identified type of event associates, for at least one type of event, at least one description that acknowledges said occurrence of said event without describing the nature of said event.

29. The computer program product according to claim 25, wherein said computer usable program code configured to associate a description with each identified type of event associates, for at least one type of event, a contextually meaningless personalized reference defined by said user.

30. The computer program product according to claim 25, wherein said computer usable program code configured to associate a description with each identified type of event associates, for at least one type of event, a reference defined by said aggregating entity.

31. The computer program product according to claim 25, wherein said computer usable program code configured to associate a description with each identified type of event associates, for at least one type of event, a reference defined by said transaction entity.

32. The computer program product according to claim 25, wherein said computer usable program code configured to generate an event message dynamically generating at least part of at least one description based on at least one of a predetermined preference, a rule and an expression.

33. The computer program product according to claim 25, wherein said computer usable program code configured to generate an event message retrieves at least one description from a static list of descriptions associated with identified types of events.

34. The computer program product according to claim 25, wherein:

said computer usable program code configured to associate a description with each identified type of event associates a plurality of different descriptions for a select one type of event in a many to one relationship; and

said computer usable program code configured to generate an event message selects one of said plurality of descriptions to include in a corresponding event message if said occurrence of said event is of said select one type of event.

35. The computer program product according to claim 25, wherein:

said computer usable program code configured to associate a description with each identified type of event associates a same description with a plurality of types of events in a one to many relationship; and

said computer usable program code configured to generate an event message selects said same description to include in a corresponding event message if said occurrence of said event is of any one of said plurality of types of events.

36. The computer program product according to claim 25, wherein said computer usable program code configured to identify at least one type of event that is of interest to a user and that corresponds to a type of event that is to be reported by a transaction entity to an aggregating entity characterizes at least one type of event based upon at least one of a rule, an expression and an exception corresponding to a preference identified by said user.