Method and apparatus for dynamic device pairing

CROSS REFERENCE TO RELATED APPLICATION

0001The present application is a divisional of U.S. patent application Ser. No. 13/595,626, filed Aug. 27, 2012, entitled “METHOD AND APPARATUS FOR DYNAMIC DEVICE PAIRING”, which is incorporated herein by this reference in its entirety.

FIELD

0002The disclosure relates to pairing communication devices within a communication system.

BACKGROUND

0003It is often advantageous to allow a user of a communication system to access different communication devices. For example, a user associated with a desk phone in the user's office may wish to access a phone in a different room. As a further example, users may have need of different communication capabilities for different communications, and those capabilities may be best supported by different communication devices. In such situations, it is often desirable to present the device used to support the communication (i.e., the media stream) to other communication devices and/or the communication system as the user's personal device. Similar situations arise when advanced call control is desired from a softclient running on a computing device.

0004Systems have been developed that allow a user to forward calls from a communication device associated with a communication address, to an alternate communication device. However, communications placed from the alternate device are typically not presented to called parties as being associated with the communication address of the user's primary device. In addition, communications conducted in connection with an alternate device using call forwarding are generally made without the application of call features or restrictions associated with the primary device.

0005Still other systems have been developed that pair an alternate device to a user's primary device. For example, systems have been developed to support telecommuters, to enable users to present a consistent communication address to called and calling parties. However, such systems suffer from deficiencies with respect to the application of calling features and restrictions. For example, where pairing is accomplished by a mechanism outside of a server responsible for applying other features and restrictions, that other server may be unaware of a pairing that has been implemented. As a result, the features and restrictions applied to a call involving paired devices may be those associated with a paired device, rather than a pairing device or both the pairing and paired devices. This can in turn result in a failure to apply restrictions that should be enforced with respect to the call and/or in desired features being unavailable.

SUMMARY

0006Embodiments of the present disclosure are directed to solving these and other problems and disadvantages of the prior art. According to embodiments of the present disclosure, systems and methods are provided that operate to pair communication devices. Pairing is accomplished such that features and restrictions associated with both the pairing and paired communication devices can be applied. Features and restrictions can be applied even if the mechanism that implements the pairing is separate from the server or other device responsible for providing features and/or enforcing restrictions associated with the devices. Moreover, a pairing device may continue to exercise control of a communication associated with a paired device, even when the media stream is directed to the paired device.

0007A system in accordance with embodiments of the present disclosure includes a pairing server or module that provides or executes a dynamic device pairing (DDP) application or function. The pairing server operates to implement the pairing of two communication devices. In particular, both the pairing and paired devices of a communication device pair are associated with the call. However, the media is routed to the paired device by using the session description protocol (SDP) identifier for the paired device. The pairing device is placed in a far end hold. Accordingly, a media path is established to the paired device, while control is maintained at the pairing device. In addition, to other endpoints in the call, the pairing device appears as a party to the call, while the paired device does not. In accordance with embodiments of the present disclosure, the pairing can be implemented at the request of a user, for example by providing user input at the pairing device that is sent to the pairing server to effect the pairing.

0008When a user associated with paired devices receives an inbound call, the dynamic device pairing application may be invoked after all other terminal applications associated with the inbound call have been invoked. The INVITE message for the call is sent to both the pairing and paired devices. When the user answers on the paired device, the paired device's SDP answer is sent back to the communication device of the caller, and a media channel is established between the paired device and the caller's communication device. The control dialog to the controlling pairing device will also be established, but it will appear to the pairing device that it is in far end hold. The pairing device is thus able to control the call while the user is talking on the paired device.

0009When an outbound call is placed by a user associated from a pairing device, the dynamic device pairing application or function may be origination sequenced before all other sequential applications. For example, the origination sequence can be paused while the DDP application initiates a call to the paired device. When the user answers at the paired device, the DDP application issues a REFER message, asking that paired device initiate a call back to the DDP application with an SDP offer. This SDP offer is substituted for that sent by the pairing device, and the origination sequence can be resumed. Alternatively, a slow start INVITE can be used where the media is established after the SIP threeway handshake (INVITE/2000K/ACK). All remaining origination applications (e.g., a call recording application) for the calling user are then sequenced. When the far end answers, the 200 OK message with the SDP answer is sent along to the paired device and a media path is established between the paired device and the called device. The pairing device is placed on far end hold, with the result that the pairing device is capable of controlling the call while the media is sent to the paired device to enable the user to talk using the paired device. In the example of a call recording application, the call recording application could be provisioned to record all calls that the pairing user makes or receives, and the architecture described herein would allow that to happen even for calls where the media goes to the paired device.

0010Additional features and advantages of embodiments of the present disclosure will become more readily apparent from the following description, particularly when taken together with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

0011<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram depicting components of a communication system in accordance with embodiments of the present disclosure;

0012<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram depicting a pairing server providing a dynamic device pairing function in accordance with embodiments of the present disclosure;

0013<figref idref="DRAWINGS">FIGS. 3A-1</figref>, <b>3</b>A-<b>2</b>, <b>3</b>B-<b>1</b> and <b>3</b>B-<b>2</b> illustrate call flow scenarios in accordance with embodiments of the present disclosure; and

0014<figref idref="DRAWINGS">FIG. 4</figref> is a flowchart illustrating aspects of a method for providing dynamic device pairing in accordance with embodiments of the present disclosure.

DETAILED DESCRIPTION

0015<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram depicting components of a communication system <b>100</b> capable of implementing dynamic device pairing in accordance with embodiments of the present disclosure. In general, the system <b>100</b> includes a communication server <b>104</b> having a user relation element <b>102</b>, one or more application servers <b>108</b> providing one or more applications <b>114</b>, and a pairing server <b>112</b> providing a dynamic device pairing (DDP) application <b>116</b>. In some embodiments, one, some, or all of the servers <b>104</b>, <b>108</b>, <b>112</b> are associated with an enterprise communication system <b>106</b>. The communication server <b>104</b> may employ the user relation element <b>102</b> to identify application sequences for different users (e.g., according to user preferences, administrative rules, etc.). The user relation element <b>102</b> may include a table or similar type of data structure that maps a user's communication preferences to a sequence of applications that are to be invoked for the user when the user either places an outbound call or receives an inbound call. Upon receiving a communication-initiating message (e.g., an INVITE message), the communication server <b>104</b> may employ the user relation element <b>102</b> to determine the next application to include in the calling or called user's application sequence and, based on such a determination, route the communication-initiating message to the appropriate server <b>108</b>, <b>112</b>.

0016Stated another way, the communication server <b>104</b> may facilitate the establishment of various application sequences for communication sessions of users belonging to the enterprise communication system <b>106</b>. In some embodiments, the communication server <b>104</b> may establish the applications as Back-to-Back User Agents (B2BUAs) or proxies in the signaling and/or media path of a communication session. The manner in which the appropriate applications are sequenced will be described in further detail herein. These sequenced applications <b>114</b>, <b>116</b> can be provided to select and control the running of services or features associated with a communication session between communication devices <b>120</b>, and/or to enforce restrictions associated with communication devices <b>120</b>.

0017The DDP application <b>116</b> represents one specific type of application that enables a user <b>112</b> to dynamically pair one communication device <b>120</b> with another communication device <b>120</b>. Examples of suitable types of other applications <b>114</b> include, without limitation, call recording applications, Find-me/Follow-me applications, Extension to Cellular (EC-500) applications, call forwarding applications, coverage applications (e.g., voicemail, transfer to assistant, etc.), encryption applications, security applications, call log applications, call history applications, presence applications, context applications, text-to-speech applications, speech-to-text applications, and so on.

0018Although only a single communication server <b>104</b> is depicted in <figref idref="DRAWINGS">FIG. 1</figref>, two or more communication servers <b>104</b> may be provided in a single system <b>100</b> or enterprise network portion <b>106</b> of a system <b>100</b>. A communication server <b>104</b> can be configured to include user communication preferences and/or restrictions vis-à-vis the user relation element <b>102</b>, which map, for a corresponding (enterprise subscriber) user, a set of communication preferences to be invoked for an incoming and/or outgoing contact or communication for each user for whom it is authoritative. The user relation element <b>112</b> may additionally include a feature sequencer that is configured to refer to the data structure that maps a user to communication preferences and then instantiate communication preferences for calling and called users and/or communication devices or endpoints <b>120</b>. The communication preferences for a particular user <b>122</b> and/or endpoint <b>120</b> are referenced by the feature sequencer functionality of the user relation element <b>102</b> to determine which, if any, features should be incorporated into a communication session for the user and/or communication device. The feature sequencer functionality can instantiate the communication features for the communication session by routing the communication-initiation message(s) to the appropriate applications <b>114</b>, <b>116</b> at the appropriate servers <b>108</b>, <b>112</b>.

0019The communication server <b>104</b> may be used to help establish communication sessions and to provide features and/or enforce restrictions with respect to communication sessions. The communication server <b>104</b> may include a private branch exchange (PBX), an enterprise switch, an enterprise server, combinations thereof, or other types of telecommunications system switch or server. The communication server <b>104</b> is, in some embodiments, configured to execute telecommunication functions such as the suite of Avaya AURA™ applications of Avaya Inc., including Communication Manager™, Avaya AURA Communication Manager™Communication Manager Branch™, Session Manager™, and combinations thereof. Features and restrictions can be provided by the communication server <b>104</b> through the incorporation of one or more sequenced applications <b>114</b>, <b>116</b> in a communication session.

0020Although depicted as being separate servers, it should be appreciated that functions of any particular server can be incorporated into any other server without departing from the scope of the present disclosure. For example, the application server <b>108</b> may incorporate the DDP application <b>116</b> or the pairing server <b>112</b> may comprise various other applications <b>114</b>. As another example, the communication server <b>104</b> may comprise the functionality of the application server <b>108</b> and/or pairing server <b>112</b>.

0021Once an application sequence is determined by the user relation element <b>102</b> for a calling and/or called user <b>122</b> and/or communication device <b>120</b>, the communication server <b>104</b> passes the communication-initiating message (e.g., an INVITE message) to a first application <b>114</b>, <b>116</b> in the application sequence, thereby allowing the first application <b>114</b>, <b>116</b> to determine the parameters of the communication session, insert itself into the control and/or media stream of the communication session, and thereby bind itself to the communication session.

0022Once the first application <b>114</b>, <b>116</b> has established itself into the communication session, the first application <b>114</b>, <b>116</b> either passes the communication-initiating message back to the communication server <b>104</b> to so that the user relation element <b>102</b> can identify the next application <b>114</b>, <b>116</b> in the application sequence and re-route the communication-initiating message to appropriate server <b>108</b>, <b>112</b>. In some embodiments, it may be desirable to have each application <b>114</b>, <b>116</b> pass the communication-initiating message back to the communication server <b>104</b> so that each application <b>114</b>, <b>116</b> can operate independently of one another (e.g., does not have to know about any other application <b>114</b>, <b>116</b> in the communication system <b>100</b>). However, it may also be possible to have one application <b>114</b>, <b>116</b> pass the communication-initiating message to the next application <b>114</b>, <b>116</b> directly. Alternatively or in addition, the message may be redirected, rejected, or the like. Moreover, parties and/or media servers may be added to the call by an application <b>114</b>, <b>116</b>, depending upon the functions provided by the application <b>114</b>, <b>116</b>.

0023As can be appreciated by one of skill in the art, this process continues until all sequenced applications <b>114</b>, <b>116</b> for implementing preferences and/or restrictions with respect to users <b>122</b> and/or communication devices <b>120</b> have been applied to the communication session.

0024As noted above, the pairing server <b>112</b> in accordance with embodiments of the present disclosure provides a DDP application or function <b>116</b>. As described in greater detail elsewhere herein, the DDP application <b>116</b> facilitates the pairing of communication devices <b>120</b> for which dynamic device pairing has been provisioned within the pairing server <b>112</b>. More particularly, the DDP application <b>116</b> executed by the pairing server <b>112</b> enables two associated endpoints <b>120</b>, more particularly a pairing and a paired endpoint <b>120</b>, to participate in a communication session with respect to control signals for that session, while providing media only to the paired device <b>120</b>. In addition, the pairing methodology disclosed herein enables other sequenced applications to apply their origination functions even on the call between the DDP application and the paired device. For instance, a primary communication feature server can ensure that the pairing user is authorized to call the paired device even though that feature server is separate from the DDP application.

0025The system <b>100</b> also includes a plurality of communication devices or endpoints <b>120</b>. In particular, the pairing server <b>112</b> may be associated with a first or pairing communication device <b>120</b><i>a </i>and a second or paired communication device <b>120</b><i>b</i>. The system <b>100</b> may also include at least one additional communication device <b>120</b>. For example, the system <b>100</b> can include a third communication device <b>120</b><i>c</i>, also referred to herein as a far end communication device <b>120</b><i>c. </i>

0026A communication device or endpoint <b>120</b> may correspond to a user agent (UA) or multiple UAs of users. Examples of communication devices <b>120</b> include, without limitation, a telephone, a soft phone, a cellular phone, a multi speaker communication device (e.g., a conference phone), a video phone, a personal computer (PC), a laptop computer, a tablet computer, a personal digital assistant (PDA), a smart phone, a thin client, or the like. It should be appreciated that a communication device <b>120</b> may be configured to support single or multi user interactions with other communication devices <b>120</b> within an enterprise, as well as other communication devices <b>120</b> that are external to the enterprise.

0027In accordance with embodiments of the present disclosure, and as described herein, a user <b>122</b> of a first communication device (the pairing communication device) <b>120</b><i>a </i>may provision the DDP application <b>116</b> running on or executed by the pairing server <b>112</b> such that the first communication device <b>120</b><i>a </i>is paired to a second communication device (the paired communication device) <b>120</b><i>b</i>. More particularly, the pairing operation enables the user <b>122</b> to present the address associated with the first communication device <b>120</b><i>a </i>to other communication devices <b>120</b> that are party to a communication session (e.g., the third communication device <b>120</b><i>c</i>) and to maintain control of such communications through the first communication device <b>120</b><i>a</i>, while establishing the media path through the second communication device <b>120</b><i>b</i>. Accordingly, the user <b>122</b> can operate his or her pairing communication device <b>120</b><i>a </i>to exercise control over the communication session, while using the paired communication device <b>120</b><i>b </i>to receive and provide media (e.g., audio content). Moreover, embodiments of the present disclosure accomplish such pairing while maintaining the application of sequenced applications <b>114</b>, <b>116</b> that provide features and/or that apply restrictions to calls associated with the first communication device <b>120</b><i>a </i>and/or the second communication device <b>120</b><i>b</i>. In addition, such pairing is accomplished through the provision of the pairing server <b>112</b> and the DDP application <b>116</b>, without requiring modifications to SIP enabled communication devices <b>120</b> or other components of the system <b>100</b>. Invocation of the DDP application <b>116</b> can be easily implemented by updating a user's communication preferences in the user relation element <b>102</b> of the communication server <b>104</b>.

0028Various nodes or devices included in the system <b>100</b> can be interconnected by one or more communication networks <b>124</b>. As examples, but without limitation, a communication network <b>124</b> may comprise any type and any number of communication mediums and devices which are capable of supporting communication sessions, such as voice calls, video calls, TTY calls, multimedia sessions, or the like. The communication network <b>124</b> may include a local area network (LAN), a wide area network (WAN), a session initiation protocol (SIP) network, and/or any other type of packet switched or circuit switched network known in the art. In addition, a first part of the network <b>124</b> can operate to interconnect one or both of the first <b>120</b><i>a </i>and second <b>120</b><i>b </i>communication devices to the pairing server <b>112</b> and in turn to the communication server <b>104</b>. The first part of the network <b>124</b> may, as an example, comprise an enterprise network. A second part of the network <b>124</b> may connect the communication server <b>104</b> to the third communication device <b>120</b><i>c. </i>

0029<figref idref="DRAWINGS">FIG. 2</figref> illustrates components of an exemplary pairing server <b>112</b> in accordance with embodiments of the present disclosure. The pairing server <b>112</b> in accordance with embodiments of the present disclosure provides DDP services to registered communication devices <b>120</b> for which pairing has been provisioned. In general, the pairing server <b>112</b> can comprise a general purpose computer or server device that provides various communication functions and features. As a further example, the pairing server <b>112</b> may comprise a particular instance of a communication server <b>104</b>, or may even be implemented by or as part of a communication server <b>104</b>, instead of as a separate system component. Accordingly, the pairing server <b>112</b> can include a processor <b>204</b>. The processor <b>204</b> may comprise a general purpose programmable processor or controller for executing application programming or instructions. As a further example, the processor <b>204</b> may comprise a specially configured application specific integrated circuit (ASIC) or other integrated circuit, a digital signal processor, a hard wired electronic or logic circuit such as a discrete element circuit, a programmable logic device or gate array, special purpose computer, or the like. The processor <b>204</b> generally functions to run programming code or instructions implementing various functions of the pairing server <b>112</b>.

0030The pairing server <b>112</b> may also include memory <b>208</b> for use in connection with the execution of application programming by the processor <b>204</b>, and for the temporary or long term storage of program instructions and/or data. As examples, the memory <b>208</b> may comprise RAM, SDRAM or other solid state memory. Alternatively or in addition, data storage <b>212</b> may be provided. In accordance with embodiments of the present disclosure, data storage <b>212</b> can contain programming code or instructions implementing various of the applications or functions executed or performed by the pairing server <b>112</b>. Like the memory <b>208</b>, the data storage <b>212</b> may comprise a solid state memory device or devices. Alternatively or in addition, the data storage <b>212</b> may comprise a hard disk drive or other random access memory.

0031In accordance with embodiments of the present disclosure, the data storage <b>212</b> can include various applications and data. For example, the data storage <b>212</b> can include the DDP application <b>116</b>, the execution of which by the processor <b>204</b> implements functions of the pairing server <b>112</b> in implementing dynamic device pairing. In addition, the data storage <b>212</b> can maintain data regarding registered communication devices <b>120</b>, and provisioning data <b>216</b> for pairing communication devices <b>120</b> to one another.

0032The pairing server <b>112</b> can additionally include a communication interface or interfaces <b>220</b>. The communication interface <b>220</b> may provide connectivity between the pairing server <b>112</b> and other components of the system <b>100</b>, including the communications server <b>104</b> and communication devices <b>120</b>, either directly or through one or more networks <b>124</b>.

0033<figref idref="DRAWINGS">FIGS. 3A-1</figref>, <b>3</b>A-<b>2</b>, <b>3</b>B-<b>1</b> and <b>3</b>B-<b>2</b> illustrate a communication session or call flow in accordance with embodiments of the present disclosure. More particularly, the call flow for an outgoing call made from a pairing device <b>120</b><i>a</i>, shown in the example of <figref idref="DRAWINGS">FIG. 3A-1</figref> and <b>3</b>A-<b>2</b> as a flare device <b>120</b><i>a</i>, after provisioning data <b>216</b> has been provided to the pairing server <b>112</b>, is shown. This provisioning data identifies the paired device <b>120</b><i>b</i>, and includes an instruction from the user <b>122</b> to utilize device <b>120</b> pairing. Initially, an INVITE message is sent from the pairing device <b>120</b><i>a </i>to the pairing server <b>112</b> to originate the call (<b>304</b>).

0034It should be noted that the communication server <b>104</b>/user relation element <b>102</b> is not depicted in <figref idref="DRAWINGS">FIGS. 3A-1</figref>, <b>3</b>A-<b>2</b>, <b>3</b>B-<b>1</b> and <b>3</b>B-<b>2</b> for simplicity. However, as discussed above, the feature sequencer functionality of the user relation element <b>102</b> may dictate that the communication server <b>104</b>/user relation element <b>102</b> is between the pairing device <b>120</b><i>a</i>, pairing server <b>112</b>, paired device <b>120</b><i>b</i>, application server <b>108</b> (referred to as a primary Feature Server (FS) in <figref idref="DRAWINGS">FIGS. 3A-1</figref>, <b>3</b>A-<b>2</b>, <b>3</b>B-<b>1</b> and <b>3</b>B-<b>2</b>), and other communication devices depicted herein. The communication server <b>104</b>/user relation element <b>102</b> has not been shown to enhance the understanding of the dynamic device pairing concepts described herein. Those skilled in the art will appreciate how the communication server <b>104</b>/user relation element <b>102</b> can be inserted into the message path between each device to ensure proper control of the communication sessions is maintained.

0035The pairing server <b>112</b> then pauses the origination sequence and sends an INVITE message to the paired device <b>120</b><i>b </i>with a fake or placeholder SDP associated therewith (<b>308</b>). Alternatively, the pairing server <b>112</b> may send the SDP offer from the pairing device <b>120</b><i>a</i>. The INVITE message can indicate in a reason header that the call to the paired device <b>120</b><i>c </i>is a service link. As used herein, the term “service link” should be understood to include any data or media connection used between the pairing device <b>120</b><i>a </i>and paired device <b>120</b><i>b </i>to enable control of one device with inputs received at the other device. The “service link” may correspond to a unidirectional or bidirectional communication link.

0036As a result, the communication server <b>104</b> can exclude this link from bandwidth calculations and to report a call topology change if there was any mid-call control on the paired device <b>120</b><i>c</i>. When the user answers at the paired device <b>120</b><i>b</i>, the DDP application <b>116</b> issues a REFER message asking that the user agent associated with the paired communication device <b>120</b><i>b </i>initiate a call back to the DDP application <b>116</b> with an SDP offer (<b>312</b>). In an alternative embodiment, a “slow start” INVITE is used with the paired device <b>120</b><i>b</i>. Specifically, the initial INVITE is sent with no SDP offer and the 200 OK from the paired device <b>120</b><i>b </i>has an SDP offer. The ACK message, which isn't sent until the called party <b>120</b><i>c </i>answers with a 200 OK message, then has the SDP answer information from the called party <b>120</b><i>c</i>. It should be appreciated that the utilization of the “slow start” INVITE achieves a simpler call flow, but the drawback is that the caller doesn't hear the ringback on the paired device <b>120</b><i>b. </i>

0037The DDP application <b>116</b> substitutes the SDP offer from the paired communication device <b>120</b><i>b </i>for the SDP offer that was sent by the pairing communication device <b>120</b><i>a</i>, and the origination sequence is resumed. Thereafter, the remaining origination applications <b>114</b> within the primary FS <b>108</b> or any other application server for the calling user are then sequenced by the communication server <b>104</b> and user relation element <b>102</b>. Notably, the INVITE message passed to the communication server <b>104</b> is associated with the initial invite from the pairing communication device <b>120</b><i>a</i>, but with the SDP of the paired communication device <b>120</b><i>b</i>. Accordingly, the INVITE message passed to the called communication device <b>120</b> (e.g., the paired communication device <b>120</b><i>c</i>) (<b>316</b>) shows the pairing communication device <b>120</b><i>a </i>as the originating device but has the media offer from the paired device. Since the pairing communication device <b>120</b><i>a </i>has an active dialog, it can control the call while the user is talking on the paired communication device <b>120</b><i>b</i>, as the media path is established between the paired communication device <b>120</b><i>b </i>and the called communication device <b>120</b><i>c</i>. The 200 OK response when the called device <b>120</b><i>c </i>answers (<b>320</b>) is sent to the paired device <b>120</b><i>b </i>(<b>324</b>), with the called device SDP answer and an indication that this is a service link call. A 200 OK is also sent to the pairing device with a “hold” SDP.

0038With respect to an inbound call to the first or pairing communication device <b>120</b><i>a</i>, the DDP application <b>116</b> is generally invoked after all other terminal applications <b>114</b> have been invoked by the communication server <b>104</b>/user relation element <b>102</b>. The call flow for an incoming call placed to a pairing device <b>120</b><i>a </i>that is associated with a paired device <b>120</b><i>b </i>is illustrated in the example of <figref idref="DRAWINGS">FIGS. 3B-1</figref> and <b>3</b>B-<b>2</b>. In this scenario, the calling party, for example using a third communication device <b>120</b><i>c</i>, places a call that results in an INVITE message being sent to the pairing server <b>112</b> with the SDP offer of the third communication device <b>120</b><i>c </i>(<b>346</b>). That INVITE message is sent to the target device, which in this case is the pairing device <b>120</b><i>a </i>(<b>350</b>). The pairing server <b>112</b> also sends an INVITE message with the SDP offer of the third communication device <b>120</b><i>c </i>to the paired communication device <b>120</b><i>b </i>(<b>354</b>). This calling identity in this INVITE to the paired device is set to the identity of the originally called user. This invokes that user's origination applications so that they can ensure that the pairing user is authorized to call the paired device. The result is that both the first <b>120</b><i>a </i>and second <b>120</b><i>b </i>communication devices are now ringing. The user <b>122</b> answers on the paired communication device <b>120</b><i>b</i>, with the result that a 200 OK message with the SDP of the paired communication device <b>120</b><i>b </i>is sent back to the pairing server <b>112</b> (<b>358</b>). The SDP of the paired device <b>120</b><i>b </i>is then included in messages passed by the pairing server <b>112</b> to the calling or third communication device <b>120</b><i>c</i>, establishing a media or speech path between the paired communication device <b>120</b><i>b </i>and the calling communication device <b>120</b><i>c </i>(<b>362</b>). In addition, a REFER message is sent by the pairing server <b>112</b> to the pairing or first communication device <b>120</b><i>a </i>to request auto answer of the call made to that communication device <b>120</b><i>a </i>by the communication server <b>112</b> (<b>366</b>). The auto answer of the call by the first communication device <b>120</b><i>a </i>establishes a control path for the communication session that extends to the pairing or first communication device <b>120</b><i>a</i>. In addition to being associated with the SDP of the paired or second communication device <b>120</b><i>b</i>, messages passed as part of the call providing an exchange of media between the second communication device <b>120</b><i>b </i>and the third communication device <b>120</b><i>c </i>are associated with the caller ID of the pairing or first communication device <b>120</b><i>a</i>. Accordingly, sequenced applications <b>108</b> can be applied by a communication server <b>104</b> (see <figref idref="DRAWINGS">FIG. 1</figref>) in the call path. Therefore, features and restrictions associated with all of the call or communication session endpoints, in this case communication devices <b>120</b><i>a</i>, <b>120</b><i>b</i>, and <b>120</b><i>c</i>, can be applied. In an alternate embodiment, the user could answer on their pairing endpoint and the DDP application could be configured to send a REFER message to the paired device with an auto answer request.

0039In both the outbound and inbound cases, the call to the paired communication device <b>120</b><i>b </i>is origination sequenced on behalf of the pairing user. This is in addition to sequencing with respect to the pairing device <b>120</b><i>a</i>. This ensures that the user doesn't circumvent their origination restrictions. For example, a do not call list application can be applied to assert restrictions. In addition, the pairing communication device <b>120</b><i>a </i>can signal call control operations as if it were operating in the absence of a pairing with the paired communication device <b>120</b><i>b</i>. Accordingly, the call or media path to the paired communication device <b>120</b><i>b </i>follows the control dialog established in connection with the pairing communication device <b>120</b><i>a</i>. In addition, the establishment of the media path with the paired communication device <b>120</b><i>b </i>is performed through SDP substitution by the DDP application <b>116</b>. Moreover, such SDP substitution is maintained by the pairing server <b>112</b> throughout the duration of the call.

0040Aspects of the operation of a system <b>100</b> in accordance with embodiments of the present invention are further described in connection with <figref idref="DRAWINGS">FIG. 4</figref>. More particularly, at step <b>404</b>, the DDP application <b>116</b> is provisioned. Provisioning the DDP application <b>116</b> can include associating a registered communication device (e.g., the pairing communication device <b>120</b><i>a</i>) with a paired communication device <b>120</b> (e.g., communication device <b>120</b><i>b</i>). Such provisioning can be accomplished through the pairing communication device <b>120</b><i>a</i>, or any other device capable of receiving input from the user and delivering such input to the DDP application <b>116</b>. Moreover, provisioning can include the user <b>122</b> logging into a user portal of the pairing server <b>112</b>, through which the user <b>122</b> can activate the DDP service provided by the DDP application <b>116</b>. Moreover, provisioning can include configuring the paired device <b>120</b><i>b </i>number, configuring a pairing duration timeout, or enabling a no timeout option. Such provisioning information can be stored as provisioning data <b>216</b> on the pairing server <b>112</b>.

0041At step <b>408</b>, a determination can be made as to whether a call has been placed from or received for the pairing communication device <b>120</b><i>a</i>. Where a call is placed from the pairing communication device <b>120</b><i>a</i>, the DDP application <b>116</b> is origination sequenced before any other sequenced applications <b>108</b> (step <b>412</b>). The origination sequencing is then paused, and a call is placed to the paired communication device <b>120</b><i>b </i>with a request for an SDP offer from the paired communication device <b>120</b><i>b</i>, and causing the paired device <b>120</b><i>b </i>to ring (step <b>416</b>). When the user <b>122</b> answers the call on the paired device <b>120</b><i>b </i>(or after an auto answer if the paired device <b>120</b><i>b </i>is capable), the called party destination communication device <b>120</b><i>c </i>will ring (step <b>420</b>). The called communication device <b>120</b><i>c </i>displays caller line identification related to the user <b>122</b>. For example, where the pairing device <b>120</b><i>a </i>is the user's <b>122</b> primary device <b>120</b>, caller ID information associated with the pairing device <b>120</b><i>a </i>is displayed by the called communication device <b>120</b><i>c</i>. Ring back is provided to both the pairing <b>120</b><i>a </i>and the paired <b>120</b><i>b </i>communication devices. Also, if early media is played from the destination, the user <b>122</b> will hear it on the paired device <b>120</b><i>b</i>, while hearing ring back on the pairing device <b>120</b><i>a. </i>

0042When the called party answers the call at the called communication device <b>120</b><i>c</i>, an audio/video media path is established between the paired communication device <b>120</b><i>b </i>and the called party communication device <b>120</b><i>c </i>(step <b>424</b>). The pairing device <b>120</b><i>a </i>will also have an established call with the called communication device <b>120</b><i>c</i>, but without any media, allowing for further call control to be exercised by the calling communication device <b>120</b><i>a</i>. More particularly, a call signaling path can be established to the pairing communication device <b>120</b><i>a</i>. Both the pairing communication device <b>120</b><i>a </i>and the paired communication device <b>120</b><i>b </i>show the name and number associated with the called communication device <b>120</b><i>c</i>. If the call is dropped from the pairing device <b>120</b><i>a</i>, the paired device <b>120</b><i>b </i>or called party device <b>120</b><i>c</i>, all parties will drop from the call.

0043Where an incoming call is placed to a pairing communication device <b>120</b><i>a</i>, both the pairing communication device <b>120</b><i>a </i>and the paired communication device <b>120</b><i>b </i>ring, and both the pairing <b>120</b><i>a </i>and paired <b>120</b><i>b </i>communication devices show the caller name and number (step <b>428</b>). If the user <b>122</b> answers the call on the pairing communication device <b>120</b><i>a</i>, the paired communication device <b>120</b><i>b </i>will stop ringing and an audio/video media path is established between the pairing communication device <b>120</b><i>a </i>and the caller device <b>120</b><i>c</i>. The call is established as if there were no pairing configured. In an alternative embodiment, the paired device <b>120</b><i>b </i>may be auto-answered if the user <b>112</b> answers the incoming call on the pairing device <b>120</b><i>a</i>. However, if the user answers the call on the paired communication device <b>120</b><i>b</i>, the media path is established between the paired communication device <b>120</b><i>b</i>, and the calling communication device <b>120</b><i>c </i>(step <b>432</b>). The call is also established, for example after an auto answer function is performed, on the pairing communication device <b>120</b><i>a</i>, but without media, for further call control. In addition, the DDP application <b>116</b> is sequenced after other sequenced applications when a call is received at a paired device. If the call is dropped from the pairing communication device <b>120</b><i>a</i>, the paired communication device <b>120</b><i>b</i>, or the calling communication device <b>120</b><i>c</i>, all communication devices <b>120</b> will drop from the call.

0044At step <b>436</b>, a determination can be made as to whether the call has been terminated. Once the call is terminated, the process ends.

0045Embodiments of the present disclosure can provide for the pairing of any communication device <b>120</b> with any other audio/video communication device <b>120</b>. In addition, pairing as disclosed herein enables call control to be maintained on a pairing communication device <b>120</b><i>a</i>, while having the media path established with the paired communication device <b>120</b><i>b</i>. Moreover, this is accomplished without media splitting or media switching between the pairing <b>120</b><i>a </i>and paired <b>120</b><i>b </i>communication devices. The other party to the call is not aware of the pairing.

0046The paired device can be identified as part of provisioning data <b>216</b> by, for example but without limitation, an enterprise canonical or E.164 format. In addition to identifying pairing <b>120</b><i>a </i>and paired <b>120</b><i>b </i>communication devices, a user <b>122</b> can configure other parameters associated with pairing. Examples of such parameters include a pairing duration timeout. In addition, the ability to pair communication devices <b>120</b> can be controlled through the assignment of user service levels. For example, pairing may be allowed only if a device to be paired has a user service level that is lower than or equal to the user service level of the user <b>122</b> and/or the pairing communication device <b>120</b><i>a</i>. In accordance with still other embodiments, if a communication device <b>120</b> is already paired to another communication device, a user <b>122</b> with a higher user service level than the user who initiated the in-place pairing can force the un-pairing of the user with the lower user service level. During ringing time, for a pairing communication device <b>120</b><i>a </i>originated call, the pairing communication device <b>120</b><i>a </i>displays the far end number only, the paired communication device <b>120</b><i>b </i>displays a message such as “AUS DDP Service”, while the far end communication device <b>120</b><i>c </i>shows the name/number information of the pairing communication device <b>120</b><i>a</i>. During ringing time for an incoming call to the pairing communication device <b>120</b><i>a</i>, both the pairing <b>120</b><i>a </i>and paired <b>120</b><i>b </i>communication devices may be configured to show the far end name and number, while the far end communication device <b>120</b><i>c </i>shows the pairing communication device <b>120</b><i>a </i>number. This display of far end name and number is not necessary and may not be performed in all instances.

0047When a call is established, both the pairing <b>120</b><i>a </i>and paired <b>120</b><i>b </i>communication devices show a far end name and number, while the far end communication device <b>120</b><i>c </i>shows the pairing communication device <b>120</b><i>a </i>name and number. In addition, while pairing is provisioned, a call originated by the paired communication device <b>120</b><i>b </i>can be controlled using the pairing communication device <b>120</b><i>a. </i>

0048The foregoing discussion of the invention has been presented for purposes of illustration and description. Further, the description is not intended to limit the invention to the form disclosed herein. Consequently, variations and modifications commensurate with the above teachings, within the skill or knowledge of the relevant art, are within the scope of the present invention. The embodiments described hereinabove are further intended to explain the best mode presently known of practicing the invention and to enable others skilled in the art to utilize the invention in such or in other embodiments and with various modifications required by the particular application or use of the invention. It is intended that the appended claims be construed to include alternative embodiments to the extent permitted by the prior art.