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

• US 8,195,836 B2
• Filed: 11/04/2009
• Issued: 06/05/2012
• Est. Priority Date: 11/16/2001
• Status: Expired due to Term

• Current Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Original Assignee: AT&T Mobility II LLC (AT&T, Inc.)
• Inventors: Lai, Danh Tan, Richardson, Simon James, Tam, Richard Man-keung, McNamara, Justin, Schlieber, Karl J., Lewis, John Ervin, Lee, Jessie T.
• Primary Examiner(s): Winder, Patrice
• Application Number:
  US12/612,156
• Publication Number:
  US 20100142700A1
• Time in Patent Office: 944 Days
• Field of Search: 709/224, 709/245
• US Class Current: 709/245
• 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. A device for routing messages to a network element, the device comprising:

a messaging interface, the messaging interface being extensible such that the messaging interface is adaptable to communicate with a messaging element;

a processor in communication with the messaging interface, the processor receiving a message incoming from the messaging interface, the processor operating to translate the message between a format of the messaging element and a common format; and

a network transport bus interface coupling the processor to a network transport bus, the network transport bus interface running a daemon to monitor network traffic on the network transport bus,

wherein the processor appends a subject address to a header of a message broadcast such that the network element monitors the network transport bus for the subject address, and

wherein the processor generates a routing request for the message, the processor receives a routing response from a router via the network transport bus in response to the routing request, the routing response containing a request for additional information, and the processor operates to request the additional information from the messaging element via the messaging interface.

2. The device of claim 1, wherein the messaging interface pre-caches the message.

3. The device of claim 1, wherein the messaging interface post-caches the message.

4. The device of claim 1, wherein the processor parses the message to retrieve an originating address and a destination address.

5. The device of claim 4, wherein the processor generates the routing request for the message based upon the destination address and originating address.

6. The device of claim 1, wherein the router is a Routing and Validation Entity (RAVE).

7. The device of claim 1, wherein the processor translates an incoming message from the network transport bus interface from the common format to the format of the messaging element.

8. A method of routing messages to a network element, the method comprising:

receiving a message from a messaging element;

appending a subject address to the message;

publishing a routing request for routing information for the message;

receiving a routing reply in response to the routing request the routing reply containing a request for additional information;

requesting additional information from the messaging element; and

determining whether the routing reply contains a valid response,

wherein the subject address is monitored by the network element for subjects of interest to the network element,

wherein when the routing reply contains a valid response the message is translated from an incoming format to a common format and a common message formed from the message in the common format is published to a destination device, and wherein when the routing reply does not contain a valid response the message is not translated to the common format.

9. The method of claim 8, wherein the messaging element receives the message from an originating device.

10. The method of claim 8, further comprising separating a header of the message from a body of the message.

11. The method of claim 10, further comprising parsing the header for an originating device address and a destination device address.

12. The method of claim 11, further comprising assigning a unique transaction identification to the message.

13. The method of claim 8, wherein a daemon examines the header of the routing reply.

14. The method of claim 8, wherein if the routing reply does not contain a valid response a reason is determined for an invalid response.

15. The method of claim 14, wherein the reason is insufficient funds in a prepaid subscriber'"'"'s device.

16. The method of claim 14, wherein the reason is a blacklist associated with the destination device.

17. The method of claim 14, wherein the reason is an insufficient class of service (COS) associated with the destination device.