# US 10,769,922 B2 · Help seeking method, system, and apparatus, and computer storage medium

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 10,769,922 B2
- Document ID: US10769922B2
- Status: Granted
- Kind: B2
- Application number: 15/950,425
- Filed: 2018-04-11
- Published: 2018-08-16
- Granted: 2020-09-08
- Earliest claimed: 2016-03-24
- Assignees: Tencent Technology (Shenzhen) Company Limited
- Applicants: Tencent Technology (Shenzhen) Company Limited
- Inventors: Wang Da Feng
- Web page: https://patentgrep.com/patent/US10769922B2

## CPC

- G06Q 10/40: Business processes related to social networking or social networking services
- B60R 21/0136: responsive to actual contact with an obstacle {, e.g. to vehicle deformation, bumper displacement or bumper velocity relative to the vehicle (monitoring crash strength in combination with passenger seat detection B60R21/01558)}
- G01S 19/42: Determining position
- G06Q 50/00: Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism (healthcare informatics G16H)
- G08B 21/02: Alarms for ensuring the safety of persons
- G08B 25/00: Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
- G16H 40/20: for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
- H04L 51/52: for supporting social networking services
- B60R 2021/0027: {Post collision measures, e.g. notifying emergency services}
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- B60R: VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
- G01S: RADIO DIRECTION-FINDING; RADIO NAVIGATION; DETERMINING DISTANCE OR VELOCITY BY USE OF RADIO WAVES; LOCATING OR PRESENCE-DETECTING BY USE OF THE REFLECTION OR RERADIATION OF RADIO WAVES; ANALOGOUS ARRANGEMENTS USING OTHER WAVES
- G08B: SIGNALLING SYSTEMS, e.g. PERSONAL CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
- G16H: HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed are help seeking methods, systems, and apparatuses, and computer storage mediums storing processor executable instructions for implementing the help seeking methods. A help seeking system includes a distress device, a distress device server, a social server, and a social client. A distress device in a vehicle obtains a geographical location and a device identifier of the distress device, and sends a rescue request to the social server. The social server receives the rescue request, determines a social client associated with the device identifier, sends the rescue request to the social client, and sends the rescue request to the distress device server. The social client and the distress device server separately receives the rescue request sent by the social server. Therefore, a rescue efficiency can be improved in scenarios where a driver is not able to request assistance.

## Claims

### Claim 1

A help seeking method, implemented by a help seeking system comprising a distress device, a distress device server, a social server, and a social client account, the social server being separately connected to the distress device and the distress device server, and the social server being a background server of the social client, and the method comprising:
determining, by the distress device included in a vehicle, the vehicle is involved in a collision, and obtaining a geographical location of the distress device and a device identifier of the distress device;
sending, by the distress device, a rescue request to the social server, the rescue request comprising at least the geographical location and the device identifier;
receiving, by the social server, the rescue request sent by the distress device;
determining, by the social server, a social client account associated with the device identifier, wherein the social client account is hosted by the social server;
including, by the social server, the rescue request with the social client account, wherein information included in the rescue request is displayable on a computing device accessing the social client account;
displaying, on a graphical user interface associated with the social client account, the rescue request, wherein the graphical user interface associated with the social client account is configured to be viewable by other social client accounts of the social server that are included in an authorization list corresponding with the social client account;
sending, by the social server, the rescue request to the distress device server;
receiving, by the distress device server, the rescue request sent by the social server; and
generating, by the distress device server according to the rescue request, a message including the geographical location for a rescue worker;
generating, by the distress device server, a rescue progress message in response to one or more rescue progress query requests sent by a subset of one or social client accounts of the other social client accounts, wherein a number of the subset is less than a total number of the other social client accounts;
sending, by the distress device server, the rescue progress message to the social server;
receiving, by the social server, the rescue progress message; and
sending, by the social server, the rescue progress message only to the subset of the other social client accounts of the social server that are included in the authorization list corresponding with the social client account and that sent the one or more rescue progress query requests.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the determining, by the social server, the social client account associated with the device identifier comprises:
determining, by the social server, the authorization list corresponding to the device identifier according to a pre-stored mapping relationship; and
determining, by the social server for each social client account, each of the other social client accounts included in the authorization list that are logged into.

### Claim 3 (depends on 1)

The method according to claim 1, wherein when the rescue request further comprises a collision degree of the vehicle, sending the rescue request to the social server comprises:
obtaining, by the distress device, a collision degree of the vehicle;
detecting, by the distress device, the collision degree is greater than a predetermined threshold; and
sending, by the distress device, the rescue request carrying the geographical location, the device identifier, and the collision degree to the social server.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the distress device server is a background server of the distress device.

### Claim 5

A help seeking system comprising:
a distress device included in a vehicle, the distress device configured to:
when a vehicle is detected to be in a collision, obtain a geographical location and a device identifier of the distress device; and
send a rescue request to a social server, the rescue request comprising at least the geographical location and the device identifier;
the social server configured to:
receive the rescue request sent by the distress device;
determine a social client account associated with the device identifier, and send the rescue request to the social client account, wherein the social client account is hosted by the social server;
include the rescue request with the social client account, wherein information included in the rescue request is displayable on a computing device accessing the social client account;
display, on a graphical user interface associated with the social client account, the rescue request, wherein the graphical user interface associated with the social client account is configured to be viewable by other social client accounts of the social server that are included in an authorization list corresponding with the social client account;
send the rescue request to a distress device server; and
a distress device server configured to:
receive the rescue request sent by the social server;
generate, according to the rescue request, a message including the geographical location for a rescue worker;
generate a rescue progress message in response to one or more rescue progress query requests sent by a subset of one or more social client accounts of the other social client accounts, wherein a number of the subset is less than a total number of the other social client accounts; and
send the rescue progress message to the social server;
wherein the social server is further configured to:
receive the rescue progress message; and
send the rescue progress message only to the subset of the other social client accounts of the social server that are included in the authorization list corresponding with the social client account and that sent the one or more rescue progress query requests.

### Claim 6 (depends on 5)

The system according to claim 5, wherein:
a computing device corresponding to the social server is configured to:
determine the authorization list corresponding to the device identifier according to a pre-stored mapping relationship; and
determine each social client account, each of the other social client accounts included in the authorization list that are logged into.

### Claim 7 (depends on 5)

The system according to claim 5, wherein the distress device is further configured to:
obtain a collision degree of the vehicle;
detect the collision degree is greater than a predetermined threshold; and
send the rescue request including the geographical location, the device identifier, and the collision degree to the social server.

### Claim 8 (depends on 7)

The system according to claim 7, wherein the distress device includes a gravity sensor configured to obtain the collision degree of the vehicle.

### Claim 9 (depends on 5)

The system according to claim 5, wherein the distress device is configured to obtain the geographical location of the distress device by communicating with a global positioning system.

### Claim 10 (depends on 5)

The system according to claim 5, wherein the distress device server is a background server of the distress device.

### Claim 11

A distress device server in communication with a social server, the distress device server comprising:
a processor; and
a memory storing processor-executable instructions that, when executed by the processor, cause the processor to:
receive a rescue request sent by the social server, wherein the rescue request is transmitted to the social server by a distress device included in a vehicle when the vehicle is detected to be involved in a collision, wherein the rescue request includes at least a geographical location of the vehicle and a device identifier of the distress device, and wherein the distress device is also configured to provide the rescue request to a social client account, and wherein the social server is configured to display the rescue request on a graphical user interface associated with the social client account, wherein the graphical user interface associated with the social client account is configured to be viewable by other social client accounts of the social server that are included in an authorization list corresponding with the social client account; and
generate, according to the rescue request, a message including the geographical location for a rescue worker;
instruct, according to the rescue request, a rescue worker to travel to the geographical location to carry out rescue;
generate a rescue progress message in response to one or more rescue progress query requests sent by a subset of one or more social client accounts of the other social client accounts, wherein a number of the subset is less than a total number of the other social client accounts; and
send the rescue progress message to the social server, wherein the social server is configured to receive the rescue progress message, and send the rescue progress message only to the subset of the other social client accounts of the social server that are included in the authorization list corresponding with the social client account and that sent the one or more rescue progress query requests.

### Claim 12 (depends on 11)

The distress device server according to claim 11, wherein the social client account is logged into with a social account in the authorization list, and the authorization list is used to record a social account that receives a rescue request when the vehicle is detected to be involved in the collision.

### Claim 13 (depends on 11)

The distress device server according to claim 11, wherein the distress device server is a background server of the distress device.

### Claim 14 (depends on 11)

The distress device server according to claim 11, wherein the processor-executable instructions, when executed by the processor, causes the processor to receive the rescue request from the social server when a collision degree detected by the distress device is greater than a predetermined threshold.