Network systems that allow callers to obtain emergency assistance generally do so by allowing a dispatcher to process emergency calls from the callers. In processing emergency calls, the dispatcher may contact potential responders, such as enterprise emergency response teams (ERTs) and/or loss prevention teams (LPTs), that are appropriate for responding to the emergency calls. Typically, a dispatcher has a line of communication with a caller, and a separate communication channel with an appropriate responder. The dispatcher then communicates directly with the caller and directly with an appropriate responder to communicate information provided by the caller to the appropriate responder. The caller and the appropriate responder do not communicate directly with one another.
The dispatcher effectively serves as an intermediary between the caller and an appropriate responder such as an ERT and/or a LPT. An overall system may alert a dispatcher of an affected location, e.g., conference the dispatcher in with a caller in need of assistance, and the dispatcher may then utilize a radio device to communicate with a potential responder to essentially direct the potential responder to support the affected location.
The invention may best be understood by reference to the following description taken in conjunction with the accompanying drawings in which:
In one embodiment, a method includes obtaining a request for a response, and identifying a first location from which the request originated. The request is obtained from a source that utilizes a phone and is located at the first location. The method also includes identifying at least one potential responder that may be capable or appropriate for providing the response. Finally, the method also includes creating a virtual talk group that includes the source and the potential responder. The potential responder may listen substantially directly to communications from the source within the virtual talk group using a land mobile radio.
An interoperability and collaboration system such as a push-to-talk management system which creates a virtual talk group that enables callers seeking emergency response to communicate substantially directly with potential responders allows information to be communicated between the callers and the potential responders in an efficient manner. The system or, more specifically, an internet protocol policy engine (IPPE) of the system, detects an emergency request, e.g., an E911 call, identifies the location from which the emergency request originated, and identifies potential responders in the vicinity of the location. The system creates a virtual talk group that includes the source of the emergency request, a dispatcher of the system, and the potential responders. In general, the system may substantially activate the virtual talk group such that the source of the emergency request and the potential responders may directly communicate.
When a system effectively connects the mobile communications devices or radios of a dispatcher, potential responders, and a requestor of an emergency response in a virtual talk group, the potential responders may listen in on communications between the dispatcher and the requestor. Hence, the potential responders may obtain details on the evolving event as described by the requestor, and may therefore respond more efficiently than if the details had to be relayed by through the dispatcher. Further, the potential responders may communicate directly with the requestor through the virtual talk group.
An interoperability and collaboration system such as the Cisco Internet Protocol Interoperability and Collaboration System (IPICS), which is available commercially from Cisco Systems, Inc., of San Jose, Calif., facilitates coordinated, interagency response for emergencies and day-to-day operations. Interoperability and collaboration systems allow radio networks, IP networks, non-IP networks, telephones, cell phones, and computing devices to communicate. When an interoperability and collaboration system detects a request for assistance, identifies the location from which the request originated, identifies potential responders to the request, and creates a virtual talk group that allows potential responders to obtain information substantially directly from the originator of the request, the potential responders may efficiently respond to the request.
In general, within an enterprise, a member of the enterprise may call E911 in search of assistance. An IPPE, e.g., IPPE 124, that is part of a communication system within the enterprise may intercept the call, and also allow the call to go through to E911. That is, IPPE 124 may patch a call which originated internally within the enterprise to enterprise safety and security personnel, while also enabling the call to be processed by the intended receiver of the E911 call.
Dispatcher arrangement 108 is arranged to identify potential responders from among responders 112a-e, and to create a virtual talk group that includes caller 104 and potential responders. Responders 112a-e may include, but are not limited to including, mobile security personnel, enterprise emergency response teams (ERTs) and/or loss prevention teams (LPTs). In one embodiment, dispatcher arrangement 108 may be a potential responder. A locator 116 of IPPE 124, which may include a global positioning system (GPS) locator, is arranged to determine the locations of responders 112a-e and to identify those responders 112a-e which are within a vicinity of caller 104. A virtual talk group arrangement 120 of IPPE 124 creates a suitable virtual talk group that includes potential responders and the caller 104.
As shown in
In one embodiment, responders 112a, 112d may have communications channels that are dedicated for use in receiving and transmitting emergency-related communications. Such communications channels may be used within virtual talk group 128 such that responders 112a, 112d may readily identify particular received transmissions as being associated with an unfolding emergency.
After the E911 call is received, the IPPE intercepts the call and determines the location from which the call is made, as well as a caller identifier (ID) of the caller, in step 309. In one embodiment, the location from which the call is made may be transmitted as part of the call control messages. In other example embodiments, the location information maybe transmitted as part of the media stream of the call, or as a separate stream altogether. Hence, determining the location may include identifying the location from which the call was placed. The location, which may be associated with a telephone number, may be stored by the IPPE or the dispatcher, as for example in a database, such that the dispatcher may access the location in the event that the E911 call is prematurely terminated. In another example embodiment, the location of the caller may be provided by the endpoint of the caller or by an appropriate service provider.
In step 313, the IPPE identifies potential responders that are within the vicinity of the location. It should be appreciated that potential responders that are considered as being in the vicinity of the location may vary. In other words, the definition of “vicinity” may vary depending upon the requirements of an overall system. For instance, the vicinity within which potential responders are located may be defined in terms of a radius around the location. Any ERTs and/or LPTs within the radius defined around the location may be considered to be potential responders. Alternatively, any available ERTs and/or LPTS within such a radius may be considered to be potential responders.
Once potential responders are identified, the IPPE effectively notifies or alerts potential responders of the E911 call from the caller in step 317, and hence, of a situation in which the potential responders may be of service. The steps associated with one method of notifying potential responders of an E911 call will be described below with reference to
A determination is made in step 325 regarding whether the dispatcher has prematurely lost communication with the caller. Such a determination may be made, in one embodiment, if the IPPE determines that the call terminated prematurely based on a disconnect cause, the IPPE dials the caller and attempts to reconnect the caller to the virtual talk group that has been established for the event. In another example embodiment, the dispatcher is able to provide an indication to the IPPE that the call has been terminated prematurely, and requests that the IPPE reconnect the caller to the virtual talk group for the specific event. If the determination is that communication has not been prematurely lost, e.g., that the connection to the caller has not been terminated before the dispatcher believes there has been a successful resolution to the call, the caller, the potential responders, and the dispatcher communicate as appropriate within the virtual talk group in step 329. That is, the caller may provide information regarding the event unfolding at his location substantially directly to the dispatcher and the potential responders. Process flow then returns to step 325 and the determination of whether the dispatcher and the potential responders have prematurely lost a connection with the caller.
If it is determined that the dispatcher and the potential responders have prematurely lost communication with the caller, process flow proceeds to step 331 in which the IPPE deactivates the virtual talk group. Then, in step 333, the IPPE places an outbound call to the caller. In one embodiment, the IPPE is able to call or otherwise access the caller to re-establish a connection using information such as the caller ID of the caller that was determined in step 309. As previously mentioned, the location information and the caller ID may be stored in a database, although it should be appreciated that the IPPE may instead capture the caller ID of the caller and use that to re-establish a connection with the caller. Once the IPPE places an outbound call to the caller and reconnects with the caller, the IPPE reactivates the virtual talk group in step 337. Process flow then returns to step 329 in which the caller, the potential responders, and the dispatcher communicate as appropriate within the virtual talk group.
With reference to
Once the IPPE determines the channel or multicast address associated with each potential responder, the IPPE sends a signal to each potential responder on the appropriate associated channel or multicast address in step 409. In one embodiment, the signal may be an alert such as a blinking indicator that indicates to a potential responder that there is an E911 call to which the potential responder is invited to join. That is, the IPPE sends an indication to potential responders that responder for an emergency call is requested.
After the IPPE sends a signal to each potential responder, the IPPE detects in step 413 when the potential responders each acknowledge the signal. When the IPPE detects that a potential responder has acknowledged the signal, i.e., has indicated an intent to effectively join the E911 call, the IPPE may add the potential responder to a virtual talk group that includes the dispatcher and the E911 caller. The process of notifying potential responders is completed once the potential responders acknowledge an alert to effectively join an E911 call.
Referring next to
After an alert is received, a potential responder may acknowledge the alert in step 509. Once the potential responder acknowledges the alert, the potential responder joins an appropriate virtual talk group in step 511, and the process of becoming a part of a virtual talk group associated with an E911 call is completed.
With reference to
An IPPE 624 of IPICS server 610 includes GPS receiving device 616 that allows IPICS server 610 to locate client 612. Specifically, a GPS transmitter 658 of client 612 may transmit location information associated with client 612 that is received on GPS receiving device 616. Using the transmitted location information, IPPE 624 may determine whether client 612 is suitable as a potential responder to E911 caller 604.
IPPE 624 also includes a virtual talk group creator 620 that is configured to create a virtual talk group that includes client 612, E911 caller 604, and a dispatcher 608 associated with IPICS server 610, if client 612 is a suitable potential responder to E911 caller 604. Virtual talk group creator 620 includes a radio connector 654 that allows the radios or communications devices of dispatcher 608, E911 caller 604, and client 612 to communicate. As previously mentioned, the communication device used by E911 caller 604 is typically a phone. In the embodiment as shown, radio connector 654 includes a stereo controller 662 that is arranged to vary the audio signals received by client 612. By way of example, when IPPE 624 detects that client 612 has accepted an invitation to join a virtual talk group, stereo controller 662 may place signals transmitted within the VTG on a relatively low priority channel of client 612. Stereo controller 662 may be arranged to place audio from a caller to E911 in a right ear, as is often associated with important communication, a left ear, or both ears. That is, stereo controller 662 may place audio into different ears as appropriate within an overall system to indicate that the audio is associated with an E911 call.
Although only a few embodiments of the present invention have been described, it should be understood that the present invention may be embodied in many other specific forms without departing from the spirit or the scope of the present invention. By way of example, any number of potential responders may generally be included in a virtual talk group. However, the number of potential responders may be limited by an IPPE such that when a predetermined number of potential responders respond to alerts or invitations to join a virtual talk group, other potential responders may be prevented from joining the virtual talk group. Alternatively, as soon as a predetermined number of potential responders indicate that they are taking ownership of an unfolding event, other potential responders may be allowed to listen in on communications in a virtual talk group, but at a lower priority. For instance, potential responders who take ownership of an unfolding event may hear conversations involving a virtual talk group on a right speaker of a push-to-talk management client, while potential responders who do not have ownership of the unfolding event may hear the conversations on a left speaker.
While it has been described that a virtual talk group includes potential responders who are within a vicinity of a requestor or E911 caller, it should be appreciated that a virtual talk group may include potential responders that are not within a predefined vicinity of the requestor. That is, substantially any responder who is accessible to an IPPE may be considered to be a potential responder. In one embodiment, the IPPE of a system may effectively create a virtual talk group that includes substantially all ERTs and/or LPTs that are associated with the system.
The steps associated with the methods of the present invention may vary widely. Steps may be added, removed, altered, combined, and reordered without departing from the spirit of the scope of the present invention. For instance, a dispatcher may deactivate a virtual talk group if it is determined that an appropriate responder has responded to an E911 call, or if a request associated with an E911 call has been otherwise accommodated. A dispatcher may also determine a type of response required by the request before identifying potential responders. Therefore, the present examples are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope of the appended claims.
Number | Name | Date | Kind |
---|---|---|---|
4931780 | LaMont et al. | Jun 1990 | A |
5387905 | Grube et al. | Feb 1995 | A |
5471646 | Schultz | Nov 1995 | A |
5515043 | Berard et al. | May 1996 | A |
5754960 | Downs et al. | May 1998 | A |
5960337 | Brewster et al. | Sep 1999 | A |
6002941 | Ablay et al. | Dec 1999 | A |
6204844 | Fumarolo et al. | Mar 2001 | B1 |
6246752 | Bscheider et al. | Jun 2001 | B1 |
6249570 | Glowny et al. | Jun 2001 | B1 |
6252946 | Glowny et al. | Jun 2001 | B1 |
6252947 | Diamond et al. | Jun 2001 | B1 |
6327342 | Mobley et al. | Dec 2001 | B1 |
6366782 | Fumarolo et al. | Apr 2002 | B1 |
6421009 | Suprunov | Jul 2002 | B2 |
6477387 | Jackson et al. | Nov 2002 | B1 |
6545606 | Piri et al. | Apr 2003 | B2 |
6687504 | Raith | Feb 2004 | B1 |
6711247 | Needham et al. | Mar 2004 | B1 |
6728345 | Glowny et al. | Apr 2004 | B2 |
6785369 | Diamond et al. | Aug 2004 | B2 |
6785370 | Glowny et al. | Aug 2004 | B2 |
6799049 | Zellner et al. | Sep 2004 | B1 |
6865185 | Patel et al. | Mar 2005 | B1 |
6865460 | Bray et al. | Mar 2005 | B2 |
6882856 | Alterman et al. | Apr 2005 | B1 |
6937706 | Bscheider et al. | Aug 2005 | B2 |
6965816 | Walker | Nov 2005 | B2 |
7031700 | Weaver et al. | Apr 2006 | B1 |
7058385 | Lauper | Jun 2006 | B2 |
7069016 | Crisler et al. | Jun 2006 | B2 |
7124188 | Mangipudi et al. | Oct 2006 | B2 |
7148797 | Albert | Dec 2006 | B2 |
7251470 | Faucher et al. | Jul 2007 | B2 |
7321926 | Zhang et al. | Jan 2008 | B1 |
7395204 | VanderBaan et al. | Jul 2008 | B2 |
7406710 | Zellner et al. | Jul 2008 | B1 |
7440442 | Grabelsky et al. | Oct 2008 | B2 |
7472412 | Wolf et al. | Dec 2008 | B2 |
7580706 | Koren et al. | Aug 2009 | B2 |
7584262 | Wang et al. | Sep 2009 | B1 |
7616936 | Shaffer et al. | Nov 2009 | B2 |
7633914 | Shaffer et al. | Dec 2009 | B2 |
7636339 | Shaffer et al. | Dec 2009 | B2 |
7639634 | Shaffer et al. | Dec 2009 | B2 |
7668925 | Liao et al. | Feb 2010 | B1 |
7702081 | Klesper et al. | Apr 2010 | B1 |
7706339 | Shaffer et al. | Apr 2010 | B2 |
7711375 | Liu | May 2010 | B2 |
7711820 | Sharma et al. | May 2010 | B2 |
7751348 | Shaffer et al. | Jul 2010 | B2 |
7764973 | Shaffer et al. | Jul 2010 | B2 |
7792899 | Shaffer et al. | Sep 2010 | B2 |
7809390 | Shaffer et al. | Oct 2010 | B2 |
7813750 | Hobby et al. | Oct 2010 | B2 |
7831270 | Kalley et al. | Nov 2010 | B2 |
7836177 | Kasriel et al. | Nov 2010 | B2 |
7840514 | Keith, Jr. | Nov 2010 | B2 |
7860070 | Shaffer et al. | Dec 2010 | B2 |
7869361 | Balay et al. | Jan 2011 | B2 |
7869386 | Shaffer et al. | Jan 2011 | B2 |
7873345 | Dunne et al. | Jan 2011 | B1 |
7885674 | Shaffer et al. | Feb 2011 | B2 |
8014324 | Oliveira et al. | Sep 2011 | B2 |
20010040942 | Glowny et al. | Nov 2001 | A1 |
20010043685 | Bscheider et al. | Nov 2001 | A1 |
20010055372 | Glowny et al. | Dec 2001 | A1 |
20020035616 | Diamond et al. | Mar 2002 | A1 |
20020077075 | Ikonen et al. | Jun 2002 | A1 |
20020086659 | Lauper | Jul 2002 | A1 |
20020102961 | Gibbons et al. | Aug 2002 | A1 |
20030093187 | Walker | May 2003 | A1 |
20040029558 | Liu | Feb 2004 | A1 |
20040121782 | Tester | Jun 2004 | A1 |
20040259581 | Crisler et al. | Dec 2004 | A1 |
20040266390 | Faucher et al. | Dec 2004 | A1 |
20050162306 | Babitch et al. | Jul 2005 | A1 |
20050187677 | Walker | Aug 2005 | A1 |
20050239436 | Bell et al. | Oct 2005 | A1 |
20050282518 | D'Evelyn et al. | Dec 2005 | A1 |
20060046697 | Koren et al. | Mar 2006 | A1 |
20060080344 | McKibben et al. | Apr 2006 | A1 |
20060114941 | Silverman et al. | Jun 2006 | A1 |
20060120516 | Armbruster et al. | Jun 2006 | A1 |
20060171520 | Kliger | Aug 2006 | A1 |
20060183460 | Srinivasan et al. | Aug 2006 | A1 |
20060208888 | Patel et al. | Sep 2006 | A1 |
20060224797 | Parish et al. | Oct 2006 | A1 |
20070004389 | Wallace et al. | Jan 2007 | A1 |
20070036100 | Shaffer et al. | Feb 2007 | A1 |
20070036118 | Shaffer et al. | Feb 2007 | A1 |
20070037596 | Shaffer et al. | Feb 2007 | A1 |
20070047479 | Shaffer et al. | Mar 2007 | A1 |
20070088836 | Tai et al. | Apr 2007 | A1 |
20070092070 | Croy et al. | Apr 2007 | A1 |
20070104121 | Shaffer et al. | May 2007 | A1 |
20070105578 | Shaffer et al. | May 2007 | A1 |
20070105579 | Shaffer et al. | May 2007 | A1 |
20070123271 | Dickinson | May 2007 | A1 |
20070159354 | Rosenberg | Jul 2007 | A1 |
20070180140 | Welch et al. | Aug 2007 | A1 |
20070201376 | Marshall-Wilson | Aug 2007 | A1 |
20070202907 | Shaffer et al. | Aug 2007 | A1 |
20070202908 | Shaffer et al. | Aug 2007 | A1 |
20070226310 | Shaffer et al. | Sep 2007 | A1 |
20070229274 | Patel et al. | Oct 2007 | A1 |
20070229350 | Scalisi et al. | Oct 2007 | A1 |
20070232293 | Goldman et al. | Oct 2007 | A1 |
20070239824 | Shaffer et al. | Oct 2007 | A1 |
20070270172 | Kalley et al. | Nov 2007 | A1 |
20070280195 | Shaffer et al. | Dec 2007 | A1 |
20080037461 | Biltz et al. | Feb 2008 | A1 |
20080037715 | Prozeniuk et al. | Feb 2008 | A1 |
20080071984 | Araki et al. | Mar 2008 | A1 |
20080102869 | Shaffer et al. | May 2008 | A1 |
20080153455 | Lancaster | Jun 2008 | A1 |
20080159128 | Shaffer et al. | Jul 2008 | A1 |
20080159490 | Gaudin et al. | Jul 2008 | A1 |
20080166992 | Ricordi et al. | Jul 2008 | A1 |
20080181145 | Chowdhury et al. | Jul 2008 | A1 |
20080220765 | Chu et al. | Sep 2008 | A1 |
20080220801 | Hobby et al. | Sep 2008 | A1 |
20080242247 | Shaffer et al. | Oct 2008 | A1 |
20080280637 | Shaffer et al. | Nov 2008 | A1 |
20080299940 | Shaffer et al. | Dec 2008 | A1 |
20080311894 | Klein et al. | Dec 2008 | A1 |
20090041206 | Hobby et al. | Feb 2009 | A1 |
20090054010 | Shaffer et al. | Feb 2009 | A1 |
20090054098 | Jorgensen | Feb 2009 | A1 |
20090125332 | Martin | May 2009 | A1 |
20090147702 | Buddhikot et al. | Jun 2009 | A1 |
20090168685 | Olivier et al. | Jul 2009 | A1 |
20090215411 | Tucker et al. | Aug 2009 | A1 |
20090254392 | Zander | Oct 2009 | A1 |
20100159975 | Shaffer et al. | Jun 2010 | A1 |
20100197333 | Shaffer et al. | Aug 2010 | A1 |
Number | Date | Country |
---|---|---|
0967820 | Dec 1999 | EP |
Number | Date | Country | |
---|---|---|---|
20080299940 A1 | Dec 2008 | US |