IP Library Granted Patent US 7,162,024
Granted Patent B2
US 7,162,024 · App. 09/962,914 · Granted Jan 9, 2007

System and method for telephony call control

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,162,024
App. No.
09/962,914
Granted
Jan 9, 2007
Kind
B2
Abstract

A telephony call manager includes a call model having call processing logic, and a signaling interface for each respective signaling protocol encountered by the call manager. Each signaling interface is operable to convert call events in each respective signaling protocol to messages of a generic protocol and communicate the messages to the call model.

Claims (96)

1. A telephony call manager, comprising:

a call model having call processing logic; and

a signaling interface for each respective one of a plurality of signaling protocols encountered by the call manager, wherein the signaling interfaces are, collectively, configured to:

convert call events in each respective signaling protocol to messages of a generic protocol and communicate the messages to the call model;

convert packet call events from a packet signaling protocol to a PSTN signaling protocol;

convert PSTN call events from a PSTN signaling protocol to a packet signaling protocol; and

convert in-band signaling messages to out-band signaling messages.

2. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a call SETUP message mappable to and from the initial address message of the SS7 signaling protocol.

3. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a call SETUP message mappable to and from an originator OFFHOOK call event.

4. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises an ALERT message mappable to and from the address complete message of the SS7 signaling protocol.

5. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises an ALERT message mappable to and from a ringing applied call event.

6. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises an INFO message mappable to and from a dialed digits call event.

7. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a CONN message mappable to and from the answer message of the SS7 signaling protocol.

8. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a CONN message mappable to and from a terminator OFFHOOK call event.

9. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a RELEASE message mappable to and from the release message of the SS7 signaling protocol.

10. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a RELEASE message mappable to and from a party ONHOOK call event of the SS7 signaling protocol sent to the call model from the SS7 signaling interface.

11. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a RELEASE message mappable to and from a request release call event of the SS7 signaling protocol sent from the call model to the SS7 signaling interface.

12. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a RELCOMP message mappable to and from the release complete message of the SS7 signaling protocol.

13. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a RELCOMP message mappable to and from a party ONHOOK call event of the SS7 signaling protocol sent to the call model from the SS7 signaling interface.

14. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises a RELCOMP message mappable to and from a acknowledge release call event of the SS7 signaling protocol sent from the call model to the SS7 signaling interface.

15. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises an INFO message mappable to and from dialed digits call event and the INFO message including an information element containing the dialed digits.

16. The telephony call manager, as set forth in claim 1 , wherein the generic protocol comprises messages containing at least one information element containing call data.

17. A telecommunications switch having a call manager, the call manager comprising:

a call model having call processing logic; and

a signaling interface for each respective one of a plurality of signaling protocols encountered by the call manager, wherein the signaling interfaces are, collectively, configured to:

convert call events in each respective signaling protocol to messages of a generic protocol and communicate the messages to the call model;

convert packet call events from a packet signaling protocol to a PSTN signaling protocol;

convert PSTN call events from a PSTN signaling protocol to a packet signaling protocol; and

convert in-band signaling messages to out-band signaling messages.

18. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a call SETUP message mappable to and from the initial address message of the SS7 signaling protocol.

19. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a call SETUP message mappable to and from an originator OFFHOOK call event.

20. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises an ALERT message mappable to and from the address complete message of the SS7 signaling protocol.

21. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises an ALERT message mappable to and from a ringing applied call event.

22. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises an INFO message mappable to and from a dialed digits call event.

23. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a CONN message mappable to and from the answer message of the SS7 signaling protocol.

24. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a CONN message mappable to and from a terminator OFFHOOK call event.

25. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a RELEASE message mappable to and from the release message of the SS7 signaling protocol.

26. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a RELEASE message mappable to and from a party ONHOOK call event of the SS7 signaling protocol sent to the call model from the SS7 signaling interface.

27. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a RELEASE message mappable to and from a request release call event of the SS7 signaling protocol sent from the call model to the SS7 signaling interface.

28. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a RELCOMP message mappable to and from the release complete message of the SS7 signaling protocol.

29. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a RELCOMP message mappable to and from a party ONHOOK call event of the SS7 signaling protocol sent to the call model from the SS7 signaling interface.

30. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises a RELCOMP message mappable to and from a acknowledge release call event of the SS7 signaling protocol sent from the call model to the SS7 signaling interface.

31. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises an INFO message mappable to and from dialed digits call event and the INFO message including an information element containing the dialed digits.

32. The telecommunications switch, as set forth in claim 17 , wherein the generic protocol comprises messages containing at least one information element containing call data.

33. A method for interfacing a telephony call manager with various signaling protocols, comprising:

converting call events between PSTN and packet signaling protocols by: mapping events of one of the signaling protocols to first messages of a generic protocol, communicating the first messages to a call model, and utilizing the call model to process the call events via the first messages; and

converting in-band signaling messages to out-band signaling messages by: mapping events of the in-band signaling messages to second messages of the generic protocol, communicating the second messages to the call model, and utilizing the call model to process the in-band signaling messages via the second messages.

34. The method, as set forth in claim 33 , wherein the call events are incoming call events, the method further comprising:

mapping third messages of the generic protocol to outgoing call events of respective ones of the signaling protocols after utilizing the call model to process the incoming call events via the first messages; and

communicating the outgoing call events to a respective signaling interface.

35. The method, as set forth in claim 33 , wherein mapping the call events comprises mapping between a call SETUP message to and from the initial address message of the SS7 signaling protocol.

36. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between a call SETUP message to and from an originator OFFHOOK call event.

37. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between an ALERT message to and from the address complete message of the SS7 signaling protocol.

38. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between an ALERT message to and from a ringing applied call event.

39. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between an INFO message to and from a dialed digits call event.

40. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between a CONN message to and from the answer message of the SS7 signaling protocol.

41. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between a CONN message to and from a terminator OFFHOOK call event.

42. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between a RELEASE message to and from the release message of the SS7 signaling protocol.

43. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between a RELEASE message to and from a party ON-HOOK call event of the SS7 signaling protocol sent to the call model from the SS7 signaling interface.

44. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between a RELEASE message to and from a request release call event of the SS7 signaling protocol sent from the call model to the SS7 signaling interface.

45. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between a RELCOMP message to and from the release complete message of the SS7 signaling protocol.

46. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between a RELCOMP message to and from a party ONHOOK call event of the SS7 signaling protocol sent to the call model from the SS7 signaling interface.

47. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between a RELCOMP message to and from a acknowledge release call event of the SS7 signaling protocol sent from the call model to the SS7 signaling interface.

48. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between an INFO message to and from dialed digits call event and the INFO message including an information element containing the dialed digits.

49. The method, as set forth in claim 33 , wherein the mapping the call events comprises mapping between messages containing at least one information element containing call data and call events.

50. A method for interfacing a telephony call manager with various signaling protocols, comprising:

receiving first call events in various PSTN signaling protocols from respective ones of various signaling interfaces each corresponding to a respective one of the PSTN signaling protocols;

converting the call events to first messages of a generic protocol;

sending the first generic protocol messages to a call model;

processing the first generic protocol messages via the call model to generate second messages of the generic protocol;

receiving the second generic protocol messages from the call model;

converting the second generic protocol messages to second call events of respective packet signaling protocols;

sending the second call events to respective ones of the signaling interfaces;

receiving third call events in various packet signaling protocols from respective ones of the signaling interfaces each corresponding to a respective one of the packet signaling protocols;

converting the third call events to third messages of a generic protocol;

sending the third generic protocol messages to the call model;

processing the third generic protocol messages via the call model to generate fourth messages of the generic protocol;

receiving the fourth generic protocol messages from the call model;

converting the fourth generic protocol messages to fourth call events of respective PSTN signaling protocols;

sending the fourth call events to respective ones of the signaling interfaces;

receiving in-band signaling messages in various signaling protocols from respective ones of the signaling interfaces;

converting the in-band signaling messages to fifth messages of the generic protocol;

sending the fifth generic protocol messages to the call model;

processing the fifth generic protocol messages via the call model to generate sixth messages of the generic protocol;

receiving the sixth generic protocol messages from the call model;

converting the sixth generic protocol messages to out-band signaling messages of respective signaling protocols; and

sending the out-band signaling messages to respective ones of the signaling interfaces.

51. The method, as set forth in claim 50 , wherein converting the call events comprises converting a call event having call data to a generic protocol message containing an information element having the call data.

52. The method, as set forth in claim 50 , wherein converting the call events comprises mapping a call event to a message from a set of generic protocol messages understandable by the call model.

53. The method, as set forth in claim 50 , wherein converting the call events comprises mapping a call event to a message indicative of setting up a call in the generic protocol.

54. The method, as set forth in claim 50 , wherein converting the call events comprises mapping a call event to a message operable indicative of processing the call in the generic protocol.

55. The method, as set forth in claim 50 , wherein converting the call events comprises mapping a call event to a message indicative of address completion in the generic protocol.

56. The method, as set forth in claim 50 , wherein converting the call events comprises mapping a call event to an information message containing dialed digits in the generic protocol.

57. The method, as set forth in claim 50 , wherein converting the call events comprises mapping a call event to a message indicative of connection made in the generic protocol.

58. The method, as set forth in claim 50 , wherein converting the call events comprises mapping a call event to a message indicative of releasing the connection in the generic protocol.

59. The method, as set forth in claim 50 , wherein converting the call events comprises mapping a call event to a message indicative of releasing the connection completed in the generic protocol.

Assignments (16)
RELEASE OF SECURITY INTEREST Recorded Jun 24, 2024
From: CITIZENS BANK, N.A.
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 067822/0433 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT AT R/F 044978/0801 Recorded Dec 6, 2021
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: RIBBON COMMUNICATIONS OPERATING COMPANY, INC. (F/K/A GENBAND US LLC AND SONUS NETWORKS, INC.)
Reel/Frame 058949/0497 →
SECURITY INTEREST Recorded Mar 3, 2020
From: RIBBON COMMUNICATIONS OPERATING COMPANY, INC.
To: CITIZENS BANK, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 052076/0905 →
SECURITY INTEREST Recorded Jan 2, 2018
From: GENBAND US LLC; SONUS NETWORKS, INC.
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 044978/0801 →
TERMINATION AND RELEASE OF PATENT SECURITY AGREEMENT Recorded Dec 29, 2017
From: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
To: GENBAND US LLC
Reel/Frame 044986/0303 →
CORRECTIVE ASSIGNMENT TO CORRECT PATENT NO. 6381239 PREVIOUSLY RECORDED AT REEL: 039269 FRAME: 0234. ASSIGNOR(S) HEREBY CONFIRMS THE PATENT SECURITY AGREEMENT. Recorded Jan 3, 2017
From: GENBAND US LLC
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 041422/0080 →
RELEASE AND REASSIGNMENT OF PATENTS Recorded Jul 7, 2016
From: COMERICA BANK, AS AGENT
To: GENBAND US LLC
Reel/Frame 039280/0467 →
PATENT SECURITY AGREEMENT Recorded Jul 6, 2016
From: GENBAND US LLC
To: SILICON VALLEY BANK, AS ADMINISTRATIVE AGENT
Reel/Frame 039269/0234 →
RELEASE OF SECURITY INTEREST Recorded Jan 10, 2014
From: ONE EQUITY PARTNERS III, L.P., AS COLLATERAL AGENT
To: GENBAND US LLC
Reel/Frame 031968/0955 →
SECURITY AGREEMENT Recorded Nov 9, 2010
From: GENBAND US LLC
To: COMERICA BANK
Reel/Frame 025333/0054 →
PATENT SECURITY AGREEMENT Recorded Jun 18, 2010
From: GENBAND US LLC
To: ONE EQUITY PARTNERS III, L.P., AS COLLATERAL AGENT
Reel/Frame 024555/0809 →
CHANGE OF NAME Recorded Jun 2, 2010
From: GENBAND INC.
To: GENBAND US LLC
Reel/Frame 024468/0507 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 5, 2009
From: SANTERA SYSTEMS, LLC
To: GENBAND, INC.
Reel/Frame 023471/0754 →
MERGER Recorded Mar 28, 2008
From: SANTERA SYSTEMS, INC.
To: SANTERA SYSTEMS, LLC
Reel/Frame 020741/0943 →
MERGER Recorded Mar 25, 2008
From: SANTERA SYSTEMS, INC.
To: SANTERA SYSTEMS, LLC
Reel/Frame 020723/0150 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 5, 2002
From: WAH, ALLEN C.; VU, JOE Q.; ROSEN, ELIOT B.; CAIN, THOMAS A.; PERRY, MATTHEW C.; BADRI, RAJAKUMAR V.
To: SANTERA SYSTEMS INC.
Reel/Frame 012668/0857 →