System and method for enabling use of a single user identifier across incompatible networks for UCC functionality

Information

  • Patent Grant
  • 10091025
  • Patent Number
    10,091,025
  • Date Filed
    Monday, April 4, 2016
    8 years ago
  • Date Issued
    Tuesday, October 2, 2018
    5 years ago
Abstract
A method and system for supporting a cross-domain communication session between communication platforms using a bridge server are provided. In one example, the method includes registering the bridge server with multiple platforms using a user identifier. A request is received from one of the platforms to establish a communication session with a user corresponding to the user identifier. A communication leg is created for each of the platforms. The leg from which the request was received is an incoming leg and the other legs are outgoing legs. The request is sent over the outgoing legs. An acceptance is received from one of the outgoing legs. A cancel message is sent over the outgoing legs from which the acceptance was not received. The acceptance is sent over the incoming leg. The incoming leg and the outgoing leg from which the acceptance was received are bridged to establish the session.
Description
BACKGROUND

Communications systems often have limitations that affect communications across system boundaries. Accordingly, what is needed are a system and method that addresses such issues.





BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding, reference is now made to the following description taken in conjunction with the accompanying Drawings in which:



FIG. 1 illustrates one embodiment of an environment with two separate domains and a bridge server for cross-domain communications;



FIG. 2 illustrates a diagrammatic view of one embodiment of data contained within a cross-domain database that is accessible to the bridge server of FIG. 1;



FIG. 3 illustrates a more detailed diagrammatic view of one embodiment of the environment of FIG. 1;



FIG. 4 illustrates a diagrammatic view of one embodiment of objects that may be used by the bridge server of FIG. 1 or FIG. 3 to maintain a communication session;



FIG. 5A illustrates a diagrammatic view of one embodiment of a communication session within the environment of FIG. 1 or FIG. 3;



FIG. 5B illustrates a sequence diagram of one embodiment of the communication session of FIG. 5A;



FIGS. 5C and 5D illustrate diagrammatic views of embodiments of objects that may be used by the bridge server to manage the communication session of FIGS. 5A and 5B;



FIG. 6A illustrates a diagrammatic view of another embodiment of a communication session within the environment of FIG. 1 or FIG. 3;



FIG. 6B illustrates a sequence diagram of one embodiment of the communication session of FIG. 6A;



FIGS. 6C-6E illustrate diagrammatic views of embodiments of objects that may be used by the bridge server to manage the communication session of FIGS. 6A and 6B;



FIG. 6F illustrates a diagrammatic view of one embodiment of objects that may be used by the media gateway to manage media legs for the communication session of FIGS. 6A and 6B;



FIG. 7A illustrates a diagrammatic view of another embodiment of a communication session within the environment of FIG. 1 or FIG. 3;



FIG. 7B illustrates a sequence diagram of one embodiment of the communication session of FIG. 7A;



FIGS. 7C-7E illustrate diagrammatic views of embodiments of objects that may be used by the bridge server to manage the communication session of FIGS. 7A and 7B;



FIG. 7F illustrates a diagrammatic view of one embodiment of objects that may be used by the media gateway to manage media legs for the communication session of FIGS. 7A and 7B;



FIG. 8A illustrates a diagrammatic view of another embodiment of a communication session within the environment of FIG. 1 or FIG. 3;



FIG. 8B illustrates a sequence diagram of one embodiment of the communication session of FIG. 8A;



FIGS. 8C-8E illustrate diagrammatic views of embodiments of objects that may be used by the bridge server to manage the communication session of FIGS. 8A and 8B;



FIG. 8F illustrates a diagrammatic view of one embodiment of objects that may be used by the media gateway to manage media legs for the communication session of FIGS. 8A and 8B;



FIG. 9A illustrates a diagrammatic view of another embodiment of a communication session within the environment of FIG. 1 or FIG. 3;



FIG. 9B illustrates a sequence diagram of one embodiment of the communication session of FIG. 9A;



FIGS. 9C-9E illustrate diagrammatic views of embodiments of objects that may be used by the bridge server to manage the communication session of FIGS. 9A and 9B;



FIG. 9F illustrates a diagrammatic view of one embodiment of objects that may be used by the media gateway to manage media legs for the communication session of FIGS. 9A and 9B;



FIG. 10A illustrates a diagrammatic view of another embodiment of a communication session within the environment of FIG. 1 or FIG. 3;



FIG. 10B illustrates a sequence diagram of one embodiment of the communication session of FIG. 10A;



FIGS. 10C-10E illustrate diagrammatic views of embodiments of objects that may be used by the bridge server to manage the communication session of FIGS. 10A and 10B;



FIG. 10F illustrates a diagrammatic view of one embodiment of objects that may be used by the media gateway to manage media legs for the communication session of FIGS. 10A and 10B;



FIG. 11A illustrates a diagrammatic view of another embodiment of a communication session within the environment of FIG. 1 or FIG. 3;



FIG. 11B illustrates a sequence diagram of one embodiment of the communication session of FIG. 11A;



FIGS. 11C-11E illustrate diagrammatic views of embodiments of objects that may be used by the bridge server to manage the communication session of FIGS. 11A and 11B;



FIG. 11F illustrates a diagrammatic view of one embodiment of objects that may be used by the media gateway to manage media legs for the communication session of FIGS. 11A and 11B;



FIGS. 12A and 12B illustrate diagrammatic views of embodiments of objects that may be used by the bridge server of FIG. 1 or FIG. 3 for an instant messaging communication session;



FIGS. 13 and 14 illustrate diagrammatic views of embodiments of objects that may be used by the bridge server of FIG. 1 or FIG. 3 for terminating a communication session;



FIG. 15 illustrates a flowchart of one embodiment of a method that may be executed by the bridge server of FIG. 1 or FIG. 3 to manage messages;



FIG. 16 illustrates a finite state machine diagram of one embodiment of available communication leg states on the bridge server of FIG. 1 or FIG. 3; and



FIG. 17 illustrates a diagrammatic view of one embodiment of a device that may be used within the environments of FIG. 1 and FIG. 3.





DETAILED DESCRIPTION

It is understood that the following disclosure provides many different embodiments or examples. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting. In addition, the present disclosure may repeat reference numerals and/or letters in the various examples. This repetition is for the purpose of simplicity and clarity and does not in itself dictate a relationship between the various embodiments and/or configurations discussed.


Referring to FIG. 1, there is illustrated one embodiment of an environment 100 with a domain 102 and a domain 104 (shown as separated by a line 105). In the present example, the domains 102 and 104 include separate, and likely incompatible, communication platforms that support one or more Unified Communications and Collaboration (UCC) functions, such as presence, instant messaging (IM), audio communications, video communications, screen sharing, file transfers, whiteboards, and conferencing (each of which may be referred to herein as a communication session). Examples of such platforms include Microsoft® Lync™ (referred to hereinafter as “Lync”), Skype™, IBM™ Sametime™, Cisco™ Jabber™, GoToMeeting™, and WebEx™. One or both of the domains may also include a Private Branch Exchange (PBX) system.


Domain 102 includes at least a server 106 as its communication platform and domain 104 includes at least a server 110 as its communication platform. It is understood that the communication platform(s) provided within one or both of the domains 102 and 104 may include multiple servers, gateways, and/or other components, and that the servers 106 and 110 may be gateway servers. In the present embodiment, both servers 106 and 110 support at least some UCC functionality.


A client 108 is coupled to the server 106 and a client 112 is coupled to the server 110. Each client 108 and 112 may be any type of communications device and examples of such communication devices include cellular telephones (including smart phones), personal digital assistants (PDAs), netbooks, tablets, laptops, desktops, workstations, and any other computing device that can communicate with another computing device using a wireless and/or wireline communication link. Such communications may be direct (e.g., via a peer-to-peer network, an ad hoc network, or using a direct connection), indirect, such as through a server or other proxy (e.g., in a client-server model), or may use a combination of direct and indirect communications. In some embodiments, a single device may represent multiple clients. For example, a single device may have one application for one client and another application for another client. In such embodiments, depending on the capabilities and configuration of the device, multiple clients on the device may be logged in simultaneously or only one client may be logged in at a time.


As the servers 106 and 110 are incompatible and in separate domains, each client 108 and 112 must register with the corresponding server 106 and 108, respectively, in order to be able to operate within that domain. The UCC functions available to the clients 108 and 112 depend on such factors as the respective server's configuration and supported UCC functionality, the access rights of each client to various UCC functions (e.g., whether a client is subscribed to a particular UCC function if a subscription is required), and the physical limitations of each client (e.g., does the client have the necessary bandwidth, processing power, and/or memory to use a particular UCC function).


It is desirable for a user to have a single identity in both of the domains 102 and 104. For example, the user may be identified as johndoe@company.com in both the domain 102 and the domain 104. This enables third parties to contact the user via the single identity regardless of which domain the third party is using and which domain(s) the user is currently logged into. However, for this cross-domain communication to occur, there must be coordination between the domains 102 and 104.


Accordingly, a bridge server 114 is provided as part of a cross-domain system 120 to manage communications between the domain 102 and the domain 104. The bridge server 114 accomplishes this by managing notifications and other signaling communications using protocol and authorization information of the domain 102 and the domain 104 that is stored in a cross-domain database 116. The bridge server 114 is able to communicate with each domain 102 and 104 using that domain's protocols and expected message sequences. Although shown as a separate component from the bridge server 114 within the cross-domain system 120, it is understood that the database 116 may be part of the bridge server 114 in some embodiments.


While the bridge server 114 handles signaling, a media server 118 (also referred to as a media gateway (MGW) herein) may be used as part of the cross-domain system 120 to handle media during cross-domain communications. This media handling may include performing conversions between media types and various protocols that may be used by the servers 106 and 110. Although shown as a separate component from the bridge server 114, it is understood that the media server 118 may be part of the bridge server 114 in some embodiments. If separate from the bridge server 114, the media server 118 may be coupled to the bridge server 114, or the bridge server 114 may simply be aware of the media server 118 and pass contact information (e.g., address and port information) of the media server 118 to the domains 102 and/or 104 when setting up a communication session.


The bridge server 114 allows a first user having an account with the bridge server 114 to receive communication requests on both clients 108 and 112 from a second user's client (not shown), and to participate in communications sessions using either client 108 or client 112, regardless of which server 106 or 110 the second user is using. For example, if the second user attempts to contact the first user via the domain 102, the first user may receive a communication request on both clients 108 and 112 (if both clients are logged into their respective servers 106 and 110), on only one of the clients 108 or 112 (if the other client is not currently logged in), or on neither client 108 or 112 (if neither of the clients are logged in). If the first user answers the communication request via client 112, the bridge server 114 allows the first user and the second user to communicate, even though the first user is using client 112 in the domain 104 and the second user is using the domain 102. If the first user answers the communication request via client 108, the bridge server 114 may not be needed following establishment of the communication session as the two users are in the same domain. Various embodiments of such communication sessions are illustrated in detail below.


To enable cross-domain communications using a single user identifier, the servers 106 and 110 should support both multiple registration and forking. Multiple registration enables multiple devices to log into a single server using identical authentication information. For example, the user identifier johndoe@company.com may be simultaneously registered multiple times on both the server 106 and the server 110. Multiple registration is needed because it enables the bridge server 114 to log in as a client to the servers 106 and 110 without disrupting identical simultaneous logins from the clients 108 and 112. Forking enables an incoming communication request to be routed to multiple potential destinations (e.g., to all destinations corresponding to a registered user identifier) and then a communication session can be established based on the destination (or destinations) that responds affirmatively.


It is understood that the server 106 and the server 110 may continue to operate normally even during cross-domain communications. More specifically, because the cross-domain system 120 is able to register as a client with the servers 106 and 110 using the appropriate protocols and signaling sequences, the servers themselves do not need to be changed to accommodate cross-domain communication sessions. This enables the cross-domain system 120 to be inserted between incompatible domains (e.g., the domains 102 and 104) and then configured as needed to communicate with the servers 106 and 110 to support cross-domain communications.


Referring to FIG. 2, there is illustrated one embodiment of various entries and data that may be contained within the cross-domain database 116. The cross-domain database 116 may contain a user table 202. The user table 202 may store particular information related to a user associated with the bridge server 114, such as a username 204 and one or more credentials 206 for various communication platforms. In the present example, user table 202 includes a username 204 listed in the user table 202 as “UR1=johndoe@company.com,” Lync credentials, generic UCC credentials (e.g., credentials for another type of UCC platform), and PBX credentials for a traditional PBX system. The user may have the same username 204 across all platforms. So, in the present example, the user has the username “johndoe@company.com” associated with each of the Lync, Generic UCC, and PBX platforms. The credentials 206 for each of the platforms may be associated with a system table 208. In some embodiments, each credential may be associated with its own system table 208, while in other embodiments a single system table 208 may be used for all credentials of a user.


The system table 208 includes a plurality of information 210 particular to the associated communications platform. In the present example, such plurality of information 210 includes an IP address used to connect with the communications platform server (e.g., the server 106 or the server 110 of FIG. 1), a port number of the communications platform server, and various functionality identifiers. The identifiers may be used to indicate whether the communications platform supports particular types of UCC communications, such as presence, IM, audio, video, screen sharing, file transfer, whiteboard, and conferencing. It is understood that the functions illustrated in the system table 208 are for purposes of example only and many different functionalities that are not shown may be included.


The system table 208 may also include one or more variant entries 212. The variant entry 212 may be used to identify a particular variant of the communications platform, and therefore at least a portion of the plurality of information 210 that is associated with the credentials. For example, the variant entry 212 may identify whether the communications platform is running a particular release (e.g., Lync 2010 or Lync 2013), as well as various types of application packages (e.g., Skype for Business or Office 365). The variant entry 212 may be used to select an appropriate set of functions and also an appropriate set of protocols and signaling message sequences for use by the bridge server 114 when communicating with a particular server 106 or 110.


Referring to FIG. 3, there is illustrated one embodiment of an environment 300 that provides a more detailed view of the environment 100 of FIG. 1. The environment 300 includes a bridge server 302a that may be similar or identical to the bridge server 114 of FIG. 1. For purposes of illustration, the bridge server 302a may have an associated bridge ID (BID) that can be used to identify the bridge server 302a (e.g., as BID1) when multiple bridge servers 302a, 302b, . . . , 302n are present. Similarly, a media gateway (MGW) 304a, which may be similar or identical to the media server 118 of FIG. 1, may be one of multiple available media gateways 304a, 304b, . . . , 304m. The use of multiple bridge servers and media gateways enables the cross-domain system 120 of FIG. 1 to scale as needed depending on the needs of the domains 102 and 104.


In the present example, the environment 300 includes a Lync server 306 representing the server 106 of FIG. 1, a generic UCC server 308 (e.g., a server representing a non-Lync UCC platform that is incompatible with Lync) representing the server 110 of FIG. 1, and PBX system 310. However, in other embodiments, the generic UCC server 308 may be a Lync platform or another non-Lync platform that is compatible with Lync, wherein the bridge server 302a would still perform the same operations as described herein. Accordingly, it is understood that two domains may include compatible communications platforms of various types, and the bridge server 302a may operate in the same manner as described herein. The user johndoe@company.com is simultaneously registered with the Lync server 306 using a Lync client 312 (e.g., the client 108 of FIG. 1), with the UCC server 308 using a UCC client 314 (e.g., the client 112 of FIG. 1), and with the PBX 310 using a PBX client 316.


In addition, the bridge server 302a (that may be referred to hereinafter as BID1) is registered with the Lync server 306, the UCC server 308, and the PBX 310 as johndoe@company.com. This means that the Lync server 306, the UCC server 308, and the PBX 310 each have two simultaneous registrations for johndoe@company.com, one from the user and one from the bridge server 302a. Although not shown, it is understood that johndoe@company.com may also be logged into one or more of the Lync server 306, the generic UCC server 308, and the PBX 310 with additional devices, in which case additional registrations would be present. In the following embodiments, the REGISTER messages of FIG. 3 are not shown, but it is understood that the registrations of FIG. 3 have been performed before the various messages illustrated with respect to a particular embodiment are sent. In addition, the user associated with johndoe@company.com may be referred to as the “bridge server user” in various embodiments. It is understood that this refers to the fact that the bridge server 302a has this user's information stored in the database 116 and uses the information to support cross-domain communications for the user.


Referring to FIG. 4, there is illustrated a diagrammatic view of one embodiment of a communication session 400 on the bridge server 302a of FIG. 3. The session 400 includes a plurality of legs 402 that are labeled Leg 1-Leg n. A leg 402 is a protocol element or object that is used by the bridge server 302a as a logical, semantic, processing entity to handle communications with one of a number of UCC platforms (e.g., the Lync server 306, the generic UCC server 308, and the PBX 310 of FIG. 3). Generally, each platform with which the bridge server 302a is communicating will have its own leg 402. A leg 402 is configured by the bridge server 302a to send and receive messages using the appropriate protocol or protocols for the corresponding platform, such as SIP, HTTP, H.323, MGCP, and/or XMPP. By passing a message received via one leg 402 to another leg 402 within the bridge server 302a, the message may be converted from one domain's communication format to another domain's communication format. Accordingly, the legs 402 are utilized by the bridge server 302a to execute communications between disparate communications platforms as each leg is configured for its particular domain's communication format.


For purposes of example, legs 402 may recognize various message types, such as REGISTER, INVITE, CANCEL, OK, BYE, and MESSAGE. It is understood that these message types are not intended to be protocol specific terms, but are used in the present disclosure to indicate the purpose of the message being sent or received. For example, an INVITE message is not necessarily a SIP INVITE (although it may be if SIP is the protocol being used for a particular leg 402), but is instead intended to be an initiation message for an IM, a voice or video call, a file transfer, a screen sharing or conference call request, whiteboard functionality, mid-call features, and/or any other features. Similarly, an OK message is not necessarily a SIP OK (although it may be if SIP is the protocol being used for a particular leg 402), but is instead intended to be an acceptance message for a previously received INVITE. A CANCEL message cancels an INVITE previously sent. A BYE message terminates a current communication session. A MESSAGE message handles instant message (IM) transactions. A REGISTER message registers or unregisters (e.g., logs in or logs out) the sender with a platform using a given user identifier (e.g., johndoe@company.com).


Referring now to FIG. 5A, there is illustrated a diagrammatic view of an environment 500 that shows one embodiment of the environment 300 with a communication session between a third-party Lync client 502 and the Lync client 512 corresponding to johndoe@company.com. As described with respect to FIG. 3, the user identifier johndoe@company.com is simultaneously registered by multiple clients and by the bridge server 504. In the present example, the bridge server 504 is registered as johndoe@company.com with a Lync server 506, a generic UCC server 508, and a PBX system 510. In addition, the bridge server user has registered johndoe@company.com with a Lync client 512 registered with the Lync server 506, a UCC client 514 registered with the UCC server 508, and a PBX client 516 registered with the PBX 510.


With additional reference to FIG. 5B and continued reference to FIG. 5A, there is illustrated a sequence diagram 501 of one embodiment of a message sequence that may be used to establish a communication session between the third-party Lync client 502 and the Lync client 512. In step 518, the third-party Lync client 502 initiates a communication session with the bridge server user by sending an INVITE from the third-party Lync client 502 to the Lync server 506. In step 520, an INVITE is then sent from the Lync server 506 to the Lync client 512. In step 522, an INVITE is sent from the Lync server 506 to the bridge server 504. The bridge server 504 then sends an INVITE to the PBX 510 in step 524, which causes the PBX 510 to send an INVITE to the PBX client 516 in step 526. Although not shown, it is understood that the bridge server 504 (in each communication of which a bridge server is a part in this embodiment and/or other embodiments) may perform the conversions or other translations as described with respect to FIG. 4. Another INVITE is sent from the bridge server 504 to the generic UCC server 508 in step 528, which causes the generic UCC server 508 to send an INVITE to the generic UCC client 514 in step 530.


At this point, an INVITE has been sent to each of the bridge server user's clients (Lync, generic UCC, and PBX), allowing the bridge server user to answer the communication using any of these clients. In the present example, the bridge server user answers via the Lync client 512. This results in the sending of an OK message from the Lync client 512 to the Lync server 506 in step 532. The Lync server 506 then sends an OK to the third-party Lync client 502 in step 534. A CANCEL is sent from the Lync server 506 to the bridge server 504 in step 536. The bridge server 504 then sends a CANCEL to the PBX 510 in step 538, which then sends a CANCEL to the PBX client in step 540. The bridge server 504 also sends a CANCEL to the generic UCC server 508 in step 542, which then sends a CANCEL to the generic UCC client 514 in step 544. As the communication session has been established between the third-party Lync client 502 and the bridge server user's Lync client 512 through the Lync server 506, the bridge server 504 is not needed for the remainder of the communication session.


A media flow 546 is therefore established between the third-party Lync client 502 and the Lync client 512. To end the communication session, a BYE is sent from the third-party Lync client 502 to the Lync server 506 in step 548, which then sends a BYE to the Lync client 512 in step 550. It is understood that the BYE may originate from either side of the communication session.


It is understood with respect to FIGS. 5A, 5B, and other embodiments herein that contain similar steps (e.g., FIGS. 6A, 6B, 7A, 7B, 8A, 8B, 9A, 9B, 10A, 10B, 11A, and 11B), that some steps need not be performed in the exact order shown. For example, while the sequence of OK steps must generally occur as shown due to the natural propagation of the OK from the accepting client to the client initiating the INVITE, other messages may occur in different orders. For example, the INVITE of step 528 may occur before or simultaneously with the INVITE of step 524. Similarly, the CANCEL of step 542 may occur before or simultaneously with the CANCEL of step 538. In another example, the CANCEL of step 536 may occur before or simultaneously with the OK of step 534. Furthermore, it is possible for a CANCEL to be sent before the corresponding INVITE had reached its destination. Accordingly, it is understood that while some steps must logically occur in a certain order, other steps need not occur in the exact order shown in a particular embodiment.


Referring now to FIGS. 5C and 5D, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 5A and 5B on the bridge server 504. In FIG. 5C, a Lync leg 552 of the bridge server 504 receives the INVITE of step 522. The INVITE of step 528 is sent out over a generic UCC leg 554 and the INVITE of step 524 is sent out over a PBX leg 556. In FIG. 5D, after the bridge server user has answered using the Lync client 512, the CANCEL of step 536 is received via the Lync leg 552. The CANCEL of step 538 is then sent out over the PBX leg 556 and the CANCEL of step 542 is sent out over the generic UCC leg 554. The Lync leg 552, the generic UCC leg 554, and the PBX leg 556 are then destroyed because they are not needed for the communication session that has been established between the Lync client 512 and the third-party Lync client 502 via the Lync server 506.


A similar process as that illustrated in FIGS. 5A-5D would occur for other scenarios where the bridge server 504 is not needed to create the signaling and media paths, such as when a third-party generic UCC client attempts to contact the bridge server user and the bridge server user answers using the generic UCC client 514, or when a third-party PBX client attempts to contact the bridge server user and the bridge server user answers using the PBX client 516. In such cases, the communication session exists within a single domain and does not need the cross-domain support of the bridge server 504. Accordingly, while the bridge server 504 may be active prior to establishment of the communication session, such as by passing INVITE messages to other domains, its role generally ends once a communication session is established within a single domain. It will be understood that any type of communications platform may be used, and that Lync and PBX platforms are merely used for illustrative purposes.


Referring now to FIG. 6A, there is illustrated a diagrammatic view of an environment 600 that shows one embodiment of the environment 300 with a communication session between a third-party Lync client 602 and a generic UCC client 614 corresponding to johndoe@company.com. As described with respect to FIG. 3, the user identifier johndoe@company.com is simultaneously registered by multiple clients and by the bridge server 604. In the present example, the bridge server 604 is registered as johndoe@company.com with a Lync server 606, a generic UCC server 608, and a PBX system 610. In addition, the bridge server user has registered johndoe@company.com with a Lync client 612 registered with the Lync server 606, a UCC client 614 registered with the UCC server 608, and a PBX client 616 registered with the PBX 610.


With additional reference to FIG. 6B and continued reference to FIG. 6A, there is illustrated a sequence diagram 601 of one embodiment of a message sequence that may be used to establish a communication session between the third-party Lync client 602 and the generic UCC client 614. In step 618, the third-party Lync client 602 initiates a communication session with the bridge server user by sending an INVITE from the third-party Lync client 602 to the Lync server 606. An INVITE is then sent from the Lync server 606 to the Lync client 612 in step 620. Another INVITE is sent from the Lync server 606 to the bridge server 604 in step 622. The bridge server 604 then sends an INVITE to the PBX 610 in step 624, which causes the PBX 610 to send an INVITE to the PBX client 616 in step 626. Another INVITE is sent from the bridge server 604 to the generic UCC server 608 in step 628, which causes the generic UCC server 608 to send an INVITE to the generic UCC client 614 in step 630.


At this point, an INVITE has been sent to each of the bridge server user's clients (Lync, generic UCC, and PBX), allowing the bridge server user to answer the communication using any of these clients. In the present example, the bridge server user answers via the generic UCC client 614. This causes an OK message to be sent from the generic UCC client 614 to the generic UCC server 608 in step 632. The generic UCC server 608 then sends an OK to the bridge server 604 in step 634. The bridge server 604 then sends an OK to the Lync server 606 in step 636. The Lync server 606 then sends an OK to the third-party Lync client 602 in step 638. Since the communication has been accepted between the third-party Lync client 602 and the bridge server user's generic UCC client 614, a CANCEL is sent from the bridge server 604 to the PBX 610 in step 640, which causes the PBX 610 to send a CANCEL to the PBX client 616 in step 642. A CANCEL is also sent from the Lync server 606 to the Lync client 612 in step 644.


A media flow 646 is therefore established between the third-party Lync client 602 and the generic UCC client 614, with the media gateway 605 acting to bridge the media path 646, as shown in FIG. 6A. To end the communication session, a BYE is sent from the generic UCC client 614 to the generic UCC server 608 in step 648, which then sends a BYE to the bridge server 604 in step 650. The bridge server 604 then sends a BYE to the Lync server 606 in step 652, which then sends a BYE to the third-party Lync client 602 in step 654. It is understood that the BYE may originate from either side of the communication session.


Referring now to FIGS. 6C-6E, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 6A and 6B on the bridge server 604. In FIG. 6C, a Lync leg 656 receives the INVITE of step 622. The INVITE of step 628 is sent out over a generic UCC leg 658 and the INVITE of step 624 is sent out over a PBX leg 660, to reach their respective server, as described herein. In FIG. 6D, after the bridge server user has answered using the generic UCC client 614, the OK of step 634 is received via the generic UCC leg 658. The CANCEL of step 540 is then sent out over the PBX leg 640 and the OK of step 636 is sent out over the Lync leg 656. This results in a signaling path being formed using the Lync leg 656 and the generic UCC leg 658, while the PBX leg 660 can be destroyed as shown in FIG. 6E. It will be understood that any type of communications platform may be used, and that Lync and PBX platforms are merely used for illustrative purposes.


Referring to FIG. 6F, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 6A and 6B on the media server 604. The media server 604 establishes a Lync leg 670 with the Lync server 606 and a generic UCC leg 672 with the generic UCC server 608. The media server 604 then bridges the two legs 670 and 672. The bridging process may include converting between different media formats and/or protocols in order to make the media received by one of the legs 670 and 672 compatible with the media requirements of the domain coupled to the other of the legs.


It will be understood that, in some embodiments, the generic UCC server 608 may be a communications platform that is compatible with the Lync server 606 or the Lync server 606 may be a different communications platform that is compatible with the generic UCC server 608. In such a scenario, the bridge server 604 may perform the same operations as in the embodiments where the generic UCC server 608 is incompatible with the Lync server. The bridge server 604 may still, using the information contained in the cross-domain database 116, translate the information received from the Lync server 606 and the UCC server 608 into the required protocols, even if no translation is needed. It will be appreciated that this treatment of compatible communications platforms can be applied in any of the embodiments described herein. In other embodiments, the bridge server 604 may perform a check to determine whether a communications platform, such as the Lync server 606, is compatible with another communications platform, such as the generic UCC server 608, and then skip any translations. It will be appreciated that this treatment of compatible communications platforms can be applied in any of the embodiments described herein.


Referring now to FIG. 7A, there is illustrated a diagrammatic view of an environment 700 that shows one embodiment of the environment 300 with a communication session between a third-party Lync client 702 and a PBX client 716 corresponding to johndoe@company.com. As described with respect to FIG. 3, the user identifier johndoe@company.com is simultaneously registered by multiple clients and by the bridge server 704. In the present example, the bridge server 704 is registered as johndoe@company.com with a Lync server 706, a generic UCC server 708, and a PBX system 710. In addition, the bridge server user has registered johndoe@company.com with a Lync client 712 registered with the Lync server 706, a UCC client 714 registered with the UCC server 708, and a PBX client 716 registered with the PBX 710.


With additional reference to FIG. 7B and continued reference to FIG. 7A, there is illustrated a sequence diagram 701 of one embodiment of a message sequence that may be used to establish a communication session between the third-party Lync client 702 and the PBX client 716. In step 718, the third-party Lync client 702 initiates a communication session with the bridge server user by sending an INVITE from the third-party Lync client 702 to the Lync server 706. An INVITE is then sent from the Lync server 706 to the Lync client 712 in step 720. Another INVITE is sent from the Lync server 706 to the bridge server 704 in step 722. The bridge server 704 then sends an INVITE to the PBX 710 in step 724, which causes the PBX 710 to send an INVITE to the PBX client 716 in step 726. Another INVITE is sent from the bridge server 704 to the generic UCC server 708 in step 728, which causes the generic UCC server 708 to send an INVITE to the generic UCC client 714 in step 730.


At this point, an INVITE has been sent to each of the bridge server user's clients (Lync, generic UCC, and PBX), allowing the bridge server user to answer the communication using any of these clients. In the present example, the bridge server user answers via the PBX client 716. This causes an OK to be sent from the PBX client 716 to the PBX system 710 in step 732. The PBX system 710 then sends an OK to the bridge server 704 in step 734. The bridge server 704 then sends an OK to the Lync server 706 in step 736. The bridge server 704 also sends a CANCEL to the generic UCC server 708 in step 738, which sends a CANCEL to the generic UCC client 714 in step 740. The Lync server 706 sends a CANCEL to the Lync client 712 in step 742. The Lync server 706 sends an OK to the third-party Lync client 702 in step 744.


A media flow 746 is therefore established between the third-party Lync client 702 and the PBX client 716, with the media gateway 705 acting to bridge the media path 746, as shown in FIG. 7A. To end the communication session, a BYE is sent from the third-party Lync client 702 to the Lync server 706 in step 748, which then sends a BYE to the bridge server 704 in step 750. The bridge server 704 then sends a BYE to the PBX system 710 in step 752, which then sends a BYE to the PBX client 716 in step 754. It will be understood that the BYE may originate from either side of the communication session.


Referring now to FIGS. 7C-7E, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 7A and 7B on the bridge server 704. In FIG. 7C, a Lync leg 756 receives the INVITE of step 722. The INVITE of step 728 is sent out over a generic UCC leg 758 and the INVITE of step 724 is sent out over a PBX leg 760, to reach their respective server, as described herein. In FIG. 7D, after the bridge server user has answered using the PBX client 716, the OK of step 734 is received via the PBX leg 760. The CANCEL of step 738 is then sent out over the generic UCC leg 758 and the OK of step 736 is sent out over the Lync leg 756. This results in a signaling path being formed between the Lync leg 756 and the PBX leg 760, while the generic UCC leg 758 can be destroyed as shown in FIG. 7E. It will be understood that any type of communications platform may be used, and that Lync and PBX platforms are merely used for illustrative purposes.


Referring to FIG. 7F, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 7A and 7B on the media server 704. The media server 704 establishes a Lync leg 770 with the Lync server 706 and a PBX leg 772 with the PBX 710. The media server 704 then bridges the two legs 770 and 772. The bridging process may include converting between different media formats and/or protocols in order to make the media received from one of the legs 770 and 772 compatible with the media requirements of the other of the legs.


Referring now to FIG. 8A, there is illustrated a diagrammatic view of an environment 800 that shows one embodiment of the environment 300 with a communication session between a third-party PBX client 802 and a Lync client 812 corresponding to johndoe@company.com. As described with respect to FIG. 3, the user identifier johndoe@company.com is simultaneously registered by multiple clients and by the bridge server 804. In the present example, the bridge server 804 is registered as johndoe@company.com with a Lync server 806, a generic UCC server 808, and a PBX system 810. In addition, the bridge server user has registered johndoe@company.com with a Lync client 812 registered with the Lync server 806, a UCC client 814 registered with the UCC server 808, and a PBX client 816 registered with the PBX 810.


With additional reference to FIG. 8B and continued reference to FIG. 8A, there is illustrated a sequence diagram 801 of one embodiment of a message sequence that may be used to establish a communication session between the third-party PBX client 802 and the Lync client 812. In step 818, the third-party PBX client 802 initiates a communication session with the bridge server user by sending an INVITE from the PBX client 802 to the PBX 810. An INVITE is then sent from the PBX 810 to the PBX client 816 in step 820. Another INVITE is sent from the PBX 810 to the bridge server 804 in step 822. The bridge server 804 then sends an INVITE to the Lync server 806 in step 824, which causes the Lync server 806 to send an INVITE to the Lync client 812 in step 826. Another INVITE is sent from the bridge server 804 to the generic UCC server 808 in step 828, which causes the generic UCC server 808 to send an INVITE to the generic UCC client 814 in step 830.


At this point, an INVITE has been sent to each of the bridge server user's clients (Lync, generic UCC, and PBX), allowing the bridge server user to answer the communication using any of these clients. In the present example, the bridge server user answers via the Lync client 812. This causes an OK to be sent from the Lync client 812 to the Lync server 806 in step 832. The Lync server 806 then sends an OK to the bridge server 804 in step 834. The bridge server 804 then sends an OK to the PBX 810 in step 836. The bridge server 804 also sends a CANCEL to the generic UCC server 808 in step 838, which sends a CANCEL to the generic UCC client 814 in step 840. The PBX 810 sends an OK to the third-party PBX client 802 in step 842 and the PBX 810 also sends a CANCEL to the PBX client 816 in step 844.


A media flow 846 is therefore established between the third-party PBX client 802 and the Lync client 812, with the media gateway 805 acting to bridge the media path 846, as shown in FIG. 8A. To end the communication session, a BYE is sent from the third-party PBX client 802 to the PBX 810 in step 848, which then sends a BYE to the bridge server 804 in step 850. The bridge server 804 then sends a BYE to the Lync server 806 in step 852, which then sends a BYE to the Lync client 812 in step 854. It will be understood that the BYE may originate from either side of the communication session.


Referring now to FIGS. 8C-8E, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 8A and 8B on the bridge server 804. In FIG. 8C, a PBX leg 860 receives the INVITE of step 822. The INVITE of step 828 is sent out over a generic UCC leg 858 and the INVITE of step 824 is sent out over a Lync leg 856, to reach their respective server, as described herein. In FIG. 8D, after the bridge server user has answered using the Lync client 812, the OK of step 834 is received via the Lync leg 856. The CANCEL of step 838 is then sent out over the generic UCC leg 858 and the OK of step 836 is sent out over the PBX leg 860. This results in a signaling path being formed between the Lync leg 856 and the PBX leg 860, while the generic UCC leg 858 can be destroyed as shown in FIG. 8E. It will be understood that any type of communications platform may be used, and that Lync and PBX platforms are merely used for illustrative purposes.


Referring to FIG. 8F, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 8A and 8B on the media server 804. The media server 804 establishes a Lync leg 870 with the Lync server 806 and a PBX leg 872 with the PBX 810. The media server 804 then bridges the two legs 870 and 872. The bridging process may include converting between different media formats and/or protocols in order to make the media received from one of the legs 870 and 872 compatible with the media requirements of the other of the legs.


Referring now to FIG. 9A, there is illustrated a diagrammatic view of an environment 900 that shows one embodiment of the environment 300 with a communication session between a third-party PBX client 902 and a generic UCC client 914 corresponding to johndoe@company.com. As described with respect to FIG. 3, the user identifier johndoe@company.com is simultaneously registered by multiple clients and by the bridge server 904. In the present example, the bridge server 904 is registered as johndoe@company.com with a Lync server 906, a generic UCC server 908, and a PBX system 910. In addition, the bridge server user has registered johndoe@company.com with a Lync client 912 registered with the Lync server 906, a UCC client 914 registered with the UCC server 908, and a PBX client 916 registered with the PBX 910.


With additional reference to FIG. 9B and continued reference to FIG. 9A, there is illustrated a sequence diagram 901 of one embodiment of a message sequence that may be used to establish a communication session between the third-party PBX client 902 and the generic UCC client 914. In step 918, the third-party PBX client 902 initiates a communication session with the bridge server user by sending an INVITE from the PBX client 902 to the PBX 910. An INVITE is then sent from the PBX 910 to the PBX client 916 in step 920. Another INVITE is sent from the PBX 910 to the bridge server 904 in step 922. The bridge server 904 then sends an INVITE to the Lync server 906 in step 924, which causes the Lync server 906 to send an INVITE to the Lync client 912 in step 926. Another INVITE is sent from the bridge server 904 to the generic UCC server 908 in step 928, which causes the generic UCC server 908 to send an INVITE to the generic UCC client 914 in step 930.


At this point, an INVITE has been sent to each of the bridge server user's clients (Lync, generic UCC, and PBX), allowing the bridge server user to answer the communication using any of these clients. In the present example, the bridge server user answers via the generic UCC client 914. This causes an OK to be sent from the generic UCC client 914 to the generic UCC server 908 in step 932. The generic UCC server 908 then sends an OK to the bridge server 904 in step 934. The bridge server 904 sends a CANCEL to the Lync server 906 in step 936, which sends a CANCEL to the Lync client 812 in step 938. The bridge server 904 also sends an OK to the PBX 910 in step 940. The PBX 910 sends a CANCEL to the PBX client 916 in step 942 and also sends an OK to the third-party PBX client 902 in step 944.


A media flow 946 is therefore established between the third-party PBX client 902 and the generic UCC client 914, with the media gateway 905 acting to bridge the media path 946, as shown in FIG. 9A. To end the communication session, a BYE is sent from the generic UCC client 914 to the generic UCC server 908 in step 948, which then sends a BYE to the bridge server 904 in step 950. The bridge server 904 then sends a BYE to the PBX 910 in step 952, which then sends a BYE to the third-party PBX client 902 in step 954. It will be understood that the BYE may originate from either side of the communication session.


Referring now to FIGS. 9C-9E, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 9A and 9B on the bridge server 904. In FIG. 9C, a PBX leg 960 receives the INVITE of step 922. The INVITE of step 928 is sent out over a generic UCC leg 958 and the INVITE of step 924 is sent out over a Lync leg 956, to reach their respective server, as described herein. In FIG. 9D, after the bridge server user has answered using the generic UCC client 914, the OK of step 934 is received via the generic UCC leg 958. The CANCEL of step 936 is then sent out over the Lync leg 956 and the OK of step 940 is sent out over the PBX leg 960. This results in a signaling path being formed between the generic UCC leg 958 and the PBX leg 960, while the Lync leg 956 can be destroyed as shown in FIG. 9E. It will be understood that any type of communications platform may be used, and that Lync and PBX platforms are merely used for illustrative purposes.


Referring to FIG. 9F, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 9A and 9B on the media server 904. The media server 904 establishes a generic UCC leg 970 with the generic UCC server 908 and a PBX leg 972 with the PBX 910. The media server 904 then bridges the two legs 970 and 972. The bridging process may include converting between different media formats and/or protocols in order to make the media received from one of the legs 970 and 972 compatible with the media requirements of the other of the legs.


Referring now to FIG. 10A, there is illustrated a diagrammatic view of an environment 1000 that shows one embodiment of the environment 300 with a communication session between a third-party generic UCC client 1002 and a Lync client 1012 corresponding to johndoe@company.com. As described with respect to FIG. 3, the user identifier johndoe@company.com is simultaneously registered by multiple clients and by the bridge server 1004. In the present example, the bridge server 1004 is registered as johndoe@company.com with a Lync server 1006, a generic UCC server 1008, and a PBX system 1010. In addition, the bridge server user has registered johndoe@company.com with the Lync client 1012 registered with the Lync server 1006, a UCC client 1014 registered with the UCC server 1008, and a PBX client 1016 registered with the PBX 1010.


With additional reference to FIG. 10B and continued reference to FIG. 10A, there is illustrated a sequence diagram 1001 of one embodiment of a message sequence that may be used to establish a communication session between the third-party generic UCC client 1002 and the Lync client 1012. In step 1018, the third-party generic UCC client 1002 initiates a communication session with the bridge server user by sending an INVITE from the third-party generic UCC client 1002 to the generic UCC server 1008. An INVITE is then sent from the generic UCC server 1008 to the generic UCC client 1014 in step 1020. Another INVITE is sent from the generic UCC server 1008 to the bridge server 1004 in step 1022. The bridge server 1004 then sends an INVITE to the Lync server 1006 in step 1024, which causes the Lync server 1006 to send an INVITE to the Lync client 1012 in step 1026. Another INVITE is sent from the bridge server 1004 to the PBX 1010 in step 1028, which causes the PBX 1010 to send an INVITE to the PBX client 1016 in step 1030.


At this point, an INVITE has been sent to each of the bridge server user's clients (Lync, generic UCC, and PBX), allowing the bridge server user to answer the communication using any of these clients. In the present example, the bridge server user answers via the Lync client 1012. This causes an OK to be sent from the Lync client 1012 to the Lync server 1006 in step 1032. The Lync server 1006 then sends an OK to the bridge server 1004 in step 1034. The bridge server 1004 sends a CANCEL to the PBX 1010 in step 1036, which sends a CANCEL to the PBX client 1016 in step 1038. The bridge server 1004 also sends an OK to the generic UCC server 1008 in step 1040. The generic UCC server 1008 sends a CANCEL to the generic UCC client 1014 in step 1042 and also sends an OK to the third-party generic UCC client 1002 in step 1044.


A media flow 1046 is therefore established between the third-party generic UCC client 1002 and the Lync client 1012, with the media gateway 1005 acting to bridge the media path 1046, as shown in FIG. 10A. To end the communication session, a BYE is sent from the third-party generic UCC client 1002 to the generic UCC server 1008 in step 1048, which then sends a BYE to the bridge server 1004 in step 1050. The bridge server 1004 then sends a BYE to the Lync server 1006 in step 1052, which then sends a BYE to the Lync client 1012 in step 1054. It will be understood that the BYE may originate from either side of the communication session.


Referring now to FIGS. 10C-10E, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 10A and 10B on the bridge server 1004. In FIG. 10C, a generic UCC leg 1058 receives the INVITE of step 1022. The INVITE of step 1024 is sent out over a Lync leg 1056 and the INVITE of step 1028 is sent out over a PBX leg 1060, to reach their respective server, as described herein. In FIG. 10D, after the bridge server user has answered using the Lync client 1012, the OK of step 1034 is received via the Lync leg 1056. The CANCEL of step 1036 is then sent out over the PBX leg 1060 and the OK of step 1040 is sent out over the generic UCC leg 1058. This results in a signaling path being formed between the Lync leg 1056 and the generic UCC leg 1058, while the PBX leg 1060 can be destroyed as shown in FIG. 10E. It will be understood that any type of communications platform may be used, and that Lync and PBX platforms are merely used for illustrative purposes.


Referring to FIG. 10F, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 10A and 10B on the media server 1004. The media server 1004 establishes a Lync leg 1070 with the Lync server 1006 and a generic UCC leg 1072 with the generic UCC server 1008. The media server 1004 then bridges the two legs 1070 and 1072. The bridging process may include converting between different media formats and/or protocols in order to make the media received from one of the legs 1070 and 1072 compatible with the media requirements of the other of the legs.


Referring now to FIG. 11A, there is illustrated a diagrammatic view of an environment 1100 that shows one embodiment of the environment 300 with a communication session between a third-party generic UCC client 1102 and a PBX client 1116 corresponding to johndoe@company.com. As described with respect to FIG. 3, the user identifier johndoe@company.com is simultaneously registered by multiple clients and by the bridge server 1104. In the present example, the bridge server 1104 is registered as johndoe@company.com with a Lync server 1106, a generic UCC server 1108, and a PBX system 1110. In addition, the bridge server user has registered johndoe@company.com with a Lync client 1112 registered with the Lync server 1106, a UCC client 1114 registered with the UCC server 1108, and the PBX client 1116 registered with the PBX 1110.


With additional reference to FIG. 11B and continued reference to FIG. 11A, there is illustrated a sequence diagram 1101 of one embodiment of a message sequence that may be used to establish a communication session between the third-party generic UCC client 1102 and the PBX client 1116. In step 1118, the third-party generic UCC client 1102 initiates a communication session with the bridge server user by sending an INVITE from the third-party generic UCC client 1102 to the generic UCC server 1108. An INVITE is then sent from the generic UCC server 1108 to the generic UCC client 1114 in step 1120. Another INVITE is sent from the generic UCC server 1108 to the bridge server 1104 in step 1122. The bridge server 1104 then sends an INVITE to the Lync server 1106 in step 1124, which causes the Lync server 1106 to send an INVITE to the Lync client 1112 in step 1126. Another INVITE is sent from the bridge server 1104 to the PBX 1110 in step 1128, which causes the PBX 1110 to send an INVITE to the PBX client 1116 in step 1130.


At this point, an INVITE has been sent to each of the bridge server user's clients (Lync, generic UCC, and PBX), allowing the bridge server user to answer the communication using any of these clients. In the present example, the bridge server user answers via the PBX client 1116. This causes an OK to be sent from the PBX client 1116 to the PBX 1110 in step 1132. The PBX 1110 then sends an OK to the bridge server 1104 in step 1134. The bridge server 1104 sends a CANCEL to the Lync server 1106 in step 1136, which sends a CANCEL to the Lync client 1112 in step 1138. The bridge server 1104 also sends an OK to the generic UCC server 1108 in step 1140. The generic UCC server 1108 sends a CANCEL to the generic UCC client 1114 in step 1142 and also sends an OK to the third-party generic UCC client 1102 in step 1144.


A media flow 1146 is therefore established between the third-party generic UCC client 1102 and the PBX client 1116, with the media gateway 1105 acting to bridge the media path 1146, as shown in FIG. 11A. To end the communication session, a BYE is sent from the PBX client 1116 to the PBX 1110 in step 1148, which then sends a BYE to the bridge server 1104 in step 1150. The bridge server 1104 then sends a BYE to the generic UCC server 1108 in step 1152, which then sends a BYE to the third-party generic UCC client 1102 in step 1154. It will be understood that the BYE may originate from either side of the call.


Referring now to FIGS. 11C-11E, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 11A and 11B on the bridge server 1104. In FIG. 11C, a generic UCC leg 1158 receives the INVITE of step 1122. The INVITE of step 1124 is sent out over a Lync leg 1156 and the INVITE of step 1128 is sent out over a PBX leg 1160, to reach their respective server, as described herein. In FIG. 11D, after the bridge server user has answered using the PBX client 1116, the OK of step 1134 is received via the PBX leg 1160. The CANCEL of step 1136 is then sent out over the Lync leg 1156 and the OK of step 1140 is sent out over the generic UCC leg 1158. This results in a signaling path being formed between the PBX leg 1160 and the generic UCC leg 1158, while the Lync leg 1156 can be destroyed as shown in FIG. 11E. It will be understood that any type of communications platform may be used, and that Lync and PBX platforms are merely used for illustrative purposes.


Referring to FIG. 11F, there is illustrated a diagrammatic view of one embodiment of the communication session of FIGS. 11A and 11B on the media server 1104. The media server 1104 establishes a generic UCC leg 1172 with the generic UCC server 1108 and a PBX leg 1172 with the PBX 1110. The media server 1104 then bridges the two legs 1170 and 1172. The bridging process may include converting between different media formats and/or protocols in order to make the media received from one of the legs 1170 and 1172 compatible with the media requirements of the other of the legs.


Referring to FIGS. 12A and 12B, there is illustrated a diagrammatic view of one embodiment of an instant messaging communication session that may be supported by a bridge server, such as the bridge server 302a of FIG. 3, or a media server, such as the media server 304a of FIG. 3. A first leg 1202 receives a message 1204 and a second leg 1206 sends the message 1204 out. When a user who received the message 1204 responds to the message 1204 with a message 1208, the message 1208 is received by the second leg 1206 and then sent out over the first leg 1202.


Referring to FIG. 13, there is illustrated a diagrammatic view of one embodiment of messages used to terminate a communication session being supported by a bridge server, such as the bridge server 302a of FIG. 3. A first leg 1302 receives a BYE 1304 and a second leg 1306 then sends out the BYE 1304, resulting in both first and second legs 1302 and 1306 being torn down.


Referring to FIG. 14, there is illustrated a diagrammatic view of one embodiment of messages used to terminate a communication session being supported by a bridge server, such as the bridge server 302a of FIG. 3. A second leg 1406 receives a BYE 1404 and a first leg 1402 then sends out the BYE 1404, resulting in both first and second legs 1402 and 1406 being torn down.


Referring to FIG. 15, there is illustrated a flowchart of one embodiment of a method 1500 of conducting a communications session. The steps for conducting the communications session are specific to a single communications session for a single user. The method 1500 begins at step 1502 when a message is received by a leg on a bridge server, such as the bridge server 302a of FIG. 3. The method 1500 then moves to step 1504 where it is determined whether the message is an INVITE. If the message is an INVITE, at step 1506, call legs are created by assigning the leg from which the INVITE was received as the incoming leg and assigning the other legs as outgoing legs. The INVITE is then sent out over the outgoing legs. The method 1500 then returns to step 1502 to wait for another message to be received.


If the message is not an INVITE as determined at step 1504, the method 1500 moves to step 1508, where it is determined if the message is a CANCEL. If the message is a CANCEL, at step 1510, a CANCEL is sent out over any outgoing legs that are in an INVITE state, resulting in these legs being destroyed. The method 1500 then moves back to step 1502 to await another message to be received.


If the message is not a CANCEL as determined at step 1508, the method 1500 moves to step 1512, where it is determined whether the message is an OK. If the message is an OK, at step 1514, the OK is sent over the incoming leg to transition the incoming leg to an active state, while a CANCEL is sent out over any other legs that are in an INVITE state. This destroys those legs while the leg that is now in an active state participates in the communication session. The method 1500 then moves back to step 1502 to await another message.


If it is determined that the message is not an OK as determined at step 1512, the method 1500 moves to step 1516, where it is determined whether the message is a BYE. If the message is a BYE, the method 1500 moves to step 1518, where a BYE is sent on a leg that is in an active state, and then all legs are destroyed. The method 1500 then moves back to step 1502 to await another message.


If it is determined that the message is not a BYE as determined at step 1516, the method 1500 moves back to step 1502 to await another message, since a check has now been made for all message types (e.g., INVITE, CANCEL, OK, and BYE) and the message was found to contain none of these. It will be understood that the order in which each command is checked may be different, as the method 1500 is able to react to any message received at any time, and follows the proper procedure depending on what type of message is received. In addition, it is understood that additional message types may be checked.


Referring now to FIG. 16, there is illustrated a finite state machine diagram view of one embodiment of a bridge server 1600, that may be similar or identical the bridge server 302a of FIG. 3. Different states may be associated for each call leg. In the present example, there is an IDLE state 1602, an INVITED state 1604, and an ACTIVE state 1606. When in the IDLE state 1602, the receipt of an OK 1608, a BYE 1610, and a CANCEL 1612 for the call leg will result in the call leg remaining in the IDLE state 1602. The only way for the call leg to leave the IDLE state 1602 is for an INVITE 1614 to be received. If the INVITE 1614 is received, the call leg's state changes to the INVITED state 1604.


While in the INVITE state 1604, a CANCEL 1616 or a BYE 1618 will return the call leg's state to the IDLE state 1602. If an OK 1620 is received, the state changes from the INVITE stated 1604 to the ACTIVE state 1606. While in the ACTIVE state 1606, if an OK 1622 is received, the state remains in the ACTIVE state 1606. If a BYE 1624 or a CANCEL 1626 is received, the state changes from the ACTIVE state 1606 to the IDLE state 1602. If any INVITE messages are received while in the INVITED state 1604 or the ACTIVE state 1606, the state will remain unchanged.


It is understood that, in all the embodiments described herein, the INVITE, OK, CANCEL, and BYE messages sent over the legs of the communication session may be separate messages passed between each node in the communication session, or they may be single messages. For example, an INVITE sent from a client to a server may be one unique INVITE command, while the subsequent INVITE message sent from the server to the bridge server may be another unique message. However, a single INVITE sent from a client to a server may also be forwarded to the bridge server as the same message, rather than as a unique message.


Referring to FIG. 17, one embodiment of a device 1700 is illustrated. The device 1700 is one example of a portion or all of the server 108, the server 110, the client 108, the client 112, the bridge server 114, and/or the media server 118 of FIG. 1, as well as other clients and servers described in other embodiments, including FIG. 3. The system 1700 may include a controller (e.g., a processor/central processing unit (“CPU”)) 1702, a memory unit 1704, an input/output (“I/O”) device 1706, and a network interface 1708. The components 1702, 1704, 1706, and 1708 are interconnected by a data transport system (e.g., a bus) 1710. A power supply (PS) 1712 may provide power to components of the system 1700 via a power transport system 1714 (shown with data transport system 180, although the power and data transport systems may be separate).


It is understood that the system 1700 may be differently configured and that each of the listed components may actually represent several different components. For example, the CPU 1702 may actually represent a multi-processor or a distributed processing system; the memory unit 1704 may include different levels of cache memory, main memory, hard disks, and remote storage locations; the I/O device 1706 may include monitors, keyboards, and the like; and the network interface 1708 may include one or more network cards providing one or more wired and/or wireless connections to a network 1716. Therefore, a wide range of flexibility is anticipated in the configuration of the system 1700, which may range from a single physical platform configured primarily for a single user or autonomous operation to a distributed multi-user platform such as a cloud computing system.


The system 1700 may use any operating system (or multiple operating systems), including various versions of operating systems provided by Microsoft (such as WINDOWS), Apple (such as Mac OS X), UNIX, and LINUX, and may include operating systems specifically developed for handheld devices (e.g., iOS, Android, Blackberry, and/or Windows Phone), personal computers, servers, and other computing platforms depending on the use of the system 1700. The operating system, as well as other instructions (e.g., for telecommunications and/or other functions provided by the device 1700), may be stored in the memory unit 1704 and executed by the processor 1702. For example, if the system 1700 is the device 1700, the memory unit 1704 may include instructions for performing some or all of the steps, process, and methods described herein.


The network 1716 may be a single network or may represent multiple networks, including networks of different types, whether wireless or wireline. For example, the device 1700 may be coupled to external devices via a network that includes a cellular link coupled to a data packet network, or may be coupled via a data packet link such as a wide local area network (WLAN) coupled to a data packet network or a Public Switched Telephone Network (PSTN). Accordingly, many different network types and configurations may be used to couple the device 1700 with external devices.


While the preceding description shows and describes one or more embodiments, it will be understood by those skilled in the art that various changes in form and detail may be made therein without departing from the spirit and scope of the present disclosure. For example, various steps illustrated within a particular flow chart or sequence diagram may be combined or further divided. In addition, steps described in one flow chart or diagram may be incorporated into another flow chart or diagram. Furthermore, the described functionality may be provided by hardware and/or software, and may be distributed or combined into a single platform. Additionally, functionality described in a particular example may be achieved in a manner different than that illustrated, but is still encompassed within the present disclosure. Therefore, the claims should be interpreted in a broad manner, consistent with the present disclosure.

Claims
  • 1. A method for supporting a cross-domain communication session between communication platforms using a bridge server, the method comprising: registering, by a bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;receiving, by the bridge server, a request to establish a communication session with a user corresponding to the user identifier, the request being received from one of the communication platforms;creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as an incoming leg and any other of the communication legs are designated as outgoing legs;sending, by the bridge server, the request to establish the communication session over the outgoing legs;receiving, by the bridge server, a communication acceptance from one of the outgoing legs;sending, by the bridge server, a cancel message over any of the outgoing legs from which the communication acceptance was not received;sending, by the bridge server, the communication acceptance over the incoming leg; andbridging, by the bridge server, the incoming leg and the outgoing leg from which the communication acceptance was received to establish the communication session, wherein bridging the incoming leg and the outgoing leg to establish the communication session includes creating a bridged media path through which communications sent over the incoming leg and the outgoing leg by the communication platforms during the communication session are first received by the bridge server before transmitting the communications to the communication platforms, and wherein the bridge server is configured to convert information received over the bridged media path between different media formats if the media format used by the incoming leg is different than the media format used by one of the outgoing legs.
  • 2. The method of claim 1 further comprising: receiving, from one of the incoming leg and the outgoing leg from which the communication acceptance was received, a communication session termination request;sending the communication session termination request over the incoming leg or the outgoing leg from which the communication session termination request was not received; anddestroying all of the communication legs.
  • 3. The method of claim 1, wherein the bridge server is coupled to a media server that forms part of a cross-domain system with the bridge server, wherein the media server handles media legs for the communication session.
  • 4. The method of claim 3, wherein the cross-domain system includes a cross-domain database having a plurality of information specific to the communication platforms.
  • 5. The method of claim 4, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.
  • 6. The method of claim 5 further comprising managing the communication session by the bridge server, wherein the bridge server uses the plurality of information contained in the cross-domain database to enable communications between the communication platforms that are in incompatible domains and cannot communicate directly with one another.
  • 7. The method of claim 1 wherein the bridge server bridges the incoming leg and the outgoing leg both when the communication platforms corresponding to the incoming leg and outgoing leg are in incompatible domains and cannot communicate directly with one another and when the communication platforms corresponding to the incoming leg and outgoing leg are in compatible domains and can communicate directly with one another.
  • 8. The method of claim 1 further comprising: receiving, by the bridge server, a second request to establish a second communication session with the user corresponding to the user identifier, the second request being received from one of the communication platforms;creating, by the bridge server, a separate second communication leg for each of the communication platforms, wherein the second communication leg created for the communication platform from which the second request was received is designated as a second incoming leg and any other of the second communication legs are designated as second outgoing legs;sending, by the bridge server, the second request to establish the communication session over the second outgoing legs;receiving, by the bridge server, a cancel message from the second incoming leg;sending, by the bridge server, the cancel message over the second outgoing legs; anddestroying, by the bridge server, the second communication legs.
  • 9. A method for supporting a cross-domain communication session between communication platforms using a bridge server, the method comprising: registering, by a bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;receiving, by the bridge server, a request to establish a communication session with the user corresponding to the user identifier, the request being received from one of the communication platforms;creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as an incoming leg and any other of the communication legs are designated as outgoing legs;sending, by the bridge server, the request to establish the communication session over the outgoing legs;receiving, by the bridge server, a cancel message from the incoming leg;sending, by the bridge server, a cancel message over the outgoing legs; anddestroying, by the bridge server, all of the communication legs,wherein the bridge server is configured to: bridge the incoming leg and the outgoing leg to establish the communication session to create a bridged media path through which communications sent over the incoming leg and the outgoing leg by the communication platforms during the communication session are first received by the bridge server before transmitting the communications to the communication platforms, andconvert information received over the bridge media path between different media formats if the media format used by the incoming leg is different than the media format used by one of the outgoing legs.
  • 10. The method of claim 9, wherein the bridge server is coupled to a media server that forms part of a cross-domain system with the bridge server, wherein the media server handles media legs for any communication sessions managed by the bridge server.
  • 11. The method of claim 10, wherein the cross-domain system includes a cross-domain database having a plurality of information specific to the communication platforms.
  • 12. The method of claim 11, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.
  • 13. The method of claim 12 wherein the bridge server uses the plurality of information contained in the cross-domain database to enable communications between any of the communication platforms that are in incompatible domains and cannot communicate directly with one another.
  • 14. A system for supporting a cross-domain communication session between communication platforms using a bridge server, the system comprising: a processor; anda memory coupled to the processor, the memory containing computer executable instructions for: providing a bridge server;registering, by the bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;receiving, by the bridge server, a request to establish a communication session with a user corresponding to the user identifier, the request being received from one of the communication platforms;creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as an incoming leg and any other of the communication legs are designated as outgoing legs;sending, by the bridge server, the request to establish the communication session over the outgoing legs;receiving, by the bridge server, a communication acceptance from one of the outgoing legs;sending, by the bridge server, a cancel message over any of the outgoing legs from which the communication acceptance was not received;sending, by the bridge server, the communication acceptance over the incoming leg; andbridging, by the bridge server, the incoming leg and the outgoing leg from which the communication acceptance was received to establish the communication session,wherein bridging the incoming leg and the outgoing leg to establish the communication session includes creating a bridged media path through which communications sent over the incoming leg and the outgoing leg by the communication platforms during the communication session are first received by the bridge server before transmitting the communications to the communication platforms, andwherein the bridge server is configured to convert information received over the bridged media path between different media formats if the media format used by the incoming leg is different than the media format used by one of the outgoing legs.
  • 15. The system of claim 14 further comprising instructions for: receiving, from one of the incoming leg and the outgoing leg from which the communication acceptance was received, a communication session termination request;sending the communication session termination request over the incoming leg or the outgoing leg from which the communication session termination request was not received; anddestroying all of the communication legs.
  • 16. The system of claim 14, wherein the bridge server is coupled to a media server that forms part of a cross-domain system with the bridge server, wherein the media server handles media legs for the communication session.
  • 17. The system of claim 16, wherein the cross-domain system includes a cross-domain database having a plurality of information specific to the communication platforms.
  • 18. The system of claim 17, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.
  • 19. The system of claim 18 further comprising instructions for managing the communication session by the bridge server, wherein the bridge server uses the plurality of information contained in the cross-domain database to enable communications between the communication platforms that are in incompatible domains and cannot communicate directly with one another.
  • 20. The system of claim 14, wherein the bridge server bridges the incoming leg and the outgoing leg both when the communication platforms corresponding to the incoming leg and outgoing leg are in incompatible domains and cannot communicate directly with one another and when the communication platforms corresponding to the incoming leg and outgoing leg are in compatible domains and can communicate directly with one another.
  • 21. The system of claim 14 further comprising instructions for: receiving, by the bridge server, a second request to establish a second communication session with the user corresponding to the user identifier, the second request being received from one of the communication platforms;creating, by the bridge server, a separate second communication leg for each of the communication platforms, wherein the second communication leg created for the communication platform from which the second request was received is designated as a second incoming leg and any other of the second communication legs are designated as second outgoing legs;sending, by the bridge server, the second request to establish the communication session over the second outgoing legs;receiving, by the bridge server, a cancel message from the second incoming leg;sending, by the bridge server, the cancel message over the second outgoing legs; anddestroying, by the bridge server, the second communication legs.
  • 22. A system for supporting a cross-domain communication session between communication platforms using a bridge server, the system comprising: a processor; anda memory coupled to the processor, the memory containing computer executable instructions for: providing a bridge server;registering, by the bridge server, with a plurality of communication platforms using a user identifier, wherein at least two of the communication platforms are in incompatible domains and cannot communicate directly with one another, and wherein the user identifier is registered with each of the communication platforms via one or more clients that are in communication with the communication platforms;receiving, by the bridge server, a request to establish a communication session with the user corresponding to the user identifier, the request being received from one of the communication platforms;creating, by the bridge server, a separate communication leg for each of the communication platforms, wherein the communication leg created for the communication platform from which the request was received is designated as an incoming leg and any other of the communication legs are designated as outgoing legs;sending, by the bridge server, the request to establish the communication session over the outgoing legs;receiving, by the bridge server, a cancel message from the incoming leg;sending, by the bridge server, the cancel message over the outgoing legs; anddestroying, by the bridge server, all of the communication legs,wherein the bridge server is configured to: bridge the incoming leg and the outgoing leg to establish the communication session to create a bridged media path through which communications sent over the incoming leg and the outgoing leg by the communication platforms during the communication session are first received by the bridge server before transmitting the communications to the communication platforms, andconvert information received over the bridged media path between different media formats if the media format used by the incoming leg is different than the media format used by one of the outgoing legs.
  • 23. The system of claim 22, wherein the bridge server is coupled to a media server that forms part of a cross-domain system with the bridge server, wherein the media server handles media legs for any communication sessions managed by the bridge server.
  • 24. The system of claim 23, wherein the cross-domain system includes a cross-domain database having a plurality of information specific to the communication platforms.
  • 25. The system of claim 24, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.
  • 26. The system of claim 25 wherein the bridge server uses the plurality of information contained in the cross-domain database to enable communications between any of the communication platforms that are in incompatible domains and cannot communicate directly with one another.
  • 27. A system for supporting a cross-domain communication session between communication platforms, the system comprising: a bridge server registered with at least two communication platforms using a user identifier, wherein the at least two communication platforms are in separate and incompatible domains and wherein the user identifier is recognized by all of the at least two communication platforms; anda cross-domain database having a plurality of information specific to the at least two communication platforms and the user identifier,wherein the bridge server is configured to receive communications requests from the at least two communication platforms, to manage communication sessions between the at least two communication platforms using the plurality of information specific to the at least two communication platforms, to create a bridged media path through which communications for the communication session between the at least two communication platforms are first received by the bridge server before transmitting the communications to the communication platforms, and to convert information received over the bridge media path between different media formats if the media format used by one of the at least two communication platforms is different than the media format used by another one of the at least two communication platforms.
  • 28. The system of claim 27 further comprising a media server interfaced with the bridge server.
  • 29. The system of claim 27, wherein the plurality of information includes an IP address, a port number, and a plurality of functionality identifiers, the plurality of functionality identifiers indicating whether each of the communication platforms supports certain Unified Communications and Collaboration (UCC) functions.
  • 30. The system of claim 27, wherein one of the at least two communication platforms is compatible with another one of the at least two communication platforms.
CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No. 62/316,133, filed on Mar. 31, 2016, entitled SYSTEM AND METHOD FOR ENABLING USE OF A SINGLE USER IDENTIFIER ACROSS INCOMPATIBLE NETWORKS FOR UCC FUNCTIONALITY, which is incorporated by reference in its entirety.

US Referenced Citations (321)
Number Name Date Kind
5442637 Nguyen Aug 1995 A
5761309 Ohashi et al. Jun 1998 A
5790637 Johnson et al. Aug 1998 A
5818447 Wolf et al. Oct 1998 A
5889762 Pajuvirta et al. Mar 1999 A
6031818 Lo et al. Feb 2000 A
6128283 Sabaa et al. Oct 2000 A
6141687 Blair Oct 2000 A
6161082 Goldberg et al. Dec 2000 A
6195694 Chen et al. Feb 2001 B1
6202084 Kumar et al. Mar 2001 B1
6219638 Padmanabhan et al. Apr 2001 B1
6298129 Culver et al. Oct 2001 B1
6311150 Ramaswamy et al. Oct 2001 B1
6343067 Drottar et al. Jan 2002 B1
6360196 Poznaski et al. Mar 2002 B1
6389016 Sabaa et al. May 2002 B1
6438376 Elliott et al. Aug 2002 B1
6473425 Bellaton et al. Oct 2002 B1
6574668 Gubbi et al. Jun 2003 B1
6606112 Falco Aug 2003 B1
6654794 French Nov 2003 B1
6741691 Ritter et al. May 2004 B1
6754181 Elliott et al. Jun 2004 B1
6766373 Beadle Jul 2004 B1
6826613 Wang et al. Nov 2004 B1
6836765 Sussman Dec 2004 B1
6842460 Olkkonen et al. Jan 2005 B1
6850769 Grob et al. Feb 2005 B2
6898413 Yip et al. May 2005 B2
6912278 Hamilton Jun 2005 B1
6940826 Simard et al. Sep 2005 B1
6963555 Brenner et al. Nov 2005 B1
6975718 Pearce et al. Dec 2005 B1
6987756 Ravindranath et al. Jan 2006 B1
6999469 Chu Feb 2006 B1
6999575 Sheinbein Feb 2006 B1
6999932 Zhou Feb 2006 B1
7006508 Bondy et al. Feb 2006 B2
7010109 Gritzer et al. Mar 2006 B2
7013155 Ruf et al. Mar 2006 B1
7028312 Merrick Apr 2006 B1
7079529 Khuc Jul 2006 B1
7080158 Squire Jul 2006 B1
7092385 Gallant et al. Aug 2006 B2
7117526 Short Oct 2006 B1
7123710 Ravishankar Oct 2006 B2
7184415 Chaney et al. Feb 2007 B2
7185114 Hariharasubrahmanian Feb 2007 B1
7272377 Cox et al. Sep 2007 B2
7302496 Metzger Nov 2007 B1
7304985 Sojka et al. Dec 2007 B2
7345999 Su et al. Mar 2008 B2
7346044 Chou et al. Mar 2008 B1
7353252 Yang et al. Apr 2008 B1
7353255 Acharya et al. Apr 2008 B2
7412374 Seiler et al. Aug 2008 B1
7457279 Scott et al. Nov 2008 B1
7477282 Firestone et al. Jan 2009 B2
7487248 Moran et al. Feb 2009 B2
7512652 Appelman et al. Mar 2009 B1
7542472 Gerendai et al. Jun 2009 B1
7564843 Manjunatha et al. Jul 2009 B2
7570743 Barclay et al. Aug 2009 B2
7574523 Traversat et al. Aug 2009 B2
7590758 Takeda et al. Sep 2009 B2
7613171 Zehavi et al. Nov 2009 B2
7623476 Ravikumar et al. Nov 2009 B2
7623516 Chaturvedi et al. Nov 2009 B2
7656870 Ravikumar et al. Feb 2010 B2
7664495 Bonner et al. Feb 2010 B1
7665094 Frender Feb 2010 B2
7769881 Matsubara et al. Aug 2010 B2
7774495 Pabla et al. Aug 2010 B2
7778187 Chaturvedi et al. Aug 2010 B2
7782866 Walsh et al. Aug 2010 B1
7796984 Hursey Sep 2010 B2
7882247 Sturniolo Feb 2011 B2
7917584 Arthursson Mar 2011 B2
8009586 Chaturvedi et al. Aug 2011 B2
8065418 Abuan et al. Nov 2011 B1
8200796 Margulis Jun 2012 B1
8218532 Burritt Jul 2012 B1
8407576 Yin et al. Mar 2013 B1
9712507 Chaturvedi Jul 2017 B2
10002115 Killian Jun 2018 B1
20010050923 Park et al. Dec 2001 A1
20020031212 O'Neil et al. Mar 2002 A1
20020037000 Park et al. Mar 2002 A1
20020038282 Montgomery Mar 2002 A1
20020042769 Gujral et al. Apr 2002 A1
20020062285 Amann et al. May 2002 A1
20020064167 Khan et al. May 2002 A1
20020080719 Parkvall et al. Jun 2002 A1
20020087887 Busam et al. Jul 2002 A1
20020097150 Sandelman et al. Jul 2002 A1
20020120757 Sutherland et al. Aug 2002 A1
20020124096 Loguinov et al. Sep 2002 A1
20020143548 Korall et al. Oct 2002 A1
20020150110 Inbar et al. Oct 2002 A1
20020152325 Elgebaly et al. Oct 2002 A1
20020156844 Maehiro Oct 2002 A1
20020166053 Wilson Nov 2002 A1
20020173303 Shibutani Nov 2002 A1
20020176404 Girard Nov 2002 A1
20020178087 Henderson et al. Nov 2002 A1
20020184310 Traversat et al. Dec 2002 A1
20030009565 Arao Jan 2003 A1
20030031210 Harris Feb 2003 A1
20030035441 Cheng et al. Feb 2003 A1
20030043764 Kim et al. Mar 2003 A1
20030044020 Aboba et al. Mar 2003 A1
20030046056 Godoy et al. Mar 2003 A1
20030046585 Minnick Mar 2003 A1
20030061025 Abir Mar 2003 A1
20030061481 Levine et al. Mar 2003 A1
20030072485 Guerin et al. Apr 2003 A1
20030076815 Miller et al. Apr 2003 A1
20030078858 Angelopoulos et al. Apr 2003 A1
20030088676 Smith et al. May 2003 A1
20030105812 Flowers, Jr. et al. Jun 2003 A1
20030110047 Santosuosso Jun 2003 A1
20030115251 Fredrickson et al. Jun 2003 A1
20030126213 Betzler Jul 2003 A1
20030135569 Khakoo et al. Jul 2003 A1
20030137939 Dunning et al. Jul 2003 A1
20030158722 Lord Aug 2003 A1
20030163525 Hendriks et al. Aug 2003 A1
20030163697 Pabla et al. Aug 2003 A1
20030172145 Nguyen Sep 2003 A1
20030174707 Grob et al. Sep 2003 A1
20030177186 Goodman et al. Sep 2003 A1
20030177422 Tararoukhine et al. Sep 2003 A1
20030187650 Moore et al. Oct 2003 A1
20030202480 Swami Oct 2003 A1
20030212772 Harris Nov 2003 A1
20030214955 Kim Nov 2003 A1
20030217171 Von Stuermer et al. Nov 2003 A1
20030217318 Choi Nov 2003 A1
20030220121 Konishi et al. Nov 2003 A1
20030229715 Baratakke et al. Dec 2003 A1
20040005877 Vaananen Jan 2004 A1
20040024879 Dingman et al. Feb 2004 A1
20040034776 Fernando et al. Feb 2004 A1
20040034793 Yuan Feb 2004 A1
20040039781 Lavallee et al. Feb 2004 A1
20040044517 Palmquist Mar 2004 A1
20040052234 Ameigeiras et al. Mar 2004 A1
20040062267 Minami et al. Apr 2004 A1
20040068567 Moran et al. Apr 2004 A1
20040100973 Prasad May 2004 A1
20040103212 Takeuchi et al. May 2004 A1
20040128554 Maher, III et al. Jul 2004 A1
20040133689 Vasisht Jul 2004 A1
20040139225 Takahashi Jul 2004 A1
20040139228 Takeda et al. Jul 2004 A1
20040139230 Kim Jul 2004 A1
20040143678 Chari et al. Jul 2004 A1
20040148434 Matsubara et al. Jul 2004 A1
20040153858 Hwang Aug 2004 A1
20040158471 Davis et al. Aug 2004 A1
20040162871 Pabla et al. Aug 2004 A1
20040203834 Mahany Oct 2004 A1
20040213184 Hu et al. Oct 2004 A1
20040228279 Midtun et al. Nov 2004 A1
20040240399 Corrao et al. Dec 2004 A1
20040249885 Petropoulakis et al. Dec 2004 A1
20040249953 Fernandez et al. Dec 2004 A1
20040260952 Newman et al. Dec 2004 A1
20040267527 Creamer et al. Dec 2004 A1
20040267938 Shoroff et al. Dec 2004 A1
20040268257 Mudusuru Dec 2004 A1
20050004982 Vernon et al. Jan 2005 A1
20050008024 Newpol et al. Jan 2005 A1
20050015502 Kang et al. Jan 2005 A1
20050033843 Shahi et al. Feb 2005 A1
20050033985 Xu et al. Feb 2005 A1
20050050227 Michelman Mar 2005 A1
20050071481 Danieli Mar 2005 A1
20050086309 Galli et al. Apr 2005 A1
20050091407 Vaziri et al. Apr 2005 A1
20050105524 Stevens et al. May 2005 A1
20050119005 Segal et al. Jun 2005 A1
20050120073 Cho Jun 2005 A1
20050130650 Creamer et al. Jun 2005 A1
20050132009 Solie Jun 2005 A1
20050136911 Csapo et al. Jun 2005 A1
20050138119 Saridakis Jun 2005 A1
20050138128 Baniel et al. Jun 2005 A1
20050143105 Okamoto Jun 2005 A1
20050144242 Marston Jun 2005 A1
20050144288 Liao Jun 2005 A1
20050187781 Christensen Aug 2005 A1
20050187957 Kramer et al. Aug 2005 A1
20050195802 Klein et al. Sep 2005 A1
20050198499 Salapaka et al. Sep 2005 A1
20050201357 Poyhonen Sep 2005 A1
20050201485 Fay Sep 2005 A1
20050208947 Bahl Sep 2005 A1
20050220017 Brand et al. Oct 2005 A1
20050246193 Roever et al. Nov 2005 A1
20050249196 Ansari et al. Nov 2005 A1
20050254440 Sorrell Nov 2005 A1
20050259656 Dollar Nov 2005 A1
20050270992 Sanzgiri et al. Dec 2005 A1
20050286519 Ravikumar et al. Dec 2005 A1
20060002355 Baek et al. Jan 2006 A1
20060026091 Keen, Jr. Feb 2006 A1
20060062180 Sayeedi et al. Mar 2006 A1
20060069775 Artobello et al. Mar 2006 A1
20060072506 Sayeedi et al. Apr 2006 A1
20060120375 Ravikumar et al. Jun 2006 A1
20060121902 Jagadeesan et al. Jun 2006 A1
20060121986 Pelkey et al. Jun 2006 A1
20060123428 Burns Jun 2006 A1
20060148516 Reddy et al. Jul 2006 A1
20060165029 Melpignano et al. Jul 2006 A1
20060168643 Howard et al. Jul 2006 A1
20060171534 Baughman Aug 2006 A1
20060182100 Li et al. Aug 2006 A1
20060183476 Morita et al. Aug 2006 A1
20060187926 Imai Aug 2006 A1
20060195402 Malina et al. Aug 2006 A1
20060203750 Ravikumar et al. Sep 2006 A1
20060205436 Liu et al. Sep 2006 A1
20060218624 Ravikumar et al. Sep 2006 A1
20060230166 Philyaw Oct 2006 A1
20060233117 Tomsu et al. Oct 2006 A1
20060246903 Kong et al. Nov 2006 A1
20060258289 Dua Nov 2006 A1
20070016921 Levi et al. Jan 2007 A1
20070019545 Alt et al. Jan 2007 A1
20070025270 Sylvain Feb 2007 A1
20070078785 Bush et al. Apr 2007 A1
20070082671 Feng et al. Apr 2007 A1
20070110043 Girard May 2007 A1
20070111794 Hogan et al. May 2007 A1
20070116224 Burke et al. May 2007 A1
20070130253 Newson et al. Jun 2007 A1
20070136459 Roche et al. Jun 2007 A1
20070165629 Chaturvedi et al. Jul 2007 A1
20070190987 Vaananen Aug 2007 A1
20070206563 Silver et al. Sep 2007 A1
20070239892 Ott et al. Oct 2007 A1
20070253435 Keller et al. Nov 2007 A1
20070260359 Benson et al. Nov 2007 A1
20070274276 Laroia et al. Nov 2007 A1
20070280253 Rooholamini et al. Dec 2007 A1
20070288657 Koskimies Dec 2007 A1
20070294626 Fletcher et al. Dec 2007 A1
20070297430 Nykanen et al. Dec 2007 A1
20080005328 Shively et al. Jan 2008 A1
20080019285 John et al. Jan 2008 A1
20080032695 Zhu et al. Feb 2008 A1
20080046984 Bohmer et al. Feb 2008 A1
20080069105 Costa et al. Mar 2008 A1
20080080392 Walsh et al. Apr 2008 A1
20080091813 Bodlaender Apr 2008 A1
20080123685 Varma et al. May 2008 A1
20080130639 Costa-Requena et al. Jun 2008 A1
20080168440 Regnier et al. Jul 2008 A1
20080192756 Damola et al. Aug 2008 A1
20080235362 Kjesbu et al. Sep 2008 A1
20080235511 O'Brien et al. Sep 2008 A1
20080244718 Frost et al. Oct 2008 A1
20080250408 Tsui et al. Oct 2008 A1
20080273541 Pharn Nov 2008 A1
20080320096 Szeto Dec 2008 A1
20080320565 Buch et al. Dec 2008 A1
20090003322 Isumi Jan 2009 A1
20090006076 Jindal Jan 2009 A1
20090052399 Silver et al. Feb 2009 A1
20090055473 Synnergren Feb 2009 A1
20090088150 Chaturvedi et al. Apr 2009 A1
20090136016 Gornoi et al. May 2009 A1
20090156217 Bajpai Jun 2009 A1
20090182815 Czechowski et al. Jul 2009 A1
20090187831 Tiwana Jul 2009 A1
20090192976 Spivack et al. Jul 2009 A1
20090234967 Yu et al. Sep 2009 A1
20090240821 Juncker et al. Sep 2009 A1
20090257433 Mutikainen et al. Oct 2009 A1
20090300673 Bachet et al. Dec 2009 A1
20090303926 Den Hartog Dec 2009 A1
20090327516 Amishima et al. Dec 2009 A1
20100011108 Clark et al. Jan 2010 A1
20100011111 Vizaei Jan 2010 A1
20100049980 Barriga et al. Feb 2010 A1
20100077023 Eriksson Mar 2010 A1
20100103837 Jungck Apr 2010 A1
20100107205 Foti Apr 2010 A1
20100174783 Zarom Jul 2010 A1
20100191954 Kim et al. Jul 2010 A1
20100208634 Eng Aug 2010 A1
20100212004 Fu Aug 2010 A1
20100223047 Christ Sep 2010 A1
20100279670 Ghai et al. Nov 2010 A1
20100299150 Fein et al. Nov 2010 A1
20100299313 Orsini et al. Nov 2010 A1
20100312832 Allen et al. Dec 2010 A1
20100312897 Allen et al. Dec 2010 A1
20110040836 Allen et al. Feb 2011 A1
20110099612 Lee et al. Apr 2011 A1
20110122864 Cherifi et al. May 2011 A1
20110141220 Miura Jun 2011 A1
20110145687 Grigsby et al. Jun 2011 A1
20110307556 Chaturvedi et al. Dec 2011 A1
20110314134 Foti Dec 2011 A1
20110320821 Alkhatib et al. Dec 2011 A1
20120078609 Chaturvedi et al. Mar 2012 A1
20120124191 Lyon May 2012 A1
20120246325 Pancorbo Marcos Sep 2012 A1
20120263144 Nix Oct 2012 A1
20130067004 Logue et al. Mar 2013 A1
20130106989 Gage et al. May 2013 A1
20130111064 Mani et al. May 2013 A1
20150207846 Famaey Jul 2015 A1
20160260003 Hill Sep 2016 A1
20160314211 Kerai Oct 2016 A1
20170236206 Keen Aug 2017 A1
20180069878 Martini Mar 2018 A1
Foreign Referenced Citations (15)
Number Date Country
1404082 Mar 2004 EP
160339 Dec 2005 EP
1638275 Mar 2006 EP
1848163 Oct 2007 EP
1988697 Nov 2008 EP
1988698 Nov 2008 EP
2005-94600 Apr 2005 JP
2007-043598 Feb 2007 JP
10-2005-0030548 Mar 2005 KR
WO 2003079635 Sep 2003 WO
WO 2004063843 Jul 2004 WO
WO 2005009019 Jan 2005 WO
2006064047 Jun 2006 WO
WO 2006075677 Jul 2006 WO
WO 2008099420 Aug 2008 WO
Non-Patent Literature Citations (77)
Entry
International Search Report and Written Opinion of the International Searching Authority from PCT/US2006/040312, dated Mar. 2, 2007.
International Search Report and Written Opinion of the International Searching Authority from PCT/US2006/047841, dated Sep. 12, 2008.
International Search Report and Written Opinion of the International Searching Authority from PCT/US2007/002424, dated Aug. 14, 2007.
International Search Report and Written Opinion of the International Searching Authority from PCT/US2007/068820, dated Jun. 11, 2008.
International Search Report and Written Opinion of the International Searching Authority from PCT/US2007/068821, dated Jun. 14, 2008.
International Search Report and Written Opinion of the International Searching Authority from PCT/U52007068823, dated Jun. 1, 2008.
Jeff Tyson, “How Instant Messaging Works”, www.verizon.com/learningcenter, Mar. 9, 2005.
Rory Bland, et al,“P2P Routing” Mar. 2002.
Rosenberg, “STUN—Simple Traversal of UDP Through NAT”, Sep. 2002, XP015005058.
Salman A. Baset, et al, “An Analysis of the Skype Peer-To-Peer Internet Telephony Protocol”, Department of Computer Science, Columbia University, New York, NY, USA, Sep. 15, 2004.
Singh et al., “Peer-to Peer Internet Telephony Using SIP”, Department of Computer Science, Columbia University, Oct. 31, 2004, XP-002336408.
Sinha, S. and Oglieski, A., A TCP Tutorial, Nov. 1998 (Date posted on Internet: Apr. 19, 2001) [Retrieved from the Internet <URL:http//www.ssfnet.org/Exchange/tcp/tcpTutorialNotes.html>].
Pejman Khadivi, Terence D. Todd and Dongmei Zhao, “Handoff trigger nodes for hybrid IEEE 802.11 WLAN/cellular networks,” Proc. of IEEE International Conference on Quality of Service in Heterogeneous Wired/Wireless Networks, pp. 164-170, Oct. 18, 2004.
International Search Report and Written Opinion of the International Searching Authority from PCT/US2008/078142, dated Mar. 27, 2009.
International Search Report and Written Opinion of the International Searching Authority from PCT/US2008/084950, dated Apr. 27, 2009.
Hao Wang, Skype VoIP service-architecture and comparison, In: INFOTECH Seminar Advanced Communication Services (ASC), 2005, pp. 4, 7, 8.
Seta, N.; Miyajima, H.; Zhang, L;; Fujii, T., “All-SIP Mobility: Session Continuity on Handover in Heterogeneous Access Environment,” Vehicular Technology Conference, 2007. VTC 2007—Spring. IEEE 65th, Apr. 22-25, 2007, pp. 1121-1126.
International Search Report and Written Opinion of the International Searching Authority from PCT/US2008/075141, dated Mar. 5, 2009.
Qian Zhang; Chuanxiong Guo; Zihua Guo; Wenwu Zhu, “Efficient mobility management for vertical handoff between WWAN and WLAN,” Communications Magazine, IEEE, vol. 41. issue 11, Nov. 2003, pp. 102-108.
Isaacs, Ellen et al., “Hubbub: A sound-enhanced mobile instant messenger that supports awareness and opportunistic interactions,” Proceedings of the SIGCHI Conference on Human Factors in Computing Systems; vol. 4, Issue No. 1; Minneapolis, Minnesota; Apr. 20-25, 2002; pp. 179-186.
PCT: International Preliminary Report on Patentability of PCT/US2008/084950; Jun. 1, 2010; 5 pgs.
International Search Report and Written Opinion of the International Searching Authority from PCT/US2014/039777, dated Sep. 30, 2014.
International Search Report and Written Opinion of the International Searching Authority from PCT/U52014/39782, dated Oct. 17, 2014.
International Search Report and Written Opinion of PCT/US2015/43633, dated Oct. 26, 2015, 21 pgs.
PCT: International Search Report and Written Opinion of PCT/US2015/43630 (related application), dated Oct. 30, 2015, 20 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2014/039777; dated Jan. 28, 2016; 8 pgs.
PCT: International Preliminary Report on Patentability of PCT/US14/39782; dated Apr. 19, 2016; 9 pgs.
PCT: International Search Report and Written Opinion for PCT/US2011/024870; dated Oct. 26, 2011; 12 pages.
J. Rosenberg et al. “Session Traversal Utilities for NAT (STUN)”, draft-ieff-behave-rfc3489bis-06, Mar. 5, 2007.
PCT: International Search Report and Written Opinion for PCT/US2011/028685; dated Nov. 9, 2011; 10 pages.
PCT: International Search Report and Written Opinion for PCT/US2011/029954; dated Nov. 24, 2011; 8 pages.
PCT: International Search Report and Written Opinion for PCT/US2011/024891; dated Nov. 25, 2011; 9 pages.
PCT: International Search Report and Written Opinion for PCT/US2011/031245; dated Dec. 26, 2011; 13 pages.
Wireless Application Protocol—Wireless Transport Layer Security Specification, Version Feb. 18, 2000, Wireless Application Forum, Ltd. 2000; 99 pages.
PCT: International Search Report and Written Opinion for PCT/US2011/040864; dated Feb. 17, 2012; 8 pages.
PCT: International Search Report and Written Opinion for PCT/US2011/041565; dated Jan. 5, 2012; 7 pages.
PCT: International Search Report and Written Opinion for PCT/US2011/031246; dated Dec. 27, 2011; 8 pages.
PCT: International Search Report and Written Opinion for PCT/US2011/049000; dated Mar. 27, 2012; 10 pages.
PCT: International Search Report and Written Opinion for PCT/US2011/051877; dated Apr. 13, 2012; 7 pages.
PCT: International Search Report and Written Opinion for PCT/US2011/055101; dated May 22, 2012; 9 pages.
Balamurugan Karpagavinayagam et al. (Monitoring Architecture for Lawful Interception in VoIP Networks, ICIMP 2007, Aug. 24, 2008).
NiceLog User's Manual 385A0114-08 Rev. A2, Mar. 2004.
WISPA: Wireless Internet Service Providers Association; WISPA-CS-IPNA-2.0; May 1, 2009.
PCT: International Preliminary Report on Patentability of PCT/US2011/024870; dated Aug. 30, 2012; 7 pgs.
RFC 5694 (“Peer-to-Peer (P2P) Architecture: Definition, Taxonomies, Examples, and Applicability”, Nov. 2009).
Mahy et al., The Session Initiation Protocol (SIP) “Replaces” Header, Sep. 2004, RFC 3891, pp. 1-16.
PCT: International Preliminary Report on Patentability of PCT/US2011/024891; dated Aug. 30, 2012; 6 pgs.
T. Dierks & E. Rescorla, The Transport Layer Security (TLS) Protocol (Ver. 1.2, Aug. 2008) retrieved at http://tools.ietf.org/htmllrfc5246. Relevant pages provided.
J. Rosenberg et al., SIP: Session Initiation Protocol (Jun. 2008) retrieved at hftp://tools.ietf.org/html/rfc3261. Relevant pages provided.
Philippe Bazot et al., Developing SIP and IP Multimedia Subsystem (IMS) Applications (Feb. 5, 2007) retrieved at redbooks IBM form No. SG24-7255-00. Relevant pages provided.
PCT: International Preliminary Report on Patentability of PCT/US2011/028685; dated Oct. 4, 2012; 6 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2011/031245; dated Oct. 26, 2012; 9 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2011/029954; dated Oct. 11, 2012; 5 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2011/031246; dated Nov. 8, 2012; 5 pgs.
Rosenberg, J; “Interactive Connectivity Establishment (ICE): A Protocol for Network Address Translator (NAT) Traversal for Offer/Answer Protocols”; Oct. 29, 2007; I ETF; I ETF draft of RFC 5245, draft-ietf-mmusic-ice-19; pp. 1-120.
Blanchet et al; “IPv6 Tunnel Broker with the Tunnel Setup Protocol (TSP)”; May 6, 2008; IETF; IETF draft of RFC 5572, draftblanchet-v6ops-tunnelbroker-tsp-04; pp. 1-33.
Cooper et al; “NAT Traversal for dSIP”; Feb. 25, 2007; IETF; IETF draft draft-matthews-p2psip-dsip-nat-traversal-00; pp. 1-23.
Cooper et al; “The Effect of NATs on P2PSIP Overlay Architecture”; IETF; IETF draft draft-matthews-p2psip-nats-and-overlays-01.txt; pp. 1-20.
Srisuresh et al; “State of Peer-to-Peer(P2P) Communication Across Network Address Translators(NATs)”; Nov. 19, 2007; I ETF; I ETF draft for RFC 5128, draft-ietf-behave-p2p-state-06.txt; pp. 1-33.
PCT: International Search Report and Written Opinion for PCT/US2012/046026; dated Oct. 18, 2012; 6 pages.
Dunigan, Tom, “Almost TCP over UDP (atou),” last modified Jan. 12, 2004; retrieved on Jan. 18, 2011 from <http://www.csm.ornl.gov/˜dunigan/net100/atou.html> 18 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2011/040864; dated Jan. 3, 2013; 6 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2011/041565; dated Jan. 10, 2013; 6 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2011/049000; dated Feb. 26, 2013; 6 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2011/051877; dated Mar. 26, 2013; 5 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2011/055101; dated Apr. 16, 2013; 7 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2012/046026; dated Jan. 30, 2014; 5 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2008/075141; dated Mar. 9, 2010; 5 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2007/068820; dated Dec. 31, 2008; 8 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2007/068823; dated Nov. 27, 2008; 8 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2006/047841; dated Nov. 6, 2008; 7 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2007/002424; dated Aug. 7, 2008; 6 pgs.
PCT: International Preliminary Report on Patentability of PCT/US2006/040312; dated May 2, 2008; 5 pgs.
PCT: International Preliminary Report on Patentability of PCT/IB2005/000821; dated Oct. 19, 2006; 10 pgs.
Chathapuram, “Security in Peer-To-Peer Networks”, Aug. 8, 2001, XP002251813.
International Search Report and Written Opinion of the International Searching Authority from PCT/IB2005/000821, dated Aug. 5, 2005.
International Search Report and Written Opinion of the International Searching Authority from PCT/US2006/032791, dated Dec. 18, 2006.
Related Publications (1)
Number Date Country
20170288904 A1 Oct 2017 US
Provisional Applications (1)
Number Date Country
62316133 Mar 2016 US