Message management systems and method

• US 20020143987A1
• Filed: 08/21/2001
• Published: 10/03/2002
• Est. Priority Date: 08/22/2000
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Durbin, David John, McMillan, Craig Phillip, Sadler, Andrew Paul, Patterson, Andrew John
• Application Number:
  US09/934,184
• Publication Number:
  US 20020143987A1
• Time in Patent Office: Days
• US Class Current: 709/238
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce data processing systems or methods, specially adapted for e-commerce G06Q30/00
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers

Abstract

A method and system for routing messages comprising: converting a message received from a sender into an internal format comprising at least an attribute part and a data part, writing into said attribute part data extracted from said received message; and routing said converted message in dependence on the data in said attribute part.

Claims

1. A method for routing messages comprising:

converting a message received from a sender into an internal format comprising at least an attribute part and a data part, writing into said attribute part data extracted from said received message; and

routing said converted message in dependence on the data in said attribute part.

2. The method of claim 1, comprising identifying the format in which the message was received, and writing data identifying that format into said attribute part.

3. The method of claim 1, comprising determining where to send the message in dependence on the attributes.

4. The method of claim 1, comprising authenticating the identity of the sender of the message.

5. The method of claim 1, comprising identifying a set of services to which the message is addressed.

6. The method of claim 4, comprising determining whether the sender is authorised to access at least one service;

and,

in dependence on the result of said authorisation determination, sending the converted message to the identified service.

7. The method of claim 6, in which said identified service updates the data held in the attribute part of the message.

8. The method of claim 6, comprising storing a plurality of routing rules and in which determining whether the sender is authorised to access at least one service comprises comparing said plurality of routing rules with the attributes of a converted message.

9. The method of claim 1, wherein said received message comprises a digital signature, the method comprising verifying the signature.

10. The method of claim 9, comprising writing into said attribute part data identifying the received digital signature.

11. The method of claim 1, comprising storing a plurality of routing rules;

comparing the attributes of a converted message with the routing rules; and

routing said converted message in dependence on said comparison.

12. The method of claim 1 comprising searching for a transaction identifier in the received message.

13. The method of claim 12, comprising allocating a new transaction identifier if no transaction identifier is detected in the received message.

14. The method of claim 12, comprising, if a transaction identifier is detected, searching for data identifying the status of a transaction by reference to the detected transaction identifier.

20. The computer system of claim 19, in which said parser is configured to identify the format in which the message was received, and to write data identifying that format into said attribute part.

21. The computer system of claim 19, in which said router is configured to determine where to send the message in dependence on the attributes.

22. The computer system of claim 19, in which said the router is configured to authenticate the identity of the sender of the message.

23. The computer system of claim 19, in which said router is configured to identify a set of services to which the message is addressed.

24. The computer system of claim 19, in which said router is configured to:

identify at least one service to which the message should be sent;

determine whether the sender is authorised to access said identified service; and

,

in dependence on the result of said authorisation determination, selectively send the converted message to the identified service.

25. The computer system of claim 19, said router being configured to store a plurality of routing rules and to determine whether the sender is authorised to access a service by applying said rules to the attributes of a converted message.

26. The computer system of claim 19, wherein said parser is configured to verify signatures included in said received messages.

27. The computer system of claim 19, said parser comprising a plurality of applications for converting said received message, said parser selecting at least one of said applications in dependence on the data extracted from said received message.

28. The computer system of claim 27, wherein said data extracted from said received message includes a message type, said parser selecting at least one of said applications in dependence on the type of a message.

29. The computer system of claim 27, wherein said data extracted from said received message includes protocol data, and said parser selects at least one of said applications in dependence or the protocol(s) under which the message was received.

30. The computer system of claim 19, configured to search for a transaction identifier in the received message.

31. The computer system of claim 30, configured to allocate a new transaction identifier if no transaction identifier is detected in the received message.

32. The computer system of claim 30, configured to search for data identifying the status of a transaction by reference to the detected transaction identifier.

15. A program element comprising program code for configuring a computer system to route a message, the program code operable to:

convert a message received from a sender into an internal format comprising at least an attribute part and a data part;

write into said attribute part data extracted from said received message; and

route said converted message in dependence on the data in said attribute part.

16. A program element comprising program code translatable to configure a computer system to route a message, the program code operable to:

convert a message received from a sender into an internal format comprising at least an attribute part and a data part;

write into said attribute part data extracted from said received message; and

route said converted message in dependence on the data in said attribute part.

17. A computer-readable medium encoded with computer-readable program code for configuring a computer system to route a message, the program code operable to:

convert a message received from a sender into an internal format comprising at least an attribute part and a data part;

write into said attribute part data extracted from said received message; and

route said converted message in dependence on the data in said attribute part.

18. A computer-readable medium encoded with computer-readable program code translatable to configure a computer system to route a message, the program code operable to:

convert a message received from a sender into an internal format comprising at least an attribute part and a data part;

write into said attribute part data extracted from said received message; and

route said converted message in dependence on the data in said attribute part.

19. A computer system for routing messages to one or more services comprising:

a parser for converting a message received from a sender into an internal format comprising an attribute part and a data part, said attribute part containing data extracted from the received message; and

a router for routing the converted message in dependence on the data in said attribute part.

33. A computer system configured to provide a plurality of protocol handlers each configured to extract protocol data from a message received in a particular format.

34. A computer system according to claim 33, configured to select a protocol handler for extracting data from a received message, in dependence on the format in which the message is received.

35. A computer system according to claim 33 configured to select a protocol handler in dependence on the type of data in the received message.

36. A computer system according to claim 35, in which said protocol handler extracts message level protocol data and writes this into the attribute part of the converted message.

38. The computer program of claim 37, comprising computer executable instructions for identifying the format in which the message was received, and writing data identifying that format into said attribute part.

39. The computer program of claim 37, comprising computer executable instructions for determining where to send the message in dependence on the attributes.

40. The computer program of claim 37, comprising computer executable instructions for authenticating the identity of the sender of the message.

41. The computer program of claim 37, comprising computer executable instructions for identifying a set of services to which the message is addressed.

42. The computer program of claim 37, comprising computer executable instructions for determining whether the sender is authorised to access at least one service;

and,

in dependence on the result of said authorisation determination, sending the converted message to the identified service.

43. The computer program of claim 37, comprising computer executable instructions for searching for data identifying the status of a transaction by reference to a detected transaction identifier.

37. A computer program for routing messages, said program comprising computer executable instructions for converting a message received from a sender into an internal format comprising at least an attribute part and a data part, writing into said attribute part data extracted from said received message;

and routing said converted message in dependence on the data in said attribute part.

44. A computer system for routing messages to one or more services, comprising:

means for parsing a message received from a sender;

means for parsing including means for converting the message into an internal format comprising an attribute part and a data part, said attribute part containing data extracted from received message; and

means for routing the converted message in dependence on the data in the attribute part.

45. A computer network comprising at least one computer system connectable to at least one further computer system via a network, the at least one computer system comprising:

a parser for converting a message received from a sender into an internal format comprising an attribute part and a data part, said attribute part containing data extracted from the received message; and

a router for routing the converted message in dependence on the data in said attribute part.