# US 10,455,397 B1 · Context aware subscriber service > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 10,455,397 B1 - Document ID: US10455397B1 - Status: Granted - Kind: B1 - Application number: 15/940,214 - Filed: 2018-03-29 - Granted: 2019-10-22 - Earliest claimed: 2018-03-29 - Assignees: West Corporation - Applicants: West Corporation - Inventors: Gautham Pallapa; Santhosh Shetty - Web page: https://patentgrep.com/patent/US10455397B1 ## CPC - H04W 4/90: Services for handling of emergency or hazardous situations, e.g. earthquake and tsunami warning systems [ETWS] - A61B 5/1112: {Global tracking of patients, e.g. by using GPS} - A61B 5/747: {in case of emergency, i.e. alerting emergency services} - G16H 10/60: for patient-specific data, e.g. for electronic patient records - G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms - G16H 40/67: for remote operation - A61B 5/021: Measuring pressure in heart or blood vessels - A61B 5/024: Measuring pulse rate or heart rate - A61B 5/0816: {Measuring devices for examining respiratory frequency (measuring frequency of electric signals G01R23/00)} - A61B 5/4803: {Speech analysis specially adapted for diagnostic purposes} - H04W 4/02: Services making use of location information - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - A61B: DIAGNOSIS; SURGERY; IDENTIFICATION (usefulness limited to only animals A61D) - G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA ## Abstract One example method of operation provides receiving, at a server, event data generated by a user device indicating an emergency event, initiating an emergency application on the user device, processing the event data to identify whether the event data exceeds an emergency status threshold, transmitting a notification to the user device, and based on a response from the user device, notifying third party services of the emergency event. ## Claims ### Claim 1 A method comprising: initiating, via a user device, an emergency application on the user device in response to an event associated with a user of the user device; generating, via the user device, event data associated with the event; pre-processing, via the user device, the event data to make an initial determination as to whether the event data indicates a potential emergency event based on one or more data thresholds; identifying, via the user device, that the event data indicates a potential emergency event; transmitting, via the user device, the event data to a remote server for analysis based on the identification of the potential emergency event; and receiving, via the user device, a request from the remote server to automatically provide additional data for ongoing analysis by the remote server based on a determination by the remote server that the event data identifies an emergency event. ### Claim 2 (depends on 1) The method of claim 1, wherein the event data comprises one or more of: accelerometer data, global positioning satellite data, and biometric data. ### Claim 3 (depends on 2) The method of claim 2, wherein the biometric data comprises one or more of: a user heart rate, blood pressure, breathing rate, brain activity, and voice sample. ### Claim 4 (depends on 1) The method of claim 1, wherein the receiving a request from the remote server further comprises: receiving, via the user device, a request from the remote server when the analysis by the remote server identifies an emergency event based on the event data being compared to pre-stored model event data based on emergency events. ### Claim 5 (depends on 1) The method of claim 1, further comprising: retrieving a user record associated with the user device; and identifying user attributes. ### Claim 6 (depends on 1) The method of claim 1, further comprising: continuously transmitting, via the user device, information regarding a status of the user based on the request from the remote server. ### Claim 7 (depends on 6) The method of claim 6, further comprising: receiving, via the user device, and from the remote server, a request to confirm the existence of an emergency event. ### Claim 8 A mobile device, comprising: a memory to store at least one instruction that when executed by a processor causes the processor to: initiate an emergency application in response to an event associated with a user of the mobile device; generate event data associated with the event; pre-process the event data to make an initial determination as to whether the event data indicates a potential emergency situation based on one or more data thresholds; and cause a transmitter to transmit the event data to a remote server for analysis, if the initial determination identifies that the event data indicates a potential emergency situation. ### Claim 9 (depends on 8) The mobile device of claim 8, wherein the event data comprises one or more of: accelerometer data, global positioning satellite data, and biometric data. ### Claim 10 (depends on 9) The mobile device of claim 9, wherein the biometric data comprises one or more of: a user heart rate, blood pressure, breathing rate, brain activity, and voice sample. ### Claim 11 (depends on 8) The mobile device of claim 8, wherein the memory further is to store at least one instruction that when executed by the processor causes the processor to: receive a request from the remote server when the analysis by the remote server identifies an emergency event. ### Claim 12 (depends on 8) The mobile device of claim 8, wherein the memory further is to store at least one instruction that when executed by the processor causes the processor to: retrieve a user record associated with the user device; and identify user attributes. ### Claim 13 (depends on 8) The mobile device of claim 8, wherein the memory further is to store at least one instruction that when executed by the processor causes the processor to: cause the transmitter to continuously transmit information regarding a status of the user based on the request from the remote server. ### Claim 14 (depends on 13) The mobile device of claim 13, wherein the memory further is to store at least one instruction that when executed by the processor causes the processor to: receive a request to confirm the existence of an emergency situation from the remote server. ### Claim 15 A method comprising: receiving, via a remote server, event data generated by a user device in response to an event associated with a user of the user device, wherein the event data is pre-processed by the user device to make an initial determination as to whether the event data indicates a potential emergency event; identifying, via the remote server, that the potential emergency event is an emergency event based on an analysis of the event data; communicating, via the remote server, a request to the user device to automatically provide additional data based on the identification of the emergency event; performing, via the remote server, an ongoing analysis of the additional data received from the user device; and notifying, via the remote server, a third party service provider of the emergency event. ### Claim 16 (depends on 15) The method of claim 15, wherein the event data comprises one or more of: accelerometer data, global positioning satellite data, and biometric data. ### Claim 17 (depends on 16) The method of claim 16, wherein the biometric data comprises one or more of: a user heart rate, blood pressure, breathing rate, brain activity, and voice sample. ### Claim 18 (depends on 15) The method of claim 15, wherein the communicating a request to the user device further comprises: communicating a request to the user device when the analysis by the remote server identifies an emergency event based on a comparison of the event data to pre-stored model event data based on emergency events. ### Claim 19 (depends on 15) The method of claim 15, further comprising: retrieving a user record associated with the user device; and identifying user attributes. ### Claim 20 (depends on 15) The method of claim 15, further comprising: continuously receiving, via the remote server, information regarding a status of the user based on the request from the remote server; and determining, via the remote server, whether to elevate a status associated with the emergency event status based on the status of the user. ### Claim 21 (depends on 15) The method of claim 15, further comprising: communicating, via the remote server, a request to confirm the existence of the emergency event to the user device; and automatically identifying an existence of the emergency event based on a lack of response to the request.