IP Library Granted Patent US 9,706,351
Granted Patent B1
US 9,706,351 · App. 15/142,185 · Granted Jul 11, 2017

Emergency call over a data network

Inventor: James E. Brewer (Chicago, IL)
Assignee: PEERLESS NETWORK, INC.
H04W4/02H04L65/1006H04L69/22H04W4/22H04W40/02H04M7/006
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,706,351
App. No.
15/142,185
Granted
Jul 11, 2017
Kind
B1
Abstract

Techniques for originating an emergency call over a data network include determining whether or not a location services are currently available. Call control may be released to the native dialer when the location services are currently unavailable. Otherwise, the call may be processed by the application dialer, and may be routed from the mobile device towards a Public Safety Answering Point (PSAP) by using a private packet backbone network exchange. The application dialer may be configured to utilize a packet header format that indicates a geographic location of the mobile device when communicating with an emergency call router interconnected with the private packet backbone network exchange.

Claims (31)

1. A mobile device, comprising:

an application that includes an application dialer communicatively connected to a wireless communication interface, wherein the application is configured to:

receive user input indicative of an emergency call;

determine whether location services are currently available for the mobile device;

when the location services are currently unavailable, pass control to a native dialer to originate, via the wireless communication interface, the emergency call; and

when the location services are currently available:

determine a geographic location of the mobile device based upon an output from an API supported by an operating system of the mobile device, wherein the geographic location of the mobile device is not an IP address; and

communicate, via the wireless communication interface, with an emergency call router, wherein data packets forming communications with the emergency call router utilize a packet header format that indicates the geographic location.

2. The mobile device of claim 1 , wherein the application communicates with the emergency call router by routing the data packets over a private packet network exchange.

3. The mobile device of claim 1 , wherein the native dialer is factory installed onto the mobile device, and the application dialer is a default dialer of the mobile device.

4. The mobile device of claim 1 , to pass control to the native dialer, the application dialer is further configured to utilize an intent to originate the emergency call via the native dialer.

5. The mobile device of claim 1 , wherein when the location services are currently available, the application dialer originates, via the wireless communication interface, the emergency call.

6. The mobile device of claim 5 , wherein the application is further configured to cause the mobile device to enter a pseudo-emergency mode when the application dialer originates the emergency call.

7. The mobile device of claim 6 , wherein to cause the mobile device to enter the pseudo-emergency mode, the application is further configured to increase an accuracy of the geographic location output by the API.

8. The mobile device of claim 6 , wherein to cause the mobile device to enter the pseudo-emergency mode, the application is further configured to prevent the mobile device from indicating the presence of an incoming call when the incoming call is originated from a number not associated with an emergency response center.

9. The mobile device of claim 6 , wherein to cause the mobile device to enter the pseudo-emergency mode, the application is further configured to cause a visual indication that the mobile phone has entered the pseudo-emergency mode to be displayed by a display of the mobile device.

10. The mobile device of claim 5 , wherein to originate the emergency call, the application dialer is further configured to transmit a SIP invite message to the emergency call router.

11. The mobile device of claim 1 , wherein the application is factory installed onto the mobile device.

12. The mobile device of claim 1 , wherein the application is loaded onto the mobile device after a factory installation of the mobile device has been completed.

13. A method comprising:

receiving, at an application dialer of a mobile communication device, user input indicative of an emergency call;

determining, by the application dialer, whether or not location services are currently available for the mobile device;

when location services are currently unavailable, releasing control of an origination of the emergency call to a native dialer of the mobile communication device, wherein the native dialer is not the application dialer; and

when location services are currently available, originating, by the application dialer, the emergency call by transmitting a SIP invite message to an emergency call router, wherein the SIP invite message utilizes a packet header format that includes an indication of a geographic location.

14. The method of claim 13 , wherein utilizing the packet header format that includes the indication of the geographic location comprises:

receiving, by the application dialer, the geographic location as an output of an API.

15. The method of claim 13 , wherein the application dialer is included within an application, and wherein the method further comprises:

causing, by the application, the mobile device to enter a pseudo-emergency mode when the application dialer originates the emergency call.

16. The method of claim 15 , wherein causing the mobile device to enter the pseudo-emergency mode comprises:

causing, by the application, the mobile communication device to increase an accuracy of a geographic location output by an API.

17. The method of claim 15 , wherein causing the mobile device to enter the pseudo-emergency mode comprises: preventing, by the application, the mobile communication device from indicating the presence of an incoming call when the incoming call is originated from a number not associated with an emergency response center.

Assignments (8)
SECURITY INTEREST Recorded Jul 17, 2025
From: PEERLESS NETWORK, INC.
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 071745/0311 →
RELEASE OF SECURITY INTEREST Recorded Sep 12, 2022
From: FIFTH THIRD BANK, NATIONAL ASSOCIATION (SUCCESSOR TO FIFTH THIRD BANK)
To: PEERLESS NETWORK, INC.; WAVENATION, LLC
Reel/Frame 061065/0390 →
RELEASE BY SECURED PARTY Recorded Jun 7, 2019
From: MONROE CAPITAL MANAGEMENT ADVISORS, LLC
To: PEERLESS NETWORK, INC.
Reel/Frame 049409/0091 →
RELEASE OF SECURITY INTERESTS IN INTELLECTUAL PROPERTY Recorded Jun 14, 2018
From: MONROE CAPITAL MANAGEMENT ADVISORS, LLC
To: PEERLESS NETWORK, INC.
Reel/Frame 046367/0991 →
RELEASE OF SECURITY INTEREST IN INTELLECTUAL PROPERTY Recorded May 31, 2018
From: MONROE CAPITAL MANAGEMENT ADVISORS, LLC
To: PEERLESS NETWORK, INC.
Reel/Frame 046276/0677 →
INTELLECTUAL PROPERTY SECURTITY AGREEMENT Recorded May 31, 2018
From: PEERLESS NETWORK, INC.; WAVENATION, LLC
To: FIFTH THIRD BANK
Reel/Frame 046275/0811 →
SECURITY INTEREST Recorded Dec 14, 2016
From: PEERLESS NETWORK, INC.; AIRUS, INC.; AIRUS CLOUD COMMUNICATIONS, LLC; AIRUS VIRGINIA, INC.; PEERLESS ATLANTA DATA CENTER, LLC; PEERLESS CHICAGO DATACENTER, LLC; PEERLESS ENTERPRISE CLOUD SERVICES, LLC; PEERLESS NETWORK OF ALABAMA, LLC; PEERLESS NETWORK OF ARIZONA, LLC; PEERLESS NETWORK OF ARKANSAS, LLC; PEERLESS NETWORK OF CALIFORNIA, LLC; PEERLESS NETWORK OF COLORADO, LLC; PEERLESS NETWORK OF CONNECTICUT, LLC; PEERLESS NETWORK OF DELAWARE, LLC; PEERLESS NETWORK OF FLORIDA, LLC; PEERLESS NETWORK OF GEORGIA, LLC; PEERLESS NETWORK OF HAWAII, LLC; PEERLESS NETWORK OF IDAHO, LLC; PEERLESS NETWORK OF ILLINOIS, LLC; PEERLESS NETWORK OF INDIANA, LLC; PEERLESS NETWORK OF IOWA, LLC; PEERLESS NETWORK OF KANSAS, LLC; PEERLESS NETWORK OF KENTUCKY, LLC; PEERLESS NETWORK OF LOUISIANA, LLC; PEERLESS NETWORK OF MAINE, LLC; PEERLESS NETWORK OF MARYLAND, LLC; PEERLESS NETWORK OF MASSACHUSETTS, LLC; PEERLESS NETWORK OF MICHIGAN, LLC; PEERLESS NETWORK OF MINNESOTA, LLC; PEERLESS NETWORK OF MISSISSIPPI, LLC; PEERLESS NETWORK OF MISSOURI, LLC; PEERLESS NETWORK OF MONTANA, LLC; PEERLESS NETWORK OF NEBRASKA, LLC; PEERLESS NETWORK OF NEVADA, LLC; PEERLESS NETWORK OF NEW HAMPSHIRE, LLC; PEERLESS NETWORK OF NEW JERSEY, LIMITED LIABILITY COMPANY; PEERLESS NETWORK OF NEW MEXICO, LLC; PEERLESS NETWORK OF NEW YORK, LLC; PEERLESS NETWORK OF NORTH CAROLINA, LLC; PEERLESS NETWORK OF NORTH DAKOTA, LLC; PEERLESS NETWORK OF OHIO, LLC; PEERLESS NETWORK OF OKLAHOMA, LLC; PEERLESS NETWORK OF OREGON, LLC; PEERLESS NETWORK OF PENNSYLVANIA, LLC; PEERLESS NETWORK OF RHODE ISLAND, LLC; PEERLESS NETWORK OF SOUTH CAROLINA, LLC; PEERLESS NETWORK OF SOUTH DAKOTA, LLC; PEERLESS NETWORK OF TENNESSEE, LLC; PEERLESS NETWORK OF TEXAS, LLC; PEERLESS NETWORK OF THE DISTRICT OF COLUMBIA, LLC; PEERLESS NETWORK OF UTAH, LLC; PEERLESS NETWORK OF VERMONT, LLC; PEERLESS NETWORK OF VIRGINIA, LLC; PEERLESS NETWORK OF WASHINGTON, LLC; PEERLESS NETWORK OF WEST VIRGINIA, LLC; PEERLESS NETWORK OF WISCONSIN, LLC; PEERLESS NETWORK OF WYOMING, LLC; PEERLESS NETWORK REAL ESTATE HOLDINGS, LLC; WAVENATION, LLC; PEERLESS NETWORK HOLDINGS, INC.
To: MONROE CAPITAL MANAGEMENT ADVISORS, LLC, AS COLLATERAL AGENT
Reel/Frame 040734/0883 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 29, 2016
From: BREWER, JAMES E.
To: PEERLESS NETWORK, INC.
Reel/Frame 038419/0995 →