Patent Description:
<CIT> is directed generally to geographic referenced telephone switching. <NUM>-<NUM>-<NUM> emergency telephone calls are routed to alternative public safety answering points (PSAPs) based on the caller's location in relation to the proper emergency service provider and the availability of primary and backup PSAPs. Essentially the formatter gathers and verifies caller information, matches transmission formats with a determined call destination, generates and transmits a data communication with caller information, and terminates the phone call at the proper endpoint.

<CIT> discloses a method for communicating information associated with emergency calls communicated to emergency response centers including receiving, by an emergency call analysis system, emergency call information that defines an emergency call communicated to an emergency response center within a geographic region. The emergency call information includes location information of the emergency call. The emergency call analysis system may then determine statistical information associated with emergency calls made within a geographic region. A computer server may then generate browser code executable by a browser to cause the browser to display the statistical information.

The accompanying figures where like reference numerals refer to identical or functionally similar elements throughout the separate views, and which together with the detailed description below are incorporated in and form part of the specification, serve to further illustrate various embodiments and to explain various principles and advantages all in accordance with the present invention.

For example, the dimensions and/or relative positioning of some of the elements in the figures may be exaggerated relative to other elements to help to improve understanding of various embodiments of the present invention. Also, common but well-understood elements that are useful or necessary in a commercially feasible embodiment are often not depicted in order to facilitate a less obstructed view of these various embodiments of the present invention. It will further be appreciated that certain actions and/or steps may be described or depicted in a particular order of occurrence while those skilled in the art will understand that such specificity with respect to sequence is not actually required.

In order to address the above-mentioned need, a method and apparatus for displaying information regarding calls to a plurality of PSAPs is provided herein. During operation, an interface will display information as to whether a PSAP is receiving calls it normally would not be receiving, information as to whether or not a PSAP is not working correctly, and information on a status of any re-routed calls to a PSAP. In an alternate embodiment of the present invention, a reason for a PSAP call re-route in tabular fashion is also provided.

As one of ordinary skill in the art will recognize, a PSAP is preferably accessed by a user by dialing an emergency number. It should be noted that the term "emergency number" refers to the enhanced <NUM>, E-<NUM>, or E911. E911 is a system used in North America to automatically provide the caller's location and telephone number to <NUM> dispatchers at a PSAP. However, in other jurisdictions, the term "emergency number" encompasses any universal emergency telephone number in the region (e.g., European Union, <NUM>) utilized for non-anonymous reporting of public-safety incidents.

The calling of the emergency number results in the caller being directed to a live operator (dispatcher) at a PSAP, and information being provided to the operator about the caller (e.g., name, number, and location). Thus, regardless of the actual telephone number utilized, a call to an emergency number is routed to a PSAP, which is a call center operated by the local government. At the PSAP, the emergency call is answered by a specially trained official known as an emergency dispatcher or PSAP operator. The operator's computer receives information from the telephone company about the physical address (for landlines) or geographic coordinates (for wireless) of the caller. The dispatch operator is trained to collect pertinent information about the incident from the caller. This information is used to dispatch police, fire, medical, and other services as needed.

<FIG> illustrates a system for implementing the present invention showing several PSAPS <NUM>-<NUM>. System <NUM> includes one or more radio access networks (RANs) <NUM>, a public-safety core network <NUM>, device <NUM>, public network <NUM>, interfaces <NUM>, and emergency dispatch centers <NUM>-<NUM> serving as a PSAPs <NUM>-<NUM>, router <NUM>, officer <NUM>, and user <NUM>.

As shown in <FIG>, several separate networks exist, namely public-safety core network <NUM>, and public network <NUM> (e.g., Verizon, Spring, AT&T,. Public network <NUM> may be wired or wireless, and comprises a standard network configured to facilitate standard data transmission and calls between any device <NUM> and PSAPs <NUM>-<NUM>.

Each RAN <NUM> includes typical RAN elements such as base stations, base station controllers (BSCs), routers, switches, and the like, arranged, connected, and programmed to provide wireless service to user equipment (e.g., radio operated by officer <NUM>) in a manner known to those of skill in the relevant art.

In a similar manner, public network <NUM> includes elements (which may be shared) such as base stations, base station controllers (BSCs), routers, switches, and the like, arranged, connected, and programmed to provide data service to user equipment <NUM> (e.g., smart phone or computer <NUM> operated by user <NUM>) in a manner known to those of skill in the relevant art.

The public-safety core network <NUM> may include one or more packet-switched networks and/or one or more circuit-switched networks, and in general provides one or more public-safety agencies with any necessary computing and communication needs, transmitting any necessary public-safety-related data and communications to/from officer <NUM>.

Device <NUM> may be any suitable computing and communication devices configured to engage in wired or wireless communication over public network <NUM>. Such communication may comprise standard cellular data. For example, device <NUM> may comprise a mobile device running an Android ™ or iOS ™ operating system capable of placing calls to PSAPs <NUM>-<NUM> and receiving standard text messages from PSAPs <NUM>-<NUM>.

PSAPs <NUM>-<NUM> are preferably manned by an operator (also referred to as a dispatcher) and configured to receive emergency calls from device <NUM>, information about the call may be provided/forwarded to officer <NUM> (via core network <NUM> and RAN <NUM>).

PSAPs <NUM>-<NUM> comprises interface <NUM> that provides the dispatch operator necessary information about the call. Although interface <NUM> is shown existing within PSAPs <NUM>-<NUM>, in alternate embodiments, interface <NUM> may be located outside of PSAPs <NUM>-<NUM> and used to provide information about emergency calls to. When located outside of PSAPs <NUM>-<NUM>, interface <NUM> is connected to router <NUM> through an intervening network (e.g., networks <NUM> or <NUM>).

Router <NUM> is provided to receive calls to various PSAPs and route them accordingly. The routing of calls to various PSAPs typically occurs based on a location of caller <NUM>, so that typically the call is routed to a "primary" PSAP within a proper jurisdiction. However, there may be instances where the primary PSAP is offline, or otherwise unavailable. In this situation, a decision will be made by router <NUM> to route the call from user <NUM> to a "secondary" available PSAP (i.e., typically, a working PSAP that is closest geographically to caller <NUM>).

Information about the call, PSAPS, and routes is maintained within database <NUM>, which comprises standard memory (e.g., ROM). Such information includes, but is not limited to the callers telephone number, geographic locations for all PSAPs, a primary (first) PSAP identity where the call was attempted to be routed, a secondary (second) PSAP identity where the call was routed if the first PSAP was offline or otherwise unavailable, a third PSAP identity where the call was routed if the first and the second PSAP were offline or otherwise unavailable,. , etc. This is illustrated in Table <NUM>.

The information in Table <NUM> (or a portion of the information) is displayed on interface <NUM>. In one embodiment, only PSAPs that have been unsuccessfully routed to are displayed along with PSAPS where calls have been rerouted to. An example of this is shown in <FIG>.

As is evident, in <FIG>, interface <NUM> presents a first icon (or fist color PSAP) that is utilized to illustrate PSAPs that are unavailable, and a second icon (or second color PSAP) that is utilized to illustrate a PSAP that is available. Additionally, a first formatted line is presented to illustrate a successful re-route of a call, and a second formatted line is utilized to illustrate an unsuccessful re-rout of a call.

With the above in mind, <FIG> shows interface <NUM> presenting information that PSAP <NUM> is unavailable and a call to PSAP <NUM> has been successfully re-routed to PSAP <NUM>, as indicated by the solid line between PSAP <NUM> and PSAP <NUM>. Also shown in <FIG> interface <NUM> is presenting that PSAP <NUM> is unavailable, and a call to PSAP <NUM> was unsuccessfully re-routed to PSAP <NUM>, and ultimately successfully rerouted to PSAP <NUM>.

It should be noted that a further icon (or color of a PSAP) may be utilized to further distinguish a reason for a PSAP being unavailable. Thus, although not shown in <FIG>, a first icon (or similar icon with first PSAP color) may be used to designate PSAPs that are overloaded, while a second icon (or similar icon with a second PSAP color) may be used to designate PSAPs that are offline.

It should also be noted that all PSAPs and connecting lines in <FIG> may be displayed over a map, with the PSAPs being located at their approximate real-life geographic locations.

In an alternate embodiment, interface <NUM> is configured to present a textual (tabular) representation of the PSAPs <NUM> comprising a name of the first PSAP, the status of the first PSAP, a name of the second PSAP, and the status of the second PSAP. A time is also presented that includes a time in which the call was routed to each PSAP.

<FIG> is a block diagram of interface <NUM>. Interface <NUM> is capable of executing instructions (sequential or otherwise) that specify actions to be taken by the server. Interface <NUM> may include various components connected by bus <NUM>. Interface <NUM> may include hardware processor (logic circuitry) <NUM> such as one or more central processing units (CPUs) or other processing circuitry able to provide any of the functionality described herein when running instructions. Processor <NUM> may be connected to memory <NUM> that may include a non-transitory machine-readable medium on which is stored one or more sets of instructions. Memory <NUM> may include one or more of static or dynamic storage, or removable or non-removable storage, for example. A machine-readable medium may include any medium that is capable of storing, encoding, or carrying instructions for execution by processor <NUM>, such as solid-state memories, magnetic media, and optical media. Machine-readable medium may include, for example, Electrically Programmable Read-Only Memory (EPROM), Random Access Memory (RAM), or flash memory.

The instructions may enable interface <NUM> to operate in any manner thus programmed, such as the functionality described specifically herein (displaying PSAP status, etc.), when processor <NUM> executes the instructions. The machine-readable medium may be stored as a single medium or in multiple media, in a centralized or distributed manner. In some embodiments, instructions may further be transmitted or received over a communications network via a network interface <NUM> utilizing any one of a number of transfer protocols (e.g.,MPLS, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.).

Network interface <NUM> may thus enable interface <NUM> to communicate with router <NUM>, to access database <NUM> to access the information shown in Table <NUM>. Network interface <NUM> may include electronic components such as a transceiver that enables IP, serial or parallel communication. The wireless connections may use one or more protocols, including Institute of Electrical and Electronics Engineers (IEEE) Wi-Fi <NUM>, Long Term Evolution (LTE)/<NUM>, <NUM>, Universal Mobile Telecommunications System (UMTS), or peer-to-peer (P2P), for example, or short-range protocols such as Bluetooth, Zigbee, or near field communication (NFC). Wireless communication may occur in one or more bands, such as the <NUM>-<NUM> range, <NUM>-<NUM> range, <NUM>-<NUM> range, <NUM> range, and others, including infrared (IR) communications. Example communication networks to which camera may be connected via network interface <NUM> may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), and wireless data networks.

GUI <NUM> provides a mechanism for displaying information. For example, GUI <NUM> may provide a way for a user view information as shown in <FIG>. In order to provide the above features (and additional features), GUI <NUM> may comprise any combination of a touch screen, a computer screen, or any other interface needed to display information to the user.

Transceiver <NUM> comprises well known long-range transceivers that utilize any number of network system protocols. (As one of ordinary skill in the art will recognize, a transceiver comprises both a transmitter and a receiver for transmitting and receiving voice and data). For example, transceiver <NUM> may be configured to utilize IP, Internet or a next-generation cellular communications protocol operated by a cellular service provider, or any public-safety protocol such as an APCO <NUM> network or the FirstNet broadband network. Transceiver <NUM> allows communications with public-safety officers <NUM>.

As is evident, the interface <NUM> comprises network interface <NUM> configured to access database <NUM> and provide PSAP information to processor <NUM>. Processor <NUM> is configured to determine that an attempt was made to route an emergency call to a second public-safety access point (PSAP) because a first PSAP is overloaded or unavailable. Processor <NUM> is configured to cause GUI <NUM> to present a first icon representing the first PSAP at a first location, wherein a format of the first icon indicates a current status of the first PSAP, a second icon representing the second PSAP at a second location, wherein a format of the second icon indicates a current status of the second PSAP, and a path between the first PSAP and the second PSAP, wherein a format of the path indicates a status of whether or not the emergency call was successfully routed to the second PSAP.

As shown in <FIG>, the first icon, the second icon, and the path can be presented over a map, wherein the first icon and the second icon are located on the map at their real-life geographic locations. Additionally, the current status of PSAPs comprises whether or not the PSAP is overloaded, or whether or not the PSAP is unavailable or otherwise offline.

As shown in <FIG>, the database may be located on a router that routes emergency calls to various PSAPs and the format of the path may comprise a dashed line, a solid line, a first color, or a second color.

<FIG> is a flow chart showing operation of interface <NUM>. The logic flow begins at step <NUM> where logic circuitry <NUM> utilizes interface <NUM> to accesses database <NUM> to determine that an attempt was made to route an emergency call to a second public-safety access point (PSAP) because a first PSAP is overloaded or unavailable. At step <NUM> logic circuitry <NUM> causes information to be presented on electronic display <NUM> (GUI <NUM>). The information comprises a first icon representing the first PSAP, wherein a format of the first icon indicates a current status of the first PSAP, a second icon representing the second PSAP, wherein a format of the second icon indicates a current status of the second PSAP, and a path between the first PSAP and the second PSAP, wherein a format of the path indicates a status of whether or not the emergency call was successfully routed to the second PSAP.

As discussed above, in a further embodiment of the present invention, electronic display <NUM> may further display a name of the first PSAP, the status of the first PSAP, a name of the second PSAP, and the status of the second PSAP.

Those skilled in the art will further recognize that references to specific implementation embodiments such as "circuitry" may equally be accomplished via either on general purpose computing apparatus (e.g., CPU) or specialized processing apparatus (e.g., DSP) executing software instructions stored in non-transitory computer-readable memory. It will also be understood that the terms and expressions used herein have the ordinary technical meaning as is accorded to such terms and expressions by persons skilled in the technical field as set forth above except where different specific meanings have otherwise been set forth herein.

The invention is defined solely by the appended claims.

Moreover in this document, relational terms such as first and second, top and bottom, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms "comprises," "comprising," "has", "having," "includes", "including," "contains", "containing" or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises, has, includes, contains a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises. a", "includes. a", "contains. a" does not, without more constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises, has, includes, contains the element. The terms "a" and "an" are defined as one or more unless explicitly stated otherwise herein. The terms "substantially", "essentially", "approximately", "about" or any other version thereof, are defined as being close to as understood by one of ordinary skill in the art, and in one non-limiting embodiment the term is defined to be within <NUM>%, in another embodiment within <NUM>%, in another embodiment within <NUM>% and in another embodiment within <NUM>%. The term "coupled" as used herein is defined as connected, although not necessarily directly and not necessarily mechanically. A device or structure that is "configured" in a certain way is configured in at least that way, but may also be configured in ways that are not listed.

Moreover, an embodiment can be implemented as a computer-readable storage medium having computer readable code stored thereon for programming a computer (e.g., comprising a processor) to perform a method as described and claimed herein. Examples of such computer-readable storage mediums include, but are not limited to, a Virtualized, Cloud, a hard disk, a CD-ROM, an optical storage device, a magnetic storage device, a ROM (Read Only Memory), a PROM (Programmable Read Only Memory), an EPROM (Erasable Programmable Read Only Memory), an EEPROM (Electrically Erasable Programmable Read Only Memory) and a Flash memory. Further, it is expected that one of ordinary skill, notwithstanding possibly significant effort and many design choices motivated by, for example, available time, current technology, and economic considerations, when guided by the concepts and principles disclosed herein will be readily capable of generating such software instructions and programs and ICs with minimal experimentation.

Claim 1:
A method comprising:
accessing a database (<NUM>) to determine that an attempt was made to route an emergency call to a second public-safety access point, PSAP, (<NUM>) because a first PSAP (<NUM>) is overloaded or unavailable;
presenting on an electronic display (<NUM>):
a first icon representing the first PSAP (<NUM>), wherein a format of the first icon indicates a current status of the first PSAP (<NUM>),
a second icon representing the second PSAP (<NUM>), wherein a format of the second icon indicates a current status of the second PSAP (<NUM>); and
a path between the first PSAP (<NUM>) and the second PSAP (<NUM>), wherein a format of the path indicates a status of whether or not the emergency call was successfully routed to the second PSAP (<NUM>).