Conference call bridge arrangement

• US 6,990,081 B2
• Filed: 03/27/2001
• Issued: 01/24/2006
• Est. Priority Date: 03/27/2001
• Status: Expired due to Term

• Current Assignee: Google Technology Holdings LLC (Alphabet Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Armbruster, Peter J., Shaughnessy, Mark L., Schaefer, Bradley R.
• Primary Examiner(s): Pham, Chi
• Assistant Examiner(s): Wong, Blanche
• Application Number:
  US09/819,020
• Publication Number:
  US 20020141383A1
• Time in Patent Office: 1,764 Days
• Field of Search: 370/352, 370260-261, 370/263, 370266-267, 370/422, 370/426, 370/465, 370/468, 370360-366, 709227-229
• US Class Current: 370/260
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/4038 with floor control
• CPC Class Codes: H04L 9/40 Network security protocols
• CPC Class Codes: H04M 2201/14 Delay circuits; Timers
• CPC Class Codes: H04M 3/56 Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities video conference systems H04N7/15
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42

Abstract

A user terminal (10) initiates an internet protocol using session initiation protocol to interconnect a number of user terminals (11–13) in a conference call. Signaling connections (41, 42, and 43) are established between one user terminal and each of the plurality of user terminals. Common bearer formats are negotiated among the plurality of user terminals (113). If a common bearer format exists (115), the conference bridge is established for data (voice) transmission (127).

Claims

1. A method for a voice over internet protocol conference bridge among a plurality of user terminals comprising the steps of:

originating an internet protocol call using session initiation protocol (SIP) among the plurality of user terminals;

negotiating by the plurality of user terminals a common bearer format among the plurality of user terminals via SIP, wherein said step of negotiating further includes the step of determining whether the plurality of user terminals support multiple bearer formats, wherein the step of determining includes the steps of;

negotiating a homogeneous bearer format among the plurality of user terminals which have multiple bearer formats;

determining whether a common bearer format exists among the plurality of user terminals;

canceling the step of coupling the plurality of user terminals; and

coupling a data input/output of each of the plurality of user terminals to a conference bridge.

2. The method for a voice over internet protocol conference bridge as claimed in claim 1, wherein there is further included the step of coupling the plurality of user terminals with homogeneous bearer formats.

3. A method for a voice over internet protocol conference bridge among a plurality of user terminals comprising the steps of:

originating an internet protocol call using session initiation protocol (SLP) among the plurality of user terminals;

negotiating by the plurality of user terminals a common bearer format among the plurality of user terminals via SIP, wherein said step of negotiating further includes the step of determining whether the plurality of user terminals support multiple bearer formats;

coupling a data input/output of each of the plurality of user terminals to a conference bridge; and

if the plurality of user terminals supports multiple bearer formats, there is further included the steps of;

transmitting by each of said plurality of user terminals in a native bearer format; and

each of said plurality of user terminals receiving a bearer format of others of said plurality of user terminals and converting the received bearer format to the native bearer format for use by each of the plurality of user terminals.

4. A method for a voice over internet protocol conference bridge among a plurality of user terminals comprising the steps of:

originating an internet protocol call using session initiation protocol (SIP) among the plurality of user terminals, wherein the step of originating includes the steps of;

originating an internet call between a first party and a second party of said plurality of user terminals;

negotiating a common bearer format between the first party and the second party;

originating an internet call to a third party by the first party;

negotiating a common bearer format between the first party and the third party;

repeating the steps of originating, negotiating and coupling between the first party and another party for each of the plurality of user terminals

negotiating by the plurality of user terminals a common bearer format among the plurality of user terminals via SIP; and

coupling a data input/output of each of the plurality of user terminals to a conference bridge.

5. A method for a voice over internet protocol conference bridge among a plurality of user terminals comprising the steps of:

originating an internet protocol call using session initiation protocol (SIP) among the plurality of user terminals;

negotiating by the plurality of user terminals a common bearer format among the plurality of user terminals via SIP;

coupling a data input/output of each of the plurality of user terminals to a conference bridge, wherein the step of coupling includes the steps of;

receiving by the conference bridge an origination from a first party of the plurality of user terminals, said origination indicating other parties of the plurality of user terminals to be coupled for data transfer;

originating by the conference bridge a coupling to each of the other parties of the plurality of user terminals; and

sending a message to each of the plurality of user terminals establishing a data connection of the data input/output of each of the plurality of user terminals.

6. In a user terminal, a method for a voice over internet protocol conference bridge among a plurality of user terminals comprising the steps of:

originating by the user terminal an internet protocol call using session initiation protocol (SIP) among the plurality of user terminals;

negotiating by the user terminal and the plurality of user terminals a common bearer format among the user terminal and the plurality of user terminals via SIP, wherein said step of negotiating further includes the step of determining whether the plurality of user terminals support multiple bearer formats, wherein the step of determining includes the steps of;

negotiating a homogeneous bearer format among the plurality of user terminals which have multiple bearer formats;

determining whether a common bearer format exists among the plurality of user terminals;

canceling the step of coupling the plurality of user terminals; and

requesting by the user terminal a data coupling between the user terminal and the plurality of user terminals via a conference bridge.

7. The method for a voice over internet protocol conference bridge as claimed in claim 6, wherein there is further included the step of coupling the plurality of user terminals with homogeneous bearer formats.

8. In a user terminal, a method for a voice over internet protocol conference bridge among a plurality of user terminals comprising the steps of:

originating by the user terminal an internet protocol call using session initiation protocol (SIP) among the plurality of user terminals;

negotiating by the user terminal and the plurality of user terminals a common bearer format among the user terminal and the plurality of user terminals via SIP, wherein said step of negotiating further includes the step of determining whether the plurality of user terminals support multiple bearer formats;

requesting by the user terminal a data coupling between the user terminal and the plurality of user terminals via a conference bridge;

if the plurality of user terminals supports multiple bearer formats, there is further included the steps of;

transmitting by each of said plurality of user terminals in a native bearer format; and

each of said plurality of user terminals receiving a bearer format of others of said plurality of user terminals and converting the received bearer format to the native bearer format for use by the user terminal.