Methods, systems, and computer readable media for unifying fixed and mobile devices via third party call control

Abstract

Methods, systems, and computer readable media for unifying fixed and mobile devices via third party call control (3PCC) are disclosed. The method is performed at a dedicated application server (AS) that supports a third-party call control (3PCC) interface. According to one method, a call addressed to a unified subscriber identifier associated with a terminating subscriber is detected, where the terminating subscriber is associated with two or more terminating endpoints. The call is offered to each of the terminating endpoints by initiating signaling to each of the terminating endpoints using the 3PCC interface. One of the terminating endpoints used to answer the call is detected and the call is redirected to the terminating endpoint used to answer the call. Signaling messages are sent to all of the terminating endpoints other than the terminating endpoint used to answer the call for instructing the terminating endpoints to release resources associated with the offered call.

1 . A method for unifying fixed and mobile devices via third party call control, the method comprising:
 at an application server (AS) that supports a third-party call control (3PCC) interface:
 detecting a call addressed to a unified subscriber identifier associated with a terminating subscriber, wherein the terminating subscriber is associated with two or more terminating endpoints; 
 offering the call to each of the terminating endpoints by initiating signaling to each of the terminating endpoints using the 3PCC interface; 
 detecting one of the terminating endpoints used to answer the call; 
 redirecting the call to the terminating endpoint used to answer the call; and 
 sending signaling messages to all of the terminating endpoints other than the terminating endpoint used to answer the call for instructing the terminating endpoints to release resources associated with the offered call. 
   
     
     
         2 . The method of  claim 1  wherein offering the call to the two more terminating endpoints includes offering the call to at least one of a mobile endpoint and a fixed endpoint. 
     
     
         3 . The method of  claim 1  comprising paging and alerting at least one of the terminating endpoints. 
     
     
         4 . The method of  claim 1  comprising maintaining state information for the session such that the state information is visible to services running on the application server. 
     
     
         5 . The method of  claim 1  wherein detecting a call includes detecting an active call originating at an originating endpoint and terminating at a first terminating endpoint of the two or more terminating endpoints. 
     
     
         6 . The method of  claim 5  wherein offering the call to each of the terminating endpoints includes receiving an indication that the terminating subscriber wishes to terminate the call at a second terminating endpoint being different from the first terminating endpoint. 
     
     
         7 . The method of  claim 6  comprising, in response to receiving the indication that the terminating subscriber wishes to terminate the call at the second terminating endpoint:
 initiating a call grabber service for invoking a call grabber session; 
 correlating the incoming call grabber session to the active call; 
 negotiating an end-to-end media path between the originating subscriber and the second terminating endpoint; and 
 sending signaling messages to the first terminating endpoint for instructing the first terminating endpoint to release resources associated with the offered call. 
 
     
     
         8 . The method of  claim 6  wherein receiving the indication that the terminating subscriber wishes to terminate the call at a second terminating endpoint includes receiving a service code from the second terminating endpoint. 
     
     
         9 . The method of  claim 8  comprising allocating a temporary location directory number (TLDN) to the call grabber session and instructing a signaling node to deflect the call grabber session to the specified TLDN. 
     
     
         10 . The method of  claim 1  comprising registering interest in termination or origination events by an endpoint associated with the unified subscriber that includes requesting notification of events whenever a session originates or terminates to the endpoint associated with the unified subscriber identifier. 
     
     
         11 . An application server for unifying fixed and mobile devices via third party call control, the application server comprising:
 a third-party call control (3PCC) interface for:
 detecting a call addressed to a unified subscriber identifier associated with a terminating subscriber, wherein the terminating subscriber is associated with two or more terminating endpoints; 
 offering the call to each of the terminating endpoints by initiating signaling to each of the terminating endpoints; and 
 detecting one of the terminating endpoints used to answer the call; 
   a communications module for:
 redirecting the call to all of the terminating endpoint used to answer the call; and 
 sending signaling messages to all of the terminating endpoints other than the terminating endpoint used to answer the call for instructing the terminating endpoints to release resources associated with the offered call. 
   
     
     
         12 . The application server of  claim 10  wherein the 3PCC interface is configured to offer the call to at least one of a mobile endpoint and a fixed endpoint. 
     
     
         13 . The application server of  claim 10  wherein the 3PCC interface is configured to page and alert at least one of the terminating endpoints. 
     
     
         14 . The application server of  claim 10  wherein the 3PCC interface is configured to maintain state information for the session such that the state information is visible to services running on the application server. 
     
     
         15 . The application server of  claim 10  wherein the 3PCC interface is configured to detect an active call originating at an originating endpoint and terminating at a first terminating endpoint of the two or more terminating endpoints. 
     
     
         16 . The application server of  claim 15  wherein the 3PCC interface is configured to receive an indication that the terminating subscriber wishes to terminate the call at a second terminating endpoint being different from the first terminating endpoint. 
     
     
         17 . The application server of  claim 16  wherein the 3PCC interface, in response to receiving the indication that the terminating subscriber wishes to terminate the call at the second terminating endpoint, is configured to:
 initiate a call grabber service for invoking a call grabber session; 
 correlate the incoming call grabber session to the active call; and 
 the communications module is configured to: 
 negotiate an end-to-end media path between the originating subscriber and the second terminating endpoint; and 
 send signaling messages to the first terminating endpoint for instructing the first terminating endpoint to release resources associated with the offered call. 
 
     
     
         18 . The application server of  claim 17  wherein the indication that the terminating subscriber wishes to terminate the call at the second terminating endpoint comprises a service code from the second terminating endpoint. 
     
     
         19 . The application server of  claim 10  wherein the communications module is configured to communicate with one of a private branch exchange (PBX), a softswitch, and an end-office telephony node. 
     
     
         20 . The application server of  claim 10  wherein the 3PCC interface includes one of a technical report (TR)-87 interface and a telephony application programming interface (TAPI)-based interface. 
     
     
         21 . The application server of  claim 10  wherein the application server provides uniform services for the unified subscriber identity. 
     
     
         22 . The application server of  claim 10  wherein the unified subscriber identifier includes one of a directory number (DN) and a uniform resource identifier (URI). 
     
     
         23 . The application server of  claim 10  wherein the 3PCC interface is configured to register interest in termination or origination events by an endpoint associated with the unified subscriber that includes requesting notification of events whenever a session originates or terminates to the endpoint associated with the unified subscriber identifier. 
     
     
         24 . A computer readable medium comprising computer executable instructions embodied in a non-transitory computer readable medium and when executed by a processor of a computer performs steps comprising:
 at a dedicated application server (AS) that supports a third-party call control (3PCC) interface:
 detecting a call addressed to a unified subscriber identifier associated with a terminating subscriber, wherein the terminating subscriber is associated with two or more terminating endpoints; 
 offering the call to each of the terminating endpoints by initiating signaling to each of the terminating endpoints using the 3PCC interface; 
 detecting one of the terminating endpoints used to answer the call; 
 redirecting the call to the terminating endpoint used to answer the call; and 
 sending signaling messages to all of the terminating endpoints other than the terminating endpoint used to answer the call for instructing the terminating endpoints to release resources associated with the offered call.