WO2017162212A1 - 求救方法、系统、装置及计算机存储介质 - Google Patents

求救方法、系统、装置及计算机存储介质 Download PDF

Info

Publication number
WO2017162212A1
WO2017162212A1 PCT/CN2017/078196 CN2017078196W WO2017162212A1 WO 2017162212 A1 WO2017162212 A1 WO 2017162212A1 CN 2017078196 W CN2017078196 W CN 2017078196W WO 2017162212 A1 WO2017162212 A1 WO 2017162212A1
Authority
WO
WIPO (PCT)
Prior art keywords
rescue
social
server
request
progress
Prior art date
Application number
PCT/CN2017/078196
Other languages
English (en)
French (fr)
Inventor
王达峰
Original Assignee
腾讯科技（深圳）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to EP17769489.0A priority Critical patent/EP3367356A4/en
Priority to KR1020187011377A priority patent/KR102045977B1/ko
Priority to JP2018521067A priority patent/JP6918291B2/ja
Publication of WO2017162212A1 publication Critical patent/WO2017162212A1/zh
Priority to US15/950,425 priority patent/US10769922B2/en

Links

Images

Classifications

    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
    • G08B25/14—Central alarm receiver or annunciator arrangements
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/02—Alarms for ensuring the safety of persons
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
    • B60R21/01—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents
    • B60R21/013—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting collisions, impending collisions or roll-over
    • B60R21/0136—Electrical circuits for triggering passive safety arrangements, e.g. airbags, safety belt tighteners, in case of vehicle accidents or impending vehicle accidents including means for detecting collisions, impending collisions or roll-over responsive to actual contact with an obstacle, e.g. to vehicle deformation, bumper displacement or bumper velocity relative to the vehicle
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • 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
    • G01S19/00—Satellite radio beacon positioning systems; Determining position, velocity or attitude using signals transmitted by such systems
    • G01S19/38—Determining a navigation solution using signals transmitted by a satellite radio beacon positioning system
    • G01S19/39—Determining a navigation solution using signals transmitted by a satellite radio beacon positioning system the satellite radio beacon positioning system transmitting time-stamped messages, e.g. GPS [Global Positioning System], GLONASS [Global Orbiting Navigation Satellite System] or GALILEO
    • G01S19/42—Determining position
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • 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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • 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
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/01—Social networking
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B21/00—Alarms responsive to a single specified undesired or abnormal condition and not otherwise provided for
    • G08B21/18—Status alarms
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B25/00—Alarm systems in which the location of the alarm condition is signalled to a central station, e.g. fire or police telegraphic systems
    • G—PHYSICS
    • G08—SIGNALLING
    • G08B—SIGNALLING OR CALLING SYSTEMS; ORDER TELEGRAPHS; ALARM SYSTEMS
    • G08B27/00—Alarm systems in which the alarm condition is signalled from a central station to a plurality of substations
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16H—HEALTHCARE INFORMATICS, i.e. INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR THE HANDLING OR PROCESSING OF MEDICAL OR HEALTHCARE DATA
    • G16H40/00—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices
    • G16H40/20—ICT specially adapted for the management or administration of healthcare resources or facilities; ICT specially adapted for the management or operation of medical equipment or devices for the management or administration of healthcare resources or facilities, e.g. managing hospital staff or surgery rooms
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/52—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
    • B—PERFORMING OPERATIONS; TRANSPORTING
    • B60—VEHICLES IN GENERAL
    • B60R—VEHICLES, VEHICLE FITTINGS, OR VEHICLE PARTS, NOT OTHERWISE PROVIDED FOR
    • B60R21/00—Arrangements or fittings on vehicles for protecting or preventing injuries to occupants or pedestrians in case of accidents or other traffic risks
    • B60R2021/0027—Post collision measures, e.g. notifying emergency services

Definitions

  • the present application relates to the field of intelligent transportation, and in particular, to a rescue method, system, device and computer storage medium.
  • the owner of the accident vehicle can only take the initiative to seek help if his own activity is not affected. If the owner of the accident vehicle is seriously injured or has entered a coma state, other rescuers cannot arrive in time, and it is easy to miss. The best time to rescue the owner of the accident vehicle.
  • the present application provides a rescue method, system, device and computer storage medium.
  • the technical solution is as follows:
  • a help-seeking method for use in a help-seeking system, the help-seeking system comprising a call-calling device, a call-to-call device server, a social server, and a social client, respectively, the social server and the call-calling device Connected to the call for help device server, the social server is a background server of the social client, and the method includes:
  • the calling device in the vehicle acquires a geographical location and a device identifier of the calling device
  • the calling device sends a rescue request to the social server, and the rescue request is at least a package Include the geographic location and the device identification;
  • the social server determines a social client associated with the device identifier, and sends the rescue request to the social client;
  • the call forbidden device server instructs the rescuer to go to the geographic location for rescue according to the rescue request.
  • a method for salvaging is provided, which is applied to a call for help device server, and the call forbidden device server is connected to a social server, and the method includes:
  • the rescue request is sent to the social server when the vehicle is in a collision, and the rescue request includes at least a geographical location and a location of the vehicle Describe the equipment identification of the rescue device;
  • the rescuer is instructed to go to the geographic location for rescue according to the rescue request.
  • a help-seeking method for use in a social server, the method comprising:
  • the rescue request including at least a geographical location of the vehicle and the device identifier
  • Determining a social client associated with the device identification Determining a social client associated with the device identification, transmitting the rescue request to the social client, and transmitting a rescue request to the rescue device server.
  • a help system comprising a call for help device, a call for help device server, a social server, and a social client, wherein the social server is respectively connected to the call for help device and the call for help device server
  • the social server is a background server of the social client, and the system includes:
  • the calling device in the vehicle is used to acquire a geographical location and a device identifier of the calling device;
  • the calling device is configured to send a rescue request to the social server, where the rescue request includes at least the geographic location and the device identifier;
  • the social server is configured to receive the rescue request sent by the calling device
  • the social server is configured to determine a social client associated with the device identifier, and send the rescue request to the social client;
  • the social client is configured to receive the rescue request sent by the social server
  • the social server is configured to send the rescue request to the calling device server
  • the call for help device server configured to receive the rescue request sent by the social server
  • the call for help device server is configured to instruct the rescuer to go to the geographic location for rescue according to the rescue request.
  • a help device which is applied to a call for help device server, and the call service device server is connected to a social server, and the device includes:
  • a rescue request receiving module configured to receive a rescue request sent by the social server, where the rescue request is sent to the social server when the vehicle is in a collision, and the rescue request includes at least Describe the geographic location of the vehicle and the device identification of the call for help device;
  • the indication module is configured to instruct the rescuer to go to the geographic location for rescue according to the rescue request received by the rescue request receiving module.
  • a help device for use in a social server, the device comprising:
  • a rescue request receiving module configured to receive a rescue request sent by the calling device in the vehicle when the vehicle collides, where the rescue request includes at least a geographic location of the vehicle and the device identifier;
  • a first request sending module configured to determine a social client associated with the device identifier, and send the rescue request to the social client
  • the second request sending module is configured to send a rescue request to the calling device server.
  • a computer storage medium comprising a set of instructions that, when executed, cause at least one processor to perform operations comprising:
  • the calling device in the vehicle acquires a geographical location and a device identifier of the calling device
  • the calling device sends a rescue request to the social server, where the rescue request includes at least the geographic location and the device identifier;
  • the social server determines a social client associated with the device identifier, and sends the rescue request to the social client;
  • the call forbidden device server instructs the rescuer to go to the geographic location for rescue according to the rescue request.
  • a computer storage medium comprising a set of instructions that, when executed, cause at least one processor to perform operations comprising:
  • the rescue request is sent to the social server when the vehicle is in a collision, and the rescue request includes at least a geographical location and a location of the vehicle Describe the equipment identification of the rescue device;
  • the rescuer is instructed to go to the geographic location for rescue according to the rescue request.
  • a computer storage medium comprising a set of instructions that, when executed, cause at least one processor to perform operations including the following Make:
  • the rescue request including at least a geographical location of the vehicle and the device identifier
  • Determining a social client associated with the device identification Determining a social client associated with the device identification, transmitting the rescue request to the social client, and transmitting a rescue request to the crying device server.
  • the calling device in the vehicle acquires the geographical location and the device identifier of the calling device, and then the calling device sends a rescue request to the social server, and the social server determines the social client associated with the device identifier according to the received rescue request.
  • the social client sends a rescue request to the social client
  • the social server sends a rescue request to the rescue device server
  • the help-rescue device instructs the rescuer to go to the rescue according to the received rescue request; because the vehicle is in a collision, the rescue device is used to send the social assistance to the social server.
  • the social server sends a rescue request to the social client and the call for help device, without the need for the owner to use the call for help, avoiding the inconvenience of the owner's own help or other rescuers can not arrive in time, which will lead to easy to miss
  • the best time for rescue has reached the goal of being able to notify the relatives and friends of the owner in the first time, gaining the attention of relatives and friends, improving rescue efficiency and reducing the rate of death and injury.
  • 1-1 is a schematic diagram of an implementation environment of a method for salvage according to some exemplary embodiments
  • FIG. 1-2 are schematic diagrams of an implementation environment of another rescue method according to some exemplary embodiments.
  • FIG. 2 is a flowchart of a method for salvage according to an exemplary embodiment
  • FIG. 3 is a flowchart of a method for salvage according to another exemplary embodiment
  • FIG. 4 is a flowchart of a method for salvage according to another exemplary embodiment
  • FIG. 5A is a schematic diagram of an implementation of a method for salvage according to an exemplary embodiment
  • FIG. 5B is a schematic diagram of an implementation of a method for salvage according to an exemplary embodiment
  • FIG. 5C is a schematic diagram of an implementation of a method for salvage according to an exemplary embodiment
  • FIG. 5D is a schematic diagram of an implementation of a method for salvage according to an exemplary embodiment
  • FIG. 5E is a schematic diagram of an implementation of a method for salvage according to an exemplary embodiment
  • FIG. 6 is a block diagram showing the structure of a help device according to an exemplary embodiment
  • FIG. 7 is a block diagram showing the structure of a help device according to another exemplary embodiment.
  • FIG. 8 is a block diagram showing the structure of a help device according to an exemplary embodiment
  • FIG. 9 is a block diagram showing the structure of a help device according to an exemplary embodiment.
  • FIG. 10 is a schematic structural diagram of a hardware component of the present application.
  • FIG. 1-1 shows a schematic structural diagram of an implementation environment provided by the present application.
  • the implementation environment includes: a call for help device 110, a call for help device server 120, a terminal 130, and a social server 140, wherein:
  • the call for help device 110 is installed in the vehicle 150 and has the capability of data transmission.
  • the call for help device can be an ecall device.
  • the vehicle 150 is a driving tool having a driving function, such as a car, a bicycle, an electric car, a wheelchair, and the like.
  • the call device server 120 is a background server of the call-in device 110 and has the capability of data transmission.
  • the call service device server 120 is monitored by the call service device and has a display Function, when the call forbidden device server 120 receives and displays the rescue request, the call service device service provider can arrange rescue personnel to go to the collision location of the vehicle for rescue according to the rescue request.
  • the terminal 130 has the capability of data transmission, and the social client is installed in the terminal 130.
  • the social client is an instant messaging application, such as: MSN, WeChat, QQ, and so on.
  • the social server 140 is a background server of the social client, and may be a server cluster or a cloud computing center composed of one server or multiple servers.
  • the social server 140 stores a mapping relationship between the device identifier of the call forbidden device and the social account that receives the rescue request when the vehicle collides.
  • the call for help device 110 is connected to the social server 140 via a wireless network.
  • the call device server 120 and the social server 140 are connected by a wired network or a wireless network or a data transmission line.
  • the social clients in the at least one terminal 130 are connected to the social server 140 via a wired network or a wireless network or a data transmission line.
  • FIG. 2 shows a flowchart of a method for salvage provided by an exemplary embodiment of the present invention.
  • This embodiment is exemplified by applying the rescue method to the implementation environment shown in FIG. 1-1.
  • the rescue method includes the following steps:
  • Step 201 When the vehicle collides, the calling device in the vehicle acquires the geographical location and the device identification of the calling device.
  • the call for help device in the vehicle acquires the geographical location of the location where the vehicle collided and the device identification of the call for help device.
  • Step 202 The rescue device sends a rescue request to the social server, where the rescue request includes at least a geographic location and a device identifier.
  • Step 203 The social server receives the rescue request sent by the calling device.
  • Step 204 The social server determines a social client associated with the device identifier, and sends a rescue request to the social client.
  • the social server determines a social client associated with the device identifier according to the device identifier carried in the received rescue request, and sends a rescue request to the determined social client.
  • Step 205 The social client receives the rescue request sent by the social server.
  • Step 206 The social server sends a rescue request to the call for help device server.
  • Step 207 The call for help device server receives the rescue request sent by the social server.
  • Step 208 The help-rescue device server instructs the rescuer to go to the geographic location for rescue according to the rescue request.
  • step 206 to step 207 may be performed before step 204 to step 205 or concurrently with step 204 to step 205, which is not limited in this embodiment.
  • the steps 201 and 202 can be implemented separately as an embodiment on the side of the calling device; the steps 203, 204 and 206 can be implemented separately as an embodiment on the social server side; and the steps 207 and 208 can be implemented separately as an embodiment on the server side of the calling device.
  • the help-rescue device server instructs the rescuer to go to the geographic location of the location where the vehicle collided according to the rescue request for rescue.
  • the present invention provides a method for salvaging.
  • the calling device in the vehicle acquires the geographic location and the device identification of the calling device, and then the rescue device sends a rescue request to the social server, and the social server receives the request according to the receiving.
  • the rescue request After the rescue request determines the social client associated with the device identifier, the rescue request is sent to the social client, and the social server sends a rescue request to the call for help device server, and the call for help device server instructs the rescuer to go to the rescue according to the received rescue request;
  • the rescue device is used to send a rescue request to the social server, and then the social server sends a rescue request to the social client and the rescue device, without the need for the owner to use the call for help, thereby avoiding the inconvenience of the owner or other help.
  • Rescuers can not arrive in time, which will lead to the problem of the best time to miss the rescue. It can reach the relatives and friends of the owner in the first time, get the attention of relatives and friends, improve the rescue efficiency and reduce the death and injury rate.
  • FIG. 3 shows a flowchart of a method for salvage provided by another exemplary embodiment of the present invention.
  • This embodiment is exemplified by applying the rescue method to the implementation environment shown in FIG. 1-1.
  • the rescue method includes the following steps:
  • Step 301 When the vehicle collides, the calling device in the vehicle acquires the geographical location and the device identifier of the calling device.
  • a gravity sensor (G-sensor) is installed in the rescue device, and the rescue device can sense the change of the acceleration force of the vehicle through the gravity sensor, thereby determining whether the vehicle collides according to the change of the acceleration force, and the acceleration force refers to
  • the force that the physics exerts on the object during the acceleration process can be converted into an electrical signal by the gravity sensor when the object changes, such as shaking, falling, rising, falling, and the like.
  • the gravity sensor converts the change of the acceleration force of the vehicle into an electrical signal, and then sends the electrical signal to the calling device, and the calling device determines whether the vehicle collides according to the electrical signal.
  • a communication signal is automatically sent to the calling device to make the calling device know that the vehicle has an accident.
  • the geographic location of the location where the vehicle collides and the device identification of the calling device are obtained.
  • the call-calling device may acquire a geographic location through a Global Positioning System (GPS), or may be obtained through a base station that provides a data service.
  • GPS Global Positioning System
  • the calling device 110 is triggered; at this time, the calling device 110 acquires the current address position of the vehicle through the GPS or the base station.
  • Step 302 the call for help device acquires the degree of impact of the vehicle.
  • the salvage device can also use the gravity sensor to obtain the impact degree of the vehicle.
  • the salvage device calculates the specific value of the impact degree by using the electric signal converted by the gravity sensor and the calculation formula of the impact degree; in another possible implementation manner, the salvage device is converted according to the gravity sensor.
  • the electrical signal determines the level of impact, for example: at a certain The values of the electrical signals in the range correspond to the same level of impact.
  • Step 303 The calling device detects whether the impact level is greater than a predetermined threshold.
  • the call detection device detects whether the impact degree is greater than a predetermined threshold. When the impact level is greater than the predetermined threshold, the rescue request is sent to the social server, and if the impact level is not greater than the predetermined threshold, the rescue request is not sent to the social server.
  • the predetermined threshold is a default value set by the user or a default value in the call for help device, which is not limited in this embodiment.
  • the rescue device sets a default predetermined threshold according to the model of the vehicle and the impact resistance of the vehicle.
  • Step 304 If the impact level is greater than a predetermined threshold, the call-calling device sends a rescue request carrying the geographic location, the device identifier, and the impact level to the social server.
  • the rescue request sent by the rescue device may be a statement conforming to language logic, or may be several phrases capable of indicating a geographical location, a device identifier, and a degree of impact. That is to say, when the calling device determines that the degree of the received impact of the vehicle exceeds a certain threshold, the package is automatically requested based on the geographic location, the device identification, and the impact level.
  • the rescue request sent by the rescue device can be: the vehicle corresponding to the rescue device 2Q is at the xx city xx building A level 3 collision event occurred, or 31.5685 north latitude, 120.3841, 2Q, and 3 east longitude.
  • the call-in device does not send a rescue request to the social server.
  • the call for help device sends a rescue request carrying the geographic location, the device identifier, and the impact level to the call for help device server, in order to timely report the impact of the vehicle to the call for help device server, and the call for help device server receives After the rescue request,
  • the background personnel who monitor the rescue device server decide whether to carry out subsequent rescue work.
  • the call for help device may not directly detect whether the impact level is greater than a predetermined threshold, directly acquire the device identifier of the geographic location and the call for help device, and send the rescue request carrying the geographic location and the device identifier to the social server.
  • step 302 to step 304 are not performed.
  • the device identifier may be identification information corresponding to the vehicle, for example, may be unique identification information such as a license plate number of the vehicle.
  • Step 305 The social server receives the rescue request sent by the calling device.
  • the rescue request is reported to the social server 140 by the call-calling device 110, and at least the geographic location is carried in the rescue request.
  • Step 306 The social server determines, according to the pre-stored mapping relationship, an authorization list corresponding to the device identifier.
  • the mapping relationship is used to record the correspondence between the device identification and the authorization list, and the authorization list is used to record the social account that receives the rescue request when the vehicle collides.
  • the social account number recorded in the authorization list corresponding to one device identifier is at least one.
  • the social account recorded in the authorization list may be the social account of each relative of the owner.
  • mapping relationship pre-stored in the social server As shown in the following table, it exemplarily shows a part of the mapping relationship pre-stored in the social server:
  • the owner can associate the device identification with the social account through the social client. For example, the owner adds a device identifier of the call-in device to the social client, and then sends a request for associating the social account with the device identifier to the selected social account, and if the social account is determined to be associated with the device identifier, The social server adds the social account to the authorization list corresponding to the device identifier; or, after the owner adds the device identifier of the call-in device to the social client, the social server adds the social account with the owner's social account frequency to meet certain conditions to the authorization.
  • the process may require confirmation of the added social account, or may not need to be confirmed by the added social account; or, after the vehicle owner adds the device identification of the calling device in the social client, the social client will be a specific group If a social account in a group of friends and relatives is added to the authorization list, the process may require confirmation of the added social account or may not require confirmation of the added social account.
  • Step 307 The social server determines each social client, and each social client is registered with a social account recorded in the authorization list.
  • the social account in the authorization list can be obtained, and then the social client that logs in the social account recorded in the authorization list is determined.
  • step 308 the social server sends a rescue request to the social client.
  • the rescue request sent by the social server to the social client may be a statement conforming to the language logic.
  • the social client receives the rescue request sent by the social server.
  • the social client is an instant messaging application such as MSN, WeChat, QQ, etc.; for example, as shown in FIG. 1-2, the terminal 130 as a social client receives the rescue request through the instant communication A.
  • Step 310 The social server sends a rescue request to the call for help device server.
  • Step 311 The help-rescue device server receives the rescue request sent by the social server.
  • step 310 to step 311 may be performed before step 308 to step 309, and may also be performed simultaneously with step 308 to step 309.
  • the calling device instructs the rescuer to go to the geographic location for rescue according to the rescue request.
  • the rescue request is sent to the rescue station or rescue personnel, so that the rescue station dispatches rescue personnel to rescue the corresponding geographic location; or directly sends the rescue request to the rescue personnel, so that the rescue personnel directly The location determines where to go for rescue.
  • step 313 the call for help device server sends the rescue progress and the device identifier to the social server.
  • the help-rescue device server instructs the rescuer to go to the geographical location where the collision occurred to perform the rescue, or the background personnel arranges the rescue personnel to go to the geographical location where the collision occurs to perform the rescue, and the rescue personnel will rescue the progress and the device identification.
  • the call for help device server sends the rescue progress and device identification to the social server.
  • the rescue progress can indicate the rescue status of the rescue personnel to the vehicle collision event.
  • the rescue progress is: on the way to the accident location, or, at the accident location, or has arrived at the accident location, or the owner has been Sent to the hospital.
  • step 314 the social server receives the rescue progress and the device identification.
  • the social server determines the social client associated with the device identification and sends the rescue progress to the social client.
  • the social server sends a rescue progress to the social client that logs in to the social account in the authorized list, so that the user using the social client can know the progress of the rescue in time. For example, as shown in Figure 1-2, the client on the left can show the progress of the rescue as "on the way to the accident site.”
  • the social server sends the rescue progress to all social clients that log in to the social account in the authorized list, or the social server sends the rescue progress to a part of the social clients that log in to the social account in the authorized list.
  • step 316 the social client receives the rescue progress sent by the social server.
  • the steps 301 to 304 can be implemented separately as the embodiment of the call device side; the steps 305 to 308, the step 310, the steps 314 to 315 can be separately implemented as the embodiment on the social server side; the steps 311 to 313 can be separately performed. It is realized as an embodiment of the server side of the call for help device.
  • the present invention provides a rescue method by using a vehicle when a collision occurs in the vehicle.
  • the calling device obtains the geographic location and the device identifier of the calling device, and then the rescue device sends a rescue request to the social server, and the social server determines the social client associated with the device identifier according to the received rescue request, and sends a rescue request to the social client.
  • the social server sends a rescue request to the call for help device server, and the call forbidden device server instructs the rescuer to go to the rescue according to the received rescue request; because the rescue device sends a rescue request to the social server when the vehicle collides, and then the social server socializes
  • the client and the call for help server send a rescue request, without requiring the owner to use the call for help to avoid the problem, because the owner is inconvenient to ask for help or other rescuers can not arrive in time, which will lead to the best opportunity to miss the rescue. It is possible to inform the relatives and friends of the owner in the first time, get the attention of relatives and friends, improve the rescue efficiency, and reduce the effect of the death and injury rate.
  • the user can also actively query the rescue progress through the social client, that is, after step 311, the method further includes the following steps, as shown in FIG. 4:
  • step 401 the social client sends a rescue progress inquiry request to the social server.
  • the rescue progress inquiry request includes at least the device identification and the social account registered in the social client, and the social account is the social account recorded in the authorization list.
  • the user corresponding to the social account enters a statement of the device identifier and the rescue progress query in the social client, and the social client generates a rescue progress inquiry request according to the statement input by the user, and sends a rescue progress inquiry request to the social server; or
  • the user triggers a shortcut key for inquiring about the rescue progress in the social client, and the social client automatically generates a rescue progress inquiry request according to the previously received device identifier, and sends a rescue progress inquiry request to the social server.
  • the social server has previously sent a rescue request with the device identifier Q2 to the social client, and the user inputs “inquiry rescue progress, Q2” in the social client, and the social client automatically generates at least the device identifier and the social client.
  • the user triggers a shortcut key for inquiring the rescue progress in the social client, and the social client generates a rescue including at least the device identifier and the social account registered in the social client in the social client according to the device identifier Q2 received by the social client.
  • the progress asks for the request and sends a rescue progress inquiry request to the social server.
  • Step 402 The social server receives the rescue progress inquiry request sent by the social client.
  • step 403 the social server sends a rescue progress inquiry request to the call for help device server.
  • Step 404 the call for help device server receives the rescue progress inquiry request.
  • Step 405 The help-rescue device server determines the rescue progress according to the device identifier carried in the rescue progress inquiry request.
  • the help-rescue device server sends a rescue progress inquiry to the rescue personnel corresponding to the device identifier, and the rescue personnel feedback the rescue progress to the call-for-rescue device server after receiving the rescue progress inquiry, wherein the rescue progress inquiry may be that the call-rescue device server directly sends the rescue personnel
  • the sender can also send the background personnel of the call for help server to the rescue personnel.
  • the rescue personnel can directly report the rescue progress to the call service server, or the background personnel of the call service server can feedback the rescue progress.
  • Step 406 The help-rescue device server sends the rescue progress and the device identifier to the social server.
  • step 407 the social server receives the rescue progress and the device identification.
  • Step 408 The social server determines a rescue progress inquiry request according to the device identifier, and determines the social client according to the social account carried in the rescue progress inquiry request.
  • step 409 the social server sends the rescue progress to the social client.
  • the social server only sends the rescue progress to the social client corresponding to the social account that issued the rescue progress inquiry request.
  • the social server may also send the rescue progress to the social client corresponding to all the social accounts in the authorization list corresponding to the device identifier.
  • the social client receives the rescue progress sent by the social server.
  • help-seeking method provided by the present application also sends a rescue progress inquiry request to the social server through the social client, and the social server only feeds back the rescue progress to the social client that sends the rescue request request, so that the user can query the rescue progress at any time, and obtain the timely response.
  • Information about the progress of the rescue the server only feedbacks the rescue progress to a specific social client, which helps the social server to process and send information faster, saving the resources of the social server.
  • the salvage method provided by the present application may also perform only steps 301 to 311 in the embodiment shown in FIG. 3, and steps 401 to 409 in the embodiment shown in FIG. Those skilled in the art can also freely combine the above steps according to actual needs, and obtain other implementation manners, which are not described herein again.
  • the vehicle in which the collision event occurs is a car
  • the owner is a small king
  • the calling device installed on the vehicle is an ecall device
  • the device identification of the ecall device is E1
  • the social client is QQ
  • the social server is The QQ server and the call for help device server are examples of the ecall server.
  • the rescue method includes:
  • Step 501 When the vehicle collides, the ecall device in the vehicle acquires the geographic location and the device identification of the ecall device.
  • the ecall device judges that the car has collided according to the electrical signal sent by the gravity sensor.
  • the geographical location of the collision obtained by the GPS is 31.5685 north latitude and 120.3841 east longitude, and the obtained device identifier is E1.
  • step 502 the ecall device acquires the degree of impact of the vehicle.
  • the ecall device calculates the impact level of the car based on the electrical signal to three levels.
  • step 503 the ecall device detects whether the impact level is greater than a predetermined threshold.
  • the ecall device detects that the car has a greater impact than the second level.
  • Step 504 The ecall device sends a rescue request carrying the geographic location, the device identifier, and the impact degree to the QQ server.
  • the rescue request sent by the ecall device to the QQ server is:
  • the car corresponding to the ecall device E1 has a three-level collision event at 31.5685 north latitude and 120.3841 east longitude, requesting immediate rescue.
  • Step 505 The QQ server receives the rescue request sent by the ecall device.
  • Step 506 The QQ server determines an authorization list corresponding to E1 according to the pre-stored mapping relationship.
  • Step 507 The QQ server determines each QQ client, and each QQ client registers the QQ number recorded in the authorization list.
  • the QQ server determines three QQ clients.
  • the three QQ clients are respectively registered with QQ No. Xiao Li, Lao Wang and Xiao Hua. These three QQ numbers correspond to Xiao Wang’s wife, father and son respectively.
  • step 508 the QQ server sends a rescue request to the QQ client.
  • the QQ server converts the geographic location into a specific location name according to the latitude and longitude of the geographical location in the received rescue request, and sends a rescue request to the QQ client of Xiao Li, Lao Wang, and Xiao Hua registered with the QQ number.
  • step 509 the QQ client receives the rescue request sent by the QQ server.
  • Xiaoli’s QQ client receives a rescue request sent by the QQ server, and the rescue request is as shown in FIG. 51. “The car corresponding to the rescue device E1 has a three-level collision event near No. 23, Xingfu Avenue, Green City, requesting Rescue, similarly, both Pharaoh and Xiaohua’s QQ clients received the same rescue request.
  • step 510 the QQ server sends a rescue request to the ecall device server.
  • Step 511 The ecall device server receives the rescue request sent by the QQ server.
  • the ecall device server After receiving the rescue request, the ecall device server arranges rescue personnel to go to the collision site near No. 23, Xingfu Avenue, Greenland for rescue.
  • step 512 the ecall device server sends the rescue progress and the device identifier to the QQ server.
  • the ecall device server sends the rescue progress "alarm has arrived at the scene" and the device identification E1 to the QQ server.
  • step 513 the QQ server receives the rescue progress and the device identifier sent by the ecall device.
  • Step 514 the QQ server determines the QQ client associated with the device identifier E1, and sends the rescue progress to the QQ client.
  • the QQ server determines, according to the device identifier E1, that the QQ client is a QQ client that has the QQ number Xiao Li, Lao Wang, and Xiao Hua, and sends the rescue progress to the three QQ clients.
  • step 515 the QQ client receives the rescue progress sent by the QQ server.
  • Xiaoli's QQ client receives the rescue progress sent by the QQ server.
  • the rescue request is as shown in 52. “Rescue personnel have arrived near No. 23, Xingfu Avenue, Green City. Similarly, Lao Wang and Xiaohua The QQ client receives the same rescue progress.
  • step 516 the QQ client sends a rescue progress inquiry request to the QQ server.
  • the QQ client registered with QQ No. Xiaohua sends a rescue progress inquiry request to the QQ server to "inquire about the rescue progress of the car corresponding to E1", as shown in FIG. 5D.
  • the rescue progress inquiry request also includes the QQ number Xiaohua registered in the QQ client.
  • Step 517 the QQ server receives the rescue progress inquiry request sent by the QQ client.
  • step 518 the QQ server sends a rescue progress inquiry request to the ecall device server.
  • step 519 the ecall device server receives the rescue progress inquiry request.
  • Step 520 The ecall device server determines the rescue progress according to the device identifier carried in the rescue progress inquiry request.
  • the ecall device determines the rescue progress according to the device identification E1 as "the owner has been sent to the hospital.”
  • Step 521 the ecall device server sends the rescue progress and the device identifier to the QQ server.
  • the ecall device sends the rescue progress "to the hospital to the hospital" and the device identification E1 to the QQ server.
  • Step 522 The QQ server determines a rescue progress inquiry request according to the device identifier, and determines the QQ client according to the QQ number carried in the rescue progress inquiry request.
  • the QQ server determines the rescue progress inquiry request according to the device identifier E1 from the QQ client registered with the QQ number Xiaohua.
  • step 523 the QQ server sends a rescue progress to the QQ client.
  • the QQ server sends a rescue progress to the QQ client who has logged in QQ No. Xiaohua, and has sent the owner to the hospital.
  • the QQ client registered with QQ No. Xiaohua receives the rescue progress, as shown in FIG. 5E.
  • FIG. 6 is a structural block diagram of a rescue device provided by an exemplary embodiment of the present invention.
  • the help-seeking device can be implemented as all or part of the above-mentioned help-seeking device server capable of providing a rescue method by software, hardware or a combination of both.
  • the device includes:
  • the rescue request receiving module 610 is configured to receive a rescue request sent by the social server, where the rescue request is sent to the social server when the vehicle is in a collision, and the rescue request includes at least a geographic location of the vehicle and a device identifier of the calling device. .
  • the indication module 620 is configured to instruct the rescuer to go to the geographic location for rescue according to the rescue request received by the rescue request receiving module 610.
  • the help-seeking device receives the rescue request sent by the social server when the vehicle collides, and instructs the rescuer to go to the geographic location for rescue; because the vehicle is in collision, the call-calling device is used.
  • FIG. 7 is a structural block diagram of a rescue device provided by another exemplary embodiment of the present invention.
  • the help-seeking device can be implemented as all or part of the above-mentioned help-seeking device server capable of providing a rescue method by software, hardware or a combination of both.
  • the device includes:
  • the rescue request receiving module 710 is configured to receive a rescue request sent by the social server, where the rescue request is sent to the social server when the vehicle is in a collision, and the rescue request includes at least a geographic location of the vehicle and a device identifier of the calling device. .
  • the indication module 720 is configured to instruct the rescuer to go to the geographic location for rescue according to the rescue request received by the rescue request receiving module 710.
  • the device further includes:
  • the progress obtaining module 730 is configured to obtain a rescue progress of the rescue personnel on the vehicle.
  • the first progress sending module 740 is configured to send the rescue progress and the device identifier acquired by the progress obtaining module 1030 to the social server.
  • the device further includes:
  • the query request receiving module 750 is configured to receive a rescue progress query request sent by the social server, where the rescue progress query request is sent by the social client to the social server, and the rescue progress query request includes at least the device identifier and the social account of the login social client, and the social The client has a social account registered in the authorization list, and the authorization list is used to record the social account that receives the rescue request when the vehicle collides.
  • the progress determining module 760 is configured to determine a rescue progress according to the device identifier carried in the rescue progress query request received by the query request receiving module 750.
  • the second progress sending module 770 is configured to send the rescue progress and the device identifier determined by the progress determining module 760 to the social server.
  • the help-seeking device receives the rescue request sent by the social server when the vehicle collides, and instructs the rescuer to go to the geographic location for rescue; because the vehicle is in collision, the call-calling device is used.
  • Send a rescue to a social server Request and then the social server sends a rescue request to the social client and the call for help device, without the need for the owner to use the call for help, avoiding the inconvenience of the owner or other rescuers can not get in time, which will lead to easy to miss the rescue.
  • the best timing problem has reached the ability to notify the relatives and friends of the owner in the first time, get the attention of relatives and friends, improve the rescue efficiency, and reduce the death and injury rate.
  • FIG. 8 is a structural block diagram of a rescue device according to an embodiment of the present invention.
  • the help-seeking device can be implemented as all or part of the above-mentioned social server capable of providing a rescue method by software, hardware or a combination of both.
  • the device includes:
  • the rescue request receiving module 810 is configured to receive a rescue request sent by the calling device in the vehicle when the vehicle collides, where the rescue request includes at least a geographical location of the vehicle and the device identifier;
  • the first request sending module 820 is configured to determine a social client associated with the device identifier, and send the rescue request to the social client.
  • the second request sending module 830 is configured to send a rescue request to the calling device server.
  • the present invention provides a rescue device that receives a rescue request sent by a call-in device when a collision occurs in a vehicle, and the social server determines a social client associated with the device identifier, and sends the social client to the social client and the call-forcing device server.
  • FIG. 9 is a structural block diagram of a rescue device according to another embodiment of the present invention.
  • the rescue device can be implemented by software, hardware or a combination of the two. All or part of the social server for the method of help.
  • the device includes:
  • the rescue request receiving module 910 is configured to receive a rescue request sent by the calling device in the vehicle when the vehicle collides, where the rescue request includes at least a geographic location of the vehicle and a device identifier;
  • the first request sending module 920 is configured to determine a social client associated with the device identifier, and send a rescue request to the social client.
  • the second request sending module 930 is configured to send a rescue request to the calling device server.
  • the device further includes:
  • the first progress receiving module 940 is configured to receive a rescue progress and a device identifier sent by the call for help device server;
  • the determining sending module 950 is configured to determine a social client associated with the device identifier and send the rescue progress to the social client.
  • the determining sending module 950 includes:
  • the first determining unit 951 is configured to determine, according to the pre-stored mapping relationship, an authorization list corresponding to the device identifier, where the mapping relationship is used to record a correspondence between the device identifier and the authorization list, where the authorization list is used to record a rescue request when the vehicle collides.
  • Social account number
  • the second determining unit 952 is configured to determine each social client, where each social client is registered with a social account recorded in the authorization list.
  • the device comprises:
  • the query request receiving module 960 is configured to receive a rescue progress query request sent by the social client, where the rescue progress query request includes at least a device identifier and a social account registered to the social client, where the social account is a social account recorded in the authorization list;
  • An inquiry request sending module 970 configured to send a rescue progress inquiry request to the calling device server
  • the second progress receiving module 980 is configured to receive the rescue progress and the device identifier sent by the call forbidden device server, where the rescue progress is determined and sent by the call assisting device server according to the device identifier;
  • a determining module 990 configured to determine a rescue progress inquiry request according to the device identifier, and determine a social client according to the social account carried in the request for the rescue request;
  • the sending module 991 is configured to send a rescue progress to the social client.
  • the present invention provides a rescue device that receives a rescue request sent by a call-in device when a collision occurs in a vehicle, and the social server determines a social client associated with the device identifier, and sends the social client to the social client and the call-forcing device server.
  • the help-seeking device provided by the foregoing embodiment is only illustrated by the division of each functional module. In actual applications, the function distribution may be completed by different functional modules as needed. The internal structure of the device is divided into different functional modules to complete all or part of the functions described above.
  • the embodiment of the present invention is the same as the method for the rescue method. The specific implementation process is described in detail in the method embodiment, and details are not described herein again.
  • a person skilled in the art may understand that all or part of the steps of implementing the above embodiments may be completed by hardware, or may be instructed by a program to execute related hardware, and the program may be stored in a computer readable storage medium.
  • the storage medium mentioned may be a read only memory, a magnetic disk or an optical disk or the like.
  • an apparatus provided by this embodiment is an example of a hardware entity, as shown in FIG. 10, including a processor, a storage medium, and at least one external communication interface; the processor, the storage medium, and an external communication interface. Both are connected via a bus.
  • the processor of the apparatus of the present application performs the following processing:
  • the calling device in the vehicle acquires a geographical location and a device identifier of the calling device
  • the calling device sends a rescue request to the social server, where the rescue request includes at least the geographic location and the device identifier;
  • the social server determines a social client associated with the device identifier, and sends the rescue request to the social client;
  • the call forbidden device server instructs the rescuer to go to the geographic location for rescue according to the rescue request.
  • the processor of the apparatus of the present application performs the following processing:
  • the rescue request is sent to the social server when the vehicle is in a collision, and the rescue request includes at least a geographical location and a location of the vehicle Describe the equipment identification of the rescue device;
  • the rescuer is instructed to go to the geographic location for rescue according to the rescue request.
  • the processor of the apparatus of the present application performs the following processing:
  • the rescue request including at least a geographical location of the vehicle and the device identifier
  • the program may be stored in a storage medium of a computer system and executed by at least one processor in the computer system to implement a process comprising an embodiment of the methods as described above.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Emergency Management (AREA)
  • General Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • General Health & Medical Sciences (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Theoretical Computer Science (AREA)
  • Computing Systems (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Remote Sensing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Biomedical Technology (AREA)
  • Epidemiology (AREA)
  • Medical Informatics (AREA)
  • Public Health (AREA)
  • Mechanical Engineering (AREA)
  • Signal Processing (AREA)
  • Alarm Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Emergency Lowering Means (AREA)
  • Emergency Alarm Devices (AREA)

Abstract

一种求救方法、系统及装置，属于智能交通领域。该方法用于求救系统中，该系统包括呼救设备（110）、呼救设备服务器（120）、社交服务器（140）和社交客户端（130）：车辆中的呼救设备（110）获取地理位置和呼救设备（110）的设备标识，向社交服务器（140）发送救援请求；社交服务器（140）接收救援请求，确定与设备标识关联的社交客户端（130），向社交客户端（130）发送救援请求，向呼救设备服务器（120）发送救援请求；社交客户端（130）和呼救设备服务器（120）分别接收社交服务器（140）发送的救援请求；解决了当车辆发生碰撞时，车主自身不方便求救，其他救援人员又不能及时赶到时，容易错过救援的最佳时机的问题；达到了在车辆发生碰撞时，能够在第一时间内通知车主的亲友，获得亲友的关注，提高救援效率，降低死伤率的效果。

Description

求救方法、系统、装置及计算机存储介质 技术领域
本申请涉及智能交通领域，特别涉及一种求救方法、系统、装置及计算机存储介质。
背景技术
随着经济的发展，越来越多人的选用私人汽车作为一种代步工具，马路上的车辆数量也随之增加，发生交通事故的概率也大大提高。
现有技术中，当车辆发生事故时，往往由事故车辆的车主自行向医院或亲友求救，或者由热心路人帮助车主联系救援人员，或者直到交警到达后才联系救援人员。
现有技术至少存在以下问题：事故车辆车主只能够在自身活动不受影响的情况下主动求救，如果事故车辆的车主受伤较重或已经进入昏迷状态，其他救援人员又不能及时赶到，容易错过救援事故车辆车主的最佳时机。
发明内容
为了解决现有技术的问题，本申请提供了一种求救方法、系统、装置及计算机存储介质。所述技术方案如下：
根据本申请的第一方面，提供了一种求救方法，用于求救系统中，所述求救系统包括呼救设备、呼救设备服务器、社交服务器和社交客户端，所述社交服务器分别与所述呼救设备与所述呼救设备服务器相连，所述社交服务器是所述社交客户端的后台服务器，所述方法包括：
当车辆发生碰撞时，所述车辆中的呼救设备获取地理位置和所述呼救设备的设备标识；
所述呼救设备向所述社交服务器发送救援请求，所述救援请求至少包 括所述地理位置和所述设备标识；
所述社交服务器接收所述呼救设备发送的所述救援请求；
所述社交服务器确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求；
所述社交客户端接收所述社交服务器发送的所述救援请求；
所述社交服务器向所述呼救设备服务器发送所述救援请求；
所述呼救设备服务器接收所述社交服务器发送的所述救援请求；
所述呼救设备服务器根据所述救援请求指示救援人员前往所述地理位置进行救援。
根据本发明的第二方面，提供了一种求救方法，应用于呼救设备服务器，所述呼救设备服务器与社交服务器连接，所述方法包括：
接收所述社交服务器发送的救援请求，所述救援请求是车辆中的呼救设备在所述车辆发生碰撞时发送给所述社交服务器的，且所述救援请求至少包括所述车辆的地理位置和所述呼救设备的设备标识；
根据所述救援请求指示救援人员前往所述地理位置进行救援。
根据本发明的第三方面，提供了一种求救方法，应用于社交服务器中，所述方法包括：
接收车辆中的呼救设备在所述车辆发生碰撞时发送的救援请求，所述救援请求至少包括所述车辆的地理位置和所述设备标识；
确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求，并向所述呼救设备服务器发送救援请求。
根据本申请的第四方面，提供了一种求救系统，所述系统包括呼救设备、呼救设备服务器、社交服务器和社交客户端，所述社交服务器分别与所述呼救设备与所述呼救设备服务器相连，所述社交服务器是所述社交客户端的后台服务器，所述系统包括：
当车辆发生碰撞时，所述车辆中的呼救设备，用于获取地理位置和所述呼救设备的设备标识；
所述呼救设备，用于向所述社交服务器发送救援请求，所述救援请求至少包括所述地理位置和所述设备标识；
所述社交服务器，用于接收所述呼救设备发送的所述救援请求；
所述社交服务器，用于确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求；
所述社交客户端，用于接收所述社交服务器发送的所述救援请求；
所述社交服务器，用于向所述呼救设备服务器发送所述救援请求；
所述呼救设备服务器，用于接收所述社交服务器发送的所述救援请求；
所述呼救设备服务器，用于根据所述救援请求指示救援人员前往所述地理位置进行救援。
根据本申请的第五方面，提供了一种求救装置，应用于呼救设备服务器，所述呼救设备服务器与社交服务器连接，所述装置包括：
救援请求接收模块，用于接收所述社交服务器发送的救援请求，所述救援请求是车辆中的呼救设备在所述车辆发生碰撞时发送给所述社交服务器的，且所述救援请求至少包括所述车辆的地理位置和所述呼救设备的设备标识；
指示模块，用于根据所述救援请求接收模块接收的所述救援请求指示救援人员前往所述地理位置进行救援。
根据本申请的第六方面，提供了一种求救装置，应用于社交服务器中，所述装置包括：
救援请求接收模块，用于接收车辆中的呼救设备在所述车辆发生碰撞时发送的救援请求，所述救援请求至少包括所述车辆的地理位置和所述设备标识；
第一请求发送模块，用于确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求；
第二请求发送模块，用于向所述呼救设备服务器发送救援请求。
根据本申请的第七方面，一种计算机存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行包括以下的操作：
当车辆发生碰撞时，所述车辆中的呼救设备获取地理位置和所述呼救设备的设备标识；
所述呼救设备向所述社交服务器发送救援请求，所述救援请求至少包括所述地理位置和所述设备标识；
所述社交服务器接收所述呼救设备发送的所述救援请求；
所述社交服务器确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求；
所述社交客户端接收所述社交服务器发送的所述救援请求；
所述社交服务器向所述呼救设备服务器发送所述救援请求；
所述呼救设备服务器接收所述社交服务器发送的所述救援请求；
所述呼救设备服务器根据所述救援请求指示救援人员前往所述地理位置进行救援。
根据本申请的第八方面，提供了一种计算机存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行包括以下的操作：
接收所述社交服务器发送的救援请求，所述救援请求是车辆中的呼救设备在所述车辆发生碰撞时发送给所述社交服务器的，且所述救援请求至少包括所述车辆的地理位置和所述呼救设备的设备标识；
根据所述救援请求指示救援人员前往所述地理位置进行救援。
根据本申请的第九方面，提供了一种计算机存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行包括以下的操 作：
接收车辆中的呼救设备在所述车辆发生碰撞时发送的救援请求，所述救援请求至少包括所述车辆的地理位置和所述设备标识；
确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求，并向呼救设备服务器发送救援请求。
本申请提供的技术方案带来的有益效果是：
通过当车辆发生碰撞时，车辆中的呼救设备获取地理位置和呼救设备的设备标识，再由呼救设备向社交服务器发送救援请求，社交服务器根据接收到的救援请求确定与设备标识关联的社交客户端后，向社交客户端发送救援请求，社交服务器再向呼救设备服务器发送救援请求，呼救设备服务器根据接收到的救援请求指示救援人员前往救援；由于在车辆发生碰撞时，利用呼救设备向社交服务器发送救援请求，再由社交服务器向社交客户端和呼救设备服务器发救援请求，而不需要车主利用呼救设备求救，避免了因车主自身不方便求救或者其他救援人员又不能及时赶到，会导致容易错过救援的最佳时机的问题，达到了能够在第一时间内通知车主的亲友，获得亲友的关注，提高救援效率，降低死伤率的效果。
附图说明
为了更清楚地说明本申请中的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1-1是根据部分示例性实施例示出的一种求救方法的实施环境的示意图；
图1-2是根据部分示例性实施例示出的另一种求救方法的实施环境的示意图；
图2是根据一示例性实施例示出的一种求救方法的流程图；
图3是根据另一示例性实施例示出的一种求救方法的流程图；
图4是根据另一示例性实施例示出的一种求救方法的流程图；
图5A是根据一示例性实施例示出的一种求救方法的实施示意图；
图5B是根据一示例性实施例示出的一种求救方法的实施示意图；
图5C是根据一示例性实施例示出的一种求救方法的实施示意图；
图5D是根据一示例性实施例示出的一种求救方法的实施示意图；
图5E是根据一示例性实施例示出的一种求救方法的实施示意图；
图6是根据一示例性实施例示出的一种求救装置的结构方框图；
图7是根据另一示例性实施例示出的一种求救装置的结构方框图；
图8是根据一示例性实施例示出的一种求救装置的结构方框图；
图9是根据一示例性实施例示出的一种求救装置的结构方框图；
图10为本申请一种硬件组成结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合附图对本申请实施方式作进一步地详细描述。
请参考图1-1，其示出了本申请提供的一种实施环境的结构示意图。该实施环境包括：呼救设备110、呼救设备服务器120、终端130、社交服务器140，其中：
呼救设备110安装在车辆150中，具有数据传输的能力。比如：呼救设备可以是ecall设备。其中，车辆150是具有代步功能的行驶工具，比如：汽车、自行车、电动车、轮椅等等。
呼救设备服务器120是呼救设备110的后台服务器，具有数据传输的能力。可选的，呼救设备服务器120受呼救设备服务商监控，且具有显示 功能，当呼救设备服务器120接收并显示救援请求时，呼救设备服务商可以根据救援请求安排救援人员前往车辆的碰撞地点进行救援。
终端130具有数据传输的能力，且终端130中安装有社交客户端。其中，社交客户端是即时通讯类应用程序，比如：MSN、微信、QQ等等。
社交服务器140是社交客户端的后台服务器，可以是一台服务器或多台服务器组成的服务器集群或云计算中心。其中，社交服务器140中存储有呼救设备的设备标识和车辆发生碰撞时接收救援请求的社交帐号的映射关系。
呼救设备110与社交服务器140通过无线网络连接。
呼救设备服务器120与社交服务器140通过有线网络或无线网络或数据传输线连接。
至少一个终端130中的社交客户端与社交服务器140通过有线网络或无线网络或数据传输线连接。
请参考图2，其示出了本发明一个示例性实施例提供的求救方法的流程图。本实施例以该求救方法应用于图1-1所示的实施环境中来举例说明。该求救方法包括以下步骤：
步骤201，当车辆发生碰撞时，车辆中的呼救设备获取地理位置和呼救设备的设备标识。
当车辆发生碰撞时，车辆中的呼救设备获取该车辆发生碰撞的地点的地理位置和该呼救设备的设备标识。
步骤202，呼救设备向社交服务器发送救援请求，救援请求至少包括地理位置和设备标识。
步骤203，社交服务器接收呼救设备发送的救援请求。
步骤204，社交服务器确定与设备标识关联的社交客户端，向社交客户端发送救援请求。
社交服务器根据接收到的救援请求中携带的设备标识确定与设备标识关联的社交客户端，并向确定的社交客户端发送救援请求。
步骤205，社交客户端接收社交服务器发送的救援请求。
步骤206，社交服务器向呼救设备服务器发送救援请求。
步骤207，呼救设备服务器接收社交服务器发送的救援请求。
步骤208，呼救设备服务器根据救援请求指示救援人员前往该地理位置进行救援。
需要说明的是，步骤206至步骤207可以在步骤204至步骤205之前执行，或者与步骤204至步骤205同时执行，本实施例不作限定。
其中，步骤201和202可以单独实现成为呼救设备侧的实施例；步骤203、204和206可以单独实现成为社交服务器侧的实施例；步骤207和208可以单独实现成为呼救设备服务器侧的实施例。
可选的，呼救设备服务器接收到社交服务器发送的救援请求后，根据救援请求指示救援人员前往车辆发生碰撞的地点的地理位置进行救援。
综上所述，本申请提供的求救方法，通过当车辆发生碰撞时，车辆中的呼救设备获取地理位置和呼救设备的设备标识，再由呼救设备向社交服务器发送救援请求，社交服务器根据接收到的救援请求确定与设备标识关联的社交客户端后，向社交客户端发送救援请求，社交服务器再向呼救设备服务器发送救援请求，呼救设备服务器根据接收到的救援请求指示救援人员前往救援；由于在车辆发生碰撞时，利用呼救设备向社交服务器发送救援请求，再由社交服务器向社交客户端和呼救设备服务器发救援请求，而不需要车主利用呼救设备求救，避免了因车主自身不方便求救或者其他救援人员又不能及时赶到，会导致容易错过救援的最佳时机的问题，达到了能够在第一时间内通知车主的亲友，获得亲友的关注，提高救援效率，降低死伤率的效果。
请参考图3，其示出了本发明另一个示例性实施例提供的求救方法的流程图。本实施例以该求救方法应用于图1-1所示的实施环境中来举例说明。该求救方法包括以下步骤：
步骤301，当车辆发生碰撞时，车辆中的呼救设备获取地理位置和呼救设备的设备标识。
其中，呼救设备中安装有重力传感器(Gravity-sensor，G-sensor)，呼救设备可以通过重力感应器感知车辆的加速力的变化，从而根据加速力的变化确定车辆是否发生碰撞，加速力是指物理在加速过程中作用在物体上的力，当物体发生晃动、跌落、上升、下降等移动变化时都能够被重力传感器转化为电信号。当车辆在行驶过程中受到碰撞时，重力传感器将车辆的加速力的变化转化为电信号，再将该电信号发送至呼救设备，呼救设备根据电信号确定车辆是否发生碰撞。
也就是说，在车辆行驶过程中若出现碰撞等问题时，自动的向呼救设备发出通信信号，以使得呼救设备得知车辆出现意外。
当呼救设备确定车辆发生碰撞时，获取该车辆发生碰撞的地点的地理位置和该呼救设备的设备标识。具体地，呼救设备可以通过全球定位系统(Global Positioning System，GPS)、或者，可以通过提供数据服务的基站等方式获取地理位置。比如，可以参见图1-2，当车辆出现意外时，触发呼救设备110；此时呼救设备110通过GPS或基站获取到车辆当前的地址位置。
步骤302，呼救设备获取车辆的撞击程度。
可选的，呼救设备还可以利用重力传感器获取车辆的撞击程度。在一种可能的实现方式中，呼救设备利用重力传感器转化的电信号和撞击程度的计算公式，计算得到撞击程度的具体数值；在另一种可能的实现方式中，呼救设备根据重力传感器转化的电信号确定撞击程度的等级，比如：在某 范围内的电信号的数值对应的撞击程度都是同一等级的。
步骤303，呼救设备检测撞击程度是否大于预定阈值。
由于某些碰撞的撞击程度不会导致车主受伤，也不会影响车主继续驾驶，为避免呼救设备频繁向社交服务器发送救援请求，造成一定程度上的资源浪费，呼救设备检测撞击程度是否大于预定阈值，当撞击程度大于预定阈值时，向社交服务器发送救援请求，若撞击程度不大于预定阈值，则不向社交服务器发送救援请求。
其中，预定阈值是用户预先设置的，或者是呼救设备中默认的数值，本实施例不作限定。
比如：呼救设备根据车辆的型号以及车辆的抗撞击能力设置默认的预定阀值。
步骤304，若撞击程度大于预定阈值，则呼救设备向社交服务器发送携带有地理位置、设备标识和撞击程度的救援请求。
具体地，呼救设备发送的救援请求可以是符合语言逻辑的语句，也可以是能够表示地理位置、设备标识和撞击程度的几个短语。也就是说，当呼救设备确定车辆的收到撞击的程度超过一定的阈值之后，自动的基于地理位置、设备标识以及撞击程度等信息，封装得到救援请求。
比如，车辆发送碰撞的地点的地理位置是北纬31.5685，东经120.3841，设备标识是2Q，撞击程度为3级，则呼救设备发送的救援请求可以是：呼救设备2Q对应的车辆在xx市xx大厦处发生3级碰撞事件，或者，北纬31.5685，东经120.3841、2Q、3级。
若撞击程度小于预定阀值，则呼救设备不向社交服务器发送救援请求。
可选的，若撞击程度小于预定阀值，呼救设备为了及时向呼救设备服务器反馈车辆的撞击情况，可以向呼救设备服务器发送携带有地理位置、设备标识和撞击程度的救援请求，呼救设备服务器接收到救援请求后，可 以由监控呼救设备服务器的后台人员决定是否进行后续救援工作。
需要说明的是，当车辆发生碰撞时，呼救设备还可以不检测撞击程度是否大于预定阈值，直接获取地理位置和呼救设备的设备标识，将携带有地理位置和设备标识的救援请求发送至社交服务器，此时不执行步骤302至步骤304。其中，设备标识可以为车辆对应的标识信息，比如，可以为车辆的车牌号等唯一识别信息。
步骤305，社交服务器接收呼救设备发送的救援请求。比如，参见图1-2，通过呼救设备110，向社交服务器140上报救援请求，在救援请求中至少携带有地理位置。
步骤306，社交服务器根据预存的映射关系确定与设备标识对应的授权列表。
映射关系用于记录设备标识和授权列表之间的对应关系，授权列表用于记录车辆发生碰撞时接收救援请求的社交帐号。其中，一个设备标识对应的授权列表中记录的社交帐号至少为一个。比如，授权列表中记录的社交帐号可以是车主的各个亲友的社交帐号。
如下表所示，其示例性地示出了社交服务器中预存的映射关系的一部分：
Figure PCTCN2017078196-appb-000001
可选的，车主可以通过社交客户端将设备标识和社交帐号关联。比如：车主在社交客户端中添加呼救设备的设备标识，再向选中的社交帐号发送将社交帐号与设备标识关联的请求，若社交帐号确定与设备标识关联，则 社交服务器将社交帐号添加至设备标识对应的授权列表中；或者，车主在社交客户端中添加呼救设备的设备标识后，社交服务器将与车主的社交帐号联系频率满足一定条件的社交帐号添加至授权列表，该过程可以需要被添加的社交帐号的确认，也可以不需要通过被添加的社交帐号的确认；或者，车主在社交客户端中添加呼救设备的设备标识后，社交客户端将特定群组如亲友群组中的社交账号添加至授权列表，该过程可以需要被添加的社交帐号的确认，也可以不需要被添加的社交帐号的确认。
步骤307，社交服务器确定各个社交客户端，每个社交客户端中登录有授权列表中记录的社交帐号。
社交服务器确定出授权列表后，可以获取授权列表中的社交帐号，再确定出登录有授权列表中记录的社交帐号的社交客户端。
步骤308，社交服务器向社交客户端发送救援请求。
可选的，为了便于使用社交客户端的用户阅读救援信息，社交服务器向社交客户端发送的救援请求可以是符合语言逻辑的语句。
步骤309，社交客户端接收社交服务器发送的救援请求。这里，社交客户端是即时通讯类应用程序，比如：MSN、微信、QQ等等；比如，图1-2中所示，作为社交客户端的终端130通过即时通信A接收到救援请求。
步骤310，社交服务器向呼救设备服务器发送救援请求。
步骤311，呼救设备服务器接收社交服务器发送的救援请求。
需要说明的是，步骤310至上述步骤311可在步骤308至步骤309之前执行，还可以与步骤308至步骤309同时执行。
步骤312，呼救设备根据救援请求指示救援人员前往该地理位置进行救援。比如图1-2所示，将救援请求发送给救援站或救援人员，以使得救援站派出救援人员向对应的地理位置进行救援；或者，直接将救援请求发送给救援人员，使得救援人员直接根据地理位置确定去哪里进行救援。
步骤313，呼救设备服务器向社交服务器发送救援进度和设备标识。
可选的，呼救设备服务器接收到救援请求后，指示救援人员前往碰撞发生的地理位置进行救援，或者，由后台人员安排救援人员前往碰撞发生的地理位置进行救援，救援人员将救援进度和设备标识反馈给呼救设备服务器，呼救设备服务器向社交服务器发送救援进度和设备标识。
可选的，救援进度能够表示救援人员对车辆碰撞事件的救援状态，比如：救援进度是：在前往事故地点的路上，或，快到达事故地点，或，已到达事故地点，或，已将车主送往医院。
步骤314，社交服务器接收救援进度和设备标识。
步骤315，社交服务器确定与设备标识关联的社交客户端，并向社交客户端发送救援进度。
社交服务器确定与设备标识关联的社交客户端的具体实现方式如上述步骤306至步骤307，这里不再赘述。
社交服务器向登录有授权列表中社交帐号的社交客户端发送救援进度，以便使用社交客户端的用户能够及时了解救援进度。比如，参见图1-2中所示，左侧的客户端可以展示救援进度为“在前往事故地点的路上”。
可选的，社交服务器向登录有授权列表中的社交帐号的全部社交客户端发送救援进度，或者，社交服务器向登录有授权列表中的社交帐号的部分社交客户端发送救援进度。
步骤316，社交客户端接收社交服务器发送的救援进度。
其中，步骤301至步骤304可以单独实现成为呼救设备侧的实施例；步骤305至步骤308、步骤310、步骤314至步骤315可以单独实现成为社交服务器侧的实施例；步骤311至步骤313可单独实现成为呼救设备服务器侧的实施例。
综上所述，本申请提供的求救方法，通过当车辆发生碰撞时，车辆中 的呼救设备获取地理位置和呼救设备的设备标识，再由呼救设备向社交服务器发送救援请求，社交服务器根据接收到的救援请求确定与设备标识关联的社交客户端后，向社交客户端发送救援请求，社交服务器再向呼救设备服务器发送救援请求，呼救设备服务器根据接收到的救援请求指示救援人员前往救援；由于在车辆发生碰撞时，利用呼救设备向社交服务器发送救援请求，再由社交服务器向社交客户端和呼救设备服务器发救援请求，而不需要车主利用呼救设备求救，避免了因车主自身不方便求救或者其他救援人员又不能及时赶到，会导致容易错过救援的最佳时机的问题，达到了能够在第一时间内通知车主的亲友，获得亲友的关注，提高救援效率，降低死伤率的效果。
在基于图2或图3所示实施例的可选实施例中，在用户还可以通过社交客户端主动询问救援进度，即在步骤311之后该方法还包括如下步骤，如图4所示：
在步骤401中，社交客户端向社交服务器发送救援进度询问请求。
救援进度询问请求至少包括设备标识和社交客户端中登录的社交帐号，社交帐号是授权列表中记录的社交帐号。
可选的，对应于社交帐号的用户在社交客户端中输入设备标识和救援进度询问的语句，社交客户端根据用户输入的语句生成救援进度询问请求，并向社交服务器发送救援进度询问请求；或者，用户在社交客户端中触发询问救援进度的快捷键，社交客户端根据之前接收到的设备标识自动生成救援进度询问请求，并向社交服务器发送救援进度询问请求。
比如：社交服务器之前已经向社交客户端发送过携带有设备标识为Q2的救援请求，用户在社交客户端中输入“询问救援进度，Q2”，则社交客户端自动生成至少包括设备标识和社交客户端中的社交客户端中登录的社交帐号的救援进度询问请求，并向社交服务器发送救援进度询问请求；或者， 用户在社交客户端中触发询问救援进度的快捷键，社交客户端根据社交客户端之前接收到的设备标识Q2，生成至少包括设备标识和社交客户端中的社交客户端中登录的社交帐号的救援进度询问请求，并向社交服务器发送救援进度询问请求。
步骤402，社交服务器接收社交客户端发送的救援进度询问请求。
步骤403，社交服务器向呼救设备服务器发送救援进度询问请求。
步骤404，呼救设备服务器接收救援进度询问请求。
步骤405，呼救设备服务器根据救援进度询问请求中携带的设备标识确定救援进度。
可选的，呼救设备服务器向与设备标识对应的救援人员发送救援进度询问，救援人员接收到救援进度询问后向呼救设备服务器反馈救援进度，其中，救援进度询问可以是呼救设备服务器直接向救援人员发送的，也可以是呼救设备服务器的后台人员向救援人员发送的，同样地，救援人员可以直接向呼救设备服务器反馈救援进度，也可以通过呼救设备服务器的后台人员反馈呼救援进度。
步骤406，呼救设备服务器向社交服务器发送救援进度和设备标识。
步骤407，社交服务器接收救援进度和设备标识。
步骤408，社交服务器根据设备标识确定救援进度询问请求，并根据救援进度询问请求中携带的社交帐号确定社交客户端。
步骤409，社交服务器向社交客户端发送救援进度。
通常情况下，社交服务器只向发出救援进度询问请求的社交帐号对应的社交客户端发送救援进度。在一种可能的实现方式中，社交服务器也可以向与设备标识对应的授权列表中的全部社交帐号对应的社交客户端发送救援进度。
相应地，社交客户端接收社交服务器发送的救援进度。
此外，本申请提供的求救方法，还通过社交客户端向社交服务器发送救援进度询问请求，社交服务器仅向发送救援进行询问请求的社交客户端反馈救援进度，使得用户能够随时询问救援进度，及时获取救援进度的相关信息，服务器只向特定社交客户端反馈救援进度，有助于社交服务器更快地处理、发送信息，节省社交服务器的资源。
需要说明的是，本申请提供的求救方法，还可以只执行如图3所示实施例中步骤301至步骤311，和如图4所示实施例中的步骤401至步骤409。本领域技术人员还可以根据实际需要对上述步骤进行自由组合，得到其他实现方式，这里不再赘述。
在一个示意性地例子中，以发生碰撞事件的车辆为汽车，车主为小王，安装在车辆上的呼救设备为ecall设备，ecall设备的设备标识为E1，社交客户端为QQ，社交服务器为QQ服务器，呼救设备服务器为ecall服务器为例，如图5A所示，该求救方法包括：
步骤501，当车辆发生碰撞时，车辆中的ecall设备获取地理位置和ecall设备的设备标识。
ecall设备根据重力传感器发送的电信号判断出该汽车发生了碰撞，通过GPS获取到发生碰撞的地理位置为北纬31.5685，东经120.3841，获取到的设备标识为E1。
步骤502，ecall设备获取车辆的撞击程度。
ecall设备根据电信号计算出汽车的撞击程度为三级。
步骤503，ecall设备检测撞击程度是否大于预定阈值。
假设预定阈值为二级，ecall设备检测出该汽车的撞击程度大于二级。
步骤504，ecall设备向QQ服务器发送携带有地理位置、设备标识和撞击程度的救援请求。
ecall设备向QQ服务器发送的救援请求为：ecall设备E1对应的汽车在北纬31.5685，东经120.3841发生三级碰撞事件，请求立即救援。
步骤505，QQ服务器接收ecall设备发送的救援请求。
步骤506，QQ服务器根据预存的映射关系确定与E1对应的授权列表。
QQ服务器中与E1对应的授权列表中记录的QQ号有3个，分别为小李、老王、小华。
步骤507，QQ服务器确定各个QQ客户端，每个QQ客户端中登录有授权列表中记录的QQ号。
QQ服务器确定三个QQ客户端，这三个QQ客户端中分别登录有QQ号小李、老王、小华，这三个QQ号分别对应小王的妻子、父亲、儿子。
步骤508，QQ服务器向QQ客户端发送救援请求。
QQ服务器根据接收到的救援请求中的地理位置的经纬度将地理位置转换为具体的地点名称，分别向登录有QQ号的小李、老王、小华的QQ客户端发送救援请求。
步骤509，QQ客户端接收QQ服务器发送的救援请求。
如图5B所示，小李的QQ客户端接收发QQ服务器发送的救援请求，救援请求如51所示“呼救设备E1对应的汽车在格陵市幸福大道23号附近发生三级碰撞事件，请求救援”，同样地，老王和小华的QQ客户端都接收到同样的救援请求。
步骤510，QQ服务器向ecall设备服务器发送救援请求。
步骤511，ecall设备服务器接收QQ服务器发送的救援请求。
ecall设备服务器接收到救援请求后安排救援人员前往碰撞地点格陵市幸福大道23号附近进行救援。
救援人员到达现场后，将救援进度“已到达事故现场”和设备标识E1反馈给ecall设备服务器。
步骤512，ecall设备服务器向QQ服务器发送救援进度和设备标识。
ecall设备服务器向QQ服务器发送救援进度“已到达事故现场”和设备标识E1。
步骤513，QQ服务器接收ecall设备发送的救援进度和设备标识。
步骤514，QQ服务器确定与设备标识E1关联的QQ客户端，并向QQ交客户端发送救援进度。
QQ服务器根据设备标识E1确定出QQ客户端为登录有QQ号小李、老王、小华的QQ客户端，向这三个QQ客户端发送救援进度。
步骤515，QQ客户端接收QQ服务器发送的救援进度。
如图5C所示，小李的QQ客户端接收发QQ服务器发送的救援进度，救援请求如52所示“救援人员已到达格陵市幸福大道23号附近”，同样地，老王和小华的QQ客户端都接收到同样的救援进度。
步骤516，QQ客户端向QQ服务器发送救援进度询问请求。
登录有QQ号小华的QQ客户端向QQ服务器发送救援进度询问请求“询问E1对应的汽车的救援进度”，如图5D所示。
救援进度询问请求中还包括有QQ客户端中登录的QQ号小华。
步骤517，QQ服务器接收QQ客户端发送的救援进度询问请求。
步骤518，QQ服务器向ecall设备服务器发送救援进度询问请求。
步骤519，ecall设备服务器接收救援进度询问请求。
步骤520，ecall设备服务器根据救援进度询问请求中携带的设备标识确定救援进度。
ecall设备根据设备标识E1确定出救援进度为“已将车主送至医院”。
步骤521，ecall设备服务器向QQ服务器发送救援进度和设备标识
ecall设备向QQ服务器发送救援进度“已将车主送至医院”和设备标识E1。
步骤522，QQ服务器根据设备标识确定救援进度询问请求，并根据救援进度询问请求中携带的QQ号确定QQ客户端。
QQ服务器根据设备标识E1确定救援进度询问请求来自登录有QQ号小华的QQ客户端。
步骤523，QQ服务器向QQ客户端发送救援进度。
QQ服务器向登录有QQ号小华的QQ客户端发送救援进度“已将车主送至医院”。
相应地，登录有QQ号小华的QQ客户端接收救援进度，如图5E所示。
请参考图6，其示出了本发明一个示例性实施例提供的求救装置的结构方框图。该求救装置可以通过软件、硬件或者两者的结合实现成为上述可提供求救方法的呼救设备服务器的全部或一部分。该装置包括：
救援请求接收模块610，用于接收社交服务器发送的救援请求，救援请求是车辆中的呼救设备在车辆发生碰撞时发送给社交服务器的，且救援请求至少包括车辆的地理位置和呼救设备的设备标识。
指示模块620，用于根据救援请求接收模块610接收的救援请求指示救援人员前往地理位置进行救援。
综上所述，本申请提供的求救装置，通过在车辆发生碰撞时，呼救设备服务器接收社交服务器发送的救援请求，并指示救援人员前往地理位置进行救援；由于在车辆发生碰撞时，利用呼救设备向社交服务器发送救援请求，再由社交服务器向社交客户端和呼救设备服务器发救援请求，而不需要车主利用呼救设备求救，避免了因车主自身不方便求救或者其他救援人员又不能及时赶到，会导致容易错过救援的最佳时机的问题，达到了能够在第一时间内通知车主的亲友，获得亲友的关注，提高救援效率，降低死伤率的效果。
请参考图7，其示出了本发明另一个示例性实施例提供的求救装置的结构方框图。该求救装置可以通过软件、硬件或者两者的结合实现成为上述可提供求救方法的呼救设备服务器的全部或一部分。该装置包括：
救援请求接收模块710，用于接收社交服务器发送的救援请求，救援请求是车辆中的呼救设备在车辆发生碰撞时发送给社交服务器的，且救援请求至少包括车辆的地理位置和呼救设备的设备标识。
指示模块720，用于根据救援请求接收模块710接收的救援请求指示救援人员前往地理位置进行救援。
可选的，该装置，还包括：
进度获取模块730，用于获取救援人员对车辆的救援进度。
第一进度发送模块740，用于向社交服务器发送进度获取模块1030获取的救援进度和设备标识。
可选的，该装置还包括：
询问请求接收模块750，用于接收社交服务器发送的救援进度询问请求，救援进度询问请求是社交客户端发送给社交服务器的，且救援进度询问请求至少包括设备标识和登录社交客户端的社交帐号，社交客户端中登录有授权列表中社交帐号，授权列表用于记录车辆发生碰撞时接收救援请求的社交帐号。
进度确定模块760，用于根据询问请求接收模块750接收的救援进度询问请求中携带的设备标识确定救援进度。
第二进度发送模块770，用于向社交服务器发送进度确定模块760确定的救援进度和设备标识。
综上所述，本申请提供的求救装置，通过在车辆发生碰撞时，呼救设备服务器接收社交服务器发送的救援请求，并指示救援人员前往地理位置进行救援；由于在车辆发生碰撞时，利用呼救设备向社交服务器发送救援 请求，再由社交服务器向社交客户端和呼救设备服务器发救援请求，而不需要车主利用呼救设备求救，避免了因车主自身不方便求救或者其他救援人员又不能及时赶到，会导致容易错过救援的最佳时机的问题，达到了能够在第一时间内通知车主的亲友，获得亲友的关注，提高救援效率，降低死伤率的效果。
请参考图8，其示出了本发明一个实施例提供的求救装置的结构方框图。该求救装置可以通过软件、硬件或者两者的结合实现成为上述可提供求救方法的社交服务器的全部或一部分。该装置包括：
救援请求接收模块810，用于接收车辆中的呼救设备在所述车辆发生碰撞时发送的救援请求，所述救援请求至少包括所述车辆的地理位置和所述设备标识；
第一请求发送模块820，用于确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求。
第二请求发送模块830，用于向所述呼救设备服务器发送救援请求。
综上所述，本申请提供的求救装置，通过在车辆发生碰撞时，社交服务器接收呼救设备发送的救援请求，社交服务器确定与设备标识关联的社交客户端，向社交客户端和呼救设备服务器发送救援请求；由于在车辆发生碰撞时，利用呼救设备向社交服务器发送救援请求，再由社交服务器向社交客户端和呼救设备服务器发救援请求，而不需要车主利用呼救设备求救，避免了因车主自身不方便求救或者其他救援人员又不能及时赶到，会导致容易错过救援的最佳时机的问题，达到了能够在第一时间内通知车主的亲友，获得亲友的关注，提高救援效率，降低死伤率的效果。
请参考图9，其示出了本发明另一个实施例提供的求救装置的结构方框图。该求救装置可以通过软件、硬件或者两者的结合实现成为上述可提供 求救方法的社交服务器的全部或一部分。该装置包括：
救援请求接收模块910，用于接收车辆中的呼救设备在车辆发生碰撞时发送的救援请求，救援请求至少包括车辆的地理位置和设备标识；
第一请求发送模块920，用于确定与设备标识关联的社交客户端，向社交客户端发送救援请求。
第二请求发送模块930，用于向呼救设备服务器发送救援请求。
可选的，该装置还包括：
第一进度接收模块940，用于接收呼救设备服务器发送的救援进度和设备标识；
确定发送模块950，用于确定与设备标识关联的社交客户端，并向社交客户端发送救援进度。
可选的，确定发送模块950包括：
第一确定单元951，用于根据预存的映射关系确定与设备标识对应的授权列表，映射关系用于记录设备标识和授权列表之间的对应关系，授权列表用于记录车辆发生碰撞时接收救援请求的社交帐号；
第二确定单元952，用于确定各个社交客户端，每个社交客户端中登录有授权列表中记录的社交帐号。
可选的，该装置包括：
询问请求接收模块960，用于接收社交客户端发送的救援进度询问请求，救援进度询问请求至少包括设备标识和登录社交客户端的社交帐号，社交帐号是授权列表中记录的社交帐号；
询问请求发送模块970，用于向呼救设备服务器发送救援进度询问请求；
第二进度接收模块980，用于接收呼救设备服务器发送的救援进度和设备标识，救援进度是呼救设备服务器根据设备标识确定并发送的；
确定模块990，用于根据设备标识确定救援进度询问请求，并根据救援进行询问请求中携带的社交帐号确定社交客户端；
发送模块991，用于向社交客户端发送救援进度。
综上所述，本申请提供的求救装置，通过在车辆发生碰撞时，社交服务器接收呼救设备发送的救援请求，社交服务器确定与设备标识关联的社交客户端，向社交客户端和呼救设备服务器发送救援请求；由于在车辆发生碰撞时，利用呼救设备向社交服务器发送救援请求，再由社交服务器向社交客户端和呼救设备服务器发救援请求，而不需要车主利用呼救设备求救，避免了因车主自身不方便求救或者其他救援人员又不能及时赶到，会导致容易错过救援的最佳时机的问题，达到了能够在第一时间内通知车主的亲友，获得亲友的关注，提高救援效率，降低死伤率的效果。
需要说明的是：上述实施例提供的求救装置在实现上述求救方法时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将设备的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的求救装置与求救方法实施例属于同一构思，其具体实现过程详见方法实施例，这里不再赘述。
上述本申请序号仅仅为了描述，不代表实施例的优劣。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成，也可以通过程序来指令相关的硬件完成，所述的程序可以存储于一种计算机可读存储介质中，上述提到的存储介质可以是只读存储器，磁盘或光盘等。
以上所述仅为本发明的较佳实施例，并不用以限制本发明，凡在本发明的精神和原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。
在前述场景的基础上，本实施例所提供的装置作为硬件实体的一个示例如图10所示，包括处理器、存储介质以及至少一个外部通信接口；所述处理器、存储介质以及外部通信接口均通过总线连接。
本申请装置的处理器执行以下处理：
当车辆发生碰撞时，所述车辆中的呼救设备获取地理位置和所述呼救设备的设备标识；
所述呼救设备向所述社交服务器发送救援请求，所述救援请求至少包括所述地理位置和所述设备标识；
所述社交服务器接收所述呼救设备发送的所述救援请求；
所述社交服务器确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求；
所述社交客户端接收所述社交服务器发送的所述救援请求；
所述社交服务器向所述呼救设备服务器发送所述救援请求；
所述呼救设备服务器接收所述社交服务器发送的所述救援请求；
所述呼救设备服务器根据所述救援请求指示救援人员前往所述地理位置进行救援。
或者，本申请装置的处理器执行以下处理：
接收所述社交服务器发送的救援请求，所述救援请求是车辆中的呼救设备在所述车辆发生碰撞时发送给所述社交服务器的，且所述救援请求至少包括所述车辆的地理位置和所述呼救设备的设备标识；
根据所述救援请求指示救援人员前往所述地理位置进行救援。
或者，本申请装置的处理器执行以下处理：
接收车辆中的呼救设备在所述车辆发生碰撞时发送的救援请求，所述救援请求至少包括所述车辆的地理位置和所述设备标识；
确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述 救援请求，并向呼救设备服务器发送救援请求。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述程序可存储于一计算机可读取存储介质中，如本申请中，该程序可存储于计算机系统的存储介质中，并被该计算机系统中的至少一个处理器执行，以实现包括如上述各方法的实施例的流程。其中，所述存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
以上所述实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本发明的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干变形和改进，这些都属于本发明的保护范围。因此，本发明专利的保护范围应以所附权利要求为准。

Claims (27)

  1. 一种求救方法，用于求救系统中，所述求救系统包括呼救设备、呼救设备服务器、社交服务器和社交客户端，所述社交服务器分别与所述呼救设备与所述呼救设备服务器相连，所述社交服务器是所述社交客户端的后台服务器，所述方法包括：
    当车辆发生碰撞时，所述车辆中的呼救设备获取地理位置和所述呼救设备的设备标识；
    所述呼救设备向所述社交服务器发送救援请求，所述救援请求至少包括所述地理位置和所述设备标识；
    所述社交服务器接收所述呼救设备发送的所述救援请求；
    所述社交服务器确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求；
    所述社交客户端接收所述社交服务器发送的所述救援请求；
    所述社交服务器向所述呼救设备服务器发送所述救援请求；
    所述呼救设备服务器接收所述社交服务器发送的所述救援请求；
    所述呼救设备服务器根据所述救援请求指示救援人员前往所述地理位置进行救援。
  2. 根据权利要求1所述的方法，其中，所述方法还包括：
    所述呼救设备服务器向所述社交服务器发送救援进度和所述设备标识；
    所述社交服务器接收所述救援进度和所述设备标识；
    所述社交服务器确定与所述设备标识关联的社交客户端，并向所述社交客户端发送所述救援进度。
  3. 根据权利要求1或2所述的方法，其中，所述社交服务器确定与所述设备标识关联的社交客户端，包括：
    所述社交服务器根据预存的映射关系确定与所述设备标识对应的授权列表，所述映射关系用于记录设备标识和授权列表之间的对应关系，所述授权列表用于记录车辆发生碰撞时接收救援请求的社交帐号；
    所述社交服务器确定各个社交客户端，每个社交客户端中登录有所述授权列表中记录的社交帐号。
  4. 根据权利要求3所述的方法，其中，所述方法还包括：
    所述社交客户端向所述社交服务器发送救援进度询问请求，所述救援进度询问请求至少包括所述设备标识和所述社交客户端中登录的社交帐号，所述社交帐号是所述授权列表中记录的社交帐号；
    所述社交服务器接收所述社交客户端发送的所述救援进度询问请求；
    所述社交服务器向所述呼救设备服务器发送所述救援进度询问请求；
    所述呼救设备服务器接收所述救援进度询问请求；
    所述呼救设备服务器根据所述救援进度询问请求中携带的所述设备标识确定所述救援进度；
    所述呼救设备服务器向所述社交服务器发送所述救援进度和所述设备标识；
    所述社交服务器接收所述救援进度和所述设备标识；
    所述社交服务器根据所述设备标识确定所述救援进度询问请求，并根据所述救援进度询问请求中携带的所述社交帐号确定所述社交客户端；
    所述社交服务器向所述社交客户端发送所述救援进度。
  5. 根据权利要求1所述的方法，其中，当所述救援请求还包括车辆的撞击程度时，所述呼救设备向社交服务器发送救援请求，包括：
    所述呼救设备获取所述车辆的撞击程度；
    所述呼救设备检测所述撞击程度是否大于预定阈值；
    若所述撞击程度大于所述预定阈值，则所述呼救设备向所述社交服务 器发送携带有所述地理位置、所述设备标识和所述撞击程度的所述救援请求。
  6. 一种求救方法，应用于呼救设备服务器，所述呼救设备服务器与社交服务器连接，所述方法包括：
    接收所述社交服务器发送的救援请求，所述救援请求是车辆中的呼救设备在所述车辆发生碰撞时发送给所述社交服务器的，且所述救援请求至少包括所述车辆的地理位置和所述呼救设备的设备标识；
    根据所述救援请求指示救援人员前往所述地理位置进行救援。
  7. 根据权利要求6所述的方法，其中，所述根据所述救援请求指示救援人员前往所述地理位置进行救援之后，还包括：
    获取所述救援人员对所述车辆的救援进度；
    向所述社交服务器发送所述救援进度和所述设备标识。
  8. 根据权利要求6所述的方法，其中，所述方法还包括：
    接收所述社交服务器发送的救援进度询问请求，所述救援进度询问请求是社交客户端发送给所述社交服务器的，且所述救援进度询问请求至少包括所述设备标识和登录所述社交客户端的社交帐号，所述社交客户端中登录有授权列表中社交帐号，所述授权列表用于记录车辆发生碰撞时接收所述救援请求的社交帐号；
    根据所述救援进度询问请求中携带的所述设备标识确定所述救援进度；
    向所述社交服务器发送所述救援进度和所述设备标识。
  9. 一种求救方法，应用于社交服务器中，所述方法包括：
    接收车辆中的呼救设备在所述车辆发生碰撞时发送的救援请求，所述救援请求至少包括所述车辆的地理位置和所述设备标识；
    确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述 救援请求，并向呼救设备服务器发送救援请求。
  10. 根据权利要求9所述的方法，其中，所述方法还包括：
    接收所述呼救设备服务器发送的救援进度和设备标识；
    确定与所述设备标识关联的社交客户端，并向所述社交客户端发送所述救援进度。
  11. 根据权利要求9或10所述的方法，其中，所述确定与所述设备标识关联的社交客户端，包括：
    根据预存的映射关系确定与所述设备标识对应的授权列表，所述映射关系用于记录设备标识和授权列表之间的对应关系，所述授权列表用于记录车辆发生碰撞时接收救援请求的社交帐号；
    确定各个社交客户端，每个社交客户端中登录有所述授权列表中记录的社交帐号。
  12. 根据权利要求11所述的方法，其中，所述方法包括：
    接收社交客户端发送的救援进度询问请求，所述救援进度询问请求至少包括所述设备标识和登录所述社交客户端的社交帐号，所述社交帐号是所述授权列表中记录的社交帐号；
    向所述呼救设备服务器发送所述救援进度询问请求；
    接收所述呼救设备服务器发送的救援进度和所述设备标识，所述救援进度是所述呼救设备服务器根据所述设备标识确定并发送的；
    根据所述设备标识确定所述救援进度询问请求，并根据所述救援进行询问请求中携带的所述社交帐号确定所述社交客户端；
    向所述社交客户端发送所述救援进度。
  13. 一种求救系统，所述系统包括呼救设备、呼救设备服务器、社交服务器和社交客户端，所述社交服务器分别与所述呼救设备与所述呼救设备服务器相连，所述社交服务器是所述社交客户端的后台服务器，所述系 统包括：
    当车辆发生碰撞时，所述车辆中的呼救设备，配置为获取地理位置和所述呼救设备的设备标识；
    所述呼救设备，配置为向所述社交服务器发送救援请求，所述救援请求至少包括所述地理位置和所述设备标识；
    所述社交服务器，配置为接收所述呼救设备发送的所述救援请求；
    所述社交服务器，配置为确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求；
    所述社交客户端，配置为接收所述社交服务器发送的所述救援请求；
    所述社交服务器，配置为向所述呼救设备服务器发送所述救援请求；
    所述呼救设备服务器，配置为接收所述社交服务器发送的所述救援请求；
    所述呼救设备服务器，配置为根据所述救援请求指示救援人员前往所述地理位置进行救援。
  14. 根据权利要求13所述的系统，其中：
    所述呼救设备服务器，配置为向所述社交服务器发送救援进度和所述设备标识；
    所述社交服务器，配置为接收所述救援进度和所述设备标识；
    所述社交服务器，配置为确定与所述设备标识关联的社交客户端，并向所述社交客户端发送所述救援进度。
  15. 根据权利要求13或14所述的系统，其中：
    所述社交服务器，配置为根据预存的映射关系确定与所述设备标识对应的授权列表，所述映射关系用于记录设备标识和授权列表之间的对应关系，所述授权列表用于记录车辆发生碰撞时接收救援请求的社交帐号；
    所述社交服务器，配置为确定各个社交客户端，每个社交客户端中登 录有所述授权列表中记录的社交帐号。
  16. 根据权利要求15所述的系统，其中：
    所述社交客户端，配置为向所述社交服务器发送救援进度询问请求，所述救援进度询问请求至少包括所述设备标识和所述社交客户端中登录的社交帐号，所述社交帐号是所述授权列表中记录的社交帐号；
    所述社交服务器，配置为接收所述社交客户端发送的所述救援进度询问请求；
    所述社交服务器，配置为向所述呼救设备服务器发送所述救援进度询问请求；
    所述呼救设备服务器，配置为接收所述救援进度询问请求；
    所述呼救设备服务器，配置为根据所述救援进度询问请求中携带的所述设备标识确定所述救援进度；
    所述呼救设备服务器，配置为向所述社交服务器发送所述救援进度和所述设备标识；
    所述社交服务器，配置为接收所述救援进度和所述设备标识；
    所述社交服务器，配置为根据所述设备标识确定所述救援进度询问请求，并根据所述救援进度询问请求中携带的所述社交帐号确定所述社交客户端；
    所述社交服务器，配置为向所述社交客户端发送所述救援进度。
  17. 根据权利要求13所述的系统，其中，当所述救援请求还包括车辆的撞击程度时：
    所述呼救设备，配置为获取所述车辆的撞击程度；
    所述呼救设备，配置为检测所述撞击程度是否大于预定阈值；
    若所述撞击程度大于所述预定阈值，则所述呼救设备，还用于向所述社交服务器发送携带有所述地理位置、所述设备标识和所述撞击程度的所 述救援请求。
  18. 一种求救装置，应用于呼救设备服务器，所述呼救设备服务器与社交服务器连接，所述装置包括：
    救援请求接收模块，配置为接收所述社交服务器发送的救援请求，所述救援请求是车辆中的呼救设备在所述车辆发生碰撞时发送给所述社交服务器的，且所述救援请求至少包括所述车辆的地理位置和所述呼救设备的设备标识；
    指示模块，配置为根据所述救援请求接收模块接收的所述救援请求指示救援人员前往所述地理位置进行救援。
  19. 根据权利要求18所述的装置，其中，所述装置，还包括：
    进度获取模块，配置为获取所述救援人员对所述车辆的救援进度；
    第一进度发送模块，配置为向所述社交服务器发送所述进度获取模块获取的所述救援进度和所述设备标识。
  20. 根据权利要求18所述的装置，其中，所述装置还包括：
    询问请求接收模块，配置为接收所述社交服务器发送的救援进度询问请求，所述救援进度询问请求是社交客户端发送给所述社交服务器的，且所述救援进度询问请求至少包括所述设备标识和登录所述社交客户端的社交帐号，所述社交客户端中登录有授权列表中社交帐号，所述授权列表用于记录车辆发生碰撞时接收所述救援请求的社交帐号；
    进度确定模块，配置为根据所述询问请求接收模块接收的所述救援进度询问请求中携带的所述设备标识确定所述救援进度；
    第二进度发送模块，配置为向所述社交服务器发送所述进度确定模块确定的所述救援进度和所述设备标识。
  21. 一种求救装置，应用于社交服务器中，所述装置包括：
    救援请求接收模块，配置为接收车辆中的呼救设备在所述车辆发生碰 撞时发送的救援请求，所述救援请求至少包括所述车辆的地理位置和所述设备标识；
    第一请求发送模块，配置为确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求；
    第二请求发送模块，配置为向呼救设备服务器发送救援请求。
  22. 根据权利要求21所述的装置，其中，所述装置还包括：
    第一进度接收模块，配置为接收所述呼救设备服务器发送的救援进度和设备标识；
    确定发送模块，配置为确定与所述设备标识关联的社交客户端，并向所述社交客户端发送所述救援进度。
  23. 根据权利要求21或22所述的装置，其中，所述确定发送模块包括：
    第一确定单元，配置为根据预存的映射关系确定与所述设备标识对应的授权列表，所述映射关系用于记录设备标识和授权列表之间的对应关系，所述授权列表用于记录车辆发生碰撞时接收救援请求的社交帐号；
    第二确定单元，配置为确定各个社交客户端，每个社交客户端中登录有所述授权列表中记录的社交帐号。
  24. 根据权利要求23所述的装置，其中，所述装置包括：
    询问请求接收模块，配置为接收社交客户端发送的救援进度询问请求，所述救援进度询问请求至少包括所述设备标识和登录所述社交客户端的社交帐号，所述社交帐号是所述授权列表中记录的社交帐号；
    询问请求发送模块，配置为向所述呼救设备服务器发送所述救援进度询问请求；
    第二进度接收模块，配置为接收所述呼救设备服务器发送的救援进度和所述设备标识，所述救援进度是所述呼救设备服务器根据所述设备标识 确定并发送的；
    确定模块，配置为根据所述设备标识确定所述救援进度询问请求，并根据所述救援进行询问请求中携带的所述社交帐号确定所述社交客户端；
    发送模块，配置为向所述社交客户端发送所述救援进度。
  25. 一种计算机存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行包括以下的操作：
    当车辆发生碰撞时，所述车辆中的呼救设备获取地理位置和所述呼救设备的设备标识；
    所述呼救设备向所述社交服务器发送救援请求，所述救援请求至少包括所述地理位置和所述设备标识；
    所述社交服务器接收所述呼救设备发送的所述救援请求；
    所述社交服务器确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求；
    所述社交客户端接收所述社交服务器发送的所述救援请求；
    所述社交服务器向所述呼救设备服务器发送所述救援请求；
    所述呼救设备服务器接收所述社交服务器发送的所述救援请求；
    所述呼救设备服务器根据所述救援请求指示救援人员前往所述地理位置进行救援。
  26. 一种计算机存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行包括以下的操作：
    接收所述社交服务器发送的救援请求，所述救援请求是车辆中的呼救设备在所述车辆发生碰撞时发送给所述社交服务器的，且所述救援请求至少包括所述车辆的地理位置和所述呼救设备的设备标识；
    根据所述救援请求指示救援人员前往所述地理位置进行救援。
  27. 一种计算机存储介质，该存储介质包括一组指令，当执行所述指令时，引起至少一个处理器执行包括以下的操作：
    接收车辆中的呼救设备在所述车辆发生碰撞时发送的救援请求，所述救援请求至少包括所述车辆的地理位置和所述设备标识；
    确定与所述设备标识关联的社交客户端，向所述社交客户端发送所述救援请求，并向呼救设备服务器发送救援请求。
PCT/CN2017/078196 2016-03-24 2017-03-24 求救方法、系统、装置及计算机存储介质 WO2017162212A1 (zh)

Priority Applications (4)

Application Number Priority Date Filing Date Title
EP17769489.0A EP3367356A4 (en) 2016-03-24 2017-03-24 Method, system and device for requesting rescue and computer storage medium
KR1020187011377A KR102045977B1 (ko) 2016-03-24 2017-03-24 구조 요청 방법, 시스템 및 장치와 컴퓨터 기억 매체
JP2018521067A JP6918291B2 (ja) 2016-03-24 2017-03-24 救助方法、システム、装置及びコンピュータ記憶媒体
US15/950,425 US10769922B2 (en) 2016-03-24 2018-04-11 Help seeking method, system, and apparatus, and computer storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610173368.7A CN105761425B (zh) 2016-03-24 2016-03-24 求救方法、系统及装置
CN201610173368.7 2016-03-24

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/950,425 Continuation US10769922B2 (en) 2016-03-24 2018-04-11 Help seeking method, system, and apparatus, and computer storage medium

Publications (1)

Publication Number Publication Date
WO2017162212A1 true WO2017162212A1 (zh) 2017-09-28

Family

ID=56346302

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/078196 WO2017162212A1 (zh) 2016-03-24 2017-03-24 求救方法、系统、装置及计算机存储介质

Country Status (6)

Country Link
US (1) US10769922B2 (zh)
EP (1) EP3367356A4 (zh)
JP (1) JP6918291B2 (zh)
KR (1) KR102045977B1 (zh)
CN (1) CN105761425B (zh)
WO (1) WO2017162212A1 (zh)

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105761425B (zh) * 2016-03-24 2019-09-03 腾讯科技（深圳）有限公司 求救方法、系统及装置
CN106128039A (zh) * 2016-08-23 2016-11-16 南京野果信息技术有限公司 车载定位通讯设备及车载定位通讯系统
CN107579902A (zh) * 2017-06-22 2018-01-12 深圳小木科技有限公司 求救方法及求救系统
CN107395263A (zh) * 2017-07-19 2017-11-24 叶雷 户外工具的管理服务系统和方法
CN107450361A (zh) * 2017-08-02 2017-12-08 深圳市盛路物联通讯技术有限公司 一种车辆控制方法及装置
DE102017223005A1 (de) * 2017-12-18 2019-06-19 Robert Bosch Gmbh Verfahren und Vorrichtung zum Bereitstellen einer Verletzungsinformation über eine Verletzung eines ungeschützten Verkehrsteilnehmers bei einer Kollision mit einem Fahrzeug
US11012667B1 (en) 2018-02-21 2021-05-18 Alarm.Com Incorporated Vehicle monitoring
CN108749757A (zh) * 2018-04-25 2018-11-06 上海擎感智能科技有限公司 一种基于T-Box的自动拨打救援电话的方法及系统、T-Box
SG11202107912PA (en) * 2018-11-22 2021-08-30 Optimax Man Services Pte Ltd Intelligent impact sensor and uses
CN109800958B (zh) * 2018-12-24 2023-04-14 广东天创同工大数据应用有限公司 一种无人驾驶车辆的智联协助系统
CN109890024B (zh) * 2019-02-02 2020-09-25 上海救要救信息科技有限公司 一种用于确定救援小组信息的方法与设备
CN111846046B (zh) * 2019-04-03 2022-05-20 杭州青奇科技有限公司 一种单车安全检测的系统、方法及装置
CN110942818A (zh) * 2019-12-09 2020-03-31 新疆大学 一种院前急救方法、装置及系统
CN112298018A (zh) * 2020-10-19 2021-02-02 上海仙塔智能科技有限公司 一种求助系统、方法、车辆及计算机存储介质
CN112261574B (zh) * 2020-10-20 2023-04-07 中移雄安信息通信科技有限公司 目标救援对象的确定方法、装置、设备及计算机存储介质
CN112327814A (zh) * 2020-11-23 2021-02-05 宝能(西安)汽车研究院有限公司 车辆的故障处理方法及系统
CN115412640B (zh) * 2022-11-02 2023-05-09 北京北投智慧城市科技有限公司 一种基于知识图谱的呼叫中心信息处理方法及装置

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3672838B2 (ja) * 2001-04-18 2005-07-20 昇 赤坂 緊急対応システム
CN103247169A (zh) * 2013-04-17 2013-08-14 浙江大学 一种基于社交网络的车辆信息发布方法
CN103903406A (zh) * 2012-12-30 2014-07-02 王方淇 一种突发事件监测通知方法及系统
CN105262792A (zh) * 2015-09-09 2016-01-20 深圳市元征科技股份有限公司 一种车辆异常处理方法及车载终端
CN105407456A (zh) * 2015-10-22 2016-03-16 上海救要救信息科技有限公司 一种处理求救信息的方法和系统
CN105761425A (zh) * 2016-03-24 2016-07-13 腾讯科技（深圳）有限公司 求救方法、系统及装置

Family Cites Families (35)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE3830301A1 (de) * 1988-09-07 1990-03-08 Licentia Gmbh Anordnung zum erkennen eines in einem vorgegebenen gebiet auftretenden verkehrsunfalles
US5327990A (en) * 1989-05-16 1994-07-12 Busquets Albert B Integral automatic system for protection and rescue of occupants in crashed automobiles
KR100563258B1 (ko) * 1997-12-31 2006-05-25 (주) 만도맵앤소프트 자동차 사고 통보 장치
JP2004171394A (ja) * 2002-11-21 2004-06-17 Takanori Terajima 搬送先自動選択装置、搬送先自動選択システム、傷病者データベース生成装置、傷病者データベース検索装置並びに移動体
US7848765B2 (en) 2005-05-27 2010-12-07 Where, Inc. Location-based services
KR101257384B1 (ko) * 2007-01-08 2013-04-23 에스케이플래닛 주식회사 자동차의 위험 구호 시스템, 장치 및 방법
CN101499208A (zh) * 2008-02-02 2009-08-05 厦门雅迅网络股份有限公司 一种通过gps定位和移动通信网络处理车辆道路救援的系统和方法
CN101556735A (zh) * 2008-04-11 2009-10-14 郑波 汽车碰撞自动报警系统
CN101404705A (zh) * 2008-10-21 2009-04-08 深圳职业技术学院 一种事故报警系统
KR20100073893A (ko) * 2008-12-23 2010-07-01 이현호 차량용 블랙박스 및 이를 이용한 사고 관리 방법 및 시스템
US20100248681A1 (en) * 2009-03-27 2010-09-30 Anthony Phills Method and system for producing emergency notifications
US9491420B2 (en) * 2009-09-20 2016-11-08 Tibet MIMAR Vehicle security with accident notification and embedded driver analytics
CN101807337A (zh) * 2010-03-18 2010-08-18 北京创毅视讯科技有限公司 一种基于物联网的车载紧急救助装置和方法
CN101969474A (zh) * 2010-11-03 2011-02-09 北京中交兴路信息科技有限公司 一种车载移动终端呼叫信息管理的方法
CN102039865A (zh) * 2010-12-14 2011-05-04 洪印涛 车载交通事故智能报警系统及控制方法
KR101252670B1 (ko) 2011-01-27 2013-04-09 한국과학기술연구원 연관 콘텐츠 제공 장치, 방법 및 컴퓨터 판독 가능한 기록 매체
CN103569008A (zh) 2012-07-19 2014-02-12 福兴达科技实业（深圳）有限公司 一种汽车紧急自动报警系统及方法
US20140046701A1 (en) * 2012-08-12 2014-02-13 Insurance Services Office, Inc. Apparatus and Method for Detecting Driving Performance Data
CN102868735B (zh) * 2012-08-31 2017-10-17 厦门雅迅网络股份有限公司 一种用于紧急救援进度查询的实现方法
CN202863368U (zh) 2012-09-17 2013-04-10 宁波远景汽车零部件有限公司 一种汽车碰撞安全系统
WO2014047695A2 (en) 2012-09-25 2014-04-03 Kazamias Christian Christos "personalized emergency, safety & rules based interactive alert notification system
AU2014262897B2 (en) * 2013-05-04 2018-03-22 Christopher Decharms Mobile security technology
CN203406964U (zh) 2013-07-11 2014-01-22 深圳市得旺瑞电电子有限公司 一种微动触发式监控装置
US20150065082A1 (en) * 2013-08-27 2015-03-05 Akhil SEHGAL Personal safety device, system and a method
CN104554106A (zh) * 2013-10-17 2015-04-29 董幼兰 车辆碰撞的自动报警装置
CN104657203B (zh) * 2013-11-21 2018-07-20 腾讯科技（深圳）有限公司 任务执行方法、装置和系统
CN104753906B (zh) * 2013-12-31 2017-05-24 腾讯科技（深圳）有限公司 转移数据方法、装置和系统
JP6444604B2 (ja) * 2014-03-18 2018-12-26 株式会社デンソーテン 通信端末、通信システム、通報方法、及び、プログラム
JP6630719B2 (ja) * 2014-07-23 2020-01-15 クアルコム，インコーポレイテッド 車両開始型緊急呼
ES2950595T3 (es) * 2014-09-05 2023-10-11 Vinli Inc Sistema de información de vehículo
KR101589214B1 (ko) * 2014-09-23 2016-01-27 현대자동차주식회사 차량에서의 안테나 제어 방법 및 장치
CN204314957U (zh) 2014-12-16 2015-05-06 余世平 一种行车记录仪
WO2016095753A1 (en) * 2014-12-18 2016-06-23 Qualcomm Incorporated Techniques to support emergency calls with over-the-top service provider
US10447644B2 (en) * 2015-04-23 2019-10-15 Facebook, Inc. Sending notifications as a service
CN104965643B (zh) * 2015-06-19 2019-05-03 腾讯科技（深圳）有限公司 信息处理方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3672838B2 (ja) * 2001-04-18 2005-07-20 昇 赤坂 緊急対応システム
CN103903406A (zh) * 2012-12-30 2014-07-02 王方淇 一种突发事件监测通知方法及系统
CN103247169A (zh) * 2013-04-17 2013-08-14 浙江大学 一种基于社交网络的车辆信息发布方法
CN105262792A (zh) * 2015-09-09 2016-01-20 深圳市元征科技股份有限公司 一种车辆异常处理方法及车载终端
CN105407456A (zh) * 2015-10-22 2016-03-16 上海救要救信息科技有限公司 一种处理求救信息的方法和系统
CN105761425A (zh) * 2016-03-24 2016-07-13 腾讯科技（深圳）有限公司 求救方法、系统及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3367356A4 *

Also Published As

Publication number Publication date
CN105761425B (zh) 2019-09-03
CN105761425A (zh) 2016-07-13
KR20180057690A (ko) 2018-05-30
US10769922B2 (en) 2020-09-08
JP2019503527A (ja) 2019-02-07
JP6918291B2 (ja) 2021-08-11
US20180233015A1 (en) 2018-08-16
EP3367356A4 (en) 2018-09-05
EP3367356A1 (en) 2018-08-29
KR102045977B1 (ko) 2019-11-18

Similar Documents

Publication Publication Date Title
WO2017162212A1 (zh) 求救方法、系统、装置及计算机存储介质
US20230123348A1 (en) Systems and methods for emergency communications
WO2018177425A1 (zh) 一种请求救援的方法、装置和系统
WO2021203037A1 (en) Systems and methods for identifying and activating emergency response assets
JP6012895B1 (ja) 情報管理システム、通信端末及びプログラム
WO2017080201A1 (zh) 基于卫星定位的预警方法及系统、服务器
WO2021077843A1 (zh) 协同呼救方法、装置、可穿戴设备和存储介质
EP3545508B1 (en) Method and device for selecting notification recipient
CA2831520A1 (en) Method and system for monitoring interactions with a vehicle
US20220038880A1 (en) Vehicle with automatic reporting function
JP2021184306A (ja) 位置特定システムおよび位置特定方法
CN107529136B (zh) 基于共享信息的交通安全服务方法和系统
JP7016959B2 (ja) 運転評価装置
US20200139930A1 (en) Systems and Methods for Identifying Unauthorized Vehicle Use
KR20130006910A (ko) 차량용 블랙 박스를 이용한 사고 대응 시스템 및 그에 의한 사고 대응 방법
US11956695B2 (en) Server for automatic emergency reporting system of vehicle
JP2007004772A (ja) ワイヤレス・システムを介して緊急対応を提供するためのシステムおよび方法
Tippannavar et al. IoT enabled Smart Car with V2X Enhanced Comunication and Safety Alert system
JPWO2020031828A1 (ja) 運転評価装置
WO2022179462A1 (zh) 多设备联合呼叫方法和装置
WO2018209830A1 (zh) 提高寻找宠物效率的方法及装置
CN217902525U (zh) 车辆碰撞触发急救系统
Gadekar et al. Smart Application For Post Accident Management Using IoT
Kumar et al. Advancements in IoT Technology: A Comprehensive Approach to Accident Detection and Emergency Response
CN115862293A (zh) 信息传输方法及相关装置

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 20187011377

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2018521067

Country of ref document: JP

WWE Wipo information: entry into national phase

Ref document number: 2017769489

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE