IP Library Granted Patent US 8,705,517
Granted Patent B2
US 8,705,517 · App. 13/539,801 · Granted Apr 22, 2014

Forced hold call handling in a VoP environment

Inventors: David P. Ress (Cary, NC); William D. Gentry (Raleigh, NC); Brian Stucker (Sachse, TX); Olga Wagner (Durham, NC)
Assignee: Rockstar Consortium US LP
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 8,705,517
App. No.
13/539,801
Granted
Apr 22, 2014
Kind
B2
Abstract

The present invention provides a technique for providing a forced hold service such as is used for an emergency services call, which is supported at least in part over a packet network. The forced hold service acts to effectively hold a connection for the call with a called party, even when the caller takes an action that would normally end a call, such as going on hook, pressing end, or the like. When the caller takes an action that would normally end the call, the forced hold service allows the caller to automatically reconnect to the emergency services provider over the held connection upon going offhook, pressing send, or the like. Alternatively, the emergency services provider can effectively re-engage the call wherein the caller is reconnected over the held connection upon going offhook, pressing send, or the like.

Claims (63)

1. A method of handling a packet communication session, comprising:

receiving, from a communications client, a session initiation message comprising information associated with a requirement to maintain a communication session;

establishing a packet communication session with the communications client;

receiving, from the communications client, a message comprising information indicative of an attempt to interrupt the communication session; and

maintaining the communication session notwithstanding the received message comprising information indicative of an attempt to interrupt the communication session, wherein the message comprising information indicative of an attempt to interrupt the communication session comprises a re-invite message having an indication that an emergency services call is in progress and an indication that the call is held.

2. The method of claim 1 , wherein maintaining the communication session notwithstanding the received message comprising information indicative of an attempt to interrupt the communication session comprises putting the packet communication session on hold.

3. The method of claim 1 , wherein the information associated with a requirement to maintain a communication session comprises information indicative of an emergency services call.

4. The method of claim 1 , wherein the information associated with a requirement to maintain a communication session comprises dialed digits associated with a requirement to maintain a call.

5. The method of claim 4 , wherein the dialed digits associated with a requirement to maintain a communication session comprises dialed digits associated with an emergency services call.

6. The method of claim 1 , wherein the information associated with a requirement to maintain a communication session is provided in a priority header of the session initiation message.

7. The method of claim 1 , wherein establishing a packet communication session comprises establishing a packet communication session between the communications client and a media gateway, the media gateway being connected to an access point of a switched telephone network.

8. The method of claim 7 , wherein maintaining the communication session notwithstanding the received message comprising information indicative of an attempt to interrupt the communication session comprises sending the media gateway a hold connection message.

9. The method of claim 7 , wherein establishing a packet communication session comprises establishing a circuit-switched connection between the media gateway and the access point of the switched network via a signaling gateway connected to the switched network.

10. The method of claim 9 , wherein maintaining the communication session notwithstanding the received message comprising information indicative of an attempt to interrupt the communication session comprises sending the signaling gateway notification of the attempt to interrupt the communication session.

11. The method of claim 2 , further comprising:

receiving a message indicating an attempt by a caller to reconnect the packet communication session put on hold; and

in response to the message indicating an attempt by a caller to reconnect the packet communication session, restoring the packet communication session put on hold.

12. The method of claim 2 , further comprising:

receiving a message indicating an attempt by an operator to reconnect the packet communication session put on hold; and

in response to the message indicating an attempt by an operator to reconnect the packet communication session, restoring the packet communication session put on hold.

13. The method of claim 1 , further comprising:

receiving a release message from an entity other than the communications client; and

sending an end message to the communications client in response to the release message.

14. The method of claim 13 , further comprising:

receiving a response from the communications client acknowledging the end message; and

disconnecting the communication session in response to the acknowledgement.

15. The method of claim 2 , further comprising:

receiving a message indicating an attempt by a caller to reconnect the packet communication session put on hold; and

in response to the message indicating an attempt by a caller to reconnect the packet communication session, restoring the packet communication session put on hold, wherein restoring the packet communication session comprises:

sending a signaling gateway notification of the attempt to reconnect; and

sending a media gateway an initiation message.

16. The method of claim 2 , further comprising:

receiving a message indicating an attempt by an operator to reconnect the packet communication session put on hold; and

in response to the message indicating an attempt by an operator to reconnect the packet communication session, restoring the packet communication session put on hold, wherein restoring the packet communication session comprises:

sending a signaling gateway notification of the attempt to reconnect; and

sending a media gateway an initiation message.

17. The method of claim 10 , further comprising:

receiving a release message from an entity other than the communications client;

sending the signaling gateway a release complete notification; and

sending an end message to the communications client in response to the release message.

18. The method of claim 17 , further comprising:

receiving an acknowledgement from the communications client acknowledging the end message; and

disconnecting the communication session in response to the acknowledgement wherein disconnecting the communication session comprises sending release instructions to the media gateway.

19. A method of operating a communications client to handle a packet communication session, comprising:

receiving signaling indicating a request to establish a communication session;

determining that the communication session must be maintained;

sending a session initiation message to a service node, the session initiation message comprising information associated with a requirement that the communication session must be maintained;

detecting an attempt to interrupt the communication session; and

sending to the service node a message indicative of an attempt to interrupt the communication session, wherein the message is a re-invite message comprising an indication that an emergency services call is in progress and an indication that the call is held.

20. The method of claim 19 , wherein determining that the communication session must be maintained comprises detecting that the communications session is an emergency services call.

21. The method of claim 19 , wherein determining that the communication session must be maintained comprises detecting dialed digits associated with a requirement that the communication session must be maintained.

22. The method of claim 21 , wherein the dialed digits associated with a requirement that the communication session must be maintained comprise dialed digits associated with an emergency services call.

23. The method of claim 19 , wherein the information associated with a requirement that the communication session must be maintained is provided in a priority header of the session initiation message.

24. The method of claim 19 , wherein detecting an attempt to interrupt the communication session comprises detecting at least one flash signal.

25. The method of claim 19 , wherein detecting an attempt to interrupt the communication session comprises detecting an on-hook condition.

26. The method of claim 19 , further comprising:

detecting an attempt by a caller to reconnect the packet communication session; and

sending a message indicating an attempt by a caller to reconnect the packet communication session to the service node.

27. The method of claim 26 , wherein detecting an attempt to reconnect the packet communication session comprises detecting an off-hook condition.

28. The method of claim 26 , further comprising:

receiving a ringback message from the service node indicating an attempt by an operator to reconnect the packet communication session;

delivering a ringback alert in response to the ringback message; and

re-establishing communications over the packet communication session in response to the ringback message.

Assignments (6)
RELEASE OF SECURITY INTEREST Recorded Oct 26, 2020
From: JEFFERIES FINANCE LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 054305/0505 →
SECURITY INTEREST Recorded Jun 29, 2018
From: RPX CLEARINGHOUSE LLC
To: JEFFERIES FINANCE LLC
Reel/Frame 046485/0644 →
RELEASE (REEL 038041 / FRAME 0001) Recorded Jan 2, 2018
From: JPMORGAN CHASE BANK, N.A.
To: RPX CORPORATION; RPX CLEARINGHOUSE LLC
Reel/Frame 044970/0030 →
SECURITY AGREEMENT Recorded Mar 9, 2016
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 038041/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 9, 2015
From: ROCKSTAR CONSORTIUM US LP; ROCKSTAR CONSORTIUM LLC; BOCKSTAR TECHNOLOGIES LLC; CONSTELLATION TECHNOLOGIES LLC; MOBILESTAR TECHNOLOGIES LLC; NETSTAR TECHNOLOGIES LLC
To: RPX CLEARINGHOUSE LLC
Reel/Frame 034924/0779 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 11, 2014
From: ROCKSTAR BIDCO, LP
To: ROCKSTAR CONSORTIUM US LP
Reel/Frame 032425/0867 →
Continuity (3)
Continuation 12509528 · Jul 27, 2009
Continuation 11316430 · Dec 22, 2005
Related Publication 20120269100A1 · Oct 25, 2012