Methods and systems for providing database node access control functionality in a communications network routing node

• US 6,944,184 B1
• Filed: 03/29/2000
• Issued: 09/13/2005
• Est. Priority Date: 12/04/1998
• Status: Expired due to Term

• Current Assignee: Tekelec
• Original Assignee: Tekelec
• Inventors: Ravishankar, Venkataramaiah, Marsico, Peter Joseph, Miller, Paul Andrew, Benedyk, Robby Darren
• Primary Examiner(s): Ho, Duc
• Assistant Examiner(s): TRAN, THIEN D
• Application Number:
  US09/537,835
• Time in Patent Office: 1,994 Days
• Field of Search: 370/352, 370/353, 370/354, 370/355, 370/356, 370/385, 370/465, 370/466, 370/467, 370/469
• US Class Current: 370/467
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/085 specially adapted for interworking of IP-based networks with other networks
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/169 Special adaptations of TCP, UDP or IP for interworking of IP based networks with other networks protocols for interworking, protocol conversion H04L69/08
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 7/066 where the auxiliary connection is via an Internet Protocol network interworking of signalling system number 7 (SS7) with Internet Protocol-based session control protocols H04M7/1265, H04M7/127
• CPC Class Codes: H04M 7/1245 where a network other than PSTN/ISDN interconnects two PSTN/ISDN networks
• CPC Class Codes: H04Q 3/0025 Provisions for signalling
• CPC Class Codes: H04Q 3/0029 Provisions for intelligent networking
• CPC Class Codes: H04Q 3/0045 involving hybrid, i.e. a mixture of public and private, or multi-vendor systems
• CPC Class Codes: H04Q 3/005 Personal communication services, e.g. provisions for portability of subscriber numbers

Abstract

A network element provides service control point or database node front end processing functionality, as well as routing functionality for routing data packets through a network. The network element includes a first communication module for receiving data packets from a first communication network. A second communication module transmits data packets over a second communications network. A database access control (DAC) process queries a DAC database and modifies received packets to include information returned by the database lookup.

Claims

1. A network element for providing service control point (SCP) or database node front end processing (FEP) service and routing data packets through a communications network, the network element comprising:

(a) a first module capable of transmitting data packets to and receiving data packets from a communications network, wherein the first module is adapted to receive a data packet from the communications network;

(b) a second module for receiving the data packet and for forwarding the data packet to one of a plurality of SCP or database nodes being separate from the first module and being without individual front end processors, wherein the network element is adapted to provide FEP service for the SCP or database nodes and to eliminate the need for the SCP or database nodes to have individual front end processors.

2. The network element of claim 1 wherein the received data packet is a signaling system 7 (SS7) signaling message.

3. The network element of claim 2 wherein the SS7 signaling message is a transaction capabilities application part (TCAP) message signaling unit (MSU).

4. The network element of claim 3 wherein the TCAP MSU contains a database query message.

5. The network element of claim 1 wherein the communications network is an SS7 network.

6. The network element of claim 1 wherein the communications network is an Internet protocol (IP) network.

7. The network element of claim 1 wherein the communications network is an asynchronous transfer mode (ATM) network.

8. The network element of claim 1 wherein the first module is a signaling system 7 (SS7) link interface module (LIM).

9. The network element of claim 1 wherein the second module is an Internet protocol (IP) database communication module (DCM).

10. The network element of claim 1 comprising a database access control (DAC) database, wherein the DAC database includes a plurality of records and each DAC database record includes an IP network address associated with one of the SCP or database nodes.

11. The network element of claim 10 wherein the DAC database includes a plurality of records and each DAC database record includes operational status information associated with one of the SCP or database nodes.

12. The network element of claim 10 wherein the DAC database includes a plurality of records and each DAC database record includes ownership information associated with one of the SCP or database nodes.

13. The network element of claim 10 wherein the DAC database includes a plurality of records and each DAC database record includes database protocol information associated with one of the SCP or database nodes.

14. The network element of claim 10 wherein the DAC database includes a plurality of records and each DAC database record includes service type identification information associated with one of the SCP or database nodes.

15. The network element of claim 14 wherein the service type identification information identifies an advanced intelligent network (AIN) service.

16. The network element of claim 14 wherein the service type identification information is a translation type (TT) value.

17. The network element of claim 14 wherein the service type identification information is a subsystem number (SSN).

18. The network element of claim 14 wherein the service type identification information identifies a calling name (CNAM) service.

19. The network element of claim 14 wherein the service type identification information identifies a line information database (LIDB) service.

20. The network element of claim 14 wherein the service type identification information identifies a toll free number (800) service.

21. The network element of claim 14 wherein the service type identification information identifies a local number portability (LNP) service.

22. The network element of claim 14 wherein the service type identification information identifies a presence service.

23. The network element of claim 10 wherein the DAC database is integral with and contained within the network element.

24. The network element of claim 10 wherein the DAC database is located on an external database server communicatively coupled to the network element.

25. The network element of claim 10 wherein data that comprises the DAC database is maintained in high speed, random access memory.

26. The network element of claim 10 wherein data that comprises the DAC database is maintained on high speed, optical disc storage media.

27. The network element of claim 1 including a protocol translation process for modifying the received data packet to include predetermined database protocol information.

28. The network element of claim 27 wherein the protocol translation process is capable of translating an SCP or database query to or from a structured query language (SQL) database protocol.

29. The network element of claim 27 wherein the protocol translation process is capable of translating an SCP or database query to or from an open database connectivity (ODBC) database protocol.

30. The network element of claim 1 wherein the comprising a database access control process for examining a destination network address in the received data packet to identify one of the SCP or database nodes to which the packet is destined.

31. The network element of claim 30 wherein the destination network address is an SS7 destination point code (DPC) and subsystem (SSN).

32. The network element of claim 31 wherein, responsive to the SS7 DPC being the same as an SS7 PC assigned to the network element, the database access control process is adapted to forward the data packet to one of the SCP or database nodes.

33. The network element of claim 31 wherein the SSN corresponds to a SSN that is provisioned for FEP service.

34. The network element of claim 1 comprising a database access control process for examining a translation type (TT) value in the received data packet to identify one of the SCP or database nodes which the packet is destined.

35. The network element of claim 1 comprising a database access control process for examining a subsystem number (SSN) value in the received data packet to identify one of the SCP or database nodes to which the packet is destined.

36. The network element of claim 1 wherein providing FEP service for a plurality of SCP or database nodes comprises providing front end processing service at a signal transfer point (STP).

37. A method for providing service control point (SCP) or database node front end processing (FEP) service and for routing a data packet in a communications network, the method comprising:

providing, from a first network element having a first SS7 point code (PC), FEP service for a plurality of SCPs being separate from the first network element and being without individual front end processors, wherein providing FEP service includes;

(a) at the first network element receiving a data packet having a first SS7 destination point code (DPC) from a first communications network;

(b) determining whether the received data packet is intended for an SCP or database node that is provisioned to receive front end processing (FEP) service;

(c) in response to determining that the received data packet is intended for an SCP or database node that is provisioned to receive FEP service, modifying the received data packet; and

(d) transmitting the modified data packet to one of the SCPs over a second communications network.

38. The method of claim 37 wherein comprising performing a lookup in a database access control (DAC) database based on key information in the received data packet to identify the SCP to which the data packet should be routed, wherein the key information includes subsystem number (SSN) value.

39. The method of claim 37 wherein the received data packet is a signaling system 7 (SS7) signaling message.

40. The method of claim 39 wherein the SS7 signaling message is a transaction capabilities application part (TCAP) message signaling unit (MSU).

41. The method of claim 40 wherein the TCAP MSU contains an SCP or database query message.

42. The method of claim 37 wherein the first communications network is an SS7 network.

43. The method of claim 37 wherein the second communications network is an Internet protocol (IP) network.

44. The method of claim 37 wherein determining whether the received data packet is destined for an SCP or database node that is provisioned to receive front end processing (FEP) service includes examining the DPC value in the received data packet.

45. The method of claim 44 wherein determining whether the received data packet is destined for an SCP or database node that is provisioned to receive front end processing (FEP) service further includes examining a destination subsystem (SSN) value in the received data packet.

46. The method of claim 45 wherein the destination SSN value corresponds to a SSN that is provisioned for FEP service.

47. The method of claim 44 wherein the DPC is the same as the PC assigned to the first network element.

48. The method of claim 37 wherein comprising performing a lookup in a database access control (DAC) database based on key information in the received data packet to identify the SCP to which the data packet should be routed, wherein the key information includes the first DPC and a subsystem number (SSN) value.

49. The method of claim 37 wherein comprising performing a lookup in a database access control (DAC) database based on key information in the received data packet to identify the SCP to which the data packet should be routed, wherein the key information includes a translation type (TT) value.

50. The method of claim 37 wherein modifying the received data packet includes modifying a packet routing label in the received data packet based on information returned from a database access control (DAC) database.

51. The method of claim 50 wherein modifying the routing label includes modifying the routing label based on SCP or database node operational status information contained within the DAC database.

52. The method of claim 50 wherein modifying the routing label includes modifying the routing label based on SCP or database node congestion status information contained within the DAC database.

53. The method of claim 50 wherein modifying the routing label includes modifying the routing label based on SCP or database node ownership information contained within the DAC database.

54. The method of claim 50 wherein modifying the routing label includes modifying the routing label to include a destination IP network address.

55. The method of claim 37 wherein modifying the received data packet includes changing a protocol of a database query statement contained in the received packet.

56. The method of claim 55 wherein changing a protocol includes changing the protocol based on SCP or database node protocol information contained within a database.

57. The method of claim 37 wherein providing FEP service from the first network element comprises providing front end processing service from a signal transfer point (STP).

58. A network element for providing service control point (SCP) or database node front end processing (FEP) service and routing data packets through a communications network, the network element comprising:

(a) a first module capable of receiving data packets from a first communications network and transmitting data packets to a second communications network, wherein the first module is adapted to receive a data packet from the first communication network;

(b) a second module for receiving the data packet and for forwarding the data packet to one of a plurality of SCP or database nodes being separate from the first module and being without individual front end processors, wherein the network element is adapted to provide FEP service for the SCP or database nodes and to eliminate the need for the SCP or database nodes to have individual front end processors.

59. The network element of claim 58 comprising a database access control process for examining a subsystem number (SSN) value in the received data packet to identify one of the SCP or database nodes to which the packet is destined.

60. The network element of claim 58 wherein the received data packet is a signaling system 7 (SS7) signaling message.

61. The network element of claim 60 wherein the SS7 signaling message is a transaction capabilities application part (TCAP) message signaling unit (MSU).

62. The network element of claim 61 wherein the TCAP MSU contains a database query message.

63. The network element of claim 58 wherein the first communications network is an SS7 network.

64. The network element of claim 58 wherein the second communications network is an Internet protocol (IP) network.

65. The network element of claim 58 comprising a database access control (DAC) database, wherein the DAC database includes a plurality of records and each DAC database record includes an IP network address associated with one of the SCP or database nodes.

66. The network element of claim 58 comprising a database access control (DAC) database, wherein the DAC database includes a plurality of records and each DAC database record includes operational status information associated with one of the SCP or database nodes.

67. The network element of claim 58 comprising a database access control (DAC) database, wherein the DAC database includes a plurality of records and each DAC database record includes ownership information associated with one of the SCP or database nodes.

68. The network element of claim 58 comprising a database access control (DAC) database, wherein the DAC database includes a plurality of records and each DAC database record includes database protocol information associated with one of the SCP or database nodes.

69. The network element of claim 58 comprising a database access control (DAC) database, wherein the DAC database includes a plurality of records and each DAC database record includes service type identification information associated with one of the SCP or database nodes.

70. The network element of claim 69 wherein the service type identification information is a subsystem number (SSN) value.

71. The network element of claim 69 wherein the service type identification information is a translation type (TT) value.

72. The network element of claim 69 wherein the service type identification information identifies a calling name (CNAM) service.

73. The network element of claim 69 wherein the service type identification information identifies a line information database (LIDB) service.

74. The network element of claim 69 wherein the service type identification information identifies a toll free number (800) service.

75. The network element of claim 69 wherein the service type identification information identifies a local number portability (LNP) service.

76. The network element of claim 69 wherein the service type identification information identifies a presence service.

77. The network element of claim 58 comprising a database access control (DAC) database for storing information regarding the SCP or database nodes, wherein the DAC database is integral with and contained within the network element.

78. The network element of claim 58 comprising a database access control (DAC) database for storing information regarding the SCP or database nodes, wherein the DAC database is located on an external database server that is communicatively coupled to the network element.

79. The network element of claim 58 comprising a database access control (DAC) database for storing information regarding the SCP or database nodes, wherein data that comprises the DAC database is maintained in high speed, random access memory.

80. The network element of claim 58 comprising a database access control (DAC) database for storing information regarding the SCP or database nodes, wherein data that comprises the DAC database is maintained on high speed, optical disc storage media.

81. The network element of claim 58 including a DAC protocol translation process.

82. The network element of claim 81 wherein the DAC protocol translation process is capable of translating an SCP or database query to or from a structured query language (SQL) database protocol.

83. The network element of claim 81 wherein the DAC protocol translation process is capable of translating an SCP or database query to or from an open database connectivity (ODBC) database protocol.

84. The network element of claim 58 comprising a database access control process for examining a destination network address in the received data packet to identify one of the SCP or database nodes to which the packet is destined.

85. The network element of claim 84 wherein the destination network address is an SS7 destination point code (DPC) and a subsystem (SSN).

86. The network element of claim 83 wherein the SS7 DPC is the same as an SS7 PC assigned to the network element.

87. The network element of claim 83 wherein the SSN corresponds to an SSN that is provisioned for FEP service.

88. The network element of claim 58 comprising a database access control process for examining a translation type (TT) value in the received data packet to identify one of the SCP or database nodes to which the packet is destined.

89. The network element of claim 58 wherein providing FEP service for a plurality of SCP or database nodes comprises providing front end processing service at a signal transfer point (STP).

90. A network routing element for routing signaling messages having a first signaling system 7 (SS7) network address, the network routing element being adapted to receive messages addressed to the first SS7 network address intended for processing by a service control point (SCP) or database node that resides in an Internet protocol (IP) network, the network routing element comprising:

(a) a first module capable of receiving data packets from a communications network and transmitting data packets to a second communications network, wherein the first module is adapted to receive a data packet from the first communications network;

(b) a second module for receiving the data packet and for forwarding the data packet to one of a plurality of SCP or database nodes in the second communications network, the SCP or database nodes being separate from the first module and being without individual front end processors, wherein the second communications network comprises an IP network, and wherein the network element is adapted to provide FEP service for the SCP or database nodes and to eliminate the need for the SCP or database nodes to have individual front end processors.

91. The network element of claim 90 comprising a database access control process for examining a subsystem number (SSN) in the received data packet to identify one of the SCP or database nodes to which the packet is destined.

92. The network element of claim 90 wherein the received data packet is a signaling system 7 (SS7) signaling message.

93. The network element of claim 92 wherein the SS7 signaling message is a transaction capabilities application part (TCAP) message signaling unit (MSU).

94. The network element of claim 93 wherein the TCAP MSU contains a database query message.

95. The network element of claim 90 wherein the first communications network is an SS7 network.

96. The network element of claim 90 wherein the first communications network is an Internet protocol (IP) network transporting IP encapsulated SS7 MSUs.

97. The network element of claim 90 comprising a database access control (DAC) database for identifying one of the SCP or database nodes to which the data packet should be forwarded, wherein the DAC database includes a plurality of records and each DAC database record includes an IP network address associated with an SCP or database node.

98. The network element of claim 90 comprising a database access control (DAC) database for identifying one of the SCP or database nodes to which the data packet should be forwarded, wherein the DAC database is integral with and contained within the network element.

99. The network element of claim 90 comprising a database access control (DAC) database for identifying one of the SCP or database nodes to which the data packet should be forwarded, wherein the DAC database is located on an external database server that is communicatively coupled to the network element.

100. The network element of claim 90 comprising a database access control (DAC) database for identifying one of the SCP or database nodes to which the data packet should be forwarded, wherein data that comprises the DAC database is maintained in high speed, random access memory.

101. The network element of claim 90 comprising a database access control (DAC) database for identifying one of the SCP or database nodes to which the data packet should be forwarded, wherein data that comprises the DAC database is maintained on high speed, optical disc storage media.

102. The network element of claim 90 including a database access control (DAC) protocol translation process for translating the protocol of messages sent to one of the SCP or database nodes.

103. The network element of claim 102 wherein the DAC protocol translation process is capable of translating an SCP or database query to or from a structured query language (SQL) database protocol.

104. The network element of claim 102 wherein the DAC protocol translation process is capable of translating an SCP or database query to or from an open database connectivity (ODBC) database protocol.

105. The network element of claim 90 comprising a database access control process for examining a destination network address in the received data packet to identify one of the SCP or database nodes to which the packet is destined.

106. The network element of claim 105 wherein the destination network address is an SS7 destination point code (DPC) and subsystem (SSN).

107. The network element of claim 106 wherein the SS7 DPC is the same as the first SS7 PC assigned to the network element.

108. The network element of claim 90 comprising a database access control process for examining a translation type (TT) value in the received data packet to identify one of the SCP or database nodes to which the packet is destined.

109. The network routing element of claim 90 wherein providing FEP service for a plurality of SCP or database nodes comprises providing front end processing service at a signal transfer point (STP).