System for the validation and routing of messages

• US 20030095555A1
• Filed: 11/18/2002
• Published: 05/22/2003
• Est. Priority Date: 11/16/2001
• Status: Abandoned Application

• 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
• Application Number:
  US10/299,181
• Publication Number:
  US 20030095555A1
• Time in Patent Office: Days
• US Class Current: 370/401
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 49/102 using shared medium, e.g. bus or ring
• CPC Class Codes: H04L 49/25 Routing or path finding in a switch fabric
• CPC Class Codes: H04L 49/3009 Header conversion, routing tables or routing tags
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 88/16 Gateway arrangements
• CPC Class Codes: H04W 92/06 between gateways and public network devices

Abstract

A router for directing messages across a bus in a telecommunications system. The router comprises a bus interface and a processor. The bus interface is coupled to the bus and is operable to receive routing request in a common format from the bus, where the routing request comprising a destination device address. The processor is coupled to the bus interface and is operable to receive the routing request from the bus interface and determine routing information based on the destination device address.

Claims

1. A router for directing messages across a bus in a telecommunications infrastructure, comprising:

a bus interface coupled to the bus, the bus interface operable to receive a routing request for one of the messages, the routing request being in a common format from the bus, the routing request comprising a destination device address; and

a processor coupled to the bus interface, the processor operable to receive the routing request from the bus interface and determine routing information for the message based at least in part on the destination device address.

2. The router of claim 1, wherein the processor is further operable to generate a routing reply comprising the routing information;

and wherein the bus interface is further operable to transmit the routing reply on the bus.

3. The router of claim 2, further comprising a routing database in communication with the processor, the routing database comprising the routing information for device addresses.

4. The router of claim 3, wherein the processor is further operable to extract the routing information from the routing database.

5. The router of claim 4, wherein the routing information in the routing database comprises at least one of the following for a device address:

a device type, a device address, and an adapter.

6. The router of claim 5, wherein the routing request further comprises an originating device address.

7. The router of claim 6, wherein the routing information in the routing database further comprises an approved list associated with the destination device address;

and wherein the processor is operable to return a valid response in the routing information if the originating device address is in the approved list.

8. The router of claim 6, wherein routing information in the routing database further comprises a disapproved list associated with the device address;

and wherein the processor is operable to return an invalid response in the routing information if the originating device address is in the disapproved list.

9. The router of claim 5, wherein the routing information in the routing database further comprises a password associated with the device address;

and wherein the processor is operable to return a password request response in the routing information.

10. The router of claim 6, wherein the routing information in the routing database further comprises a class of service associated with the device address;

and wherein the processor is operable to return an invalid response in the routing information if the class of service of the originating device address does not meet the class of service associated with the destination device address.

11. The router of claim 6, wherein the routing database comprises a prepaid subscriber database in communication with the processor, the prepaid subscriber database containing account balance information for each device address.

12. The router of claim 11, wherein the processor is further operable to query the prepaid subscriber database upon receipt of the routing request and return an invalid response in the routing information if the account balance information associated with the originating device address is less than a message charge amount.

13. The router of claim 11, wherein the processor is further operable to query the prepaid subscriber database upon receipt of the routing request and return an invalid response in the routing information if the account balance information associated with the destination device address is less than a message charge amount.

14. The router of claim 2, further comprising a user alias database in communication with the processor;

and wherein the routing request comprises an alias, the user alias database containing data associating the alias with one or more destination device addresses.

15. The router of claim 14, wherein the processor is operable to extract the one or more destination device addresses associated with the alias from the user alias database and generate a routing reply containing the routing information for each of the one or more destination device addresses.

16. The router of claim 15, further comprising a routing database in communication with the processor, the routing database comprising the routing information for the one or more destination device addresses.

17. The router of claim 16, wherein the processor is further operable to extract the routing information from the routing database for each of the one or more destination device addresses.

18. The router of claim 17, wherein the routing information in the routing database comprises at least one or more of the following for each of the one or more destination device address:

a device type, a device address, and an adapter.

19. The router of claim 18, wherein the routing request further comprise an originating device address.

20. The router of claim 19, wherein routing information in the routing database further comprises an approved list associated with the destination device address;

and wherein the processor is operable to return a valid response in the routing information if the originating device address is in the approved list.

21. The router of claim 19, wherein routing information in the routing database further comprises a disapproved list associated with the device address;

and wherein the processor is operable to return an invalid response in the routing information if the originating device address is in the disapproved list.

22. The router of claim 18, wherein routing information in the routing database further comprises a password associated with the device address;

and wherein the processor is operable to return a password request response in the routing information.

23. The router of claim 19, wherein the routing information in the routing database further comprises a class of service associated with the device address;

and wherein the processor is operable to return an invalid response in the routing information if the class of service of the originating device address does not meet the class of service associated with the destination device address.

24. The router of claim 19, further comprising a prepaid subscriber database in communication with the processor, the prepaid subscriber database containing account balance information for each device address.

25. The router of claim 24, wherein the processor is further operable to query the prepaid subscriber database upon receipt of the routing request and return an invalid response in the routing information if the account balance information associated with the originating device address is less than a message charge amount.

26. The router of claim 24, wherein the processor is further operable to query the prepaid subscriber database upon receipt of the routing request and return an invalid response in the routing information if the account balance information associated with the destination device address is less than a message charge amount.

27. A method of routing messages in a telecommunications system, comprising:

receiving a routing request in a common format from a bus in the telecommunications system, the routing request comprising a destination device address;

extracting routing information from a routing database for the destination device address;

generating a routing reply to the routing request, the routing reply comprising the routing information; and

returning the routing reply on the bus.

28. The method of routing messages of claim 27, wherein extracting the routing information further comprises extracting device address information from the routing database for the destination device address.

29. The method of routing messages of claim 28, wherein the routing information comprises the device address information.

30. The method of routing messages of claim 27, wherein the routing request further comprises an originating device address;

and wherein extracting routing information further comprises checking the originating device address against an approved list associated with the destination device address in the routing database.

31. The method of routing messages of claim 30, wherein the routing information contains a valid response if the originating device address is in the approved list associated with the destination device address.

32. The method of routing messages of claim 27, wherein the routing request further comprises an originating device address;

and wherein extracting routing information further comprises checking the originating device address against a disapproved list associated with the destination device address in the routing database.

33. The method of routing messages of claim 32, wherein the routing information contains an invalid response if the originating device address is in the disapproved list associated with the destination device address.

34. The method of routing messages of claim 27, wherein extracting the routing information further comprises retrieving a password associated with the destination device address in the routing database.

35. The method of routing messages of claim 34, wherein the routing information contains a password response.