|Publication number||US8111636 B2|
|Application number||US 12/647,483|
|Publication date||Feb 7, 2012|
|Priority date||Feb 2, 2005|
|Also published as||US7664058, US20100097961|
|Publication number||12647483, 647483, US 8111636 B2, US 8111636B2, US-B2-8111636, US8111636 B2, US8111636B2|
|Inventors||Karrie Hanson, Gerald Karam|
|Original Assignee||At&T Intellectual Property Ii, L.P.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (24), Classifications (7), Legal Events (7)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application is a continuation of U.S. patent application Ser. No. 11/049,530, filed Feb. 2, 2005, now U.S. Pat. No. 7,664,058, and is herein incorporated by reference in its entirety.
The present invention relates generally to communication networks and, more particularly, to an apparatus and method for simultaneously broadcasting a message to a plurality of endpoint devices.
In some situations it may be necessary for a person to speak with a number of people at once at the spur of the moment. For example, a parent may wish to call all their teenage children at the end of the school day to arrange the rest of the afternoon. Or a person may wish to call a group of friends to plan an outing. Also, a member of a work group may wish to call a group of experts to solve an urgent problem. People are now frequently faced with problems that require the input of multiple people to find an optimal solution. With the ubiquitous presence of cell phones, this kind of “spontaneous meeting” is possible. Indeed, because cell phones are most often associated with a single person's address, rather than a residential or group address, services can now be offered based on the assumption that the recipient of the call is the person who answered the telephone.
This kind of need is normally solved by conference calls, and in particular reservationless conference calls. However, conventional conference calls require the use of bridge resources and only support conferencing, not messaging and automatic reconnection of participants.
Therefore, a need exists for a method and apparatus for providing simultaneous broadcasting of a message to a plurality of endpoint devices.
In one embodiment, the present invention provides a method for simultaneously broadcasting a message to a plurality of end-point devices. More specifically, the present invention receives a request to initiate a teleconference from a subscriber. The plurality of end-point devices is then invited to join the teleconference.
The teaching of the present invention can be readily understood by considering the following detailed description in conjunction with the accompanying drawings, in which:
To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures.
To better understand the present invention,
The customer endpoint devices can be either Time Division Multiplexing (TDM) based or IP based. TDM based customer endpoint devices 122, 123, 134, and 135 typically comprise of TDM phones or Private Branch Exchange (PBX). IP based customer endpoint devices 144 and 145 typically comprise IP phones or PBX. The Terminal Adaptors (TA) 132 and 133 are used to provide necessary interworking functions between TDM customer endpoint devices, such as analog phones, and packet based access network technologies, such as Digital Subscriber Loop (DSL) or Cable broadband access networks. TDM based customer endpoint devices access VoIP services by using either a Public Switched Telephone Network (PSTN) 120, 121 or a broadband access network via a TA 132 or 133. IP based customer endpoint devices access VoIP services by using a Local Area Network (LAN) 140 and 141 with a VoIP gateway or router 142 and 143, respectively.
A wireless access provider 170, 180 is used to provide access for wireless endpoint devices 175, 185. Although
The access networks can be either TDM or packet based. A TDM PSTN 120 or 121 is used to support TDM customer endpoint devices connected via traditional phone lines. A packet based access network, such as Frame Relay, ATM, Ethernet or IP, is used to support IP based customer endpoint devices via a customer LAN, e.g., 140 with a VoIP gateway and router 142. A packet based access network 130 or 131, such as DSL or Cable, when used together with a TA 132 or 133, is used to support TDM based customer endpoint devices.
The core VoIP infrastructure comprises of several key VoIP components, such the Border Element (BE) 112 and 113, the Call Control Element (CCE) 111, and VoIP related servers 114. The BE resides at the edge of the VoIP core infrastructure and interfaces with customers endpoints over various types of access networks. A BE is typically implemented as a Media Gateway and performs signaling, media control, security, and call admission control and related functions. The CCE resides within the VoIP infrastructure and is connected to the BEs using the Session Initiation Protocol (SIP) over the underlying IP/MPLS based core backbone network 110. The CCE is typically implemented as a Media Gateway Controller and performs network wide call control related functions as well as interacts with the appropriate VoIP service related servers when necessary. The CCE functions as a SIP back-to-back user agent and is a signaling endpoint for all call legs between all BEs and the CCE. The CCE may need to interact with various VoIP related servers in order to complete a call that require certain service specific features, e.g. translation of an E.164 voice network address into an IP address.
For calls that originate or terminate in a different carrier, they can be handled through the PSTN 120 and 121 or the Partner IP Carrier 160 interconnections. For originating or terminating TDM calls, they can be handled via existing PSTN interconnections to the other carrier. For originating or terminating VoIP calls, they can be handled via the Partner IP carrier interface 160 to the other carrier.
In order to illustrate how the different components operate to support a VoIP call, the following call scenario is used to illustrate how a VoIP call is setup between two customer endpoints. A customer using IP device 144 at location A places a call to another customer at location Z using TDM device 135. During the call setup, a setup signaling message is sent from IP device 144, through the LAN 140, the VoIP Gateway/Router 142, and the associated packet based access network, to BE 112. BE 112 will then send a setup signaling message, such as a SIP-INVITE message if SIP is used, to CCE 111. CCE 111 looks at the called party information and queries the necessary VoIP service related server 114 to obtain the information to complete this call. If BE 113 needs to be involved in completing the call; CCE 111 sends another call setup message, such as a SIP-INVITE message if SIP is used, to BE 113. Upon receiving the call setup message, BE 113 forwards the call setup message, via broadband network 131, to TA 133. TA 133 then identifies the appropriate TDM device 135 and rings that device. Once the call is accepted at location Z by the called party, a call acknowledgement signaling message, such as a SIP-ACK message if SIP is used, is sent in the reverse direction back to the CCE 111. After the CCE 111 receives the call acknowledgement message, it will then send a call acknowledgement signaling message, such as a SIP-ACK message if SIP is used, toward the calling party. In addition, the CCE 111 also provides the necessary information of the call to both BE 112 and BE 113 so that the call data exchange can proceed directly between BE 112 and BE 113. The call signaling path 150 and the call data path 151 are illustratively shown in
Note that a customer in location A using any endpoint device type with its associated access network type can communicate with another customer in location Z using any endpoint device type with its associated network type as well. For instance, a customer at location A using IP customer endpoint device 144 with packet based access network 140 can call another customer at location Z using TDM endpoint device 123 with PSTN access network 121. The BEs 112 and 113 are responsible for the necessary signaling protocol translation, e.g., SS7 to and from SIP, and media format conversion, such as TDM voice format to and from IP based packet voice format.
Although the present invention is described in the context of SIP, It should be understood that the present invention can be employed in any signaling protocols. Furthermore, the present invention can be employed in signaling protocols that are compliant to various signaling standards or their variants.
In some situations it may be necessary for a person to speak with a number of people at once at the spur of the moment. This kind of need is normally solved by conference calls, and in particular reservationless conference calls. However, conventional conference calls require the use of bridge resources and only support conferencing, not messaging and automatic reconnection of participants. The present invention provides simultaneous broadcasting of a message to a plurality of endpoint devices.
In one embodiment, the Huddle service may be launched over the internet. In this embodiment, the call is initiated via the internet. A subscriber is able to monitor and interact with the Huddle service via the internet. A record of the Huddle is maintained on a website. Thus, a subscriber would be able to monitor who is joining the huddle by viewing the website. A subscriber would also be able to ascertain when messages are received by the Huddle service on the web. Received messages may be listened to by the subscriber via the web as well. When the Huddle is over, the subscriber has a record of any messages that were delivered on the Huddle and who actually participated.
In step 310, a request to initiate a teleconference is received. Prior to initiating a request for a teleconference a subscriber establishes at least one group of attendees to be invited to a gathering. Each group has a group name, and each group comprises the name, telephone number and, optionally, the email address for each member of the group. The group may either be stored in the endpoint device or in application/media server 213. The subscriber initiates a “Gathering” or “Huddle” feature. Once the Huddle feature is initiated, the subscriber records a greeting for the huddle.
In step 315, the plurality of end-point devices is invited to join the teleconference. The Huddle service places a phone call via CCE 211 and pertinent BES to huddle attendees. When an attendee answers their phone, they hear the greeting recorded by the subscriber who initiated the huddle followed by the Gathering or Huddle menu. In one embodiment, the attendee hears an invitation generated by the Huddle Service. The Huddle service allows an attendee to join the huddle, send a reply, or decline the invitation to the huddle.
If the attendee opts to “join”, the attendee is connected with the subscriber. If there is only one attendee to the huddle, the call is treated as a person-to-person call. If more than one attendee elects to join, then the call becomes a conference call (e.g., the Huddle service sets up a conference bridge).
In one embodiment, when only one attendee has joined the huddle and a point-to-point call has been established, a subsequent attendee may elect to join the huddle. In this embodiment, application server 213 detects that greater than two people need to join the huddle. Then the application server 213 sets up a conference bridge. Call control element 211 causes the pertinent border elements to connect a media path of the attendees to the conference bridge.
If the attendee opts to “reply”, the attendee records a reply, sends the reply, and then hangs up. If there are no attendees on the call, the reply message is played to the subscriber. If there are one or more attendees on the call, the reply is played to all who are present on the call. The gathering is over when the subscriber indicates an “end” to the gathering.
If any attendees fail to answer their phone when invited by the Huddle feature, the attendees will see a call from the subscriber's service phone number. In one embodiment, a message may be left on the voice mail system of the attendee by the Huddle service. This message includes a return phone number for the gathering. If the attendee returns the call to the subscriber's service number while the gathering is still active, the attendee will hear the greeting and the Huddle menu. If the Huddle is over, the call is forwarded to the subscriber.
If the subscriber chooses to end the Huddle, the subscriber has the option of sending a message to all the members of the group who did not attend. This is done by recording a voice message and having it delivered to the attendees. The message could be delivered to either voice mail or email systems. The subscriber can end a call and without terminating the gathering, in which case if a recipient attempts to contact the gathering, a call to the subscriber is re-established.
The present invention is more flexible than a dynamic conference call or even 3-way style calling since it does not require knowledge of recipients of a conference bridge, or a requirement of the subscriber to place calls to all recipients and coordinate with them. Indeed a conference bridge may not be needed at all depending on the order in which participants join the gathering. The present invention produces more convenient results for end users and more efficient resource usage for service providers.
It should be noted that the present invention can be implemented in software and/or in a combination of software and hardware, e.g., using application specific integrated circuits (ASIC), a general purpose computer or any other hardware equivalents. In one embodiment, the huddle module 405 can be loaded into memory 404 and executed by processor 402 to implement the functions as discussed above. As such, huddle module 405 (including associated data structures) of the present invention can be stored on a computer readable medium or carrier, e.g., RAM memory, magnetic or optical drive or diskette and the like.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, and not limitation. Thus, the breadth and scope of a preferred embodiment should not be limited by any of the above-described exemplary embodiments, but should be defined only in accordance with the following claims and their equivalents.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5778053 *||Dec 21, 1995||Jul 7, 1998||Intel Corporation||Answering machine services for data conferences|
|US6011782||May 8, 1997||Jan 4, 2000||At&T Corp.||Method for managing multicast addresses for transmitting and receiving multimedia conferencing information on an internet protocol (IP) network|
|US6028922 *||Sep 3, 1997||Feb 22, 2000||Lucent Technologies Inc.||System for deferred call answering in a telecommunications system|
|US6363411 *||Oct 19, 1999||Mar 26, 2002||Mci Worldcom, Inc.||Intelligent network|
|US6628767 *||Nov 27, 1999||Sep 30, 2003||Spiderphone.Com, Inc.||Active talker display for web-based control of conference calls|
|US6674459 *||Oct 24, 2001||Jan 6, 2004||Microsoft Corporation||Network conference recording system and method including post-conference processing|
|US6873627||Jul 30, 1999||Mar 29, 2005||The Fantastic Corporation||System and method for sending packets over a computer network|
|US6996414||Apr 30, 2001||Feb 7, 2006||Motorola, Inc.||System and method of group calling in mobile communications|
|US7277697||May 24, 2004||Oct 2, 2007||Adesh Desai||Method and system for establishing a teleconference over a telephony network|
|US7330540||May 21, 2003||Feb 12, 2008||Qwest Communications International Inc.||Systems and methods for providing conference communication|
|US7418090 *||Nov 24, 2003||Aug 26, 2008||Telesector Resources Group Inc.||Methods and systems for conference call buffering|
|US7664058||Feb 16, 2010||At&T Corp.||Method and apparatus for providing spontaneous multi-way telephone conversation with inserted messaging|
|US7804948 *||Sep 28, 2010||Linqware, Inc.||System and method for initiating a conference call|
|US20030108002||Jan 30, 2002||Jun 12, 2003||Adam Chaney||System and method for establishing a conference call|
|US20030118167||Feb 11, 2003||Jun 26, 2003||Call Sciences||Personal web-based teleconferencing method and system|
|US20050058125||Mar 15, 2004||Mar 17, 2005||Nokia Corporation||IP-based services for circuit-switched networks|
|US20050074107 *||Jul 21, 2004||Apr 7, 2005||Renner W. Karl||Conference calls via an intelligent call waiting interface|
|US20050101303 *||Nov 10, 2003||May 12, 2005||Lucent Technologies Inc.||Method and system for sending personalized outgoing voicemail/multimedia mail messages based on the caller ID|
|US20050281208||Jun 17, 2004||Dec 22, 2005||Motorola, Inc.||Session control using a multicast address|
|US20060041688||Dec 30, 2004||Feb 23, 2006||Bellsouth Intellectual Property Corporation||SIP-based session control among a plurality of multimedia devices|
|US20060088152||Oct 21, 2004||Apr 27, 2006||Lightbridge, Inc.||Conference-call initiation|
|US20060250987 *||Feb 11, 2004||Nov 9, 2006||Christopher White||Conference call facility|
|US20070064898 *||Aug 2, 2006||Mar 22, 2007||Kiyoshi Amano||Telephone conference system|
|US20090097627 *||Feb 8, 2005||Apr 16, 2009||Liljestrand Keith A||Apparatus and method for providing enhanced telecommunications services|
|U.S. Classification||370/260, 379/202.01|
|Cooperative Classification||H04L65/403, H04L12/1818, H04L12/1822|
|Feb 7, 2011||AS||Assignment|
Owner name: AT&T CORP., NEW YORK
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HANSON, KARRIE;KARAM, GERALD;REEL/FRAME:025752/0061
Effective date: 20050202
|Jun 20, 2012||AS||Assignment|
Owner name: AT&T PROPERTIES, LLC, NEVADA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T CORP.;REEL/FRAME:028410/0947
Effective date: 20120620
|Jun 21, 2012||AS||Assignment|
Owner name: AT&T INTELLECTUAL PROPERTY II, L.P., GEORGIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T PROPERTIES, LLC;REEL/FRAME:028420/0305
Effective date: 20120620
|Oct 2, 2012||AS||Assignment|
Owner name: JEFFERSON VALLEY, LLC, CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:AT&T INTELLECTUAL PROPERTY II, L.P.;REEL/FRAME:029057/0932
Effective date: 20120810
|Jun 28, 2013||AS||Assignment|
Owner name: INTELLECTUAL DISCOVERY CO., LTD., KOREA, REPUBLIC
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:JEFFERSON VALLEY, LLC;REEL/FRAME:030708/0321
Effective date: 20130604
|Mar 11, 2014||RF||Reissue application filed|
Effective date: 20140207
|Jul 28, 2015||FPAY||Fee payment|
Year of fee payment: 4