Method and system for managing communication of information

• US 20020099633A1
• Filed: 11/30/2000
• Published: 07/25/2002
• Est. Priority Date: 12/03/1999
• Status: Active Grant

• Current Assignee: Citibank (South Dakota) NA (Citigroup Incorporated)
• Original Assignee: Citibank (South Dakota) NA (Citigroup Incorporated)
• Inventors: Bray, Adrian Gilmore
• Granted Patent: US 8,301,525 B2
• Time in Patent Office: Days
• US Class Current: 705/35
• CPC Class Codes: G06F 40/103 Formatting, i.e. changing of presentation of documents automatic justification G06F40/189; automatic line break hyphenation G06F40/191
• CPC Class Codes: G06F 40/151 Transformation
• CPC Class Codes: G06F 40/157 using dictionaries or tables
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes
• CPC Class Codes: G06Q 40/02 Banking, e.g. interest calculation or account maintenance credit or loans G06Q40/03

Abstract

A method and system of managing communication of information to a destination utilizes computer hardware and software and a client-server architecture. The system receives information in file form, such as ASCII file form, via a file transfer service and/or in message-based form, such as SWIFT and/or ISITC messages, via a message network. The information that is received in message-based form is converted to file form by a message to file converter and translated by a message format library to an intermediary file format, and the information that is received in file form is also translated to the intermediary format by a message format library. The intermediary file format information can be aggregated and sorted, and is then translated to a preferred file format of the destination and sent to the destination.

Claims

1. A method for managing communication of information from at least one source to at least one destination, comprising:

receiving information from at least one source in at least one of file form and message-based form;

converting the information that is received in message-based form to an intermediary file format;

translating the information that is received in file form to the intermediary file format;

translating the intermediary file format information to a preferred file format of the at least one destination; and

sending the information in the preferred file format to the at least one destination.

2. The method of claim 1, wherein receiving the information further comprises receiving financial information.

3. The method of claim 1, wherein receiving the information further comprises receiving the information from a plurality of sources.

4. The method of claim 3, wherein receiving the information further comprises receiving the information from a plurality of fund managers.

5. The method of claim 1, wherein receiving the information further comprises receiving the information from a single source.

6. The method of claim 5, wherein receiving the information further comprises receiving the information from a single fund manager.

7. The method of claim 1, wherein receiving the information further comprises receiving the information according to a predefined schedule.

8. The method of claim 1, wherein receiving the information in file form further comprises receiving the information in file form via a file transfer service.

9. The method of claim 8, wherein receiving the information in file form via the file transfer service further comprises receiving the information in file form by an input file transfer service server from a file transfer service client.

10. The method of claim 9, wherein receiving the information by the input file transfer service server further comprises rejecting bad file form information by the input file transfer service server.

11. The method of claim 1, wherein receiving the information in file form further comprises receiving the information in ASCII file form.

12. The method of claim 1, wherein receiving the information in message-based form further comprises receiving the information in message-based form via a message network.

13. The method of claim 12, wherein receiving the information in message-based form via the message network further comprises receiving the information in message-based form by a message agent server from a message node.

14. The method of claim 1, wherein receiving the information in message-based form further comprises receiving the information in at least one of SWIFT message form and ISITC message form.

15. The method of claim 1, wherein converting the information further comprises converting the information that is received in message-based form to file form by a message to file converter.

16. The method of claim 15, wherein converting the information further comprises receiving the information in message-based form by the message to file converter from a message agent server.

17. The method of claim 15, wherein converting the information further comprises translating the converted file form information to the intermediary file format.

18. The method of claim 17, wherein converting the file form information further comprises translating the converted file form information to the intermediary file format by a message format library.

19. The method of claim 18, wherein converting the file form information further comprises receiving the converted file form information by the message format library from the message to file converter.

20. The method of claim 15, wherein converting the information further comprises rejecting bad message-based information by the message to file converter.

21. The method of claim 1, wherein translating the information further comprises translating the information that is received in file form to the intermediary file format by a message format library.

22. The method of claim 21, wherein translating the information further comprises receiving the information in file form by the message format library from a input file transfer service server.

23. The method of claim 22, wherein translating the information further comprises rejecting bad files by the input file transfer service server.

24. The method of claim 1, wherein translating the intermediary file format information further comprises translating the intermediary file format information to the preferred file format of the at least one destination by a message format library.

25. The method of claim 24, wherein translating the intermediary file format information further comprises receiving the intermediary file format information by the message format library from an output file transfer service server.

26. The method of claim 25, wherein translating the intermediary file format information further comprises receiving the intermediary file format information by the output file transfer service server from at least one of a message to file converter and an input file transfer service server.

27. The method of claim 1, wherein sending the information further comprises sending the information in the preferred file format via a file transfer service.

28. The method of claim 27, wherein sending the information further comprises sending the information in the preferred file format by an output file transfer service server.

29. The method of claim 28, wherein sending the information further comprises sending the information in the preferred file format by the output file transfer service server to a file transfer service client.

30. The method of claim 1, wherein sending the information further comprises sending the information in the preferred file format to the at least one destination according to a predefined schedule.

31. The method of claim 1, wherein sending the information further comprises sending the information in the preferred file format to a single destination.

32. The method of claim 1, wherein sending the information further comprises sending the information in the preferred file format to a plurality of destinations.

33. The method of claim 1, wherein sending the information further comprises sending the information in the preferred file format to at least one plan sponsor.

34. The method of claim 1, further comprising aggregating the intermediary file format information by source.

35. The method of claim 1, further comprising sorting the intermediary file format information according to at least one predefined requirement of the destination.

36. The method of claim 1, further comprising sorting the intermediary file format information by type of transaction.

38. The system of claim 37, wherein the means for receiving the information further comprises means for receiving financial information.

39. The system of claim 37, wherein the means for receiving the information further comprises means for receiving the information from a plurality of sources.

40. The system of claim 39, wherein the means for receiving the information further comprises means for receiving the information from a plurality of fund managers.

41. The system of claim 37, wherein the means for receiving the information further comprises means for receiving the information from a single source.

42. The system of claim 41, wherein the means for receiving the information further comprises means for receiving the information from a single fund manager.

43. The system of claim 37, wherein the means for receiving the information further comprises means for receiving the information according to a predefined schedule.

44. The system of claim 37, wherein the means for receiving the information in file form further comprises means for receiving the information in file form via a file transfer service.

45. The system of claim 44, wherein the means for receiving the information in file form via the file transfer service further comprises means for receiving the information in file form by an input file transfer service server from a file transfer service client.

46. The system of claim 45, wherein the means for receiving the information by the file transfer service server further comprises means for rejecting bad file form information by the input file transfer service server.

47. The system of claim 37, wherein the means for receiving the information in file form further comprises means for receiving the information in ASCII file form.

48. The system of claim 37, wherein the means for receiving the information in message-based form further comprises means for receiving the information in message-based form via a message network.

49. The system of claim 48, wherein the means for receiving the information in message-based form via the message network further comprises means for receiving the information in message-based form by a message agent server from a message node.

50. The system of claim 37, wherein the means for receiving the information in message-based form further comprises means for receiving the information in at least one of SWIFT message form and ISITC message form.

51. The system of claim 37, wherein the means for converting the information further comprises means for converting the information that is received in message-based form to file form by a message to file converter.

52. The system of claim 51, wherein the means for converting the information further comprises means for receiving the information in message-based form by the message to file converter from a message agent server.

53. The system of claim 51, wherein the means for converting the information further comprises means for translating the converted file form information to the intermediary file format.

54. The system of claim 53, wherein the means for converting the file form information further comprises means for translating the converted file form information to the intermediary file format by a message format library.

55. The system of claim 54, wherein the means for converting the file form information further comprises means for receiving the converted file form information by the message format library from the message to file converter.

56. The system of claim 51, wherein the means for converting the information further comprises means for rejecting bad message-based information by the message to file converter.

57. The system of claim 37, wherein the means for translating the information further comprises means for translating the information that is received in file form to the intermediary file format by a message format library.

58. The system of claim 57, wherein the means for translating the information further comprises means for receiving the information in file form by the message format library from a input file transfer service server.

59. The system of claim 58, wherein the means for translating the information further comprises means for rejecting bad files by the input file transfer service server.

60. The system of claim 37, wherein the means for translating the intermediary file format information further comprises means for translating the intermediary file format information to the preferred file format of the at least one destination by a message format library.

61. The system of claim 60, wherein the means for translating the intermediary file format information further comprises means for receiving the intermediary file format information by the message format library from an output file transfer service server.

62. The system of claim 61, wherein the means for translating the intermediary file format information further comprises means for receiving the intermediary file format information by the output file transfer service server from at least one of a message to file converter and an input file transfer service server.

63. The system of claim 37, wherein the means for sending the information further comprises means for sending the information in the preferred file format via a file transfer service.

64. The system of claim 63, wherein the means for sending the information further comprises means for sending the information in the preferred file format by an output file transfer service server.

65. The system of claim 64, wherein the means for sending the information further comprises means for sending the information in the preferred file format by the output file transfer service server to a file transfer service client.

66. The system of claim 37, wherein the means for sending the information further comprises means for sending the information in the preferred file format to the at least one destination according to a predefined schedule.

67. The system of claim 37, wherein the means for sending the information further comprises means for sending the information in the preferred file format to a single destination.

68. The system of claim 37, wherein the means for sending the information further comprises means for sending the information in the preferred file format to a plurality of destinations.

69. The system of claim 37, wherein the means for sending the information further comprises means for sending the information in the preferred file format to at least one plan sponsor.

70. The system of claim 37, further comprising means for aggregating the intermediary file format information by source.

71. The system of claim 37, further comprising means for sorting the intermediary file format information according to at least one predefined requirement of the destination.

72. The system of claim 37, further comprising means for sorting the intermediary file format information by type of transaction.

37. A system for managing communication of information from at least one source to at least one destination, comprising:

means for receiving information from at least one source in at least one of file form and message-based form;

means for converting the information that is received in message-based form to an intermediary file format;

means for translating the information that is received in file form to the intermediary file format;

means for translating the intermediary file format information to a preferred file format of the at least one destination; and

means for sending the information in the preferred file format to the at least one destination.

73. A method for managing communication of information to at least one destination, comprising:

receiving information in file form by an input file transfer service server;

translating the file form information to an intermediary format by a message format library coupled to the input file transfer service server;

sending the information in intermediary format to an output file transfer service server by the input file transfer service server;

receiving information in message-based form by a message agent server;

converting the message-based form information to file form by a message to file converter coupled to the message agent server;

translating the converted file form information to the intermediary format by a message format library coupled to the message to file converter;

sending the information in intermediary format to the output file transfer service server by the message to file converter;

translating the intermediary format information to a preferred format of the at least one destination by a message format library coupled to the output file transfer service server; and

sending the information in the preferred format to the at least one destination by the output file transfer service server.