IP Library Granted Patent US 9,503,876
Granted Patent B2
US 9,503,876 · App. 15/054,544 · Granted Nov 22, 2016

Personal security system

Inventors: Ghen Saito (Maplewood, NJ); Rodger Desai (Piscataway, NJ); Raju Rishi (Manalapan, NJ)
Assignee: Rave Wirless, Inc.
H04W4/22G08B25/016G08B25/10H04L63/107H04L63/20H04M1/7258H04W4/02H04W8/10H04W12/02
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,503,876
App. No.
15/054,544
Granted
Nov 22, 2016
Kind
B2
Abstract

A method for providing assistance to each of a plurality of users, each having been enrolled as a member of a community includes receiving, at a server, communications from corresponding mobile devices, each of which is associated with a user who has enrolled as a member in a first community. These emergency communications were initiated by activation of respective personal security buttons on the mobile devices, and provide information about respective security conditions. In response to the communications, the server alerts corresponding first and second security services that are appropriate responding to the respective security conditions.

Claims (22)

1. A method for providing assistance to each of a plurality of users, each of said users having been enrolled as a member of a community, said method comprising receiving, at a server, a first communication, said first communication having come from a first mobile device associated with a first user from said plurality of users, said first user having been enrolled as a member of a first community, said first communication having been initiated by activation of a personal security button on said first mobile device, said personal security button being configured to issue a notification indicative of a first security condition associated with said first user, receiving, at said server, a second communication, said second communication having come from a second mobile device associated with a second user from said plurality of users, said second user having been enrolled as a member of said first community, said second communication having been initiated by activation of a personal security button on said second mobile device, said personal security button being configured to issue a notification indicative of a second security condition that differs from said first security condition, said second security condition being associated with said second user, in response to said first communication, causing said server to alert a first security service, said first security service being a security service that is appropriate for responding to said first security condition, and in response to said second communication, causing said server to alert a second security service that differs from said first security service, said second security service being a security service that is appropriate for responding to said second security condition.

2. The method of claim 1 , further comprising displaying, to said first security service, information characterizing said first user, and displaying, to said second security service, information characterizing said second user.

3. The method of claim 2 , further comprising, in response to said first communication, sending a communication from said first security service to said first mobile device, and in response to said second communication, sending a communication from said second security service to said second mobile device.

4. The method of claim 1 , further comprising displaying, to said first security service, information characterizing said first user and said first security condition, and displaying, to said second security service, information characterizing said second user and said second security condition.

5. The method of claim 1 , wherein causing said server to alert a first security service comprises causing said server to alert campus police.

6. The method of claim 1 , wherein causing said server to alert a first security service comprises causing said server to alert a caregiver of said first user.

7. The method of claim 1 , wherein said personal security button on said first mobile device is on a home screen of said first mobile device, and wherein said personal security button on said second mobile device is on a home screen of said second mobile device.

8. The method of claim 1 , wherein said personal security button on said first mobile device is on a dashboard of said first mobile device, and wherein said personal security button on said second mobile device is on a dashboard of said second mobile device.

9. The method of claim 1 , wherein said personal security button on said first mobile device is configured to provide one-touch access to said first security service, and wherein said personal security button on said second mobile device is configured to provide one-touch access to said second security service.

10. The method of claim 1 , wherein said first and second security services are different security services.

11. The method of claim 1 , wherein causing said server to alert a first security service comprises causing said server to select said first security service based at least in part on said community.

12. The method of claim 1 , wherein causing said server to alert a first security service comprises causing said server to select said first security service based at least in part on said location of said first mobile device.

13. The method of claim 1 , wherein causing said server to alert a first security service comprises causing said server to select said first security service based at least in part on a last-known location of said first mobile device.

14. The method of claim 1 , wherein causing said server to alert a first security service comprises causing said server to select said first security service based at least in part on a failure to receive a communication from said first mobile device.

15. The method of claim 1 , wherein receiving, at a server, a first communication comprises receiving an SMS message.

16. The method of claim 1 , further comprising causing said server to send a query to a location-based server to identify a location of said first mobile device.

17. The method of claim 1 , wherein first and second users are personnel on a military base.

18. The method of claim 1 , wherein first and second users are residents of a housing development.

19. The method of claim 1 , wherein first and second users are members of a special-interest group.

20. The method of claim 1 , wherein first and second users are guests of a first hotel.

21. The method of claim 1 , wherein said first and second users are inhabitants of a city who have registered for services provided by said server.

22. The method of claim 1 , wherein causing said server to alert a first security service comprises causing said server to select said first security service based at least in part on entry of said mobile phone into a location.

Assignments (5)
NOTICE OF RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL Recorded Dec 16, 2022
From: ANTARES CAPITAL LP, AS COLLATERAL AGENT
To: RAVE WIRELESS, INC.; SWIFTREACH NETWORKS, LLC
Reel/Frame 062141/0022 →
PATENT SECURITY AGREEMENT Recorded May 7, 2019
From: RAVE WIRELESS, INC.; SWIFTREACH NETWORKS, LLC
To: ANTARES CAPITAL LP, AS COLLATERAL AGENT
Reel/Frame 049109/0370 →
RELEASE OF SECURITY INTEREST Recorded Apr 23, 2019
From: PNC BANK, NATIONAL ASSOCIATION
To: RAVE WIRELESS, INC.; SWIFTREACH NETWORKS, LLC
Reel/Frame 048975/0921 →
SECURITY INTEREST Recorded Jun 27, 2018
From: RAVE INTERMEDIATE HOLDINGS, INC.; RAVE WIRELESS, INC.
To: PNC BANK, NATIONAL ASSOCIATION
Reel/Frame 046219/0580 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2016
From: SAITO, GHEN; DESAI, RODGER; RISHI, RAJU
To: RAVE WIRELESS, INC.
Reel/Frame 037839/0141 →
Continuity (5)
Continuation 14748721 · Jun 24, 2015
Continuation 13440319 · Apr 5, 2012
Continuation 11687818 · Mar 19, 2007
Provisional Application 60784276 · Mar 20, 2006
Related Publication 20160183073A1 · Jun 23, 2016