Methods and systems for providing message translation, accounting and routing service in a multi-protocol communications network environment

• US 6,967,956 B1
• Filed: 07/18/2000
• Issued: 11/22/2005
• Est. Priority Date: 07/18/2000
• Status: Expired due to Term

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Tinsley, Robert John, Marsico, Peter Joseph, Sprague, David Michael
• Primary Examiner(s): Patel, Ajit
• Application Number:
  US09/618,807
• Time in Patent Office: 1,953 Days
• Field of Search: 370351-356, 370/401, 370/410, 370/464, 370/465, 370/466, 370/467, 709/230
• US Class Current: 370/466
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04Q 3/0025 Provisions for signalling

Abstract

A network element that is capable facilitating the routing and accounting of messages between a plurality of network elements that do not share a common signaling application protocol nor a common transport protocol suite. In one embodiment of the present invention, a Multi-Protocol Gateway (MPG) is adapted to receive a signaling message and subsequently translate both the signaling and transport protocol suite prior to message routing. The MPG node is also configured to create and maintain usage and measurements data that may subsequently be used to produce billing records.

Claims

1. A network routing element capable of receiving, from a first communication network, a first message formatted according to a first transport protocol suite containing information that is formatted according to a first signaling protocol, and subsequently generating a second message formatted according to a second transport protocol suite containing information that is formatted in a second signaling protocol and transmitting the second message to a second communication network, the network element comprising:

a) a first communication module capable of receiving, from the first communication network, a first message formatted according to the first transport protocol suite and containing information that is formatted according to the first signaling protocol;

b) a second communication module capable of transmitting, to the second communication network, a second message formatted according to the second transport protocol suite containing information that is formatted according to the second signaling protocol;

c) a Multi-protocol Routing Database (MRD) for storing protocol translation and routing information;

d) a multi-protocol routing process for extracting information from the MRD and subsequently directing the first message to a translation process based on the information; and

e) a transport protocol suite process for receiving the second message from the multi-protocol routing process based on the first message and for applying the second transport protocol suite and associated routing instructions to the second message.

2. The network routing element of claim 1 wherein the first signaling protocol is a Signaling System 7 (SS7) signaling protocol.

3. The network routing element of claim 1 wherein the first signaling protocol is a Session Initiation Protocol (SIP) signaling protocol.

4. The network routing element of claim 1 wherein the first signaling protocol is an H.323 signaling protocol.

5. The network routing element of claim 1 wherein the first signaling protocol is a Normalized Call Control Protocol (NCCP) signaling protocol.

6. The network routing element of claim 1 wherein the second signaling protocol is an SS7 signaling protocol.

7. The network routing element of claim 1 wherein the second signaling protocol is a Session Initiation Protocol (SIP) signaling protocol.

8. The network routing element of claim 1 wherein the second signaling protocol is an H.323 signaling protocol.

9. The network routing element of claim 1 wherein the second signaling protocol is a Normalized Call Control Protocol (NCCP) signaling protocol.

10. The network routing element of claim 1 wherein the first transport protocol suite includes the Message Transfer Part (MTP) of the SS7 protocol.

11. The network routing element of claim 1 wherein the first transport protocol suite includes Transmission Control Protocol/Internet Protocol (TCP/IP).

12. The network routing element of claim 1 wherein the first transport protocol suite includes Simple Control Transmission Protocol/Internet Protocol (SCTP/IP).

13. The network routing element of claim 1 wherein the second transport protocol suite includes Message Transfer Part (MTP) of the SS7 protocol.

14. The network routing element of claim 1 wherein the second transport protocol suite includes Transmission Control Protocol/Internet Protocol (TCP/IP).

15. The network routing element of claim 1 wherein the second transport protocol suite includes Simple Control Transmission Protocol/Internet Protocol (SCTP/IP).

16. The network routing element of claim 1 including a message accounting subsystem (MAS) for generating and maintaining usage measurements and billing information associated with messages that are processed and routed through the network routing element.

17. The network routing element of claim 16 wherein the MAS is located within and integral with the network routing element.

18. The network routing element of claim 16 wherein the MAS is configured as an external database platform.

19. The network routing element of claim 18 wherein the external MAS platform is connected to the network routing element via a high-speed Ethernet link.

20. The network routing element of claim 1 wherein the MRD includes message accounting subsystem (MAS) processing instructions.

21. The network routing element of claim 16 wherein the MAS is configured to receive a copy of the first signaling message.

22. The network routing element of claim 16 wherein the MAS is configured to receive a Normalized Accounting Message (NAM) message that is based on information contained in the first message.

23. The network routing element of claim 1 wherein the MRD protocol translation instructions include signaling protocol translation instructions.

24. The network routing element of claim 1 wherein the MRD is indexed by IP host and port values.

25. The network routing element of claim 1 wherein the MRD is indexed by socket values.

26. The network routing element of claim 1 wherein the MRD is indexed by Point Code (PC) values.

27. The network routing element of claim 1 wherein the MRD is indexed by Called Party Address (CdPA) values.

28. The network routing element of claim 27 wherein the CdPA value is a telephone number.

29. The network routing element of claim 27 wherein the CdPA value is an Internet Domain Name (DN).

30. The network routing element of claim 27 wherein the CdPA value is an Internet email address.

31. A method for routing signaling messages between networks with differing signaling protocols and differing transport protocol suites, the method comprising:

a) receiving, from a first communications network that employs a first transport protocol suite, a first message formatted according to a first signaling protocol;

b) determining where to route the first message;

c) determining whether the first message requires a signaling protocol translation;

d) in response to determining that the first message requires a signaling protocol translation, directing the first message to a signaling protocol translation process for translation into an equivalent second message that is formatted in a second signaling protocol;

e) applying a second transport protocol suite to the second message; and

f) transmitting the second message into a second communication network.

32. The method of claim 31 wherein the first signaling protocol is a Signaling System 7 (SS7) signaling protocol.

33. The method of claim 31 wherein the first signaling protocol is a Session Initiation Protocol (SIP) signaling protocol.

34. The method of claim 31 wherein the first signaling protocol is an H.323 signaling protocol.

35. The method of claim 31 wherein the first signaling protocol is a Normalized Call Control Protocol (NCCP) signaling protocol.

36. The method of claim 31 wherein the second signaling protocol is an SS7 signaling protocol.

37. The method of claim 31 wherein the second signaling protocol is a Session Initiation Protocol (SIP) signaling protocol.

38. The method of claim 31 wherein the second signaling protocol is an H.323 signaling protocol.

39. The method of claim 31 wherein the second signaling protocol is a Normalized Call Control Protocol (NCCP) signaling protocol.

40. The method of claim 31 wherein the first transport protocol suite includes the Message Transport Part (MTP) of the SS7 signaling protocol.

41. The method of claim 31 wherein the first transport protocol suite includes Transmission Control Protocol/Internet Protocol (TCP/IP).

42. The method of claim 31 wherein the first transport protocol suite includes Simple Control Transmission Protocol/Internet Protocol (SCTP/IP).

43. The method of claim 31 wherein the second transport protocol suite includes the Message Transport Part (MTP) of the SS7 protocol.

44. The method of claim 31 wherein the second transport protocol suite includes Transmission Control Protocol/Internet Protocol (TCP/IP).

45. The method of claim 31 wherein the second transport protocol suite includes Simple Control Transmission Protocol/Internet Protocol (SCTP/IP).

46. The method of claim 31 wherein determining where to route the first message includes examining routing rules that are stored in a multiprotocol routing database (MRD).

47. The method of claim 31 wherein determining whether the first message requires signaling protocol translation includes signaling protocol translation rules that are stored in a Multi-protocol Routing Database (MRD).

48. The method of claim 31 comprising determining whether message accounting service is required.

49. The method of claim 48 comprising, in response to determining that message accounting service is required, sending a third message to a message accounting subsystem.

50. The method of claim 49 wherein the third message is a copy of the first message.

51. The method of claim 49 wherein the third message is a Normalized Accounting Message (NAM) message that is based on information contained in the first message.

52. The method of claim 48 wherein determining whether message accounting service is required includes examining message accounting service rules that are stored in a MRD.

53. The method of claim 31 wherein applying the second transport protocol suite includes applying the second transport protocol suite at an outbound Multi-Protocol Link Interface Module (MLIM).

54. A computer program product comprising computer-executable instructions embodied in a computer-readable medium for performing steps comprising:

a) receiving a first message formatted according to a first transport protocol suite and containing information formatted according to a first signaling protocol;

b) performing a lookup in a multiprotocol routing database to determine protocol translation instructions for the first message;

c) directing the first message to a translation process for generating a second message formatted according to second signaling protocol based on results from the lookup in the multiprotocol routing database;

d) applying a second transport protocol suite to the second message; and

e) transmitting the second message over a second network.

55. The computer program product of claim 54 wherein performing a lookup in the multiprotocol routing database includes determining whether accounting is required for the first message.

56. The computer program product of claim 55 comprising, in response to determining that accounting is required for the first message, formulating a normalized accounting message based on the accounting instructions.

57. The computer program product of claim 56 comprising routing the normalized accounting message to an accounting subsystem.

58. The computer program product of claim 54 wherein performing a lookup in the multiprotocol routing database includes performing the lookup using a point code contained in the first message.

59. The computer program product of claim 54 wherein performing a lookup in the multiprotocol routing database includes performing the lookup using a called party address contained in the first message.

60. The computer program product of claim 54 wherein performing a lookup in the multiprotocol routing database includes performing the lookup using an IP address contained in the first message.

61. The computer program product of claim 54 wherein performing a lookup in the multiprotocol routing database includes performing the lookup using a domain name contained in the first message.