System for translation and communication of messaging protocols into a common protocol

• US 20030101283A1
• Filed: 11/18/2002
• Published: 05/29/2003
• Est. Priority Date: 11/16/2001
• Status: Active Grant

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: McNamara, Justin, Richardson, Simon James, Lewis, John Ervin, Tam, Richard Man-Keung, Lee, Jessie T., Schlieber, Karl J., Lai, Danh Tan
• Granted Patent: US 7,617,328 B2
• Time in Patent Office: Days
• US Class Current: 709/246
• CPC Class Codes: H04L 12/2856 Access arrangements, e.g. Internet access asynchronous transfer mode networks H04L12/5601; broadband local area networks H04L12/2801; optical access or distribution networks H04Q11/0067; access to open networks H04L12/5691; digital subscriber line end-user equipment and bit-level processing of data on a PSTN-based network H04M11/00; home network gateways H04L12/2834; wireless access networks H04W
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/306 Route determination based on the nature of the carried application
• CPC Class Codes: H04L 45/308 Route determination based on user's profile, e.g. premium users
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/23 Reliability checks, e.g. acknowledgments or fault reporting
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 51/56 Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/18 Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals
• CPC Class Codes: H04W 40/246 Connectivity information discovery
• CPC Class Codes: H04W 40/248 Connectivity information update
• CPC Class Codes: H04W 8/18 Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
• CPC Class Codes: H04W 88/16 : Gateway arrangements
• CPC Class Codes: H04W 88/184 : Messaging devices, e.g. message centre
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements
• CPC Class Codes: H04W 92/06 : between gateways and public network devices

Abstract

An adapter for passing messages in a telecommunications infrastructure from a first device to a second device. The adapter comprises a messaging interface, a processor, and a bus interface. The messaging interface is in communication with the first device and is operable to receive a received message in a first messaging format from the first device. The processor is coupled to the messaging interface and is operable to receive the received message from the messaging interface and translate the received message into a common message in a common format. The bus interface is coupled to the processor and is operable to receive the common message from the processor and transmit the common message to the second device through a bus.

Claims

1. An adapter for passing messages in a telecommunications infrastructure from a first device to a second device, comprising:

a messaging interface in communication with the first device, the messaging interface operable to receive a received message in a first messaging format from the first device;

a processor coupled to the messaging interface, the processor operable to receive the received message from the messaging interface and translate the received message into a common message in a common format; and

a bus interface coupled to the processor, the bus interface operable to receive the common message from the processor and transmit the common message to the second device through a bus.

2. The adapter of claim 1, wherein the processor is further operable to:

identify a destination address from the received message;

request routing information for the received message, the routing information based on the destination address;

receive a routing response containing the routing information for the received message; and

generate a subject address to the common message based on the response.

3. The adapter of claim 2, wherein the request for routing information is transmitted by the processor in the common format through the bus interface.

4. The adapter of claim 3, wherein the processor is further operable to receive the routing information in the common format from the bus interface.

5. The adapter of claim 2, wherein the processor is further operable to include in the request for the routing information a routing validation request, the routing validation request including an address of the first device and an address of the second device.

6. The adapter of claim 5, wherein the processor is further operable to receive in the routing response the routing information indicating an invalid request.

7. The adapter of claim 6, wherein the processor is further operable to not transmit the common message through the bus interface if the routing information indicates an invalid response.

8. The adapter of claim 6, wherein the processor is further operable to send a declination message through the messaging interface to the first device in the first messaging format if the routing information indicates an invalid response.

9. The adapter of claim 5, wherein the processor is further operable to receive through the network transport bus interface the routing information in the routing response indicating a password request.

10. The adapter of claim 9, wherein the processor is further operable to send a password request message through the messaging interface to the first device in the first messaging format if the routing information indicates the password request.

11. The adapter of claim 10, wherein the processor is further operable to receive a password reply message containing a password through the messaging interface from the first device in the first messaging format in response to the password request message.

12. The adapter of claim 11, wherein the processor is further operable to verify the password in the password reply message, and only transmit the common message through the bus interface if the password is valid.

13. The adapter of claim 11, wherein the processor is further operable to:

translate the password reply message from the first device into a common password reply message in the common format;

provide the common password reply message over the bus interface;

receive a password validation message over the network transport bus interface; and

transmit the common message through the bus interface if the password validation message indicates that the password is valid.

14. The adapter of claim 2, wherein the routing information includes one or more device addresses and the processor is further operable to append the subject address, based on the one or more device address, to the common message.

15. The adapter of claim 14, wherein the processor is further operable to provide the address of one or more destination adapters to the message, the address of the destination adapters included in the routing information.

16. The adapter of claim 2, wherein the common format is MIME.

17. The adapter of claim 2, wherein the common format is XML.

18. The adapter of claim 2, wherein the first messaging format is SMS.

19. The adapter of claim 2, wherein the first messaging format is EMS.

20. The adapter of claim 2, wherein the first messaging format is HTML.

21. The adapter of claim 2, wherein the first messaging format is TAP.

22. The adapter of claim 2, wherein the first messaging format is WML.

23. The adapter of claim 2, wherein the first messaging format is Mobitex.

24. The adapter of claim 2, wherein the first messaging format is UPOC.

25. The adapter of claim 1, wherein the processor is further operable to:

receive a second message in the common format from the bus interface;

translate the second message from the common format into a delivery message in the first messaging format; and

transmit the delivery message to the first device through the messaging interface.

26. The adapter of claim 25, wherein the second message contains a second message subject address, and the bus interface is further operable to receive the second message based on the second message subject address.

27. The adapter of claim 25, wherein the bus interface is further operable to:

be associated with one or more second message subject addresses;

monitor message traffic within the bus; and

receive the second message over the bus if the subject address of the second message is associated with the bus interface.

28. The adapter of claim 25, wherein the second message contains an address of a destination adapter, and the network transport bus interface is operable to receive the second message based on the address of the destination adapter.

29. An adapter for passing messages in a telecommunications infrastructure from a bus to a device comprising:

a bus interface coupled to the bus, the bus interface operable to receive a common message in a common format from the bus;

a processor coupled to the bus interface, the processor operable to receive the common message from the bus interface and translate the common message into a device message in a device format; and

a messaging interface coupled to the processor and in communication with the device, the messaging interface operable to receive the device message from the processor and send the device message to the device.

30. The adapter of claim 29, wherein the common message includes a subject address and the bus interface is further operable to receive the common message based on the subject address.

31. The adapter of claim 29, wherein the common message includes a destination device address and the network transport bus interface is further operable to receive the common message based on the destination device address.

32. The adapter of claim 29, wherein the common format is one of a MIME format and an XML format.

33. The adapter of claim 29, wherein the device format is one of a MIME format, an XML format, an SMS format, an EMS format, an HTML format, a TAP format, a WML format, a Mobitex format, and a UPOC format.

34. A method of passing messages from a first device to a second device in a telecommunications system, comprising:

receiving a fist of the messages from the first device, the first message being in a first messaging format;

translating the first message from the first messaging format into a common message in a common messaging format; and

transmitting the common message through a bus in the telecommunications system to the second device.

35. The method of claim 34, wherein receiving the first message further comprises reading a destination address appended to the first message

36. The method of claim 35 further comprising:

requesting routing information for the first message, where the routing information is based on the destination address;

receiving a routing response containing the routing information for the received message; and

generating a subject address to the common message based on the response.

37. The method of claim 36, wherein requesting the routing information further comprises requesting the routing information in the common messaging format over the network transport bus.

38. The method of claim 36, wherein receiving the routing response further comprises receiving the routing response in the common format over the bus.

39. The method of claim 34, further comprising:

requesting a routing validation request, the routing validation request including an address of the first device and an address of the second device.

40. The method of claim 39, further comprising:

receiving a routing validation response, the routing validation response indicating an invalid request.

41. The method of claim 40, further comprising:

preventing the transmission of the common message through the bus if the routing information indicates an invalid response.

42. The method of claim 40, further comprising:

sending a declination message through the messaging interface to the first device in the first messaging format if the routing information indicates an invalid response.

43. The method of claim 39, further comprising:

receiving through the bus interface the routing information in the routing response indicating a password request.

44. The method of claim 43, further comprising:

sending a password request message through the messaging interface to the first device in the first messaging format if the routing information indicates the password request.

45. The method of claim 44, further comprising:

receiving a password reply message containing a password from the first device in the first messaging format in response to the password request message.

46. The method of claim 45, further comprising:

verifying the password in the password reply message; and

publishing the common message through the bus only if the password is valid.

47. The method of claim 46, wherein verifying the password in the password reply message, further comprises:

translating the password reply message from the first device into a common password reply message in a common message format;

providing the common password reply message over the bus; and

receiving a password validation message over the bus.

48. The method of claim 34, further comprising:

receiving a second message in the common format from the network transport bus;

translating the second message from the common format into a delivery message in the first messaging format; and

transmitting the delivery message to the first device

49. The method of claim 48, wherein receiving a second message further comprises:

monitoring message traffic within the bus; and

receiving the second message over the bus based on a subject address associated with the second message.

50. A computer-readable medium having executable instructions for performing steps that provide passing of messages from a first device to a second device in a telecommunication system, the steps comprising:

receiving a first of the messages from the first device, the first message being in a first messaging format;

translating the first message from the first messaging format into a common message in a common messaging format; and

transmitting the common message through a bus in the telecommunications system to the second device.

51. The computer readable medium of claim 50, wherein receiving the first message further comprises reading a destination address appended to the first message

52. The computer readable medium of claim 51 further comprising:

requesting routing information for the first message, where the routing information is based on the destination address;

receiving a routing response containing the routing information for the first message; and

generating a subject address to the common message based on the response.

53. The computer readable medium of claim 52, wherein requesting the routing information further comprises requesting the routing information in the common messaging format over the network transport bus.

54. The computer readable medium of claim 52, wherein receiving the routing response further comprises receiving the routing response in the common format over the bus.

55. The computer readable medium of claim 50, further comprising:

requesting a routing validation request, the routing validation request including an address of the first device and an address of the second device.

56. The computer readable medium of claim 55, further comprising:

receiving a routing validation response, the routing validation response indicating an invalid request.

57. The computer readable medium of claim 56, further comprising:

preventing the transmission of the common message through the bus if the routing information indicates an invalid response.

58. The computer readable medium of claim 56, further comprising:

sending a declination message through the messaging interface to the first device in the first messaging format if the routing information indicates an invalid response.

59. The computer readable medium of claim 55, further comprising:

receiving through the network transport bus interface the routing information in the routing response indicating a password request.

60. The computer readable medium of claim 59, further comprising:

sending a password request message through the messaging interface to the first device in the first messaging format if the routing information indicates the password request.

61. The computer readable medium of claim 60, further comprising:

receiving a password reply message containing a password from the first device in the first messaging format in response to the password request message.

62. The computer readable medium of claim 61, further comprising:

verifying the password in the password reply message; and

publishing the common message through the bus only if the password is valid.

63. The computer readable medium of claim 62, wherein verifying the password in the password reply message, further comprises:

translating the password reply message from the first device into a common password reply message in a common message format;

providing the common password reply message over the bus; and

receiving a password validation message over the bus.

64. The computer readable medium of claim 50, further comprising:

receiving a second message in the common format from the bus;

translating the second message from the common format into a delivery message in the first messaging format; and

transmitting the delivery message to the first device

65. The computer readable medium of claim 64, wherein receiving a second message further comprises:

monitoring message traffic within the bus; and

receiving the second message over the bus based on a subject address associated with the second message.