System and method for assisting in controlling real-time transport protocol flow through multiple networks via use of a cluster of session routers

• US 20020145975A1
• Filed: 04/27/2001
• Published: 10/10/2002
• Est. Priority Date: 12/11/2000
• Status: Active Grant

• Current Assignee: Acme Packet Incorporated (Oracle Corporation), Primary Network
• Original Assignee: Acme Packet Incorporated (Oracle Corporation)
• Inventors: Ory, Andrew D., Arens, Cynthia E., Penfield, Robert F., Pedersen, Rebecca A., Voto, Stephen T., MeLampy, Patrick J., Spencer, Clifford M., Commerford, Peter S.
• Granted Patent: US 7,002,973 B2
• Time in Patent Office: Days
• US Class Current: 370/235
• CPC Class Codes: H04L 45/3065 for real time traffic
• CPC Class Codes: H04L 45/308 Route determination based on user's profile, e.g. premium users
• 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/22 Parsing or analysis of headers
• CPC Class Codes: H04M 3/42144 by service provider
• CPC Class Codes: H04M 7/128 Details of addressing, directories or routing tables
• CPC Class Codes: H04Q 2213/13034 A/D conversion, code compression/expansion
• CPC Class Codes: H04Q 2213/13097 Numbering, addressing
• CPC Class Codes: H04Q 2213/13103 Memory
• CPC Class Codes: H04Q 2213/13106 Microprocessor, CPU
• CPC Class Codes: H04Q 2213/13138 Least cost routing, LCR
• CPC Class Codes: H04Q 2213/13141 Hunting for free outlet, circuit or channel
• CPC Class Codes: H04Q 2213/13166 Fault prevention
• CPC Class Codes: H04Q 2213/13176 Common channel signaling, CCS7
• CPC Class Codes: H04Q 2213/13204 Protocols
• CPC Class Codes: H04Q 2213/13299 Bus
• CPC Class Codes: H04Q 2213/13332 Broadband, CATV, dynamic bandwidth allocation
• CPC Class Codes: H04Q 2213/13345 Intelligent networks, SCP
• CPC Class Codes: H04Q 2213/13348 : Channel/line reservation
• CPC Class Codes: H04Q 2213/13352 : Self-routing networks, real-time routing
• CPC Class Codes: H04Q 2213/13376 : Information service, downloading of information, 0800/0900 services
• CPC Class Codes: H04Q 2213/13384 : Inter-PBX traffic, PBX networks, e.g. corporate networks
• CPC Class Codes: H04Q 2213/13389 : LAN, internet
• CPC Class Codes: H04Q 2213/13395 : Permanent channel, leased line
• CPC Class Codes: H04Q 2213/13399 : Virtual channel/circuits
• CPC Class Codes: H04Q 3/0025 : Provisions for signalling
• 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/66 : Traffic distributors

Abstract

A system for assisting in controlling real-time transport protocol flow through multiple networks via use of a cluster of session routers is disclosed. The system utilizes a first computer and a cluster of computers, wherein the cluster of computers comprises at least two associated computers that are connected to the first computer. Each of the associated computers comprises a second transceiver, a second memory having logic stored therein defining functions to be performed by the associated computers, and a second processor. The second processor is configured by the second memory to perform the functions of: performing an inbound screen on route information received by an associated computer, from the first computer, to determine if the received route information should be discarded; if the route information is not discarded, comparing the received and screened route information to a local policy defined within the cluster of computers; and performing an outbound screen on the received and screened information prior to transmitting the received and screened information outside the cluster of computers.

Claims

1. A system for controlling real-time transport protocol flow, comprising:

a plurality of computers that are connected to a first computer, wherein each of said plurality of computers comprise;

a transceiver;

software stored within said plurality of computers defining functions to be performed by said plurality of computers; and

a processor configured by said software to perform the steps of,

performing an inbound screen on route information received by said plurality of computers, from said first computer, to determine if said received route information should be discarded,

if said route information is not discarded, comparing said received and screened route information to a local policy defined within said plurality of computers; and

a database on which said local policy is stored, wherein said local policy is used by each of said associated computers within said cluster of computers.

2. The system of claim 1, wherein a single address is used for all of said plurality of computers.

3. The system of claim 1, wherein said received route information is provided within a telephony routing over Internet protocol (TRIP) update message.

4. The system of claim 1, wherein said database also stores internal route information and route information from said received and screened route information.

5. The system of claim 4, wherein said processor is further configured by said software to perform the step of, selecting a primary route from a group of routes comprising said internal route information and said received and screened route information.

6. The system of claim 5, wherein said processor is further configured by said software to perform the step of, processing a received session initiation protocol (SIP) invite message that is received on said primary route.

7. The system of claim 5, wherein said processor is further configured by said software to perform the step of, performing an outbound screen on said received and screened information prior to transmitting said received and screened information outside said cluster of computers, wherein said outbound screen is performed on said primary route prior to said transceiver transmitting said primary route to said first computer.

8. The system of claim 1, wherein said local policy comprises an activate date and time field that defines a date and time for said local policy to be enabled by said second processor.

9. The system of claim 1, wherein said local policy comprises a de-activate date and time field that defines a date and time for said local policy to be disabled by said second processor.

10. The system of claim 1, wherein said local policy comprises an origin field.

11. The system of claim 10, wherein said processor is further configured by said software to perform the step of, comparing said origin field within said local policy to an origin attribute within said received route information, if said received route information comprises said origin attribute, and utilizing said local policy if said origin attribute at least partially matches said origin field.

12. The system of claim 3, wherein said processor is further configured by said software to perform the step of, utilizing said local policy if said TRIP update message does not comprise an origin attribute.

13. The system of claim 11, wherein the format of said origin attribute and said origin field conforms to E. 164 style addresses, Internet style addresses, and, SIP telephone addresses or non-SIP telephone addresses.

14. The system of claim 1, wherein said local policy comprises a destination field.

15. The system of claim 14, wherein said processor is further configured by said software to perform the step of, comparing said destination field within said local policy to a destination attribute within said received route information, if said received route information comprises said destination attribute, and utilizing said local policy if said destination attribute at least partially matches said destination field.

16. The system of claim 15, wherein the format of said destination attribute and said destination field conforms to E. 164 style addresses, Internet style addresses, SIP telephone addresses, or non-SIP telephone addresses.

17. The system of claim 1, wherein said local policy comprises a carrier field that identifies a number of carriers from which said route information will be accepted by said plurality of computers.

18. The system of claim 17, wherein said processor is further configured by said software to perform the step of, discarding said received route information if a carrier attribute comprised by said received route information does not match at least one carrier identified by said carrier field.

19. The system of claim 1, wherein said local policy comprises a cost field that identifies an acceptable range of cost to be billed for use of a route.

20. The system of claim 19, wherein said processor is further configured by said software to perform the step of, discarding said received route information if a cost attribute comprised by said received route information does not fall within said acceptable range of cost identified by said cost field.

21. The system of claim 1, wherein said local policy comprises a quality of service (QoS) field that identifies an acceptable range of QoS associated with use of a route.

22. The system of claim 21, wherein said processor is further configured by said software to perform the step of, discarding said received route information if a QoS attribute within said received route information does not fall within said acceptable range of QoS cost identified by said QoS field.

24. The method of claim 23, wherein said route is for ranges conformed to E. 164 style numbering, Internet style addresses of endpoints, SIP telephone addresses, or non-SIP telephone addresses.

25. The method of claim 23, further comprising the step of selecting a primary route from a group of routes comprising, information regarding an internal route that is associated with said local policy, and said received and screened route information.

26. The method of claim 25, further comprising the step of processing a received session initiation protocol (SIP) invite message that is received on said primary route.

27. The method of claim 25, further comprising he step of performing an outbound screen on said received and screened information prior to transmitting said received and screened information outside said plurality of computers, wherein said outbound screening is performed on said primary route prior to transmitting said primary route.

28. The method of claim 23, further comprising the step of enabling said local policy on a specified date and at a specified time in accordance with an activate date and time field defined by said local policy.

29. The method of claim 23, further comprising the step of disabling said local policy on a specified date and at a specified time in accordance with a de-activate date and time field defined by said local policy.

30. The method of claim 23, wherein said local policy comprises an origin field.

31. The method of claim 30, further comprising the step of comparing said origin field within said local policy to an origin attribute within said received route information, if said received route information comprises said origin attribute, and utilizing said local policy if said origin attribute at least partially matches said origin field.

32. The method of claim 31, wherein the format of said origin attribute and said origin field conforms to E. 164 style addresses, Internet style addresses, SIP telephone addresses, or non-SIP telephone addresses.

33. The method of claim 23, wherein said route information is provided within a telephony routing over Internet protocol (TRIP) update message.

34. The method of claim 23, wherein said local policy comprises a destination field.

35. The method of claim 34, further comprising the step of comparing said destination field within said local policy to a destination attribute comprised by said received route information, if said received route information comprises said destination attribute, and utilizing said local policy if said destination attribute at least partially matches said destination field.

36. The method of claim 31, wherein the format of said destination attribute and said destination field conforms to E. 164 style addresses, Internet style addresses, SIP telephone addresses, or non-SIP telephone addresses.

37. The method of claim 23, wherein said local policy comprises a carrier field that identifies a number of carriers from which said route information will be accepted.

38. The method of claim 37, further comprising the step of discarding said received route information if a carrier attribute within said received route information does not match at least one carrier identified by said carrier field.

39. The method of claim 23, wherein said local policy comprises a cost field that identifies an acceptable range of cost to be billed for use of a route.

40. The method of claim 39, further comprising the step of discarding said received route information if a cost attribute with said received route information does not fall within said acceptable range of cost identified by said cost field.

41. The method of claim 23, wherein said local policy comprises a quality of service (QoS) field that identifies an acceptable range of QoS associated with use of a route.

42. The system of claim 41, further comprising the step of discarding said received route information if a QoS attribute comprised by said received route information does not fall within said acceptable range of QoS cost identified by said QoS field.

23. A method of controlling real-time transport protocol flow, comprising the steps of:

receiving information regarding a route from a first computer to a plurality of computers;

performing an inbound screen on said received route information to determine if said received route information should be discarded; and

if said received route information is not discarded, comparing said received and screened route information to a local policy that is used by the computers within plurality of computers.

43. A system for controlling real-time transport protocol flow through multiple networks, comprising:

means for receiving information regarding a route from a first computer to a plurality of computers;

means for performing an inbound screen on said received route information configured to determine if said received route information should be discarded; and

means for comparing said received and screened route information to a local policy that is used by the plurality of computers if said route information is not discarded.

44. The system of claim 43, wherein said route is for ranges conformed to E. 164 style numbering, Internet style addresses of endpoints, SIP telephone addresses, and non-SIP telephone addresses.

45. The system of claim 43, further comprising a means for selecting a primary route from a group of routes comprising, information regarding an internal route that is associated with said local policy, and said received and screened route information.

46. The system of claim 45, further comprising a means for processing a received session initiation protocol (SIP) invite message that is received on said primary route.

47. The system of claim 45, further comprising a means for performing an outbound screen on said received and screened information, configured to perform said outbound screen prior to transmitting said received and screened information outside of said plurality of computers, and wherein said means for performing said outbound screen performs outbound screening on said primary route prior to transmitting said primary route outside of said plurality of computers.

48. The system of claim 43, further comprising a means for enabling said local policy on a specified date and at a specified time in accordance with an activate date and time field defined by said local policy.

49. The system of claim 43, further comprising a means for disabling said local policy on a specified date and at a specified time in accordance with a de-activate date and time field defined by said local policy.

50. The system of claim 43, wherein said local policy comprises an origin field.

51. The system of claim 50, further comprising a means for comparing said origin field within said local policy to an origin attribute within said received route information if said received route information comprises said origin attribute, and which utilizes said local policy if said origin attribute at least partially matches said origin field.

52. The system of claim 51, wherein the format of said origin attribute and said origin field conforms to E. 164 style addresses, Internet style addresses, SIP telephone addresses, or non-SIP telephone addresses.

53. The system of claim 43, wherein said route information is provided within a telephony routing over Internet protocol (TRIP) update message.

54. The system of claim 43, wherein said local policy comprises a destination field.

55. The system of claim 54, further comprising a means for comparing said destination field within said local policy to a destination attribute within said received route information if said received route information comprises said destination attribute, and which utilizes said local policy if said destination attribute at least partially matches said destination field.

56. The system of claim 51, wherein the format of said destination attribute and said destination field conforms to E. 164 style addresses, Internet style addresses, SIP telephone addresses, or non-SIP telephone addresses.

57. The system of claim 53, wherein said local policy comprises a carrier field that identifies a number of carriers from which said route information will be accepted.

58. The system of claim 57, further comprising a means for discarding said received route information if a carrier attribute with said received route information does not match at least one carrier identified by said carrier field.

59. The system of claim 43, wherein said local policy comprises a cost field that identifies an acceptable range of cost to be billed for use of a route.

60. The system of claim 59, further comprising a means for discarding said received route information if a cost attribute comprised by said received route information does not fall within said acceptable range of cost identified by said cost field.

61. The system of claim 43, wherein said local policy comprises a quality of service (QoS) field that identifies an acceptable range of QoS associated with use of a route.

62. The system of claim 61, further comprising a means for discarding said received route information if a QoS attribute comprised by said received route information does not fall within said acceptable range of QoS cost identified by said QoS field.