System and method for transferring data between applications

• US 20060059230A1
• Filed: 08/08/2002
• Published: 03/16/2006
• Est. Priority Date: 08/08/2002
• Status: Abandoned Application

• Current Assignee: Connecticut General Life Insurance Company (CIGNA Corporation)
• Original Assignee: Connecticut General Life Insurance Company (CIGNA Corporation)
• Inventors: Wagner, Thomas F., Kirk, Alan G., Dykas, John J., Wayand, Jeffrey L.
• Application Number:
  US10/215,350
• Publication Number:
  US 20060059230A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06

Abstract

A method of transferring data between applications, wherein at least one datum relating to a subject is published by a first application over a transport infrastructure; and the published at least one datum is provided in accordance with a delivery protocol to a second application that has previously subscribed to the subject, subscription to a subject comprising specifying one of a plurality of delivery protocols; and the published at least one datum being provided in accordance with the delivery protocol specified in the course of the second application'"'"'s subscription to the subject.

Claims

1. A method of verifying the delivery of information to applications, comprising:

(a) storing in a database information regarding the expected delivery of a message generated by a first application to a second application;

(b) verifying that the second application has received the message within an anticipated time frame; and

(c) sending a second message if the message has not been received by the second application within the anticipated time frame,

wherein the first and second applications are run on different platforms.

2. The method of claim 1, wherein the second message is sent to the first application.

3. The method of claim 1, wherein the second message is sent to a third application.

4. The method of claim 1, wherein the second message is sent to at least one person.

5. The method of claim 4, wherein the second message is sent by electronic mail.

6. The method of claim 4, wherein the second message is sent by page.

7. The method of claim 1, wherein the message generated by the first application is generated on a batch schedule.

8. The method of claim 7, wherein step (a) comprises storing information related to the batch schedule in the database.

9. The method of claim 8, wherein the stored information comprises information relating to the size of the information sent.

10. The method of claim 8, wherein the stored information comprises information relating to the estimated size of the information sent.

11. The method of claim 8, wherein the stored information comprises information relating to the average size of a class of information sent by an application.

12. The method of claim 8, wherein the stored information comprises information relating to the estimated time of delivery of the information.

13. The method of claim 8, wherein the stored information comprises information relating to the estimated amount of time required for delivery of the information to the second application.

14. The method of claim 8, wherein the stored information comprises information relating to a delay tolerance relating to the delivery of the information.

15. The method of claim 8, wherein the stored information comprises information relating to the urgency of the information.

16. The method of claim 8, wherein the stored information comprises information relating to a type of second message to be sent.

17. The method of claim 8, wherein the stored information comprises information relating to the identity of the recipient of the second message.

18. The method of claim 8, wherein the stored information comprises information relating to the type of information being sent.

19. The method of claim 1, wherein the message generated by the first application is generated in near real time.

20. The method of claim 19, wherein the stored information comprises information relating to the estimated amount of time required for delivery of the information to the second application.

21. The method of claim 19, wherein the stored information comprises information relating to a delay tolerance relating to the delivery of the information.

22. The method of claim 19, wherein the stored information comprises information relating to the urgency of the information.

23. A method of verifying the delivery of information to applications, comprising steps for:

(a) storing information regarding the expected delivery of a message generated by a first application to a second application;

(b) verifying that the second application has received the message within an anticipated time frame; and

(c) sending a second message if the message has not been received by the second application within the anticipated time frame,

wherein the first and second applications are run on different platforms.

24. A system for verifying the delivery of information to applications, comprising:

means for storing in a database information regarding the expected delivery of a message generated by a first application to a second application;

means for verifying that the second application has received the message within an anticipated time frame; and

means for sending a second message if the message has not been received by the second application within the anticipated time frame,

wherein the first and second applications are run on different platforms.

25. A computer-readable medium having stored thereon computer-executable instructions for performing the steps comprising:

(a) storing in a database information regarding the expected delivery of a message generated by a first application to a second application;

(b) verifying that the second application has received the message within an anticipated time frame; and

(c) sending a second message if the message has not been received by the second application within the anticipated time frame,

wherein the first and second applications are run on different platforms.

26. A system for verifying the delivery of information to applications, comprising:

a processor;

a memory in communication with said processor; and

a database stored in said memory,

wherein said processor stores in said database information regarding the expected delivery of a message generated by a first application to a second application;

wherein said processor verifies that the second application has received the message within an anticipated time frame;

wherein said processor sends a second message if the message has not been received by the second application within the anticipated time frame; and

wherein the first and second applications are run on different platforms.

27. A computer-readable medium having stored thereon a data structure relating to the verification of delivery of information, comprising:

an attribute relating to a subject;

an attribute relating to an expected time of delivery; and

an attribute relating to a delay tolerance.

28. The computer-readable medium of claim 27, further comprising:

an attribute relating to an action to be taken if a message is not delivered within a delay tolerance of an expected time of delivery.

29. The computer readable medium of claim 27, wherein the data structure comprises an object.

30. The computer readable medium of claim 27, wherein the data structure comprises a database record.

31. The computer readable medium of claim 27, wherein the data structure comprises a record in a flat file.

32. A computer-readable medium having stored thereon a data structure relating to the verification of delivery of information, comprising:

an attribute relating to the identity of the sender of the at least one datum;

an attribute relating to an expected time of delivery; and

an attribute relating to a delay tolerance.

33. The computer-readable medium of claim 32, further comprising:

an attribute relating to an action to be taken if a message is not delivered within a delay tolerance of an expected time of delivery.

34. The computer readable medium of claim 32, wherein the data structure comprises an object.

35. The computer readable medium of claim 32, wherein the data structure comprises a database record.

36. The computer readable medium of claim 32, wherein the data structure comprises a record in a flat file.

37. A method of verifying the delivery of information to applications, comprising:

(a) storing in a computer memory information regarding the expected delivery of a message generated by a first application to a second application;

(b) verifying that the second application has received the message within an anticipated time frame; and

(c) sending a second message if the message has not been received by the second application within the anticipated time frame,

wherein the first and second applications are run on different platforms.

38. A method of verifying the delivery of information to applications, comprising:

(a) storing in a computer memory information regarding the expected delivery of a message generated by a first application to a second application;

(b) verifying that the second application has received the message within an anticipated time frame; and

(c) sending a second message if the message has not been received by the second application within the anticipated time frame,

wherein the information stored in step (a) comprises information relating to the urgency of the message.

39. A method of transferring medical insurance data between applications, comprising:

(a) in response to an event, packaging at least one datum from a first application into a message;

(b) sending the message across a transport infrastructure to a second application;

(c) unpackaging the at least one datum; and

(d) generating an event in the second application based at least in part on the at least one datum.

40. A method of transferring employee benefit data between applications, comprising:

(a) in response to an event, packaging at least one datum from a first application into a message;

(b) sending the message across a transport infrastructure to a second application;

(c) unpackaging the at least one datum; and

(d) generating an event in the second application based at least in part on the at least one datum.

41. The method of claim 40, wherein the first and second applications are incompatible.

42. The method of claim 40, wherein the first and second applications are stored on separate computers.

43. The method of claim 40, wherein the first and second applications are stored on separate computers located in different geographic locations.

44. The method of claim 40, wherein the first and second applications are stored on separate computers that run different operating systems.

45. The method of claim 40, wherein the first and second applications are stored on separate computers that run incompatible operating systems.

46. The method of claim 40, wherein the at least one datum packaged in step (a) is packaged by an adapter.

47. The method of claim 40, wherein the transport infrastructure comprises a plurality of portals.

48. The method of claim 47, wherein step (b) comprises sending the packaged message from the first application to a first portal, sending the packaged message from the first portal across the transport infrastructure to a second portal, and sending the packaged message from the second portal to the second application.

49. The method of claim 48, wherein at least one of the first and second portals comprises a message queue.

50. The method of claim 40, further comprising:

(e) dispatching a confirmation message from the second application confirming receipt of the message.

51. The method of claim 40, further comprising:

(e) generating an exception upon the failure successfully to complete any of steps (a) through (d).

52. The method of claim 51, further comprising:

(f) repeating the step with respect to which an exception was generated in step (e).

53. The method of claim 40, wherein step (b) comprises authenticating the identity of the first application.

54. The method of claim 40, wherein step (b) comprises authenticating the identity of the second application.

55. The method of claim 40, wherein step (a) comprises verifying the authority of the first application to publish data.

56. The method of claim 40, wherein step (a) comprises encrypting the at least one datum.

57. The method of claim 40, wherein step (a) comprises encrypting the message.

58. The method of claim 40, wherein step (b) comprises encrypting the message.

59. The method of claim 40, wherein step (a) comprises verifying the integrity of the at least one datum.

60. The method of claim 40, wherein step (b) comprises verifying the integrity of the at least one datum.

61. The method of claim 40, wherein step (c) comprises verifying the integrity of the at least one datum.

62. The method of claim 40, wherein step (d) comprises verifying the integrity of the at least one datum.

63. A method of transferring employee benefit data between applications, comprising steps for:

(a) in response to an event, packaging at least one datum from a first application into a message;

(b) sending the message across a transport infrastructure to a second application;

(c) unpackaging the at least one datum; and

(d) generating an event in the second application based at least in part on the at least one datum.

64. A computer-readable medium having stored thereon computer-executable instructions for performing the steps comprising:

(a) in response to an event, packaging at least one datum from a first application into a message;

(b) sending the message across a transport infrastructure to a second application;

(c) unpackaging the at least one datum; and

(d) generating an event in the second application based at least in part on the at least one datum.

65. A system for transferring employee benefit data between applications, comprising:

means for packaging at least one datum from a first application into a message in response to an event;

means for sending the message across a transport infrastructure to a second application;

means for unpackaging the at least one datum; and

means for generating an event in the second application based at least in part on the at least one datum.

66. A system for transferring employee benefit data between applications, comprising:

a first processor;

a first memory in communication with said first processor;

a second processor in communication with said first processor;

a second memory in communication with said second processor,

a first application stored in said first memory; and

a second application stored in said second memory,

wherein said first processor packages at least one datum from said first application into a message in response to an event;

wherein said first processor sends the message across a transport infrastructure to said second application;

wherein said second processor unpackages the at least one datum; and

wherein said second processor generates an event in said second application based at least in part on the at least one datum.

67. A method of transferring employee benefit data between applications, comprising:

(a) in response to an event, packaging at least a first set of data comprising at least one datum and a second set of data comprising at least one datum from a first application into a single message;

(b) sending the message to a transport infrastructure;

(c) splitting the message into at least a first sub-message comprising at least the first set of data and a second sub-message comprising at least the second set of data;

(d) sending the first sub-message to a second application and sending the second sub-message to a third application,

(e) unpackaging the first sub-message and the second sub-message; and

(f) generating an event in the second application based at least in part on the first set of data and generating an event in the third application based at least in part on the second set of data.

68. A method of transferring employee benefit data between applications, comprising:

(a) in response to events, packaging data from one or more applications including at least a first application into messages;

(b) sending the messages across a transport infrastructure to one or more applications including at least a second application;

(c) unpackaging the data; and

(d) generating events in at least the second application based at least in part on the data,

wherein the priority with which the messages are delivered in step (b) depends at least in part on priority rules associated with the first application.

69. The method of claim 68, wherein the priority with which the messages are delivered to the second application in step (b) depends in part on priority rules associated with the second application.

70. A method of transferring employee benefit data between applications, comprising:

(a) pushing data generated by a first application across a transport infrastructure in near real time to generate an event in a second application;

(b) pushing data generated by a first application across a transport infrastructure in batch mode on a predetermined schedule to a second application; and

(c) pulling data generated by a first application across a transport infrastructure in real time in response to an event in a second application.

71. The method of claim 70, wherein step (a) is performed asynchronously.

72. The method of claim 70, wherein step (b) is performed asynchronously.

73. The method of claim 70, wherein step (c) is performed synchronously.

74. A method of transferring employee benefit data between applications, comprising steps for:

(a) pushing data generated by a first application in near real time to generate an event in a second application;

(b) pushing data generated by a first application in batch mode on a predetermined schedule to a second application; and

(c) pulling data generated by a first application in real time in response to an event in a second application.

75. A computer-readable medium having stored thereon computer-executable instructions for performing the steps comprising:

(a) pushing data generated by a first application across a transport infrastructure in near real time to generate an event in a second application;

(b) pushing data generated by a first application across a transport infrastructure in batch mode on a predetermined schedule to a second application; and

(c) pulling data generated by a first application across a transport infrastructure in real time in response to an event in a second application.

76. A system for transferring employee benefit data between applications, comprising:

means for pushing data generated by a first application across a transport infrastructure in near real time to generate an event in a second application;

means for pushing data generated by a first application across a transport infrastructure in batch mode on a predetermined schedule to a second application; and

means for pulling data generated by a first application across a transport infrastructure in real time in response to an event in a second application.

77. A system for transferring employee benefit data between applications, comprising:

a processor;

a first memory in communication with said processor;

a second memory in communication with said processor;

a first application stored in said first memory; and

a second application stored in said second memory,

wherein said processor pushes data generated by said first application across a transport infrastructure in near real time to generate an event in said second application;

wherein said processor pushes data generated by said first application across a transport infrastructure in batch mode on a predetermined schedule to said second application; and

wherein said processor pulls data generated by said first application across a transport infrastructure in real time in response to an event in said second application.