Emergency help seeking method, readable storage medium and electronic equipment

Abstract

The invention relates to the technical field of terminals, and discloses an emergency help seeking method, a readable storage medium and electronic equipment. According to the method, after the terminal equipment detects that a user is in a riding state, sensor data and audio data are collected to judge whether the user has a traffic accident or not. The terminal equipment can prompt the user in the first prompt mode within the first time length after the traffic accident of the user occurs. When the user operation is not detected during the first duration, the user can be prompted in the second duration through the second prompting mode with the prompting intensity higher than that of the first prompting mode. And the terminal equipment still does not detect the user operation after the second duration ends, and can execute automatic help seeking. And in the first duration and the second duration, the terminal equipment can execute emergency help seeking or cancel emergency help seeking according to the user operation. Therefore, the success rate of help seeking is improved, and the situations of wrong help seeking and missed help seeking are reduced.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to an emergency assistance method, a readable storage medium and an electronic device. Background Art

[0002] In order to facilitate users to seek help in time when unexpected situations occur, terminal devices are usually equipped with an emergency help function, through which users can set emergency contacts. Based on the user's operation of the terminal device, such as pressing the power button of the terminal device multiple times, the terminal device executes the emergency help function and sends a message to the emergency contact preset by the user or dials the number of the emergency contact. However, in some scenarios, such as a vehicle accident, the user of the terminal device may be unable to operate the terminal device due to injury, resulting in the user being unable to seek help through the terminal device. Summary of the invention

[0003] In view of this, the present application provides an emergency assistance method, a readable storage medium and an electronic device.

[0004] In a first aspect, the present application provides an emergency assistance method, which is applied to an electronic device, and the method includes: when a user is in a riding state and first data collected by the electronic device meets a first condition, prompting the user through a first prompt method within a first time period that automatic emergency assistance will be executed, wherein the first condition is used to indicate that the user of the electronic device has been involved in a traffic accident; when no operation of the user on the electronic device is detected within the first time period, prompting the user through a second prompt method that automatic emergency assistance will be executed, wherein the prompt intensity of the second prompt method is higher than the prompt intensity of the first prompt method; when no operation of the user on the electronic device is detected within the second time period, executing automatic emergency assistance.

[0005] In this method, the electronic device collects the first data (such as sensor data and / or audio data) only when the user is in a vehicle state, and determines whether the user has a traffic accident based on the first data (such as whether the first data satisfies the first condition). When the user has a traffic accident (such as the first data satisfies the first condition), the user is prompted to perform automatic emergency assistance. In this way, it is possible to reduce false requests for assistance and missed requests for assistance, and save the power consumed by the electronic device.

[0006] In the process of prompting the user, the user is prompted by the first prompt method within the first time period that automatic emergency help will be executed; when the user's operation on the electronic device is not detected within the first time period, the user is prompted by the second prompt method that automatic emergency help will be executed, wherein the prompt intensity of the second prompt method is higher than the prompt intensity of the first prompt method; when the user's operation on the electronic device is not detected within the second time period, automatic emergency help is executed. In this way, if the user does not find that a false help request has been triggered because the prompt intensity of the first prompt method is too low, the user can be prompted by the second prompt method with higher intensity, so that the user can cancel the help request in time. In addition, prompting the user by the second prompt method can also wake up users who are in a mild coma, which is conducive to increasing the possibility of users receiving timely assistance.

[0007] In a possible implementation of the first aspect above, executing automatic emergency assistance includes at least one of the following methods: sending an assistance message to at least one contact; or dialing a number of at least one contact; or contacting at least one contact through an instant messaging application.

[0008] In a possible implementation of the first aspect, the emergency assistance method further includes: when a user confirmation of an emergency assistance operation is detected within the first time period or the second time period, executing the emergency assistance.

[0009] That is to say, while the electronic device is prompting the user, the user can immediately seek emergency help by operating the electronic device, sending a help message to at least one contact; or calling the number of at least one contact; or contacting at least one contact through an instant messaging application.

[0010] In a possible implementation of the first aspect, the emergency assistance method further includes: when a user cancelling the emergency assistance operation is detected within the first time period or the second time period, exiting the emergency assistance.

[0011] That is to say, while the electronic device is prompting the user, the user can cancel the emergency request by operating the electronic device to avoid mistakenly asking for help and affecting others.

[0012] In a possible implementation of the first aspect, the user is in a riding state, including: the electronic device is connected to the vehicle's vehicle-mounted Bluetooth; or the electronic device is connected to the vehicle's vehicle-mounted system; or the user behavior recognition module running in the electronic device recognizes that the user is in a riding state.

[0013] In this implementation, when at least one of the above conditions is met, the electronic device can identify that the user is in a vehicle. In this way, the accuracy of the electronic device in identifying that the user is in a vehicle can be improved, thereby improving the accuracy of triggering emergency assistance. For example, when the electronic device is not connected to the vehicle's vehicle-mounted Bluetooth and is not connected to the vehicle's vehicle-mounted system, it can be identified based on the electronic device user behavior identification module whether the user is in a vehicle, and when the user is in a vehicle, it is determined whether the first data collected by the electronic device meets the first condition.

[0014] In a possible implementation of the first aspect above, the first data includes sensor data and audio data; and the first condition includes: identifying that a traffic accident occurs to a user of the electronic device based on the sensor data, and identifying that a traffic accident occurs to the user of the electronic device based on the audio data.

[0015] In this implementation, the electronic device can obtain the judgment result of whether the user has a traffic accident based on the sensor data and the audio data, and determine that the first data meets the first condition when both results indicate that the user has a traffic accident. In this way, the accuracy of the electronic device in identifying that the user has a traffic accident can be improved, thereby improving the accuracy of triggering emergency assistance.

[0016] In a possible implementation of the first aspect, the identifying, based on sensor data, that a user of the electronic device has been involved in a traffic accident includes: obtaining, based on the sensor data, a neck injury index greater than a preset value.

[0017] In a possible implementation of the first aspect, the above-mentioned identification of a traffic accident involving a user of an electronic device based on audio data includes: using a pre-trained artificial intelligence model to infer the audio data to obtain an inference result indicating that the user of the electronic device has been involved in a traffic accident.

[0018] In a possible implementation of the first aspect, the method further includes: displaying a countdown for executing automatic emergency assistance within the first time period and the second time period.

[0019] In a possible implementation of the first aspect, the first prompt method includes at least one of the following methods: playing the prompt information at a first volume; vibrating a motor of the electronic device at a first vibration amplitude.

[0020] In a possible implementation of the first aspect above, the second prompt method includes at least one of the following methods: playing the prompt information at a second volume, wherein the second volume is greater than the first volume; vibrating the motor of the electronic device at a second vibration amplitude, wherein the second vibration amplitude is greater than the first vibration amplitude; flashing the light-emitting unit of the electronic device.

[0021] In a second aspect, the present application provides a readable storage medium, which includes instructions. When the instructions are executed by a device, the device implements the emergency assistance method provided by the first aspect and any possible implementation of the first aspect.

[0022] In a third aspect, the present application provides a device, comprising: a memory for storing instructions; a processor for executing instructions to enable the device to implement the emergency assistance method provided by the first aspect and any possible implementation of the first aspect.

[0023] In a fourth aspect, the present application provides a program product, which, when running on a device, enables the device to implement the emergency assistance method provided by the first aspect and any possible implementation of the first aspect.

[0024] It should be understood that the beneficial effects of the second to fourth aspects mentioned above can be referred to the description of the first aspect mentioned above, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1A According to some embodiments of the present application, a schematic diagram of an interface displayed on the mobile phone 10 when a user turns on the emergency assistance function of the mobile phone 10 is shown;

[0026] Figure 1B According to some embodiments of the present application, a schematic diagram of a mobile phone 10 detecting that a user is in a vehicle riding state is shown;

[0027] Figure 2A According to some embodiments of the present application, a schematic diagram of a prompt interface U1 displayed when the mobile phone 10 detects that a user has a traffic breakdown is shown;

[0028] Figure 2B According to some embodiments of the present application, a schematic diagram of an emergency call interface U2 displayed by a mobile phone 10 when a user chooses to enter an emergency call is shown;

[0029] Figure 2C According to some embodiments of the present application, a schematic diagram of a dialing interface U3 displayed by a mobile phone 10 when a user selects option 120 is shown;

[0030] Figure 2D According to some embodiments of the present application, a schematic diagram of a dialing interface U4 displayed by a mobile phone 10 when a user selects an emergency contact C1 option is shown;

[0031] Figure 2E According to some embodiments of the present application, a schematic diagram of an interface displayed by a mobile phone 10 during an automatic help request is shown;

[0032] Figure 2FAccording to some embodiments of the present application, a schematic diagram of a mobile phone 10 sending a help message M1 to a mobile phone 40 is shown;

[0033] Figure 3 According to some embodiments of the present application, a flowchart of an emergency assistance method is shown;

[0034] Figure 4 According to some embodiments of the present application, a schematic diagram of a software architecture is shown;

[0035] Figure 5 According to some embodiments of the present application, a schematic diagram of a process of an emergency assistance method is shown;

[0036] Figure 6 According to some embodiments of the present application, a schematic diagram of an interaction process of an emergency assistance method is shown;

[0037] Figure 7 According to some embodiments of the present application, a schematic diagram of an implementation process of an emergency assistance method is shown;

[0038] Figure 8 According to some embodiments of the present application, a schematic diagram of a data acquisition interface 51 collecting sensor data is shown;

[0039] Fig. 9 According to some embodiments of the present application, a schematic diagram of an interactive process of the collision service 423 initiating emergency assistance after receiving a collision message is shown;

[0040] Fig.10 According to some embodiments of the present application, a schematic diagram of an interaction process of registering and deregistering a ride listener for a collision service 423 is shown;

[0041] Fig.11 According to some embodiments of the present application, a schematic diagram of an interaction process of enabling and disabling collision detection by a collision service 423 is shown;

[0042] Fig.12 According to some embodiments of the present application, a schematic diagram of enabling / disabling collision detection when the connection state of the collision service 423 with the vehicle system changes is shown;

[0043] Fig.12 According to some embodiments of the present application, a schematic diagram of enabling / disabling collision detection when the connection state of the collision service 423 with the vehicle system changes is shown;

[0044] Fig.13 According to some embodiments of the present application, a schematic diagram of enabling / disabling collision detection by a collision service 423 when a user status reported by an MSDP 433 changes is shown;

[0045] Fig.14 According to some embodiments of the present application, a schematic diagram of enabling / disabling collision detection when the connection state of the collision service 423 with the vehicle Bluetooth changes is shown;

[0046] Fig.15 According to some embodiments of the present application, a schematic structural diagram of a mobile phone 10 is shown. DETAILED DESCRIPTION

[0047] Illustrative embodiments of the present application include, but are not limited to, an emergency assistance method, a readable storage medium, and an electronic device.

[0048] To ensure that when a vehicle is involved in a traffic accident, the user can also make emergency requests through the terminal device when the user is unable to operate the terminal device or it is inconvenient to operate the terminal device, the terminal device can automatically make emergency requests, such as sending a message to the user's preset emergency contact or connecting the emergency contact's phone. For example, in some embodiments, the terminal device can determine whether the terminal device has a severe collision based on the acceleration data collected by the terminal device, and perform automatic requests for help when it is determined that the terminal device has a severe collision (indicating that the user of the terminal device may be involved in a traffic accident).

[0049] However, in some scenarios, such as when the terminal device accidentally falls or when the user carries the terminal device to perform sports with drastic acceleration changes (such as bungee jumping or riding a roller coaster), the acceleration data collected by the terminal device may change in a manner similar to a traffic accident, and the terminal device will automatically perform an emergency call. In this way, the terminal device automatically performs the emergency call function in a scenario where the user has not been involved in a traffic accident, resulting in a false call for help.

[0050] In order to improve the accuracy of emergency help from terminal devices, an embodiment of the present application provides an emergency help method. The terminal device can first detect whether the user is in a riding state, and after detecting that the user is in a riding state, collect sensor data and audio data, etc., and judge whether the user has a traffic accident based on the collected sensor data and audio data. When the user has a traffic accident, the terminal device can prompt the user that automatic help is about to be executed and display the countdown for automatic help, and automatically ask for help after the countdown ends. When the terminal device detects that the user is not in a riding state, it will not detect whether the user has a traffic accident, and will not perform automatic emergency help. In this way, it can avoid the situation where the terminal device mistakenly asks for help in some scenarios (such as the terminal device falls, the user carries the terminal device for strenuous exercise, etc.). In addition, since the terminal device consumes more power in the process of detecting whether the user has a traffic accident, when the user is not in a riding state, the terminal device does not detect whether the user has a traffic accident, which can also improve the battery life of the terminal device.

[0051] It should be understood that during the prompting of the user, the terminal device can immediately make or stop the emergency assistance according to the user's operation. In this way, the user can operate the terminal device to promptly make emergency assistance when emergency assistance is currently needed, so that the user can get help in time; the user can also cancel the emergency assistance when emergency assistance is not currently needed to avoid sending a message to the emergency contact or calling the emergency contact's number to affect the emergency contact.

[0052] In some embodiments, the terminal device may first prompt the user through the first prompt method during the prompting of the user. If the terminal device does not detect the user's operation on the terminal device within the first time period, the terminal device may prompt the user in the second prompt method within the second time period after the first time period. If the terminal device still does not detect the user's operation on the terminal device after the second time period (for example, after the aforementioned countdown ends), the terminal device may automatically ask for help (for example, automatically dial a phone call, send a message, contact an emergency contact through an instant messaging application, etc.). Among them, the intensity of the second prompt method to prompt the user is higher than the first prompt method (for example, the audio volume played by the second prompt method is greater than the first prompt method, the vibration intensity of the terminal device when the second prompt method prompts the user is greater than the first prompt method, and the second prompt method has more prompt types than the first prompt method, etc.).

[0053] Since the prompt intensity of the second prompt mode is greater than that of the first prompt mode, when the user is involved in a traffic accident, the second prompt mode can be used to prompt the user in a mild coma within the second time period to wake up the user, so that the user can wake up in time and operate the terminal device for emergency help. When the user is not involved in a traffic accident, the second prompt mode can be used to prompt the user within the second time period to avoid the user not being aware of the prompt due to reasons such as a noisy environment, so that the user can operate the terminal device in time to terminate the emergency help and avoid the situation of mistaken help.

[0054] In some embodiments, the first prompting method may include: the terminal device displays a countdown for automatic emergency assistance, and the terminal device plays a prompting voice at a first volume.

[0055] Optionally, in some embodiments, the first prompting method may also include the terminal device vibrating a motor with a first vibration intensity.

[0056] In some embodiments, the second prompting method may include: the terminal device displays a countdown for automatic emergency assistance, and the terminal device plays a prompt voice at a second volume, wherein the second volume is higher than the first volume.

[0057] Optionally, in some embodiments, the second prompt method may also include at least one of the following methods: the terminal device vibrates the motor with a second vibration intensity, the terminal device flashes the display screen, the terminal device flashes or keeps the flash light on, wherein the second vibration intensity is higher than the first vibration intensity.

[0058] In some embodiments, the terminal device can detect that the user is in a vehicle when the terminal device is connected to the vehicle Bluetooth; it can also detect that the user is in a vehicle after the terminal device is connected to the vehicle through the vehicle system; it can also detect that the user is in a vehicle when the user behavior recognition module (multimodal sensor data platform, MSDP) in the terminal device determines that the user is in a vehicle. In this way, the terminal device can detect that the user is in a vehicle in a variety of ways, which can avoid the situation where the terminal device does not detect whether a traffic accident occurs when the vehicle is not equipped with Bluetooth or the vehicle system, thereby avoiding the situation where a request for help is missed.

[0059] In some embodiments, the terminal device can obtain a sensor detection result corresponding to the sensor data and an audio detection result corresponding to the audio data based on the sensor data and the audio data, respectively, and when both the sensor detection result and the audio detection result indicate that the user has had a traffic accident, it is determined that the terminal device has had a traffic accident. In this way, it is possible to avoid erroneous requests for help caused by an error in the detection result corresponding to the sensor data or the audio data.

[0060] The technical solution of the present application can be applied to any electronic device, including but not limited to mobile phones, wearable devices (such as smart bracelets, smart watches), tablet computers, etc. For ease of description, the technical solution of the present application is introduced below by taking the terminal device as a mobile phone 10 as an example.

[0061] For example, Figure 1A According to some embodiments of the present application, a schematic diagram of an interface displayed on the mobile phone 10 when a user turns on the emergency assistance function of the mobile phone 10 is shown.

[0062] The mobile phone 10 can display the following information after the user selects the security settings option in the settings application: Figure 1A The safety interface U0 shown includes options related to safety devices in the mobile phone 10, such as the SOS emergency help option U01. When the user selects the SOS emergency help option U01 in the safety interface U0, the mobile phone 10 can display the SOS emergency help interface U02. The SOS emergency help interface U02 includes settings related to SOS emergency help, such as the emergency contact option U03, the automatic help option switch U04 after a car accident, and the smooth help switch U05.

[0063] The user can set emergency contacts through the emergency contact option U03, turn on the "automatically initiate help after a car accident" function in the mobile phone 10 by turning on the automatic help after a car accident option switch U04, and turn on the function of asking for help through instant messaging applications (such as Changlian applications, etc.) through the Changlian help switch U05.

[0064] After the "automatically initiate help after a car accident" function is turned on, after a car accident occurs to the user, the mobile phone 10 can call emergency contacts in sequence and play a help recording after a 90-second countdown, automatically hang up the call after the playback is completed, and send a help message with the current location at the same time.

[0065] After the "automatically initiate help after a car accident" function is turned on, the mobile phone 10 can detect whether the user is in a car. Figure 1B , the mobile phone 10 detects that the user is in the vehicle state when it has been connected to the vehicle computer of the vehicle 20 through Bluetooth. The mobile phone 10 can also detect that the user is in the vehicle state when it is connected to the vehicle 20 through the vehicle computer system (such as the HiCar vehicle computer system). The mobile phone 10 can also detect that the user is in the vehicle state when it obtains the user's state as being in the vehicle from the calling interface of the MSDP.

[0066] It should be understood that in other embodiments, the mobile phone 10 may also detect whether the user is in a vehicle state in other ways.

[0067] When the user is in a vehicle, the mobile phone 10 can collect sensor data and audio data, and determine whether the user has a traffic accident based on the collected sensor data and audio data. After the user has a traffic accident, the mobile phone 10 can prompt the user.

[0068] For example, refer to Figure 2A After the collision between the vehicles 20 and 30, the mobile phone 10 can detect that the user has a traffic accident and display a prompt interface U1 within a preset time. The interface U1 includes a countdown control U11 for the mobile phone 10 to execute automatic help, an "enter emergency call" control U12, and an "exit" control U13.

[0069] When the mobile phone 10 displays the prompt interface U1, it prompts the user in a first prompting manner within a first time period (e.g., first 60 seconds) before a preset time period (e.g., 90 seconds). For example, the mobile phone 10 can play a prompting voice at a first volume (e.g., 80% of the maximum volume of the mobile phone 10) saying "It is detected that the vehicle you are riding in may have an accident, and emergency assistance will be automatically requested after the countdown ends."

[0070] If the mobile phone 10 does not detect the user performing an emergency assistance operation within the first time period, it can prompt the user in a second prompting manner within a second time period (e.g., the last 30 seconds) after the first time period. For example, the mobile phone 10 can play a prompting voice at a second volume (e.g., the maximum volume of the mobile phone 10) "It is detected that the vehicle you are riding in may have an accident, and emergency assistance will be automatically requested after the countdown ends", and vibrate the motor of the mobile phone 10 and flash the light-emitting unit of the mobile phone 10 (e.g., indicator light, flashlight, etc.).

[0071] In some embodiments, when the mobile phone 10 detects that the user performs an emergency request operation within the first time period or the second time period, the mobile phone 10 can dial the corresponding number according to the number or contact selected by the user. Figure 2B When the countdown control U11 counts down to 30 seconds, when the user slides to the right on the "Enter Emergency Call" control U12, the mobile phone 10 can display the emergency call interface U2. The emergency call interface U2 includes the helpline numbers preset by the mobile phone 10 (such as the emergency center's phone number 120, the police phone number 110, etc.), as well as the contact numbers of the emergency contacts set by the user (such as the emergency contact C1's phone number 123456789, the emergency contact C2's phone number 987654321, etc.). The mobile phone 10 can dial the corresponding number based on the helpline or emergency contact selected by the user. For example, refer to Figure 2C When the user selects 120 in the emergency call interface U2 (for example, when the user clicks 120), the dialing interface U3 is displayed and the number 120 is automatically dialed; for example, referring to Figure 2D When the user selects the emergency contact C1 in the emergency call interface U2 (for example, when the user clicks on the emergency contact C1), the dialing interface U4 is displayed and the number 123456789 of the emergency contact C1 is automatically dialed.

[0072] In some embodiments, if the aforementioned Changlian help switch U05 is turned on, the mobile phone 10 can also contact an emergency person through the Changlian application.

[0073] In some embodiments, when the mobile phone 10 detects that the user cancels the emergency help request within the first time period or the second time period, the emergency help request may be canceled. For example, when the user clicks the "Exit" control U13 in the aforementioned prompt interface U1, the emergency help request may be canceled.

[0074] When the mobile phone 10 does not detect the user's operation within the second time period, it can perform automatic assistance. Figure 2EAfter the countdown ends, the mobile phone 10 can dial the number 123456789 of the emergency contact C1 set by the user and display the dialing interface U4' (compared to the dialing interface U4, the "hands-free" control U41 in the dialing interface U4' is activated). After the call of the emergency contact C1 is connected, the mobile phone 10 can automatically play the help recording and display the "playing help recording" control U51 in the call interface U5. The help recording can include the help information pre-recorded by the user or preset by the mobile phone 10, the current location information of the mobile phone 10, etc.

[0075] In some embodiments, the hands-free function can be turned on when the mobile phone 10 plays the help recording. Figure 2E , the "hands-free" control U52 is activated, and the mobile phone 10 can play the help recording and call audio through the speaker. In this way, during the call for help, the mobile phone 10 can try to wake up the user in a coma by playing the help recording and call audio, and it is also convenient for the user to talk to the emergency contact when he cannot operate the mobile phone 10.

[0076] In some embodiments, when the user selects the "playing help recording" control U51 (for example, when the user clicks the "playing help recording" control U51) while the mobile phone 10 is playing the help recording, the mobile phone 10 can stop playing the help recording, turn off the hands-free function and display the call interface U6. Figure 2E In the call interface U6, the "hands-free" control U52 is in an inactive state, and the mobile phone 10 does not play audio through the speaker.

[0077] In some embodiments, when the mobile phone 10 fails to connect to a call from an emergency contact or a call for help, it can automatically dial another emergency contact or a call for help, thereby improving the success rate of emergency help.

[0078] In some embodiments, the mobile phone 10 can also send a help message, such as a help message, to the emergency contact during the automatic help process. Figure 2F , the mobile phone 10 can send a help message M1 to the mobile phone 40 of the emergency contact C1: "

Car Accident SOS Help

[0079] Combine the following Figures 1A to 2F , combined with the technical solution of this application.

[0080] Figure 3 According to some embodiments of the present application, a schematic diagram of a process of an emergency assistance method is shown. The execution subject of the process is a mobile phone 10, such as Figure 3 As shown, the process includes the following steps:

[0081] S301: Monitor the status of the "automatically initiate help after a traffic accident" function switch.

[0082] After being started, the mobile phone 10 can monitor the status of the "automatically initiate help after a car accident" function switch, and after monitoring that the "automatically initiate help after a car accident" function switch is turned on, execute step S302.

[0083] For example, refer to Figure 1A When the user turns on the "option switch U04 for automatically initiating help after a car accident", the mobile phone 10 can monitor that the function switch of "automatically initiating help after a car accident" is turned on, and execute step S302.

[0084] S302: Determine whether the user is in a riding state.

[0085] After the "automatically initiate help after a car accident" function switch is turned on, the mobile phone 10 can determine whether the user is in a car state. When the user is in a car state, the mobile phone 10 can detect whether the user has a traffic accident and go to step S303; otherwise, when the user is not in a car state, it means that the mobile phone 10 does not need to detect whether the user has a traffic accident and repeats step S302.

[0086] In some embodiments, the mobile phone 10 can determine whether the user is in a vehicle in a variety of ways, so that the mobile phone 10 can accurately detect that the user is in a vehicle in a variety of situations.

[0087] For example, the mobile phone 10 can monitor the Bluetooth of the mobile phone 10, the service or module corresponding to the vehicle system (such as Hicar), and MSDP. When the Bluetooth of the mobile phone 10 is connected to the vehicle Bluetooth, or the service or module corresponding to the vehicle system is connected to the vehicle system, or the user status reported by MSDP is the riding state, it is determined that the user is in the riding state, and the process goes to step S303. In this way, even if the mobile phone 10 is not connected to the vehicle Bluetooth or the vehicle system, the mobile phone 10 can determine whether the user is in the riding state based on MSDP, which is conducive to improving the accuracy of the mobile phone 10 in determining that the user is in the riding state.

[0088] It should be understood that in other embodiments, the mobile phone 10 may also determine whether the user is in a vehicle state by other means, which is not limited here.

[0089] It should be understood that the MSDP can determine the user status based on the location information of the mobile phone 10, the sensor data (such as acceleration data, air pressure sensor data, etc.) collected by the mobile phone 10, etc., and the user status can at least include the state of riding a vehicle (also referred to as a vehicle-mounted state). In some embodiments, the above user status can also include: riding a vehicle, riding a bicycle, walking, running, stationary, fast walking, high-speed rail, unknown, elevator, relatively stationary, hand-held walking, lying down, flying, subway, etc.

[0090] S303: Collect sensor data and audio data.

[0091] When the user of the mobile phone 10 is in a vehicle, the mobile phone 10 can collect sensor data and audio data, and the sensor data and audio data can be used to determine whether the user of the mobile phone 10 is involved in a traffic accident.

[0092] In some embodiments, the sensor data may include at least acceleration data.

[0093] In some embodiments, if the user is not in a vehicle, the mobile phone 10 may not collect sensor data and audio data. This helps to reduce the power consumption of the mobile phone 10 and avoids erroneous requests for help in some scenarios.

[0094] S304: Determine whether the user has a traffic accident.

[0095] After collecting the sensor data and the audio data, the mobile phone 10 can determine whether the user has a traffic accident. If the user has a traffic accident, it indicates that emergency assistance may need to be initiated, and the process goes to step S305; otherwise, the process goes to step S303 to continue collecting the sensor data and the audio data.

[0096] In some embodiments, the mobile phone 10 can use the sensor data and the audio data to detect whether the user has a traffic accident, and when both the detection results obtained using the sensor data and the audio data indicate that the user has a traffic accident, it is determined that the user has a traffic accident. In this way, it is possible to avoid false alarms caused by inaccurate sensor detection results based on sensor data or inaccurate audio detection results based on audio data, which is conducive to improving the accuracy of the mobile phone 10 in determining whether the user has a traffic accident.

[0097] In some embodiments, when the sensor data or audio data is abnormal, or the sensor data or audio data is not collected, the mobile phone 10 determines that the user has a traffic accident when one of the sensor detection results and the audio detection results indicates that the user has a traffic accident. In this way, when the sensor or the audio module that collects audio data fails due to a traffic accident, it can be detected that the user has a traffic accident.

[0098] For example, the mobile phone 10 may calculate a neck injury index (NIC) through sensor data, and when the value of the NIC exceeds a preset value, it is determined that the user has been involved in a traffic accident.

[0099] Exemplarily, the mobile phone 10 can match the collected audio data with the audio data of the car accident collision through a pre-trained artificial intelligence model, and when the matching degree between the collected audio data and the audio data of the car accident collision is greater than a preset matching degree, it is determined that the user has been involved in a traffic accident.

[0100] It should be understood that in other embodiments, the mobile phone 10 may also determine whether the user has a traffic accident based on the collected sensor data and / or audio data in other ways, and proceed to step S304.

[0101] S305: Displaying a prompt interface to prompt the user in a first prompting manner within a first time period that automatic assistance is about to be performed.

[0102] When a user is involved in a traffic accident, the mobile phone 10 may display a prompt interface and prompt the user that automatic assistance is about to be requested through a first prompt method within a first time period.

[0103] In some embodiments, the prompt interface may also include a countdown for the mobile phone 10 to perform automatic assistance.

[0104] For example, reference Figure 2A When a user has a traffic accident, the mobile phone 10 can display a prompt interface U1, which includes a countdown control U11 for the mobile phone 10 to automatically ask for help, an "enter emergency call" control U12, and an "exit" control U13. And within a first duration (for example, 60 seconds), the user is prompted in a first prompting manner. For example, the mobile phone 10 can play a prompt voice at a first volume (for example, 80% of the maximum volume of the mobile phone 10) within the first duration, "It is detected that the vehicle you are riding in may have an accident, and emergency help will be automatically requested after the countdown ends."

[0105] In some embodiments, when the mobile phone 10 plays the prompt voice, it can also determine the relationship between the current volume of the mobile phone 10 and the first volume. When the current volume of the mobile phone 10 is greater than the first volume, the mobile phone 10 can play the prompt voice at the current volume; when the current volume of the mobile phone 10 is less than or equal to the first volume, the mobile phone 10 can play the prompt voice at the first volume.

[0106] It should be understood that within the first time period, the mobile phone 10 can also detect the user's operations on the prompt interface, and jump to step S308 when it detects that the user performs an emergency assistance operation; jump to step S309 when it detects that the user cancels the emergency assistance operation; and jump to step S307 when no user operation is detected at the end of the first time period (for example, the countdown time reaches the first time period).

[0107] For example, for Figure 2A In the prompt interface U1 shown, when the mobile phone 10 detects that the user slides to the right on the "Enter Emergency Call" control U12 (as an operation to execute emergency assistance), it goes to step S308; when it detects that the user clicks the "Exit" control U13 (as an operation to cancel emergency assistance), it goes to step S309.

[0108] In some embodiments, the first prompt method may also include other prompt types, for example, vibrating the motor of the mobile phone 10 with a first vibration intensity, etc., which is limited here.

[0109] S306: When no user operation is detected within the first time period, prompt the user in a second prompting manner within a second time period that automatic assistance is about to be performed.

[0110] If the mobile phone 10 does not detect the user operation within the first time period, the user can be prompted by a second prompt method within the second time period that automatic help is about to be performed. The prompt intensity of the second prompt method is higher than that of the first prompt method.

[0111] In some embodiments, the second prompting method may include: playing a prompting voice at a second volume, wherein the second volume is greater than the first volume.

[0112] In some embodiments, the second prompting method may include more reminder types than the first prompting method. For example, the second prompting method may include at least one of the following methods: vibrating the motor of the mobile phone 10 at a second vibration intensity, flashing the light-emitting unit of the mobile phone 10 (such as an indicator light, a flash light, etc.).

[0113] S307: When no user operation is detected within the second time period, automatic assistance is performed.

[0114] If no user operation is detected within the second time period, the mobile phone 10 may perform automatic assistance.

[0115] For example, refer to Figure 2EWhen the countdown ends, the mobile phone 10 can dial the number 123456789 of the emergency contact C1 set by the user and display the aforementioned dialing interface U4. After the call of the emergency contact C1 is connected, the mobile phone 10 can automatically play the help recording and display the "playing help recording" control U51 in the call interface U5. The help recording can include the help information pre-recorded by the user or preset by the mobile phone 10, the current location information of the mobile phone 10, etc.

[0116] In some embodiments, when the mobile phone 10 plays the help recording, the hands-free function can be turned on so that the help recording and the call audio can be played out through the speaker. In this way, during the call for help, the mobile phone 10 can try to wake up the user who is in a coma by playing the help recording and the call audio, and it is also convenient for the user to talk to the emergency contact when he cannot operate the mobile phone 10.

[0117] In some embodiments, when the user selects the "playing help recording" control U51 (for example, when the user clicks the "playing help recording" control U51) while the mobile phone 10 is playing the help recording, the mobile phone 10 can stop playing the help recording, turn off the hands-free function and display the call interface U6. Figure 2E In the call interface U6, the "hands-free" control U52 is in an inactive state, and the mobile phone 10 does not play audio through the speaker.

[0118] In some embodiments, when the mobile phone 10 fails to connect to a call from an emergency contact or a call for help, it can automatically dial another emergency contact or a call for help, thereby improving the success rate of emergency help.

[0119] S308: In response to the user performing an emergency assistance operation within the first time period, performing emergency assistance.

[0120] When the mobile phone 10 detects that the user performs an operation of requesting emergency help within the first time period, it indicates that the user can currently operate the mobile phone 10 , and the mobile phone 10 can perform emergency help in response to the user's operation of requesting emergency help.

[0121] For example, refer to Figure 2B When the user slides right on the "Enter Emergency Call" control U12, the mobile phone 10 can display the emergency call interface U2. The emergency call interface U2 includes the helpline number preset by the mobile phone 10 and the contact number of the emergency contact set by the user. The mobile phone 10 can dial the corresponding number according to the helpline or emergency contact selected by the user. For example, refer to Figure 2C When the user selects 120 in the emergency call interface U2, the dialing interface U3 is displayed and the number 120 is automatically dialed; for example, referring to Figure 2DWhen the user selects the emergency contact C1 in the emergency call interface, the dialing interface U4 is displayed and the number 123456789 of the emergency contact C1 is automatically dialed.

[0122] S309: In response to the user canceling the emergency assistance request within the first time period, exiting the emergency assistance request.

[0123] When the mobile phone 10 detects that the user cancels the emergency assistance operation within the first time period, it means that the user confirms that emergency assistance is not needed at present (for example, no traffic accident has occurred at present, or the user is in good condition and does not need assistance), and the emergency assistance is exited.

[0124] Exemplarily, when the user clicks the "Exit" control U13 in the above prompt interface U1, the mobile phone 10 can cancel the emergency help. For example, the mobile phone 10 can switch to the interface before the prompt interface U1 is displayed, or return to the desktop of the mobile phone 10, or turn off the screen.

[0125] S310: In response to the user performing an emergency assistance operation within the second time period, performing emergency assistance.

[0126] If the mobile phone 10 detects that the user performs an emergency help operation within the second time period, it means that the user can currently operate the mobile phone 10, and the mobile phone 10 can respond to the user's emergency help operation and perform emergency help. For details, please refer to the aforementioned step S308, which will not be repeated here.

[0127] S311: In response to the user canceling the emergency assistance request within the second time period, exiting the emergency assistance request.

[0128] If the mobile phone 10 detects that the user cancels the emergency help operation within the second time period, it means that the user confirms that emergency help is not needed at present (for example, no traffic accident has occurred at present, or the user is in good condition and does not need help), and the emergency help is exited. For details, please refer to the above step S309, which is not limited here.

[0129] The emergency help method provided in the embodiment of the present application can improve the accuracy of the mobile phone 10 in automatically asking for help, and avoid wrong help requests and missed help requests in some scenarios.

[0130] Next, the technical solution of the present application is introduced in conjunction with the software architecture of the mobile phone 10.

[0131] Figure 4 According to some embodiments of the present application, a schematic diagram of a software architecture of a mobile phone 10 is shown.

[0132] like Figure 4As shown, the software architecture involves an application processor (AP) of the mobile phone 10, a smart sensor hub (Sensorhub), and a digital signal processor (DSP) for processing audio signals (referred to as audio DSP).

[0133] The software architecture involved in the AP includes an application layer 41 , a framework layer 42 and a hardware abstraction layer 43 .

[0134] The application layer 41 includes applications in the mobile phone 10, such as settings 411, Hicar 412, Bluetooth 413, cellular 414, global positioning system (GPS) 415, inertial measurement unit (IMU) 416, IncallUI 417, SMS 418, dialing 419, SOS 4110, smart domain 4111, etc.

[0135] Setting 411 is used to set the functions of the mobile phone 10, such as turning on or off the function of "automatically initiating help after a car accident" in the mobile phone 10. For example, in some embodiments, the emergency help information (EmergencyInfo) of setting 411 may include the aforementioned automatic initiation of help after a car accident option switch U04.

[0136] Hicar 412 is an application corresponding to the vehicle system, and can be used to connect to the vehicle system. In some embodiments, Hicar 412 can report the connection status with the vehicle system to other applications or services (such as collision service 423).

[0137] Bluetooth 413 can be used to communicate with other devices via Bluetooth technology. In some embodiments, Bluetooth 413 can report the connection status with the vehicle head unit Bluetooth to other applications or services (such as collision service 423).

[0138] Cellular 414 can be used to implement cellular communications of mobile phone 10 .

[0139] GPS 415 may be used to determine the location of mobile phone 10. IMU 416 may be used to measure inertial data of mobile phone 10, such as acceleration data.

[0140] IncallUI 417 can be used for displaying and updating the call interface. In some embodiments, IncallUI 417 can display a dialing interface, a communication interface, etc. in response to the scheduling of other applications or services.

[0141] The text message 418 can be used to implement the text message function of the mobile phone 10, such as the multimedia messaging service (MMS) function. In some embodiments, the text message 418 can be used to respond to the dispatch of other applications or services and send text messages to contacts (such as the aforementioned emergency contacts).

[0142] Dial 419 can be used to implement the dialing function of mobile phone 10. In some embodiments, dial 419 can be used to respond to the dispatch of other applications or services and dial a corresponding number (such as the aforementioned helpline, emergency contact number, etc.).

[0143] SOS help 4110 is used to start emergency help according to the dispatch of collision service 423, and call IncallUI 417, SMS 418, dialing 419, etc. to achieve emergency help. For example, in some embodiments, SOS help 4110 can be used to perform the process of the aforementioned steps S305 and S311.

[0144] The smart domain 4111 is used for scheduling artificial intelligence (AI) related functions in the mobile phone 10. For example, loading / unloading an AI model (hereinafter referred to as AI model) for determining whether a user has a traffic accident based on audio data, enabling / disabling audio detection, etc.

[0145] In some embodiments, collision detection may include audio detection (collecting audio data to detect whether the user has a traffic accident) and sensor detection (collecting sensor data to detect whether the user has a traffic accident).

[0146] The framework layer 42 may be used to provide an application programming interface (API) and a programming framework for the application programs of the application layer 41 .

[0147] In some embodiments, the framework layer 42 may include a system server 424 , a collision service 423 provided in the system server 424 , a telephony 421 , a telecomm 422 , and the like.

[0148] The system service 424 includes various services in the mobile phone 10. The collision service 423 is set in the system service 424 and can be resident in the mobile phone 10 as the system service runs.

[0149] The collision service 423 can be used to monitor the switch of the "automatically initiate help after a traffic accident" function in the setting 411, and determine whether the user is in a riding state by monitoring Hicar 412, Bluetooth 413, cellular 414, GPS 415, IMU 416, MSDP 433, etc., enable / disable collision detection (for example, enable / disable the audio detection module 61 and the collision detection module 52 to determine whether the user has a traffic accident), and after receiving the collision message sent by the collision detection module 52, send a collision message to the SOS help 4110.

[0150] Telephony 421 is a telephone service of the mobile phone 10 and is used to implement the telephone function of the mobile phone 10 .

[0151] telecomm 422 is located between dialing and the corresponding interface application and Phone framework, and is used to optimize the calling process of dialing related functions.

[0152] It should be understood that in some embodiments, the framework layer 42 may also include other modules, which are not limited here. For example, the framework layer 42 may also include an AI service for providing an AI function calling interface to the application layer 41.

[0153] The hardware abstraction layer (HAL) 43 may include an audio HAL 431 , a sensor HAL 432 , an MSDP 433 , and the like.

[0154] The audio HAL 321 is used to provide an access interface of the audio module to the application layer 41 and the framework layer 42. For example, an application or service in the application layer 41 or the framework layer 42 can control the audio DSP to collect audio data through the audio HAL, and determine whether the user has a traffic accident based on the collected audio data.

[0155] The sensor HAL 432 is used to provide the sensor access interface to the application layer 41 and the framework layer 42. For example, an application or service in the application layer 41 or the framework layer 42 can control the Sensorhub to collect sensor data through the sensor HAL, and determine whether the user has a traffic accident based on the collected sensor data and the detection results sent by the audio DSP.

[0156] In some embodiments, the collision detection module 52 can be abstracted as a sensor, such as a car crash sensor, and a collision sensor HAL corresponding to the collision sensor is set in the sensor HAL 432. The collision service 423 can obtain the detection result indicating whether the user has a traffic accident from the collision detection module 52 by monitoring the collision sensor HAL, such as receiving a collision message.

[0157] It should be understood that in some embodiments, the hardware abstraction layer 43 may also include other modules, such as Bluetooth HAL, etc., which are not limited here.

[0158] It should be understood that in some embodiments, the software architecture involved in the AP may also include more layers, such as a kernel layer, etc., which is used to provide the hardware abstraction layer 43 with drivers for various hardware and modules of each mobile phone 10 (such as Sensorhub driver, sensor driver, Bluetooth driver, etc.), which is not limited here.

[0159] The data acquisition interface 51 is used to receive sensor data collected by sensors in the mobile phone 10 (such as acceleration data collected by IMU, location data collected by GPS, air pressure data collected by air pressure sensor, etc.) and detection results sent by the audio DSP.

[0160] The collision detection module 52 is used to determine whether the user of the mobile phone 10 has a traffic accident based on the sensor data collected by the data acquisition interface 51 and the detection result sent by the audio DSP, and transmit the judgment result to the collision service 423 through the sensor HAL 432. For example, the collision detection module 52 can send a collision message to the collision service 423 when the user has a traffic accident.

[0161] MSDP 433 is a module for determining the user status of mobile phone 10. Other applications or services in mobile phone 10 can obtain the user status identified by MSDP 433 by monitoring MSDP 433.

[0162] In some embodiments, MSDP 433 may identify the user status based on data collected by various sensors in mobile phone 10, such as acceleration data collected by IMU, location data collected by GPS, air pressure data collected by air pressure sensor, and the like.

[0163] In some embodiments, user status may include riding in a vehicle (also referred to as in-vehicle), cycling, walking, running, stationary, brisk walking, high-speed rail, unknown, elevator, relatively stationary, handheld walking, lying down, taking a plane, taking the subway, etc.

[0164] The audio detection module 61 can call the neural-network processing unit (NPU) of the mobile phone 10 to detect whether the user has a traffic accident based on the audio data collected by the microphone of the mobile phone 10 using the aforementioned AI model, and send the detection result to the collision detection module 52 through the data acquisition interface 51.

[0165] Based on the above software architecture, the embodiment of the present application provides an emergency assistance method. The method may include:

[0166] ① After the user turns on the automatic help-seeking function after a car accident by setting 411, the emergency help method provided by this application is triggered.

[0167] For example, refer to Figure 5 After the system service 424 is running, the collision service 423 can be initialized. After the collision service 423 is running, the state of the switch of the "automatically initiate help after a car accident" function in the setting 411 can be monitored. After the switch is turned on, the riding monitor is registered; and after the switch is turned off, the riding monitor is deregistered.

[0168] ②, after the collision service 423 automatically initiates the help function after the car accident, it monitors Hicar 412, Bluetooth 413, and MSDP 433 to determine whether the user of the mobile phone 10 is in a car state.

[0169] After the collision service 423 automatically initiates the help function after a car accident, for example, after monitoring that the switch of the "automatically initiate help after a car accident" function is turned on, the riding monitoring can be registered and the user of the mobile phone 10 can be determined based on the monitored data whether it is in a riding state.

[0170] For example, reference Figure 5 , the collision service 423 can establish a connection with the MSDP 433 to monitor the user status reported by the MSDP 433. The collision service 423 can also monitor the broadcast of Hicar 412 to obtain the connection status with the vehicle system reported by Hicar 412. The collision service 423 can also monitor the broadcast of Bluetooth 413 to obtain the connection status with the vehicle Bluetooth reported by Bluetooth 413.

[0171] Exemplarily, the collision service 423 can judge that the user is in the riding state when it monitors that Hicar 412 is connected to the vehicle system, or Bluetooth 413 is connected to the vehicle Bluetooth, or MSDP 433 determines that the user status is riding based on the data of cellular 414, GPS 415, and IMU 416, and executes step ③.

[0172] ③, the collision service 423 enables collision detection when the user of the mobile phone 10 is in a vehicle.

[0173] For example, refer to Figure 4 and Figure 5 The collision service 423 can enable the audio detection module 61 to collect audio data and obtain audio detection results based on the collected audio data through the audio HAL 431 and the smart domain 4111, and can also enable the data acquisition interface 51 to perform data acquisition through the sensor HAL 432 and enable the collision detection module 52 to obtain sensor detection results based on the collected sensor data.

[0174] ④. The audio detection module 61 obtains an audio detection result based on the collected audio data, and sends the audio detection result to the collision detection module 52.

[0175] refer to Figure 5 After audio detection is enabled, the smart domain 4111 running in the mobile phone 10 can use the AI ​​service to call the NPU of the mobile phone 10 to use the aforementioned AI model to detect whether the user has a traffic accident, obtain the audio detection result, and send the audio detection result to the collision detection module 52 through the data acquisition interface 51.

[0176] ⑤. The collision detection module 52 determines whether the user of the mobile phone 10 has a traffic accident based on the audio detection result and the sensor data, and sends a collision message to the collision service 423 through the sensor HAL 432 when the user has a traffic accident.

[0177] For example, reference Figure 5 The collision detection module 52 can use the sensor data collected by the data acquisition interface 51 to obtain the sensor detection result. When the sensor detection result and the audio detection result both indicate that the user has a traffic accident, a collision message is sent to the collision service 423 through the sensor HAL 432.

[0178] ⑥. The collision service 423 initiates emergency assistance via the SOS assistance 4110.

[0179] When the collision service 423 monitors the collision message sent by the collision sensor (ie, the collision detection module 52 ), it sends the collision message to the SOS for help 4110 .

[0180] It should be understood that the SOS help 4110 can call SMS 418, dial 419, etc. to perform emergency help. For example, the aforementioned prompt interface U1 is displayed, and according to the user operation or when the countdown ends, SMS 418 is called to send a help message, and dial 419 is called to call a help phone or an emergency contact phone. For details, please refer to the aforementioned steps S305 to S311, which will not be repeated here.

[0181] Combine the following Figure 4 The software architecture shown introduces the technical solution of this application.

[0182] Figure 6 According to some embodiments of the present application, a schematic diagram of an interaction process of an emergency assistance method is shown. Figure 6 As shown, the interaction process includes the following steps:

[0183] S601: When the “automatically initiate help after a car accident” function switch is turned on, the collision service 423 registers the vehicle monitoring.

[0184] After the collision service 423 is running, it can monitor the status of the "automatically initiate help after a car accident" function switch in the setting 411, and register for the ride monitoring when it is monitored that the "automatically initiate help after a car accident" function switch of the collision service 423 is turned on.

[0185] In some embodiments, registering for on-board monitoring may include registering for connecting to the vehicle Bluetooth monitoring with Bluetooth 413 , registering for user status monitoring with MSDP 433 , registering for connecting to the vehicle system monitoring with Hicar 412 , and the like.

[0186] It should be understood that after the collision service 423 registers for the vehicle-riding monitoring, the Bluetooth 413 can report the connection status with the vehicle-machine Bluetooth to the collision service 423, the MSDP 433 can report the user status to the collision service 423 (for example, the user status is riding or not riding), and the Hicar 412 can report the connection status with the vehicle-machine system to the collision service 423.

[0187] The specific process of registering and unregistering the ride listener by the collision service 423 will be introduced below and will not be described in detail here.

[0188] S602: When the user is in a vehicle, the collision service 423 enables collision detection and monitors collision sensors.

[0189] After registering the riding monitoring, the collision service 423 can determine whether the user is in the riding state according to the data reported by the Bluetooth 413, the MSDP 433 and the Hicar 412, and enable collision detection and monitor the collision sensor when the user is in the riding state.

[0190] In some embodiments, the collision service 423 can determine that the user is in the riding state, enable collision detection and monitor the collision sensor when it monitors that Hicar 412 reports that the vehicle system has been connected, or MSDP 433 has reported that the user status is riding, or Bluetooth 413 reports that the vehicle Bluetooth has been connected.

[0191] In some embodiments, enabling collision detection means that the collision service 423 enables the audio detection module 41 to collect audio data and determine the audio detection result (indicating whether the user has a traffic accident) based on the collected audio data, and enables the data acquisition interface 51 to collect sensor data, enables the collision detection module 52 to obtain the sensor detection result based on the sensor data and judges whether the user has a traffic accident based on the audio detection result and the sensor detection result.

[0192] For example, refer to Figure 7The collision service 423 can enable or disable the audio DSP to use the audio detection module 61 for audio detection through the smart domain 4111 and the audio HAL 431. The collision service 423 can also load or unload the AI ​​module to the NPU through the smart domain 4111 and the AI ​​service. The collision service can also enable or disable sensor detection through the sensor HAL 432.

[0193] In some embodiments, after the collision service 423 monitors the collision sensor, the collision detection module 61 can send a collision message to the collision service 423 through the sensor HAL 432 when the user has a traffic accident.

[0194] It should be understood that the specific process of the collision service 423 enabling collision detection and monitoring the collision sensor will be introduced below and will not be described in detail here.

[0195] S603 : the audio detection module 61 collects audio data, obtains an audio detection result based on the audio data, and sends the audio detection result to the collision detection module 52 .

[0196] After collision detection is enabled, the audio detection module 61 can collect audio data, obtain audio detection results based on the audio data, and send the audio detection results to the collision detection module 52 .

[0197] For example, reference Figure 7 After collecting the audio data, the audio detection module 61 can first perform acoustic echo cancellation (AEC), automatic noise suppression (ANS), and automatic gain control (AGC) on the audio data (referred to as 3A pre-processing). Then, the Mel frequency cepstrum coefficient (MFCC) extraction (referred to as MFCC) is performed on the data after 3A pre-processing to obtain feature data (for example, feature data corresponding to 2 seconds of audio data). Secondly, the NPU is called to pass the feature data to the AI ​​model loaded in the Sensorhub through an inter-process communication (IPC) message through an IPC message (for example, passing the input feature data and the cache address corresponding to the audio detection result). Again, the NPU can infer the feature data through the AI ​​model to obtain the audio detection result, and pass the audio detection result to the collision detection module 52 through the cache address corresponding to the audio detection result.

[0198] In some embodiments, when MFCC extraction is performed on the data after 3A pre-processing, the audio data can be pre-emphasized by the following formula (1) to reduce some high-frequency energy; then a short-time Fourier transform and a Mel filter are performed to obtain a Mel-time spectrum; then a logarithmic separation signal is taken from the Mel-time spectrum, and a discrete cosine transform is performed to obtain feature data.

[0199] x[n]=x[n]-ax[n-1],0.9≤a≤1 (1)

[0200] Among them, x[n] is the nth data in the audio data, and x[n-1] is the n-1th data in the audio data.

[0201] It should be understood that the above process is only an example. In other embodiments, MFCC extraction may be performed on the data after 3A pre-processing in other ways, which is not limited here.

[0202] S604: The collision detection module 52 collects sensor data and obtains sensor detection results based on the sensor data.

[0203] After collision detection is enabled, the collision detection module 52 can collect sensor data based on the data acquisition interface 51, such as acceleration (ACC) data, rotation vector (RV) data, gyroscope (gyro) data, air pressure (baro) data, GPS data, etc.

[0204] For example, reference Figure 8 The data acquisition interface 51 can collect ACC data at a frequency of 500 Hz, RV data at a frequency of 200 Hz, gyro data at a frequency of 500 Hz, baro data at a frequency of 25 Hz, and GPS data at a frequency of 1 Hz, and send the collected data to the collision detection module 52. In this way, different sensors can collect data at different frequencies instead of collecting data at the same high frequency, which is conducive to reducing power consumption when collecting sensor data.

[0205] In some embodiments, after collecting the sensor data, the collision detection module 52 may calculate the neck injury index (NIC) based on the sensor data, and obtain the sensor detection result based on the value of NIC. For example, when the value of NIC is greater than a preset value (e.g., 15 m 2 / s 2 , which may also be other values ​​and are not limited here), it is determined that the user has a traffic accident. Exemplarily, NIC may be calculated by the following formula (2):

[0206] NIC(t)=0.2a rel (t)+v rel (t)2 (2)

[0207] Among them, NIC(t) represents the NIC value at time t, a rel (t) represents the acceleration of the user's center of gravity relative to the first thoracic vertebra in the anterior-posterior direction at time t, v rel (t) represents the velocity of the center of gravity of the user's body relative to the first thoracic vertebra in the anterior-posterior direction at time t.

[0208] It should be understood that in some embodiments, the collision detection module 52 may also determine the value of the NIC in other ways, and may also determine the sensor detection result based on the sensor data in other ways, which are not limited here.

[0209] S605 : When both the audio detection result and the sensor detection result indicate that the user is involved in a traffic accident, the collision detection module 52 sends a collision message to the collision service 423 .

[0210] The collision detection module 52 sends a collision message to the collision service 423 when both the audio detection result and the sensor detection result indicate that the user has a traffic accident.

[0211] For example, the collision detection module 52 may detect a traffic accident when the audio detection result indicates that the user has a traffic accident, and the NIC data obtained based on the sensor data is greater than 15m 2 / s 2 When a collision occurs, a collision message is sent to the collision service 423.

[0212] S606: After receiving the collision message, the collision service 423 initiates an emergency assistance request.

[0213] After receiving the collision message, the collision service 423 can initiate emergency assistance via SOS assistance 4110.

[0214] For example, reference Fig. 9 The collision service 423 may initiate emergency assistance after receiving the collision message based on the following steps S901 to S904.

[0215] S901: The collision detection module 62 reports a collision message to the collision service 423.

[0216] When a user has a traffic accident, the collision detection module 62 may report a collision message to the collision service 423 .

[0217] S902: The collision service 423 reports the collision message to the SOS for help 4110.

[0218] After receiving the collision message reported by the collision detection module 62 , the collision service 423 may report the collision message to the SOS for help 4110 .

[0219] S903: SOS 4110 initiates emergency assistance.

[0220] After receiving the collision message reported by the collision service 423, the SOS help 4110 may initiate emergency help. For example, the SOS help 4110 may display the aforementioned prompt interface, and prompt the user in the first prompt mode within the aforementioned first time period, prompt the user in the second prompt mode within the second time period after the first time period, and automatically ask for help when no user operation is detected after the second time period. For details, please refer to the aforementioned steps S305 to S311, which will not be described in detail here.

[0221] The emergency help method provided in the embodiment of the present application can improve the accuracy of the mobile phone 10 in automatically asking for help, and avoid wrong help requests and missed help requests in some scenarios.

[0222] The following describes the process of registering and deregistering the ride monitor for the collision service 423.

[0223] Fig.10 According to some embodiments of the present application, a schematic diagram of the interaction process of registering and unregistering a ride listener for a collision service 423 is shown. Fig.10 As shown, the interaction process includes the following steps:

[0224] S1001: The collision service 423 monitors the status of the switch of the automatic assistance function after a car accident.

[0225] After the collision service 423 is running, it can monitor the status of the switch of the automatic assistance function after the car accident.

[0226] When the collision service 423 automatically initiates a help request function after monitoring a car accident and the state of the switch is turned on, the following steps S1002 to S1005 can be executed to register the vehicle monitoring.

[0227] S1002: The collision service 423 registers with the Bluetooth 413 to connect to the vehicle Bluetooth monitoring.

[0228] When the collision service 423 automatically initiates a help request after a car accident and the switch is turned on, the collision service 423 can register with the Bluetooth 413 to connect to the vehicle's Bluetooth monitoring.

[0229] It should be understood that after the collision service 423 registers the vehicle-machine Bluetooth monitoring connection with the Bluetooth 413, the Bluetooth 413 can report the connection status with the vehicle-machine Bluetooth to the collision service 423 when establishing or disconnecting the vehicle-machine Bluetooth.

[0230] S1003 : The collision service 423 establishes a connection with the MSDP 433 .

[0231] When the state of the switch of the automatic assistance function after the car accident is turned on, the collision service 423 can establish a connection with the MSDP 433.

[0232] S1004: The collision service 423 registers user status monitoring with the MSDP 433.

[0233] After establishing a connection with the MSDP 433 , the collision service 423 may register user status monitoring with the MSDP 433 .

[0234] It should be understood that after registering user status monitoring with MSDP 433, collision service 423 can enable the MSDP 433's ride entry / exit atomic capability, so that MSDP 433 can report the user status to collision service 423 when the user status is riding or not riding.

[0235] S1005: The collision service 423 registers with Hicar 412 to connect to the vehicle system for monitoring.

[0236] When the state of the switch of the collision service 423 for automatically initiating assistance after a car accident is turned on, the collision service 423 can register with Hicar 412 to connect to the vehicle system for monitoring.

[0237] It should be understood that the collision service 423 registers with Hicar 412 to monitor the connection to the vehicle system, and Hicar 412 can report the connection status with the vehicle system to the collision service 423 when establishing or disconnecting the connection with the vehicle system.

[0238] It should be understood that the execution order of the above steps S1002 to S1005 is only an example. In other embodiments, the mobile phone 10 may first execute step S1002, step S1003 and step S1004, and step S1005. The execution order of the three may be exchanged or executed simultaneously, which is not limited here.

[0239] When the state of the switch of the collision service 423 for automatically initiating assistance after monitoring a car accident is off, the following steps S1006 to S1009 can be executed to register for the car monitoring.

[0240] S1006: The collision service 423 registers with the Bluetooth 413 to connect to the vehicle Bluetooth monitoring.

[0241] When the collision service 423 automatically initiates a help request after a car accident and the switch is turned off, the collision service 423 can register with the Bluetooth 413 to connect to the vehicle's Bluetooth monitoring.

[0242] S1007: The collision service 423 registers the user status monitoring with the MSDP 433.

[0243] When the state of the switch of the automatic assistance function after the car accident is turned off, the collision service 423 can register the user status monitoring with the MSDP 433.

[0244] S1008: The collision service 423 is disconnected from the MSDP 433.

[0245] After deregistering the user status monitoring with the MSDP 433 , the collision service 423 may be disconnected from the MSDP 433 .

[0246] S1009: The collision service 423 registers with Hicar 412 to connect to the vehicle system for monitoring.

[0247] When the state of the switch of the collision service 423 for automatically initiating assistance after a car accident is turned off, the collision service 423 can register with Hicar 412 to connect to the vehicle system for monitoring.

[0248] It should be understood that the execution order of the above steps S1006 to S1009 is only an example. In other embodiments, the mobile phone 10 may first execute step S1006, step S1007 and step S1008, and step S1009. The execution order of the three may be exchanged or executed simultaneously, which is not limited here.

[0249] Through the above method, when the state of the switch of the automatic help function after a car accident is turned off, the collision service 423 can register for vehicle monitoring, which is beneficial to reducing the power consumption and memory usage of the mobile phone 10.

[0250] The following describes the process of enabling and disabling collision detection according to the result of the monitoring after the collision service 423 registers the ride monitoring.

[0251] Fig.11 According to some embodiments of the present application, a schematic diagram of an interaction process of enabling and disabling collision detection by the collision service 423 is shown. Fig.11 As shown, the interaction process includes the following steps:

[0252] S1101: When the collision service 423 monitors that the Hicar 412 reports that the vehicle system has been connected, or the MSDP 433 reports that the user status is in the vehicle, or the Bluetooth 413 reports that the vehicle Bluetooth has been connected, the audio detection is enabled.

[0253] When the collision service 423 monitors that Hicar 412 reports that the vehicle system has been connected, or MSDP 433 reports that the user status is in the vehicle, or Bluetooth 413 reports that the vehicle Bluetooth has been connected (that is, when the user is in the vehicle state), audio detection can be enabled.

[0254] In some embodiments, the collision service 423 may enable audio detection by following steps S1101A and S1101B.

[0255] S1101A: Intelligent domain 4111 starts audio HAL 431.

[0256] The collision service 423 can start the audio HAL 431 through the smart domain, so that the audio module (such as audio DSP) of the mobile phone 10 can collect audio data through the microphone.

[0257] S1101B: Smart domain 4111 starts the AI ​​model.

[0258] After the audio HAL 431 is started, the smart domain 4111 can start the AI ​​model so that the AI ​​model can infer whether the user has a traffic accident based on the audio data reported by the audio HAL, and report the inference result as an audio detection result to the aforementioned collision detection module.

[0259] S1102: When the collision service 423 monitors that the Hicar 412 reports that the vehicle system has been connected, or the MSDP 433 reports that the user status is in the vehicle, or the Bluetooth 413 reports that the vehicle Bluetooth has been connected, the sensor detection is enabled and the collision sensor is registered for monitoring.

[0260] When the collision service 423 monitors that Hicar 412 reports that the vehicle system has been connected, or MSDP 433 has reported that the user status is in the vehicle, or Bluetooth 413 reports that the vehicle Bluetooth has been connected (that is, the user is in the vehicle state), the sensor detection can be registered to monitor the collision sensor.

[0261] It should be understood that after the collision service 423 enables sensor detection, the aforementioned data acquisition interface 51 can collect sensor data and send the sensor data to the collision detection module 52, so that the collision detection module 52 determines whether the user has a traffic accident based on the sensor data and the audio detection result.

[0262] It should be understood that after the collision service 423 registers the monitoring collision sensor with the sensor HAL, the collision detection module 52 can send a collision message to the collision service 423 when the user has a traffic accident.

[0263] S1103: When the collision service 423 monitors that the Hicar 412 reports that the vehicle system has been disconnected, the MSDP 433 reports that the user status is not in the vehicle, and the Bluetooth 413 reports that the vehicle Bluetooth has been disconnected, the audio detection is turned off.

[0264] When the collision service 423 monitors that the Hicar 412 reports that the vehicle system has been disconnected, the MSDP 433 has reported that the user status is not in the vehicle, and the Bluetooth 413 reports that the vehicle Bluetooth has been disconnected (that is, the user is not in the vehicle status), the audio detection is turned off.

[0265] In some embodiments, the collision service 423 may enable audio detection by following steps S1103A and S1103B.

[0266] S1103A: Intelligent domain 4111 stops audio HAL 431.

[0267] The collision service 423 can stop the audio HAL 431 through the smart domain 4111, so that the audio module (such as the audio DSP) of the mobile phone 10 no longer collects audio data through the microphone.

[0268] S1103B: Smart Domain 4111 stops the AI ​​model.

[0269] After the audio HAL 431 is started, the smart domain 4111 can start the AI ​​model so that the AI ​​model no longer runs.

[0270] S1104: When the collision service 423 monitors that Hicar 412 reports that the vehicle system has been disconnected, and MSDP 433 reports that the user status is not in the vehicle, and Bluetooth 413 reports that the vehicle Bluetooth has been disconnected, it turns off sensor detection and registers the collision sensor for monitoring.

[0271] When the collision service 423 monitors that Hicar 412 reports that the vehicle system has been disconnected, MSDP 433 has reported that the user status is not in the vehicle, and Bluetooth 413 reports that the vehicle Bluetooth has been disconnected (that is, the user is not in the vehicle state), the sensor detection is turned off and the collision sensor is registered for monitoring.

[0272] Through the above method, when the state of the switch for automatically initiating help after a car accident is turned on, if the user is not in a car state, the mobile phone 10 does not need to collect audio data and sensor data, which is beneficial to reducing the power consumption and memory usage of the mobile phone 10.

[0273] In some embodiments, the collision service 423 may enable / disable collision detection when the connection status with the vehicle system reported by Hicar 412 changes.

[0274] Fig.12 According to some embodiments of the present application, a schematic diagram is shown of enabling / disabling collision detection when the connection state of the collision service 423 with the vehicle system changes. Fig.12 As shown, the process includes the following steps:

[0275] S1201: The collision service 423 determines the change in the connection status between the Hicar 412 and the vehicle system.

[0276] When the connection state between Hicar 412 and the vehicle system changes, the collision service 423 can determine the change of the connection state between Hicar 412 and the vehicle system. When the connection state between Hicar 412 and the vehicle system changes from connected to disconnected, it means that the user may not be in the vehicle state, and the process goes to step S1204 for further determination; when the connection state between Hicar 412 and the vehicle system changes from disconnected to connected, it means that the user is in the vehicle state, and the process goes to step S1202.

[0277] S1202: The collision service 423 determines whether collision detection is enabled.

[0278] When the connection state between Hicar 412 and the vehicle system changes from disconnected to connected, or when the connection state between Hicar 412 and the vehicle system changes from disconnected to disconnected but MSDP 433 reports that the user status is riding, or when the connection state between Hicar 412 and the vehicle system changes from disconnected to connected but Bluetooth 413 reports that it is connected to the vehicle system via Bluetooth, it is determined whether collision detection is enabled. If collision detection is enabled, the process ends; if collision detection is not enabled, go to step S1203.

[0279] S1203: The collision service 423 enables collision detection.

[0280] The collision service 423 enables collision detection. The process of the collision service 423 enabling collision detection can refer to the aforementioned steps S1101, S1101A, S1101B and S1102, which will not be described in detail here.

[0281] S1204: The collision service 423 determines whether the user status reported by the MSDP 433 is riding in a vehicle and whether the connection status with the vehicle-mounted Bluetooth reported by the Bluetooth 413 is connected.

[0282] When the connection status between Hicar 412 and the vehicle system changes from connected to disconnected, the collision service 423 can determine whether the user status reported by MSDP 433 is riding and whether the connection status with the vehicle Bluetooth reported by Bluetooth 413 is disconnected. When the user status reported by MSDP 433 is not riding and the connection status with the vehicle Bluetooth reported by Bluetooth 413 is disconnected, go to step S1205; otherwise, go to step S1202.

[0283] S1205: The collision service 423 turns off collision detection.

[0284] The collision service 423 turns off the collision detection. The process of turning off the collision detection by the collision service 423 can refer to the aforementioned steps S1103, S1103A, S1103B and S1104, which will not be described in detail here.

[0285] In some embodiments, the collision service 423 may enable / disable collision detection when the user status reported by the MSDP 433 changes.

[0286] Fig.13 According to some embodiments of the present application, a schematic diagram of enabling / disabling collision detection by the collision service 423 when the user status reported by the MSDP 433 changes is shown. Fig.13 As shown, the process includes the following steps:

[0287] S1301: The collision service 423 determines the change of the user status reported by the MSDP 433.

[0288] When the user status reported by MSDP 433 changes, collision service 423 can determine the change of the user status reported by MSDP 433. When the user status reported by MSDP 433 changes from riding to other status, it means that the user may not be in the riding state, and the process goes to step S1304 for further determination; when the user status reported by MSDP 433 changes from other status to riding state, it means that the user is in the riding mode, and the process goes to step S1302.

[0289] S1302: The collision service 423 determines whether collision detection is enabled.

[0290] When the user status reported by MSDP 433 changes from other status to riding status, or when the user status reported by MSDP 433 changes from riding to other status but Hicar 412 reports that it is connected to the vehicle system, or when the user status reported by MSDP 433 changes from riding to other status but Bluetooth 413 reports that it is connected to the vehicle system Bluetooth, it is determined whether collision detection is enabled. If collision detection is enabled, the process ends; if collision detection is not enabled, go to step S1303.

[0291] S1303: The collision service 423 enables collision detection.

[0292] The collision service 423 enables collision detection. The process of the collision service 423 enabling collision detection can refer to the aforementioned steps S1101, S1101A, S1101B and S1102, which will not be described in detail here.

[0293] S1304: The collision service 423 determines whether the connection status with the vehicle system reported by Hicar 412 is connected and whether the connection status with the vehicle Bluetooth reported by Bluetooth 413 is connected.

[0294] When the user status reported by MSDP 433 changes from riding to other status, collision service 423 determines whether the connection status with the vehicle system reported by Hicar 412 is connected and whether the connection status with the vehicle Bluetooth reported by Bluetooth 413 is connected. When the connection status with the vehicle system reported by Hicar 412 is disconnected and the connection status with the vehicle Bluetooth reported by Bluetooth 413 is disconnected, go to step S1305; otherwise, go to step S1302.

[0295] S1305: Turn off collision detection.

[0296] The collision service 423 turns off the collision detection. The process of turning off the collision detection by the collision service 423 can refer to the aforementioned steps S1103, S1103A, S1103B and S1104, which will not be described in detail here.

[0297] In some embodiments, the collision service 423 may enable / disable collision detection when the connection status with the vehicle-mounted Bluetooth reported by the Bluetooth 413 changes.

[0298] Fig.14 According to some embodiments of the present application, a schematic diagram is shown of enabling / disabling collision detection when the collision service 423 changes the connection state with the vehicle Bluetooth. Fig.14 As shown, the process includes the following steps:

[0299] S1401: The collision service 423 determines the change in the connection status with the vehicle Bluetooth reported by the Bluetooth 413.

[0300] When the connection status with the vehicle Bluetooth reported by Bluetooth 413 changes, the collision service 423 can determine the change of the connection status with the vehicle Bluetooth reported by Bluetooth 413. When the connection status with the vehicle Bluetooth reported by Bluetooth 413 changes from connected to disconnected, it means that the user may not be in the vehicle state, and the process goes to step S1404 for further judgment; when the connection status with the vehicle Bluetooth reported by Bluetooth 413 changes from disconnected to connected, it means that the user is in the vehicle mode, and the process goes to step S1402.

[0301] S1402: The collision service 423 determines whether collision detection is enabled.

[0302] When the connection status with the vehicle Bluetooth reported by Bluetooth 413 changes from disconnected to connected, or when the connection status with the vehicle Bluetooth reported by Bluetooth 413 changes from connected to disconnected but Hicar 412 reports that it is connected to the vehicle system, or when the connection status with the vehicle Bluetooth reported by Bluetooth 413 changes from connected to disconnected but the user status reported by MSDP 433 is riding, it is determined whether collision detection is enabled. If collision detection is enabled, the process ends; if collision detection is not enabled, go to step S1403.

[0303] S1403: The collision service 423 enables collision detection.

[0304] The collision service 423 enables collision detection. The process of the collision service 423 enabling collision detection can refer to the aforementioned steps S1101, S1101A, S1101B and S1102, which will not be described in detail here.

[0305] S1404: The collision service 423 determines whether the user status reported by the MSDP 433 is riding and whether the connection status with the vehicle system reported by the Hicar 412 is connected.

[0306] When the connection status with the vehicle-mounted Bluetooth reported by Bluetooth 413 changes from connected to disconnected, the collision service 423 determines whether the user status reported by MSDP 433 is riding and whether the connection status with the vehicle-mounted system reported by Hicar 412 is connected. When the connection status with the vehicle-mounted system reported by Hicar 412 is disconnected and the user status reported by MSDP 433 is not riding, go to step S1405; otherwise, go to step S1402.

[0307] S1405: Turn off collision detection.

[0308] The collision service 423 turns off the collision detection. The process of turning off the collision detection by the collision service 423 can refer to the aforementioned steps S1103, S1103A, S1103B and S1104, which will not be described in detail here.

[0309] pass Figure 12 to Figure 14 In the method provided in the embodiment shown, the mobile phone 10 can timely disable or enable collision detection when the connection status with the vehicle Bluetooth reported by Bluetooth 413 changes, or when the connection status with the vehicle system reported by Hicar 412 changes, or when the user status reported by MSDP 433 changes. In this way, it is possible to timely detect whether the user has a traffic accident when the user is in the vehicle state, and it is also possible to disable collision detection when the user is not in the vehicle state to save power and reduce internal occupancy.

[0310] The embodiment of the present application further provides a mobile phone 10, which can be the aforementioned destination device or the aforementioned source device.

[0311] Specifically, Fig.15 According to some embodiments of the present application, a schematic structural diagram of a mobile phone 10 is shown.

[0312] like Fig.15 As shown, the mobile phone 10 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. Among them, the sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, and the like.

[0313] The processor 110 may include one or more processing units, for example, the processor 110 may include a central processing unit (CPU), an AP, a modem processor, a GPU, an image signal processor (ISP), a microcontroller unit (MCU), a video codec, a DSP, a baseband processor, an NPU, a field programmable gate array (FPGA), etc. In some embodiments, different processing units may be independent devices or may be integrated into one or more processors.

[0314] In some embodiments, the NPU can be used to run the aforementioned AI model, use the AI ​​model to infer the audio data, and obtain audio detection results indicating whether the user has been involved in a traffic accident.

[0315] The processor 110 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. The memory may store instructions or data that the processor 110 has just used or cyclically used. When the processor 110 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0316] In some embodiments, the processor 110 may be configured to execute instructions corresponding to the emergency assistance methods provided in the aforementioned embodiments.

[0317] In some embodiments, the processor 110 may include one or more interfaces. The interface may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, etc.

[0318] The USB interface 130 is an interface that complies with the USB standard specification, and specifically can be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 can be used to connect a charger to charge the mobile phone 10, and can also be used to transmit data between the mobile phone 10 and peripheral devices. For example, the interface can also be used to connect other electronic devices, such as AR devices, display devices, etc., to display a user interface through the AR devices and display devices.

[0319] The charging management module 140 is used to receive charging input from a charger. While the charging management module 140 is charging the battery 142 , it can also power the electronic device through the power management module 141 .

[0320] The power management module 141 is used to connect the battery 142, the charging management module 140 and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, the internal memory 121, the display screen 194, the camera 193, and the wireless communication module 160.

[0321] The wireless communication function of the mobile phone 10 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0322] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals.

[0323] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the mobile phone 10. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0324] In some embodiments, the mobile communication module 150 can be used for text message transmission, call data transmission, etc. between the mobile phone 10 and other devices.

[0325] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the mobile phone 10. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, modulates the frequency of the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0326] The mobile phone 10 implements the display function through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

[0327] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Mini-LED, Micro-LED, Micro-OLED, quantum dot light-emitting diodes (QLED), etc. In some embodiments, the mobile phone 10 may include 1 or N display screens 194, where N is a positive integer greater than 1.

[0328] In some embodiments, display screen 194 may be used to display the aforementioned prompt interface.

[0329] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then passes the electrical signal to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the mobile phone 10 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0330] In some embodiments, the camera 193 may include a flash, and the mobile phone 10 may flash the flash to prompt the user that emergency assistance will be automatically requested.

[0331] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone 10. The external memory card communicates with the processor 110 through the external memory interface 120 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0332] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. In some embodiments, the program storage area may store an operating system, an application required for at least one function, etc., such as instructions for the emergency help method provided in the aforementioned embodiments. The data storage area may store data created during the use of the mobile phone 10, etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications of the mobile phone 10 by running instructions stored in the internal memory 121, and / or instructions stored in a memory provided in the processor 110.

[0333] The mobile phone 10 can implement audio functions such as music playing and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the earphone interface 170D, and the application processor.

[0334] The audio module 170 is used to convert digital audio information into analog audio signal output, and also used to convert analog audio input into digital audio signal. The audio module 170 can also be used to encode and decode audio signals.

[0335] The speaker 170A, also called a "horn", is used to convert audio electrical signals into sound signals.

[0336] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals.

[0337] The microphone 170C, also called a “microphone” or “microphone”, is used to convert sound signals into electrical signals. For example, in some embodiments, the microphone 170C can be used to collect audio data and send electrical signals corresponding to the collected audio data to the audio detection module 61.

[0338] The earphone jack 170D is used to connect a wired earphone.

[0339] The pressure sensor 180A is used to sense the pressure signal and can convert the pressure signal into an electrical signal. In some embodiments, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor can be a parallel plate including at least two conductive materials. When a force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The mobile phone 10 determines the intensity of the pressure based on the change in capacitance. When a touch operation acts on the display screen 194, the mobile phone 10 detects the intensity of the touch operation based on the pressure sensor 180A. The mobile phone 10 can also calculate the position of the touch based on the detection signal of the pressure sensor 180A.

[0340] The air pressure sensor 180C may be used to detect the air pressure at the location where the mobile phone 10 is located.

[0341] The acceleration sensor 180E can detect the magnitude of the acceleration of the mobile phone 10 in various directions (generally three axes). When the mobile phone 10 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the electronic device and is applied to applications such as horizontal and vertical screen switching and pedometers.

[0342] The ambient light sensor 180L is used to sense the ambient light brightness. The mobile phone 10 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180L can also cooperate with the proximity light sensor 180G to detect whether the mobile phone 10 is in a pocket to prevent accidental touches.

[0343] The fingerprint sensor 180H is used to collect fingerprints. The mobile phone 10 can use the collected fingerprint characteristics to achieve fingerprint unlocking, access application locks, fingerprint photography, fingerprint call answering, etc.

[0344] The touch sensor 180K is also called a "touch control device". The touch sensor 180K can be set on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch control screen". The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the mobile phone 10, which is different from the position of the display screen 194.

[0345] The buttons 190 include a power button, a volume button, etc. The buttons 190 may be mechanical buttons or touch buttons. The mobile phone 10 may receive the button input and generate a key signal input related to the user settings and function control of the mobile phone 10. For example, in some embodiments, the mobile phone 10 may initiate an emergency call when the user presses the power button five times in a row.

[0346] Motor 191 can generate a vibration prompt. In some embodiments, mobile phone 10 can use vibration motor 191 to prompt the user that automatic emergency assistance will be performed.

[0347] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power changes, messages, missed calls, notifications, etc. In some embodiments, the mobile phone 10 may flash the indicator 192 to prompt the user that automatic emergency assistance will be performed.

[0348] The SIM card interface 195 is used to connect a SIM card.

[0349] It is understood that the structure of the mobile phone 10 shown in the embodiment of the present application does not constitute a specific limitation on the mobile phone 10. In other embodiments of the present application, the mobile phone 10 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0350] In the accompanying drawings, some structural or method features may be shown in a specific arrangement and / or order. However, it should be understood that such a specific arrangement and / or order may not be required. Instead, in some embodiments, these features may be arranged in a manner and / or order different from that shown in the illustrative drawings. In addition, the inclusion of structural or method features in a particular figure does not mean that such features are required in all embodiments, and in some embodiments, these features may not be included or may be combined with other features.

[0351] It should be noted that in the examples and description of this patent, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the term "includes" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "includes one" do not exclude the existence of other identical elements in the process, method, article or device including the elements.

Claims

1. An emergency assistance method, applied to electronic equipment, characterized in that: include: When the user is in a vehicle state and the first data collected by the electronic device meets a first condition, the user is prompted to perform automatic emergency assistance in a first prompting manner within a first time period, wherein the first condition is used to indicate that the user of the electronic device is in a traffic accident; When no operation of the user on the electronic device is detected within the first time period, prompting the user to perform automatic emergency assistance through a second prompting method, wherein the prompting intensity of the second prompting method is higher than the prompting intensity of the first prompting method; When no operation of the user on the electronic device is detected within the second time period, automatic emergency assistance is performed.

2. The method according to claim 1, characterized in that The automatic emergency assistance may include at least one of the following methods: sending an assistance message to at least one contact; or dialing the number of at least one contact; Or contact at least one contact via an instant messaging app.

3. The method according to claim 1, characterized in that The method further comprises: When the user's confirmation of requesting emergency assistance is detected within the first time period or the second time period, emergency assistance is performed.

4. The method according to claim 1, characterized in that: The method further comprises: When it is detected that the user cancels the emergency assistance operation within the first time period or the second time period, the emergency assistance is exited.

5. The method according to claim 1, characterized in that The user is in a riding state, including: The electronic device is connected to the vehicle's head unit Bluetooth; or the electronic device is connected to a vehicle computer system; Or the user behavior recognition module running in the electronic device recognizes that the user is in a riding state.

6. The method according to claim 1, characterized in that The first data includes sensor data and audio data; and the first condition includes: identifying that a user of the electronic device has been involved in a traffic accident based on the sensor data, and identifying that a user of the electronic device has been involved in a traffic accident based on the audio data.

7. The method according to claim 6, characterized in that Identifying that a user of the electronic device has a traffic accident based on the sensor data includes: The neck injury index obtained based on the sensor data is greater than a preset value.

8. The method according to claim 6, characterized in that The step of identifying, based on the audio data, that a user of the electronic device has had a traffic accident comprises: The inference result obtained by inferring the audio data using a pre-trained artificial intelligence model indicates that a traffic accident has occurred to the user of the electronic device.

9. The method according to claim 1, characterized in that: The method further comprises: During the first time period and the second time period, a countdown for executing the automatic emergency assistance is displayed.

10. The method according to claim 1, characterized in that The first prompting method includes at least one of the following methods: Play the prompt information at the first volume; A motor of the electronic device is vibrated with a first vibration amplitude.

11. The method according to claim 10, characterized in that The second prompting method includes at least one of the following methods: Playing the prompt information at a second volume, wherein the second volume is greater than the first volume; vibrating a motor of the electronic device with a second vibration amplitude, wherein the second vibration amplitude is greater than the first vibration amplitude; The light emitting unit of the electronic device is blinked.

12. A readable storage medium, characterized in that: The readable storage medium includes instructions, and when the instructions are executed by the electronic device, the electronic device implements the method according to any one of claims 1 to 11.

13. An electronic device, characterized in that: include: A memory for storing instructions; A processor, configured to execute the instructions so that the electronic device implements the method according to any one of claims 1 to 11.

Images