System and method for conference calling with VoIP terminal
8 claims: 2 independent, 6 dependent
- 1A method for connecting a plurality of called party terminals (14) in a bridged call session with a Voice Over Internet Protocol (VOIP) calling party terminal (12) comprising:the VOIP terminal providing the calling party with means for selecting the called party terminals to be bridged;the VOIP terminal receiving the called party terminal selections from the calling party characterized by : the VOIP terminal combining called party terminal identifiers identifying the selected called party terminals into VOIP packets, wherein each of the VOIP packets includes a VOIP header, the called party terminal identifiers and a VOIP call information payload;the VOIP terminal sending the VOIP packets to a calling party Service Control Point (SCP) (22) including an IP Gateway (24) and a Switching Center (26);and the calling party SCP creating a bridged call session connecting the called party terminals and the calling party VOIP terminal.
- 5A system for bridging a plurality of called party terminals in a call session with a Voice Over Internet Protocol (VOIP) calling party terminal comprising:means for selecting the called party terminals to be bridged characterized by : means for sending called party terminal identifiers identifying each selected called party terminal to a calling party Service Control Point (SCP) (22) including an IP Gateway (24) and a Switching Center (26) in VOIP packets, wherein each of the VOIP packets includes a VOIP header, the called party terminal identifiers and a VOIP call information payload;and means for creating a bridged call session at the calling party SCP connecting the called party terminals and the calling party VOIP terminal.
Independent claims2
23 paragraphs in 4 sections, as filed
BACKGROUND OF THE INVENTION
0001This invention relates to a method and apparatus for Voice over Internet Protocol (VOIP) communications, and more particularly bridging multiple calls into a conference call session with a VOIP terminal.
0002Conference calls enable multiple parties to communicate with each other by joining the parties together in the same call session in a manner known as bridging. Typical Plain Old Telephone Service (POTS) terminals, also known as land line terminals, connect with one other party for each telephone line associated with the terminal. The POTS terminal can initiate a conference call with several called parties if the terminal has several telephone lines.
0003Otherwise, each party taking part in the conference call dials a Public Switched Telephone (PSTN) telephone number, also known as a Directory Number (DN), which connects the party to a switching element in the communications network. The party then enters a code, such as a participant code, and the switching element connects the party to the bridged call session thereby allowing them to take part in the conference call by communicating with all the other conference call participants.
0004Voice Over Internet Protocol (VOIP) calling uses Internet Protocol (IP) addressing schemes to provide packet switched voice communications over a packet data network such as the Internet. Rather than establishing a telephone line using a physical connection between the two terminals as is done with Plain Old Telephone Switched (POTS) circuit-switched calls VOIP uses an IP address for routing packet-based information to and from the VOIP terminal over the Internet to provide voice communications referred to as a call.
0005In order to communicate with terminals over the PSTN, a VOIP terminal IP address is associated with a DN and the conversion between the two is made in the communications network. Currently, as a result of established IP addressing schemes and VOIP protocols a party using a VOIP terminal to make a call effectively establishes only one "telephone line" connecting to one called party at a time. It is desirable for a calling party to initiate a conference call using a VOIP terminal by simultaneously calling several called parties. The reference "Multi-Point Conference" XP-002371227 provides a general summary of VOIP conference calls, but does not disclose how a calling party can use a VOIP terminal to initiate a conference call with several called parties simultaneously.
0006The present invention contemplates a new and improved system and method that resolves the above-referenced difficulties and others.
SUMMARY OF THE INVENTION
0007A system and method for connecting a plurality of called party terminals with a VOIP calling party terminal in a bridged call session are provided.
0008In one aspect of the invention the method includes the VOIP terminal sending called party terminal identifiers identifying each selected called party terminal to a calling party Service Control Point and the calling party SCP creating a bridged call session connecting the called party terminals and the calling party VOIP terminal.
0009In another aspect of the invention, the system includes means for selecting the called party terminals to be bridged, means for sending called party terminal identifiers identifying each selected called party terminal to a calling party Service Control Point, and means for creating a bridged call session connecting the called party terminals and the calling party VOIP terminal.
0010Further scope of the applicability of the present invention will become apparent from the detailed description provided below. It should be understood, however that the detailed description and specific examples, while indicating preferred embodiments of the invention, are given by way of illustration only, since various changes and modifications within the spirit and scope of the invention will become apparent to those skilled in the art.
DESCRIPTION OF THE DRAWINGS
0011The present invention exists in the construction, arrangement, and combination of the various parts of the device, and steps of the method, whereby the objects contemplated are attained as hereinafter more fully set forth, specifically pointed out in the claims, and illustrated in the accompanying drawings in which: <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">Figure 1</figref> is a block diagram illustrating a communications network including a system for practicing aspects of the present inventive subject matter;</li><li><figref idref="f0002">Figure 2</figref> is a flow chart illustrating a method in accordance with the present invention; and</li><li><figref idref="f0002">Figure 3</figref> illustrates a VOIP packet sent in accordance with the present invention.</li></ul>
DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
0012Referring now to the drawings wherein the showings are for purposes of illustrating the preferred embodiments of the invention only and not for purposes of limiting same, <figref idref="f0001">Fig. 1</figref> provides a view of the overall preferred system according to the present invention.
0013As shown in <figref idref="f0001">Fig. 1</figref>, a communications network is shown generally at 10 for providing communications between a VOIP calling party terminal 12 and a plurality of called party terminals 14a - 14n referred collectively as called party terminals 14. Examples of the VOIP calling party terminal 12 can include, but are not limited to, a softphone running as an application on a computer, or a hardphone for providing voice communications using VOIP. Examples of the called party terminals 14 can include, but are not limited to, landlines also known as Plain Old Telephone Service telephones, mobile or cellular phones, VOIP terminals, or other phones capable of communicating over the Public Switched Telephone Network shown generally at 16. Each called party terminal 14 is connected to the PSTN in the usual applicable manner for providing communications to/from other terminals. Such connections may include conventional hardware and software processes which are not shown. Each called party terminal 14 has an identifier for routing calls to and from the terminal over the PSTN 16. An example of the called party terminal identifier, can include, but is not limited to a Directory Number (DN), such as a phone number from the North American Numbering Plan (NANP), among others.
0014The communications network 10 also includes a packet data network 20, such as for example the Internet, for providing the transmission of pack-based information using Internet Protocol (IP) addressing schemes. The VOIP terminal 12 is connected to the packet data network 20 for routing VOIP calls between the VOIP terminal 12 and the PSTN.
0015The communications network 10 also includes a Service Control Point 22 for handling calls to and from the calling party VOIP terminal 12 and the PSTN 16. Accordingly, the SCP 22 is referred to as the calling party SCP. The calling party SCP 22 includes an IP gateway 24, also known as a Media Gateway, for converting and/or translating IP based packet-switched calls into circuit switched calls and vice versa depending on the direction of traffic flow. That is to say, the IP gateway 24 operatively connects the packet data network 20 with the circuit switched Public Switched Telephone Network (PSTN) 16 for VOIP calls. By way of example, a suitable IP gateway 24 can include an iMerge® gateway provided by Lucent Technologies.
0016The calling party SCP 22 also includes a Switching Center 26 connected to the PSTN 16 for routing call traffic made by the VOIP terminal 12 to the PSTN and for routing call traffic from the PSTN destined for the VOIP terminal 12. The Switching Center 26 uses protocols, including but not limited to H.323 protocols among others, for routing these calls to and from the PSTN 16 using the DNs. The Switching Center 26 handles call set-ups for it's associated terminals, including the calling party VOIP terminal 12, as well as providing services for these terminals, including voice mail and others, which can be made available via subscription. The switching center 26 can be a Mobile Switching Center (MSC) for also connecting mobile phones with the PSTN 16.
0017The Switching Center 26 can be connected to a Subscriber Database 28 having subscriber information for the terminals associated with it. A subscriber identifier, such as a DN, can be used to identify the subscriber for associating the calling services ascribed to the subscriber. The subscriber database 28 and IP Gateway 24 can be located at the Switching Center 26 to form the SCP 22, or these elements can be connected in a known manner for quick and reliable communication therebetween.
0018Referring now to <figref idref="f0002">Fig. 2</figref>, a method of operation of the VOIP conference call feature, is shown generally at 100, for a calling party initiating a conference call to a plurality of called parties 14. The calling party VOIP terminal 12 provides a menu at 104 for the calling party to select the called parties to be bridged together with the calling party in the conference call call session. The menu can provide a list of parties obtained from a software application such as an electronic address book, or they can be added by the calling party in any other suitable manner. The calling party selects the parties, referred to as the called parties, which are to be included in the conference call. The VOIP terminal 12 receives the called party selections made by the calling party at 106.
0019The calling party then instructs the VOIP terminal 12 to call the called parties. The calling party can do so in a single action, such as with a mouse click or by pressing a call button to simply and automatically initiate the conference call.
0020Upon initiation of the call, the VOIP terminal software application engages in a call setup routine in which the VOIP terminal 12 sends called party identifiers to the calling party SCP 22 identifying each selected called party terminal. The called party terminal identifiers can be the PSTN directory numbers for each selected called party terminal used for routing calls and call information to/from the called party terminals over the PSTN 16. In one example, which should not be considered limiting, the VOIP terminal 12 combines the called party terminal identifiers into the VOIP packets 200 as shown in <figref idref="f0002">Fig. 3</figref>. Each VOIP packet 200 includes a VOIP header 202, the plurality of called party directory numbers 204a-204n, and a VOIP payload 206 having call information. The VOIP packets 200 can also include the IP address of the calling party VOIP gateway, the IP address of the IP gateway 24, and other information.
0021The SCP receives the VOIP packets sent by the VOIP terminal 12 over the packet data network 20 and creates a bridged call session connecting the called party terminals 14 with the calling party VOIP terminal 12 at 110. The IP gateway 24 can strip the called party directory numbers 204a-204n from the packets 200 and replicate the call information for each called party directory number. For each called party, the IP gateway can convert the VOIP call into a circuited call using the called party directory number. The Switching Center 26 can then create call sessions connecting the called party terminals 14 with the Switching Center using the called party directory numbers and bridge those call sessions together with the VOIP terminal 12 to create the bridged conference call enabling the all the parties to communicate.
0022If a called party does not answer at 112, the Switching Center 26 can drop that called party terminal from the bridged call session at 114. Further, if a called party hangs up during the call at 116, the Switching Center 26 can drop that called party terminal from the bridged call session. The VOIP terminal can end the call bridged call session at 118 by hanging up thereby disconnecting the VOIP call to the calling party SCP 22.
0023The above description merely provides a disclosure of particular embodiments of the invention and is not intended for the purposes of limiting the same thereto. As such, the invention is not limited to only the above-described embodiments. Rather, it is recognized that one skilled in the art could conceive alternative embodiments that fall within the scope of the invention.
Contents4
2 sheets
Sheet 1 Sheet 2
Every citation, both ways
| Document | Relation | Office |
|---|---|---|
| US2003185218A1 | Cites | United States of America |
| VINEET KUMAR, MARKKU KORPI, SENTHIL SENGODAN: "IP Telephony with H.323 - Architectures for Unified Networks and Integrated Services" 1 April 2001 (2001-04-01), WILEY , XP002371227 ISBN: 0-471-39343-6 * pages 145-166 * | Non-patent | – |
| IGOR FAYNBERG, LAWRENCE GABUZDA, HUI-LAN LU: "Converged Networks and Services - Internetworking IP and the PSTN" 2000, WILEY , XP002371228 ISBN: 0-471-35644-1 * pages 206-209 * * pages 230-232 * | Non-patent | – |
| SUN MICROSYSTEMS: "The JAIN APIs: Integrated Network APIs for the Java Platform" WHITE PAPER, [Online] October 2002 (2002-10), XP002371219 Retrieved from the Internet: URL:http://phoenix.labri.fr/documentation/ sip/Documentation/Papers/Programming_SIP/P aper_Publication_and_Draft/Java_SIP/WP2002 .pdf> [retrieved on 2006-03-07] | Non-patent | – |
| BURG A DESIMONE K T TEWANI AT&T LABS K VISHWANATHAN ISOCHRONE F M: "From Terminals Connected to a CallBroker over a TCP/IP Connection" IETF STANDARD-WORKING-DRAFT, INTERNET ENGINEERING TASK FORCE, IETF, CH, December 1997 (1997-12), XP015011259 ISSN: 0000-0004 | Non-patent | – |
9 members in 5 offices; this record represents the family
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 26815 | United States of America | – | |
| 2681504 | United States of America | A |
Members9
| Document | Office | Kind | |
|---|---|---|---|
| CN1798213A | China | A | |
| EP1677506A1 | European Patent Office (EPO) | A1 | |
| KR20060079109A | Republic of Korea | A | |
| US2006146793A1 | United States of America | A1 | |
| JP2006191578A | Japan | A | |
| US7693133B2 | United States of America | B2 | |
| CN1798213B | China | B | |
| EP1677506B1This record | European Patent Office (EPO) | B1 | |
| KR101206565B1 | Republic of Korea | B1 |
37 legal events, as 4 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| Application deemed withdrawn, or ip right lapsed, due to non-payment of renewal feeWithdrawnR119 | R119 | DE | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Fee paymentPLFP | PLFP | FR | |
| Lien (pledge) constitutedGC | GC | FR | |
| Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977)REGISTERED BETWEEN 20130926 AND 20131002732E | 732E | GB | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Party data changed (applicant data changed or rights of an application transferred)RAP1 | RAP1 | EP | |
| Party data changed (applicant data changed or rights of an application transferred)RAP1 | RAP1 | EP | |
| Title (correction)SYSTEM AND METHOD FOR CONFERENCE CALLING WITH VOIP TERMINALRTI1 | RTI1 | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Appeal procedure closedAppealORIGINAL CODE: EPIDOSNNOA9EAPBT | APBT | EP | |
| Party data changed (applicant data changed or rights of an application transferred)RAP3 | RAP3 | EP | |
| Appeal reference modifiedAppealORIGINAL CODE: EPIDOSCREFNEAPAF | APAF | EP | |
| Date of receipt of statement of grounds of appeal recordedAppealORIGINAL CODE: EPIDOSNNOA3EAPBR | APBR | EP | |
| Appeal reference recordedAppealORIGINAL CODE: EPIDOSNREFNEAPBK | APBK | EP | |
| Date of receipt of notice of appeal recordedAppealORIGINAL CODE: EPIDOSNNOA2EAPBN | APBN | EP | |
| Designation fees paidAKX | AKX | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 1677506
- Application
- 52577368
Titles3
- German
- System und Verfahren für Konferenzanrufe mittels eines VoIP-Terminals
- English
- System and method for conference calling with VoIP terminal
- French
- Système et procédé pour une audioconference avec un terminal VoIP
Classification
- CPC, 4
- H04M3/56
- H04L12/66
- H04M2207/203
- H04L12/28
- IPC, 2
- H04M3 56
- H04M7 00
Designated states3
- Contracting states, 3
- Germany
- France
- United Kingdom
