CN113286281B

CN113286281B - Emergency call method and related device

Info

Publication number: CN113286281B
Application number: CN202110408024.0A
Authority: CN
Inventors: 刘秀华; 熊正; 牛永民; 何彦召
Original assignee: Honor Device Co Ltd
Current assignee: Honor Device Co Ltd
Priority date: 2021-04-15
Filing date: 2021-04-15
Publication date: 2022-09-09
Anticipated expiration: 2041-04-15
Also published as: CN113286281A; WO2022218015A1

Abstract

The embodiment of the application provides an emergency call method and a related device. The method comprises the following steps: the first equipment and the second equipment establish Bluetooth connection; when the first device meets a first preset condition and supports HFP service, sending a first message comprising a first telephone number to the second device; the second device dials the first phone number in response to the first message; when the first device meets a first preset condition, does not support HFP service and supports BLE service, sending a second message comprising a second telephone number to the second device; the second device dials a second phone number in response to the second message; when the first device meets a first preset condition, the HFP service and the BLE service are not supported, and the SPP service is supported, sending a third message including a third phone number to the second device; the second device dials the third phone number in response to the third message. Therefore, the intelligent wearable device can control terminal calling according to the services supported by the intelligent wearable device.

Description

Emergency call method and related device

Technical Field

The present application relates to the field of terminal technologies, and in particular, to an emergency call method and a related device.

Background

Along with the development of communication technology, intelligent wearable equipment has entered people's life. People can know weather conditions and motion conditions in real time through the intelligent wearable device, make a call and the like.

When a user meets an emergency, the user can make a call to realize emergency call through wearing equipment such as an intelligent earphone and the like supporting voice calls.

However, some smart wearable devices, such as a bracelet, smart glasses, etc., do not support the voice telephone function. When a user meets an emergency, the user cannot make a call to realize emergency call.

Disclosure of Invention

The embodiment of the application provides an emergency call method and a related device, when an intelligent wearable device meets the preset condition of dialing a call, according to the Bluetooth characteristic of the intelligent wearable device, handheld devices such as a mobile phone and the like are controlled to dial the call, and emergency call is achieved.

In a first aspect, an embodiment of the present application provides a method, including: the first equipment and the second equipment establish Bluetooth connection; when the first device meets a first preset condition and supports the hands-free call HFP service, the first device sends a first message to the second device, wherein the first message comprises a first telephone number; the second device responds to the first message and dials the first telephone number; or when the first device meets a first preset condition, the first device does not support the HFP service, and the first device supports the Bluetooth Low Energy (BLE) service, the first device sends a second message to the second device, wherein the second message comprises a second phone number; the second device dials a second phone number in response to the second message; or when the first device meets a first preset condition, the first device does not support the HFP service and the BLE service, and the first device supports the simple parallel SPP service, the first device sends a third message to the second device, wherein the third message includes a third phone number; the second device dials the third phone number in response to the third message.

In this way, when the first device meets the preset condition for making a call, the control of the second device to make a dial call can be realized based on any one of the HFP service, the BLE service and the SPP service. Further, when the user of the first device is in an emergency, an emergency call may be implemented. When the first equipment can be intelligent wearing equipment and the second equipment can be terminal equipment, the user can control the terminal equipment to make a call through the intelligent wearing equipment.

Optionally, the method further comprises: when the first device meets a first preset condition and the first device does not support HFP service, BLE service and SPP service, the first device displays prompt information, and the prompt information is used for prompting a user to be in an emergency.

Therefore, the user of the first device can be prompted to be in an emergency, and other people can call for help conveniently.

Optionally, the first device meeting the first preset condition includes: the first equipment receives user operation; the user action is used to instruct the first device to make a call.

Optionally, the first device meeting the first preset condition includes: the method comprises the steps that the first equipment detects that gesture operation of a user meets preset gesture operation, and the preset gesture operation is used for indicating the first equipment to make a call; or the first device detects that the physiological characteristic of the user meets a preset physiological characteristic, and the preset physiological characteristic is used for indicating the first device to make a call.

Therefore, when the first equipment receives the quick operation of the user, the second equipment can be controlled to make a call, the emergency call is realized, the call time is shortened, and the emergency call speed is increased. The first equipment can automatically control the second equipment to make a call according to the physiological characteristics of the user, so that the emergency call for help is realized, the call for help time is shortened, and the emergency call for help speed is increased.

Optionally, the first message is an automatic dialing ATD command, and the ATD command includes the first phone number.

Optionally, the second message is a generic attribute profile GATT command, and the GATT command includes a second phone number; alternatively, the second message is a broadcast, the broadcast including the second phone number.

Optionally, the third message is a radio frequency communication RFCOMM command, and the RFCOMM command includes a third phone number.

Optionally, the method further comprises: the second equipment starts the outward release function; the play-out function is used to amplify the sound output by the second device.

In this way, the user is enabled to hear the sound delivered by the second device.

In a second aspect, an embodiment of the present application provides an emergency call method, which is applied to a first device, and the method includes:

the first device and the second device establish Bluetooth connection; when the first device meets a first preset condition and supports the hands-free call HFP service, the first device sends a first message to the second device, wherein the first message comprises a first telephone number; or when the first device meets a first preset condition, the first device does not support the HFP service, and the first device supports the bluetooth low energy BLE service, the first device sends a second message to the second device, where the second message includes a second phone number; or, when the first device meets the first preset condition, and the first device does not support HFP service and BLE service, and the first device supports simple parallel SPP service, the first device sends a third message to the second device, where the third message includes a third phone number.

In a third aspect, an embodiment of the present application provides an intelligent wearable device, where the intelligent wearable device may be a device that has a bluetooth function and is wearable on a user, such as a bluetooth headset, a bluetooth bracelet, a bluetooth watch, and a head-mounted display (HMD for short). The terminal device may be a bluetooth mobile phone, a Personal Digital Assistant (PDA) supporting a bluetooth function, a tablet computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, an Augmented Reality (AR) device, a Virtual Reality (VR) device, or the like.

Intelligence wearing equipment includes: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer executable instructions stored by the memory to cause the processor to perform the method of the second aspect described above.

In a fourth aspect, an embodiment of the present application provides a bracelet, including: a processor and a memory; the memory stores computer-executable instructions; the processor executes the computer executable instructions stored by the memory to cause the processor to perform the method of the second aspect described above.

In a fifth aspect, embodiments of the present application provide a computer-readable storage medium, in which a computer program or instructions are stored, and when the computer program or instructions are executed, the method of the second aspect is implemented.

In a fifth aspect, embodiments of the present application provide a computer program product, which includes a computer program or instructions, and when the computer program or instructions are executed by a processor, the method of the second aspect is implemented.

For the beneficial effects of the possible implementation manners of the second aspect to the fifth aspect, reference may be made to the beneficial effects brought by the possible implementation manners of the first aspect and the first aspect, which are not repeated herein.

Drawings

Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a method for controlling an AG to make a call by an HF according to an embodiment of the present application;

fig. 3 is a flowchart illustrating an emergency call method according to an embodiment of the present application;

fig. 4 is a schematic interface diagram when a bracelet is connected with a mobile phone bluetooth according to an embodiment of the present application;

fig. 5 is a schematic view of an interface for setting a bracelet call number for a mobile phone according to an embodiment of the application;

fig. 6 is a schematic diagram of an interface for setting a call triggering manner according to an embodiment of the present application;

fig. 7 is a schematic interface diagram of a bracelet call according to an embodiment of the present application;

fig. 8 is a schematic flowchart of a method for a bracelet to acquire a service type between the bracelet and a mobile phone according to an embodiment of the present application;

fig. 9 is a schematic interface diagram of a bracelet-search mobile phone according to an embodiment of the present application;

fig. 10 is a schematic diagram of a hardware structure of an intelligent wearable device provided in an embodiment of the present application.

Detailed Description

In the embodiments of the present application, terms such as "first" and "second" are used to distinguish the same or similar items having substantially the same function and action. For example, the first device and the second device are only used for distinguishing different devices, and the sequence order thereof is not limited. Those skilled in the art will appreciate that the terms "first," "second," etc. do not denote any order or quantity, nor do the terms "first," "second," etc. denote any order or importance.

It is noted that, in the present application, words such as "exemplary" or "for example" are used to mean exemplary, illustrative, or descriptive. Any embodiment or design described herein as "exemplary" or "e.g.," is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word "exemplary" or "such as" is intended to present concepts related in a concrete fashion.

It should be noted that the network architecture and the service scenario described in the embodiment of the present application are for more clearly illustrating the technical solution of the embodiment of the present application, and do not constitute a limitation to the technical solution provided in the embodiment of the present application, and it is known by a person skilled in the art that the technical solution provided in the embodiment of the present application is also applicable to similar technical problems along with the evolution of the network architecture and the appearance of a new service scenario.

In general, before data transmission is performed between an electronic device having a bluetooth function and an external device, a pairing connection is required. The electronic device and the external device may be collectively referred to as a bluetooth device. In order to enable interoperation between paired bluetooth devices, the bluetooth technical association (SIG) makes a bluetooth specification.

The bluetooth specification includes a core protocol (protocol) and an application protocol (profile). The core protocol includes the lowest 4 layers (Layer) in the bluetooth protocol stack, a basic Service Discovery Protocol (SDP), and a basic General Access Profile (GAP) of all profiles.

Application protocol profile, otherwise known as application layer profile. The profile may include types of phone directory access profile (PBAP), hands-free-call protocol (HFP), Object Push Profile (OPP), and the like.

Each type of profile may be understood as a protocol stack for implementing a type of application service. PBAP, for example, is a protocol stack for implementing address book synchronization. As another example, HFP is a protocol stack for implementing call control (e.g., answer, hang-up, reject, voice dialing, etc.).

The same version of protocol stack needs to be used between the bluetooth devices that are interoperating. For example, when the external device needs to perform call control on the electronic device, both the electronic device and the external device need to use the same version of HFP. Of course, different protocol stacks are required to implement different application services. For example, HFP is required to be used for implementing the call control service, PBAP is required to be used for implementing the synchronous address book service, and the like.

Before the electronic device and the external device use the profile to realize the application service, the two devices can perform dynamic negotiation on the profiles supported by the two devices. In a possible implementation manner, after an Asynchronous Connection (ACL) link is established between any two or more bluetooth devices, the bluetooth devices may dynamically query device information of an opposite terminal and a profile type supported by the opposite terminal through an SDP in a bluetooth technology framework, so that a corresponding connection is established between the bluetooth devices. Illustratively, after the ACL link is established between the electronic device and the external device, the external device sends SDP request information to the electronic device. After the electronic equipment receives the SDP request information from the external equipment, the electronic equipment sends SDP response information to the external equipment. The SDP response information includes the profile types supported by the electronic device. The external device may determine the highest profile version supported by both the electronic device and the external device according to the SDP response information.

In a possible communication scene based on the Bluetooth device, when a user encounters an emergency, the user can control a terminal device such as a mobile phone and the like to make a call to realize an emergency call through an intelligent wearing device such as an intelligent earphone and the like supporting voice calls.

Specifically, before the service connection between the mobile phone and the intelligent wearable device is established, the intelligent wearable device queries and obtains the service supported by the mobile phone through the SDP service, which specifically refers to the description of the service query of the bluetooth device, and is not described herein again. When the smart wearable device confirms that the mobile phone and the smart wearable device both support the HFP service, the smart wearable device and the mobile phone are connected through the HFP service. When the intelligent wearable device supporting the HFP service receives a triggering operation of a user for dialing a phone call, the intelligent wearable device supporting the HFP service transmits a phone number to the mobile phone through an auto-dial (ATD) command, and controls the mobile phone to dial the phone number, so that an emergency call is realized.

However, some smart wearable devices, such as a bracelet, smart glasses, and the like, do not support HFP services and do not have a voice phone function. When a user encounters an emergency, the user cannot remotely control the mobile phone to make a call to realize an emergency call.

The embodiment of the application provides a scheme, which is suitable for a bluetooth system, and when receiving a triggering operation of dialing a call by a user, the intelligent wearable device supporting the HFP service transmits a telephone number to terminal devices such as a mobile phone through an auto-dial (ATD) command, and controls the terminal devices such as the mobile phone to dial the telephone number, so that an emergency call is realized. For intelligent wearable equipment which does not support HFP service, terminal equipment such as a mobile phone and the like can be controlled to make a call through BLE service or simple parallel (SPP) service, and emergency calling is achieved. Therefore, the intelligent wearable device can select a proper mode to control terminal devices such as a mobile phone and the like to make an emergency call according to the service types supported by the intelligent wearable device.

In this application embodiment, intelligent wearing equipment can be bluetooth headset, bluetooth bracelet, bluetooth watch and wear-type display (HMD) etc. have bluetooth function wearable equipment on user's body. The terminal device may be a bluetooth mobile phone, a Personal Digital Assistant (PDA) supporting a bluetooth function, a tablet computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, an Augmented Reality (AR) device, a Virtual Reality (VR) device, or the like.

Taking an intelligent wearable device as a bracelet as an example, fig. 1 is a schematic view of an application scenario of an emergency call method provided by an embodiment of the present invention. As shown in fig. 1, the application scenario includes a bracelet 101 and a terminal device 102. The terminal device 102 may be a mobile phone, a tablet computer, or the like. Bracelet 101 and terminal equipment 102 all possess the bluetooth function to make bracelet 101 and terminal equipment 102 can communicate through the bluetooth. The bracelet 101 can recognize and respond to the trigger operation of the user, and controls the terminal device 102 to make a call, vibrate to ring or pop up a notification message through the bluetooth connection of the bracelet 101 and the terminal device 102.

The bracelet 101 and the terminal device 102 may both support an application protocol (profile) and a core protocol (protocol) of a plurality of applications. Each protocol defines respective corresponding message formats and application rules to realize interconnection and intercommunication of different devices under different platforms and meet various possible application scenarios with universal significance. The application protocols may include advanced audio distribution profile (A2 DP), handsfree call protocol HFP, and the like. The core protocol includes a bluetooth module (BTM), a service discovery protocol SDP, a logical channel control and adaptation protocol (L2 CAP), a Radio Frequency Communication (RFCOMM) protocol, and the like.

The following is a description of related concepts involved in the embodiments of the present application.

1. Bluetooth connection: a data transmission connection mode between devices. The Bluetooth connection includes a Basic Rate (BR) connection, an Enhanced Data Rate (EDR) connection, and a Bluetooth Low Energy (BLE) connection.

It should be noted that, when the bluetooth connection is a BR/EDR connection, the bluetooth devices use a synchronous connection-oriented/extended (SCO) link and an extended synchronous connection-oriented (ESCO) link to transmit call data, and use an ACL link to transmit audio data or video data. When the bluetooth connection is a BLE connection, the bluetooth devices transmit call data, audio data, or video data using an isochronous channel (ISO) therebetween.

The bluetooth connection procedure between the bluetooth devices will be explained. Bluetooth connectivity includes, but is not limited to, the following procedures: pairing connection, SDP service query and encryption, etc.

The pairing between the bluetooth devices may be Link Management Protocol (LMP) pairing, Secure Simple Pairing (SSP) pairing, or other non-standard pairing methods.

Taking a mobile phone and a bracelet as an example, the pairing connection process between the mobile phone and the bracelet can be as follows: the Bluetooth functions of the mobile phone and the bracelet are all started, when the mobile phone receives an operation that a user triggers the addition of the device control, the mobile phone inquires the surrounding Bluetooth devices with the started Bluetooth functions, and the names of the Bluetooth devices with the started Bluetooth functions are displayed on a mobile phone interface. When the mobile phone receives an operation that a user triggers the bracelet name control, the mobile phone initiates paging (page) aiming at the MAC address of the bracelet. When the bracelet receives a page sent by the mobile phone, the mobile phone and the bracelet establish an ACL link, and the pairing connection of the bracelet and the mobile phone is completed.

In a possible implementation mode, after the mobile phone and the bracelet are connected in a pairing mode, the mobile phone and the bracelet can be automatically connected within a certain range.

After the pairing between the bracelet and the mobile phone is completed, a shared secret key can be created: link key (link key). The link key is used to authenticate the device and encrypt the exchanged data. Illustratively, after the bracelet and the mobile phone are connected in a pairing manner, the bracelet and the mobile phone share the same link key. The bracelet and the mobile phone perform identity authentication through a link secret key. After the identity authentication of the bracelet and the mobile phone is completed, the bracelet and the mobile phone can acquire a random number through a link secret key and derive the random number to obtain an encryption key (encryption key). Furthermore, the bracelet and the mobile phone can encrypt data transmitted by the two parties through the encryption key, so that encrypted communication is realized. And the Bluetooth connection between the bracelet and the mobile phone is established and completed.

In a possible implementation manner, after the pairing between the bracelet and the mobile phone is completed, the bracelet can inquire the service supported by the mobile phone through the SDP. Illustratively, the bracelet sends SDP request information to the mobile phone and receives SDP response information sent by the mobile phone. The bracelet acquires the services supported by the mobile phone through the SDP response information. The services supported by the mobile phone can include: sending email, printing faxes, audio transmissions, voice conversations, and the like.

2. Hands-free talk (HFP) service: the protocol for realizing the call control by the bluetooth device (such as the bluetooth headset) comprises the steps of answering, hanging up, refusing to answer, voice dialing and the like.

Note that the HFP service includes an Audio Gateway (AG) and a hands-free component (HF). The AG is an input-output gateway for audio. The AG may be a mobile phone or the like. The HF is a remote audio input/output mechanism of the audio gateway and can provide several remote control functions, and in the embodiment of the present application, the HF may be a bracelet, an earphone, and the like.

The method by which the HF controls the AG to make a call is described below with reference to fig. 2. Fig. 2 is a schematic flow chart of a method for controlling AG to make a call by HF, as shown in fig. 2, the method includes:

s201, HF and AG establish a connection.

HF and AG establish HFP service connections. It should be noted that, in the case where the HFP service connection is established in the BR/EDR connection, the bluetooth connection process of the HF and the AG may refer to the bluetooth connection process in the above-mentioned related concept.

The following describes a process in which HF and AG establish HFP service connection. Illustratively, the HF and AG connection HFP service connection flow is as follows: the HF sends to the AG a retrieve the supported features (BRSF) command informing of the AG, the commands supported by the HF, the AT + BRSF command indicating the features supported by the HF. The HF receives a BRSF command in reply to the AG indicating the characteristics supported by the AG. The characteristics may include one or more of the following: connection management, telephone state information, audio connection processing, voice call answering, voice call refusing, call hanging up, voice link transfer in conversation, call dialing on the HF side and the like. And the HF sends an AT + CIND command to the AG, wherein the AT + CIND command is used for inquiring indexes supported by the AG and values corresponding to the indexes. The indexes include: call, call setup, call hold and roam, etc. The HF sends AT + CMER commands to the AG, which are used to enable various metrics. When there is a change in a certain index, the subsequent HF receives a + CIEV command from the AG transmission, the + CIEV command indicating the change in the index. In this way, the HF confirms the characteristics supported by the AG, the indexes supported by the AG and the values corresponding to the respective indexes, and HFP service connection between the HF and the AG is established.

S202, the HF receives a trigger operation of a user for dialing a call.

The user's trigger to place a call is used to instruct the HF to place a call. The trigger operation may be a click or touch operation by the user. The user click or touch operation may include: double-click main interface, three-click main interface, double-click power key, long-press menu key and the like. Illustratively, when the user triggers the dialing control through clicking or touching operation on the HF main interface, the HF receives the triggering operation of the user for dialing the telephone.

S203, HF sends an ATD + dd … dd command to the AG.

Wherein dd … dd is the telephone number that the AG side triggers to dial the phone.

S204, AG receives ATD command, and sends OK command to HF.

Accordingly, the HF receives an OK command from the AG.

In a possible implementation, the HF interface displays an identifier for alerting the phone status.

S205, the AG sends a + CIEV (outgoing setup 2) command to the HF.

The + CIEV command is used to indicate the current status of the AG. The outgoing call setup 2 is used to indicate that the AG successfully originates a call and places a call outward.

Accordingly, the HF receives a + CIEV (outgoing setup 2) command transmitted by the AG.

S206, if the audio connection between the AG and the HF does not exist, the AG requests the HF for audio connection establishment.

S207, AG establishes an audio connection with HF.

S208, the AG sends a + CIEV (outgoing setup — 3) command to the HF.

The outgoing call setup-3 is used to indicate that the AG is in paging and the other party rings.

Accordingly, the HF receives a + CIEV (outgoing setup ═ 3) command sent by the AG. In a possible implementation, the HF interface displays an identification of the phone page indicating that the phone is to be connected.

S209, AG sends a + CIEV (call ═ 1) command to the HF.

Call 1 is used to indicate AG to call up.

Accordingly, the HF receives a + CIEV (outgoing setup 2) command transmitted by the AG. In a possible implementation, the HF interface displays an indication of the call-through, which indicates that the call has been made.

S210, AG sends a + CIEV (outgoing setup ═ 0) command to HF.

The outgoing call setup is 0 to indicate that the AG phone hangs up or there is currently no pending phone.

Accordingly, the HF receives a + CIEV (outgoing setup ═ 0) command sent by the AG. In a possible implementation, the HF interface displays an identification of the phone hang up, which is used to indicate that the phone has hung up.

The emergency call method provided by the embodiment of the present application is described below with reference to fig. 3 to 8.

Fig. 3 is a flowchart illustrating an emergency call method according to an embodiment of the present application. And using AG as a mobile phone. HF is a bracelet as an example, as shown in fig. 3, the method comprising:

s301, Bluetooth connection is established between the bracelet and the mobile phone.

The process of establishing bluetooth connection between the bracelet and the mobile phone can be explained with reference to the related concepts. And will not be described in detail herein.

The following explains the interface display in the bluetooth connection process of the bracelet and the mobile phone. Exemplarily, fig. 4 is a schematic interface diagram of a bluetooth connection between a bracelet and a mobile phone. As shown in fig. 4, the bluetooth function is opened for both the bracelet and the mobile phone.

The mobile phone displays some APP main interface as shown in a in fig. 4, and when the mobile phone receives an operation of opening the more functions 401 by the user, the mobile phone may enter the more functions interface as shown in b in fig. 4. As shown in fig. 4 b, a sweep and add device 403 may be included in the more functional interface. When the user triggers the add device control 403 by clicking, touching, or the like in the interface with more functions shown in b in fig. 4, the mobile phone receives an operation of setting the add device 403 by the user, and the mobile phone enters the interfaces of all devices shown in d in fig. 4.

When a user triggers the add-device control 402 by clicking, touching, or other operations in a certain APP main interface shown in a in fig. 4 a, the mobile phone receives the operation of triggering the add-device control 402 by the user, and the mobile phone enters the interface of the device shown in c in fig. 4. The device interface may include a device tab 404 and a device item. The items of equipment may include one or more of: connected devices, hot activities, machine skills, or other types of equipment items. When the user triggers the add-device control 405 by clicking, touching, or the like in the interface of the device shown in c in fig. 4, the mobile phone receives an operation of setting the add-device 405 by the user, and the mobile phone enters the interfaces of all devices shown in d in fig. 4.

The all devices interface shown at d in fig. 4 includes an all devices tab column 406 and an all devices option. All device options include one or more of the following: watch, bracelet, headset, body fat scale, blood glucose meter or other types of all items of equipment. When the user triggers the bracelet control 407 through operations such as clicking, touching and the like in the interfaces of all the devices shown in d in fig. 4, the mobile phone receives the operation of triggering the bracelet control 407 by the user, and the mobile phone enters the interface of the bracelet control shown in e in fig. 4. The interface of the bracelet control may include a bracelet tab bar 408 and bracelet selection items, for example, the bracelet selection items may include one or more of the following: bracelet a, bracelet B, bracelet C, bracelet D, bracelet E and bracelet F or other types of bracelet options.

When the user triggers the bracelet a control 409 through operations such as clicking, touching and the like in the interface of the bracelet control shown in e in fig. 4, the mobile phone receives the operation that the user triggers the bracelet a control 409, and the mobile phone enters the interface of the bracelet a control shown in f in fig. 4. The interface of the bracelet a control may include a bracelet a tab bar 410 and a start pairing 411.

When the user triggers the start pairing control 411 by clicking, touching, or other operations in the interface of the bracelet a control shown in f in fig. 4, the mobile phone receives the operation of the user triggering the start pairing control 411, and the mobile phone enters the interface of the connection device shown in g in fig. 4. The interface for the connected device may include a connected device tab column 412 and a device name entry. The device name entry includes one or more of: bracelet aaa, bracelet bbb, bracelet ccc, or other types of device name items.

When the user triggers the wristband aaa control 413 through operations such as clicking, touching, and the like in the interface of the connection device shown in g in fig. 4, the mobile phone receives the operation of triggering the wristband aaa control 413 by the user, and the mobile phone enters the interface of the pairing guide shown in h in fig. 4. The pairing guide interface may include a pairing guide tab 414 and a pairing success 415. When the pairing guided interface is successfully paired 415, the bracelet and the mobile phone establish connection.

In a possible implementation mode, after the Bluetooth connection is established between the bracelet and the mobile phone, when the bracelet and the mobile phone both start the Bluetooth function, the bracelet and the mobile phone can be automatically connected within a certain range.

After the bracelet and the mobile phone are connected in a matched mode, a user can set a calling number, a function shortcut and the like in the bracelet through the mobile phone. The call number setting process in the hand ring is explained below with reference to fig. 5.

Exemplarily, fig. 5 is an interface schematic diagram of a mobile phone for setting a call number of a bracelet. After the bracelet is connected with the mobile phone, the interface of the device shown in a in fig. 5 includes; a device tab field 501 and a bracelet aaa flag 502. When the user triggers the bracelet aaa control 502 by clicking, touching, or the like in the interface of the device shown in a in fig. 5, the mobile phone receives the operation of triggering the bracelet aaa control 502 by the user, and the mobile phone enters the interface of the bracelet aaa as shown in b in fig. 5. The interface of the bracelet aaa may include a bracelet aaa label bar 503 and a bracelet aaa entry. The bracelet aaa item includes one or more of the following: find handset, weather alert, message notification, custom bracelet function, call or other type of bracelet aaa entry.

When the user triggers the call control 504 through operations such as clicking, touching and the like in the interface of the bracelet aaa shown in b in fig. 5, the mobile phone receives the operation of triggering the call control 504 by the user, and the mobile phone enters the interface of the call as shown in c in fig. 5. A call tab bar 505 and call items may be included in the interface for the call. The call item includes one or more of the following: default dialcards, number settings, shortcuts, or other types of call items.

When the user triggers the default dial card control 506 by clicking, touching, or the like in the interface of the call shown in c in fig. 5, the mobile phone receives the operation of triggering the default dial card control 506 by the user, and determines the dial card used during the call. When the user triggers the number setting control 507 by clicking, touching, or the like in the interface of the call shown in c in fig. 5, the mobile phone receives the operation of triggering the number setting control 507 by the user, and the mobile phone enters the interface of the number setting shown in d in fig. 5. The number setting interface may include a number setting tab 508 and a number setting item. The number setting item includes one or more of the following: speed dial 1, speed dial 2, speed dial 3, speed dial 4, speed dial 5 or other types of number settings.

When the user triggers the speed dial 1 control 509 by clicking, touching, or the like in the interface of the number setting shown in d in fig. 5, the mobile phone receives the operation of triggering the speed dial 1 control 509 by the user, and the mobile phone enters the interface of the speed dial 1 shown in e in fig. 5. The speed dial 1 tab 508 and speed dial entry may be included in the speed dial 1 interface. The speed dial item includes one or more of the following: select contacts, enter numbers, or other types of speed dial entries.

When the user triggers and selects the contact control 511 through operations such as clicking, touching and the like on the speed dial 1 interface shown in e in fig. 5, the mobile phone receives the operation of triggering and selecting the contact control 511 by the user, and the mobile phone enters the interface for selecting the contact as shown in f in fig. 5. The interface for selecting a contact includes selecting a contact tab 513 and a contact item. The contact items include one or more of the following: contact a, contact b, contact c, contact d, contact e, or other contacts. When the user triggers the contact a control 514 by clicking, touching and the like on the contact selection interface shown in f in fig. 5, the mobile phone receives the operation of triggering the contact a control 514 by the user, and the mobile phone determines the telephone number of the speed dial 1 associated with the contact a.

When the user triggers the input number control 512 by clicking, touching, or the like on the speed dial 1 interface shown in e in fig. 5, the mobile phone receives the operation of triggering the input number control 512 by the user, and prompts the user to input a number, thereby determining the phone number associated with the speed dial 1.

When the user determines the telephone number associated with speed dial 1 and the telephone number associated with speed dial 2, the number setting interface shown by d in fig. 5 is changed to the number setting interface shown by e in fig. 5 in which the telephone number associated with speed dial 1 and the telephone number associated with speed dial 2 are displayed.

The flows and interfaces shown in fig. 4 and 5 are only examples, and the specific connection process between the bracelet and the mobile phone, the bracelet function setting process, and the related interfaces in the embodiment of the present application are not limited in detail in the embodiment of the present application.

S302, the bracelet meets the preset condition of making a call.

The preset condition that the bracelet meets the call making requirement comprises that the bracelet detects that the gesture operation of the user is consistent with the preset gesture operation, or the bracelet detects that the physiological characteristics of the user meet the preset physiological characteristics of the user. The gesture operation of the user includes: the user clicks, the user's body movement, and the like, and the clicking operations include, but are not limited to, double-clicking the home interface, triple-clicking the home interface, double-clicking the power key, long-pressing the menu key, and the like. Limb movements include, but are not limited to, rotating the wrist, making a fist, flattening the palm, bending the palm, and the like. The preset physiological characteristics of the user include the heart rate, the change speed of the electrocardio and the like. The preset condition can also comprise that the bracelet recognizes emergency situations such as falling down of the user.

The call triggering mode setting in the hand ring is explained in conjunction with fig. 6. Fig. 6 is a schematic diagram of an interface for setting a call triggering mode.

After the connection between the bracelet and the mobile phone is established, the interface of the call shown as a in fig. 6 includes; a call tab column 601 and a call item. The call item includes one or more of the following: default dialcards, number settings, shortcuts, or other types of call items. When the user triggers the shortcut control 602 through clicking, touching and other operations on the call interface shown in a in fig. 6, the mobile phone receives the operation of triggering the shortcut control 602 by the user, and the mobile phone enters the shortcut interface shown in b in fig. 6. The shortcut interface includes a shortcut tab 603 and a shortcut item. The shortcut item includes one or more of the following: double-click main interface, triple-click main interface, wrist rotation, fist making, palm stretching, palm bending or other types of shortcut items. When the quick call interface shown in b in fig. 6 triggers the wrist rotation control 604 by clicking, touching, or the like, the mobile phone receives an operation of the user triggering the wrist rotation control 604, and determines that the call triggering mode is wrist rotation. When the bracelet receives an operation of rotating the wrist of the user, the bracelet enters and displays a telephone call interface.

S304, when the HFP service is supported between the bracelet and the mobile phone, the bracelet sends an ATD command to the mobile phone.

The ATD command is used to instruct the handset to make a call. The ATD command may include a specific number or a preset number flag. For example, the ATD command may carry a specific number or a preset number flag.

In a possible implementation manner, when the bluetooth connection (or referred to as a service type) between the bracelet and the mobile phone is BR or EDR, the bracelet confirms whether both the bracelet and the mobile phone support HFP service through SDP. For example, the bracelet may send SDP request information to the mobile phone, and when the bracelet receives SDP response information sent by the mobile phone, the bracelet may determine services supported by the mobile phone, thereby confirming whether HFP services are supported between the bracelet and the mobile phone.

S305, the mobile phone receives and responds to the ATD command.

The process of making a call by the mobile phone in response to the ATD command may refer to the description of fig. 2, and is not described herein again.

At this time, the call is successfully called out, and the bracelet and the mobile phone do not execute the subsequent steps.

Namely, when the HFP service is supported between the bracelet and the mobile phone, the bracelet and the mobile phone realize that the bracelet remotely controls the mobile phone to make an outgoing call by executing S301, S302, S304 and S305.

And when the HFP service is not supported between the bracelet and the mobile phone and the BLE service is supported, the bracelet and the mobile phone realize that the mobile phone remotely controls the call calling of the bracelet by executing S301, S302 and S307-S310. S301 and S302 can refer to the above description, and S307 to S310 will be described below.

In a possible implementation manner, when the traffic type between the bracelet and the mobile phone is BLE, BLE service is supported between the bracelet and the mobile phone.

And S307, when the BLE service is supported between the bracelet and the mobile phone, the bracelet sends a generic attribute profile (GATT) command or broadcast to the mobile phone.

In the embodiment of the application, the GATT command and broadcast are used for instructing the mobile phone to make a call. The GATT command may include a specific number or a preset number flag. The broadcast may include a specific number.

In a first possible implementation manner, the bracelet sends a handle value indication (handle value indication) command in the GATT command to the mobile phone, where the handle value indication command carries a specific number or a preset number flag.

Illustratively, the handle value indicates that the command is as shown in Table 1. The handle value indicates that the command includes an attribute opcode, an attribute handle, and an attribute value. The attribute value is used to convey a specific number or a preset number flag.

Table 1 handle value indication command

Parameter(s)	Size and breadth	Function(s)
			Attribute opcode	1	0 x 1D handle value indication
Attribute handler	2	Attribute handler
			Attribute value	0to(ATT_MTU-3)	Current handle value

In a possible implementation manner two, the bracelet sends a directional broadcast carrying a specific number to the mobile phone. The address type of the directional broadcast is public (public). The directional broadcast may include one or more of: broadcast length, broadcast type, Media Access Control (MAC) address of the handset, specific number, or other type of information. The content and format included in the directional broadcast are not particularly limited in the embodiments of the present application.

In a third possible implementation manner, the bracelet sends a non-directional broadcast carrying a specific number to the mobile phone. Wherein, the address type of the non-directional broadcast is random. The non-directed broadcast may include one or more of broadcast length, broadcast type, MAC address of the bracelet, specific number, or other types of information as described below. The content and format included in the non-directional broadcast are not particularly limited in the embodiments of the present application.

Illustratively, table 2 is a broadcast data format provided in an embodiment of the present application. Table 2 includes broadcast length, broadcast type, unique identifier (UUID), version, service, type table, MAC address, and specific number. The service and the type are used for judging whether the broadcast is a number calling broadcast or not by the mobile phone. The MAC address is used for the mobile phone to determine whether the broadcast is a broadcast sent by a connected device or received by the device itself.

Table 2 broadcast data format

S308, after receiving the GATT command from the bracelet, the mobile phone sends a response command to the bracelet.

For example, the response command sent by the handset to the bracelet may be a handle value confirmation (handle value confirmation) command in the GATT. Illustratively, the handle value confirmation command is shown in Table 3. The handle value confirmation command includes an attribute opcode.

Table 3 handle value confirm command

Parameter(s)	Size and breadth	Function(s)
			Attribute opcode	1	0 x 1E handle value validation

S309, after receiving the GATT command, the broadcast command, or the RFCOMM command from the bracelet, the mobile phone parses the GATT command, the broadcast command, or the RFCOMM command.

In a possible implementation manner, the mobile phone parses the GATT command to obtain a specific number, and dials the specific number.

In a possible implementation manner two, after receiving the directional broadcast, the mobile phone judges whether the directional broadcast is a broadcast called by an indication number through a service and type table in the directional broadcast, and when the directional broadcast is a broadcast called by an indication number, the mobile phone judges whether an MAC address carried in the directional broadcast data is the address of the mobile phone. When the MAC address carried in the directional broadcast data is the address of the mobile phone, the mobile phone analyzes the emergency number field in the directional broadcast to obtain a specific number and dials the number. When the MAC address carried in the directional broadcast data is not the address of the mobile phone, the mobile phone stops analyzing the directional broadcast. When the directional broadcast is not the broadcast indicating the number calling, the mobile phone stops analyzing the directional broadcast.

In a possible implementation manner, after receiving the non-directional broadcast, the mobile phone determines whether the non-directional broadcast is a broadcast indicating a number to call through a service and type table in the non-directional broadcast, and when the non-directional broadcast is a broadcast indicating a number to call, the mobile phone determines whether an MAC address carried in the non-directional broadcast data is an MAC address of a device to which the mobile phone is connected. When the MAC address carried in the non-directional broadcast data is the MAC address of the equipment connected with the mobile phone, the mobile phone obtains a specific number by analyzing the emergency number field in the non-directional broadcast and dials the number. When the MAC address carried in the non-directional broadcast data is not the MAC address of the equipment connected with the mobile phone, the mobile phone stops analyzing the non-directional broadcast. When the non-directional broadcast is not the broadcast indicating the number calling, the mobile phone stops analyzing the non-directional broadcast.

And S310, the mobile phone starts a play-out function, and the play-out function is used for amplifying the sound output by the mobile phone.

In a possible implementation manner, the function of turning on the mobile phone and playing the mobile phone outside may include turning on a speaker of the mobile phone, and the sound may be amplified through the speaker, so that the user may hear the sound transmitted by the mobile phone.

When the HFP service and the BLE service are not supported between the bracelet and the mobile phone and the SPP service is supported, the bracelet and the mobile phone realize remote control of the call outgoing of the mobile phone by executing S301, S302, S312, S309 and S310. S301, S302, and S310 can refer to the above description, and S312 and S309 are described below.

And S312, when the SPP service is supported between the bracelet and the mobile phone, the bracelet sends an RFCOMM command to the mobile phone.

When the SPP service is supported between the bracelet and the mobile phone, the SPP connection between the bracelet and the mobile phone can be established after the SDP service of the bracelet is found, and can also be established when the number is called out.

Illustratively, if the bracelet supports the SPP service with the mobile phone, the bracelet establishes SPP service connection, specifies the message type and transmits the number to the mobile phone through the RFCOMM DLC parameter negotiation command, and controls the mobile phone to dial out and make a call, so as to realize emergency call.

And S309, after receiving the RFCOMM command, the mobile phone analyzes the RFCOMM command.

After receiving the RFCOMM command, the mobile phone analyzes the RFCOMM command, acquires a specific number and dials out the specific number.

In a possible implementation manner, after receiving the RFCOMM command, the mobile phone replies the command to the bracelet.

When the bracelet does not support HFP service, BLE service, and SPP service, the bracelet cannot control a mobile phone call, and the bracelet performs S313.

And S313, when the SPP service is not supported between the bracelet and the mobile phone, the bracelet displays prompt information.

In the embodiment of the application, the prompt message is used for prompting the user to try to make a call in other modes or to enable the user to be in an emergency at present.

In a possible implementation manner, the bracelet may display a prompt box on the user interface, where the prompt box includes prompt information, and the prompt information may be "please make a call in other ways" or "emergency" or the like.

In summary, the bracelet may remotely control a cell phone call based on any one or more of HFP service, BLE service, and SPP service. Thus, the intelligent wearable device which does not support HFP service can control the mobile phone to realize remote calling when the BLE service and/or SPP service are supported. The emergency calling method can be applied to various intelligent wearable devices, and the application range of the remote calling function of the intelligent wearable devices is expanded.

The procedure of the hand ring call will be described with reference to fig. 7. Illustratively, fig. 7 is a schematic interface diagram of a bracelet call.

As shown in fig. 7, when the bracelet receives a user slide-up operation in the bracelet main interface shown in a in fig. 7, the bracelet can enter into a more function interface shown in b in fig. 7. The more functional interface includes more functional icons 701. When the user triggers the more-function icon control 701 through clicking, touching, or the like, the bracelet receives the operation of triggering the more-function icon control 701 by the user, and the bracelet enters a call interface shown in c in fig. 7. The call interface includes a call icon 702.

When the user triggers the call control 702 by clicking, touching, or the like, the bracelet receives the operation of triggering the call icon control 702 by the user, and enters the number 1 interface shown in d in fig. 7. The number 1 interface includes a number 1 icon 703. When the bracelet accepts the user to slide up on the number 1 interface, the bracelet enters the number 2 interface shown as e in fig. 7. The number 2 interface includes a number 2 icon 704. When the user clicks or long-presses the number 1 icon control 703 in the number 1 interface shown by d in fig. 7 or the number 2 icon control 704 in the number 2 interface shown by e in fig. 7, the bracelet performs the method shown in fig. 3 and enters the call-out interface shown by f in fig. 7.

In a possible implementation manner, when the bracelet is on the call interface shown in c in fig. 7, and a user key operation is received, the bracelet may select a corresponding number and dial out according to the frequency of key pressing. Illustratively, when the bracelet is in the call interface shown in c in fig. 7, and receives 2 key operations from the user, the bracelet selects number 2 shown in e in fig. 7, executes the method shown in fig. 3, and enters the call-out interface shown in f in fig. 7.

In a possible implementation manner, when the bracelet receives a call triggering operation set by the user, for example, the wrist rotation operation set in fig. 6, the bracelet enters an interface d shown in fig. 7, and if the bracelet does not receive an interface operation that the user exits the interface d, the bracelet executes the method shown in fig. 3 and enters a call-out interface f shown in fig. 7 within a preset time.

On the basis of the embodiment corresponding to fig. 3, the bracelet can determine the services supported between the bracelet and the mobile phone according to the service type between the bracelet and the mobile phone. The service type between the bracelet and the mobile phone can be acquired before Bluetooth connection. The method for acquiring the service type between the bracelet and the mobile phone by the bracelet is described below with reference to fig. 8.

Fig. 8 is a schematic flowchart of a method for acquiring a service type between a bracelet and a mobile phone by the bracelet according to an embodiment of the present application. As shown in fig. 8, the method includes:

s801, the bracelet acquires the characteristics of the bracelet.

In a possible implementation manner, the bracelet acquires the characteristics of the bracelet by acquiring the UUID. The UUID is used to identify bluetooth services and communication feature access attributes.

S802, the mobile phone obtains the characteristics of the mobile phone.

In a possible implementation manner, the mobile phone obtains the characteristics of the mobile phone by obtaining the UUID. The UUID is used to identify bluetooth services and communication feature access attributes.

S803, the bracelet pages the mobile phone.

In a possible implementation, the bracelet initiates paging (page) to the MAC address of the handset. Illustratively, the bracelet sends a page to the mobile phone, and after the mobile phone receives the page sent by the bracelet, the bracelet and the mobile phone start to establish an ACL link.

S804, the bracelet sends a Link Management Protocol (LMP) standard feature request to the mobile phone.

Illustratively, the bracelet sends an LMP _ FEATURES _ REQ command to the handset. And S805, the mobile phone sends an LMP standard characteristic reply to the bracelet.

Illustratively, the handset sends an LMP _ FEATURES _ RSP command to the bracelet.

And S806, the bracelet sends an LMP extension characteristic request to the mobile phone.

Illustratively, the bracelet sends an LMP _ FEATURES _ REQ _ EXT command to the handset. And S807, the mobile phone sends an LMP extension characteristic reply to the bracelet.

Illustratively, the handset sends an LMP _ FEATURES _ RSP _ EXT command to the bracelet.

And S808, the bracelet sends a characteristic notification supported by the remote terminal to the mobile phone.

And S809, the bracelet acquires the service type between the bracelet and the mobile phone.

The service type between the bracelet and the mobile phone can comprise one or more of the following types: BR, EDR, and BLE.

Therefore, the bracelet can acquire the characteristics supported by the mobile phone, so that the service type between the bracelet and the mobile phone is determined, and the bracelet can conveniently control the mobile phone call according to the supported service type.

On the basis of the embodiment corresponding to fig. 3, the bracelet can associate the local number of the mobile phone or the local number label of the mobile phone with other functions of ringing or playing music and the like in the mobile phone, so that the bracelet can search for the mobile phone or control the mobile phone to play music and the like.

In a possible implementation manner, the bracelet receives a trigger operation of a function of searching for a mobile phone or playing music outside a user, and when the bracelet and the mobile phone support HFP service, the bracelet sends an ATD command to the mobile phone, wherein the ATD command is used for instructing the mobile phone to make a call, the ATD command may carry a number or a number mark, and the number mark is associated with other functions such as ringing or music playing in the mobile phone. Correspondingly, the mobile phone receives the ATD command sent by the bracelet, and when the mobile phone analyzes the number or the number mark in the ATD command as the own number, the mobile phone starts ringing or plays music.

When the HFP service is not supported between the bracelet and the mobile phone and the BLE service is supported, the bracelet sends a GATT command or broadcast to the mobile phone, wherein the GATT command and the broadcast are used for indicating the mobile phone to make a call, the GATT command carries a specific number or a number mark, and the broadcast carries the specific number. Correspondingly, the mobile phone receives the GATT command or the broadcast sent by the bracelet, analyzes the GATT command or the broadcast sent by the bracelet, and starts ringing or playing music when the mobile phone analyzes the GATT command or the number in the broadcast or marks the number as the local number. When the bracelet and the mobile phone do not support HFP service and BLE service and support SPP service, the bracelet sends RFCOMM command to the mobile phone, wherein the RFCOMM command carries specific numbers or number marks. Correspondingly, the mobile phone receives the RFCOMM command sent by the bracelet, and when the mobile phone analyzes the number or the number mark in the RFCOMM command as the local number, the mobile phone starts ringing or plays music.

When the bracelet and the mobile phone do not support any one of HFP service, BLE service and SPP service, the bracelet prompts the user to control the mobile phone to ring or play music in other modes.

The specific implementation process of the bracelet searching the mobile phone or the bracelet controlling the music played outside the mobile phone is similar to the method shown in fig. 3, and is not described herein again.

Illustratively, fig. 9 is a schematic interface diagram of a bracelet-search mobile phone. In the search mobile phone interface shown in a in fig. 9, when the bracelet receives an operation of a search mobile phone control 901 clicked or touched by a user, the bracelet executes the method shown in fig. 3, so that the mobile phone rings, and the user can conveniently search. And displays the in-search interface shown in b of fig. 9.

When the bracelet receives a trigger operation of a user for searching the mobile phone, the bracelet enters a mobile phone searching interface shown as a in the figure 9, and if the bracelet does not receive an interface operation of the user for exiting from the interface shown as a in the figure 9 within a preset time, the bracelet executes the method shown in the figure 3, so that the mobile phone rings, and the user can conveniently search the mobile phone. And enters the in-search interface shown as b in fig. 9.

The emergency call method according to the embodiment of the present application has been described above, and the related apparatus for performing the emergency call method according to the embodiment of the present application is described below. Those skilled in the art will understand that the method and apparatus can be combined and referred to each other, and the smart wearable device provided in the embodiments of the present application can perform the steps in the emergency call method described above.

Fig. 10 is a schematic diagram of a hardware structure of an intelligent wearable device provided in an embodiment of the present application. Referring to fig. 10, the apparatus includes: memory 1001, processor 1002, and interface circuit 1003. The device may also include a display 1004, wherein the memory 1001, processor 1002, interface circuit 1003, and display 1004 may be in communication; illustratively, the memory 1001, the processor 1002, the interface circuit 1003 and the display screen 1004 may communicate via a communication bus, and the memory 1001 is used for storing computer-executable instructions, and is controlled by the processor 1002 to execute the communications, and the interface circuit 1003 executes the communications, thereby implementing the emergency call method provided by the embodiments described below in the present application.

In a possible implementation manner, the computer execution instructions in the embodiment of the present application may also be referred to as application program codes, which is not specifically limited in the embodiment of the present application.

Optionally, the interface circuit 1003 may further include a transmitter and/or a receiver. Optionally, the processor 1002 may include one or more CPUs, and may also be other general-purpose processors, Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the present application may be embodied directly in a hardware processor, or in a combination of the hardware and software modules in the processor.

The embodiment of the application also provides a computer readable storage medium. The methods described in the above embodiments may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. If implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media may include computer storage media and communication media, and may include any medium that can communicate a computer program from one place to another. A storage medium may be any target medium that can be accessed by a computer.

In one possible implementation, the computer-readable medium may include RAM, ROM, a compact disk read-only memory (CD-ROM) or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer. Also, any connection is properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of medium. Disk and Disc, as used herein, includes Disc, laser Disc, optical Disc, Digital Versatile Disc (DVD), floppy disk and blu-ray Disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

Embodiments of the present application are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

The above embodiments are only for illustrating the embodiments of the present invention and are not to be construed as limiting the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the embodiments of the present invention shall be included in the scope of the present invention.

Claims

1. An emergency call method, comprising:

the first equipment and the second equipment establish Bluetooth connection;

when the first device meets a first preset condition and supports the hands-free call HFP service, the first device sends a first message to the second device, wherein the first message comprises a first telephone number; the second device dials the first phone number in response to the first message;

when the first device does not support the HFP service and the first device supports the Bluetooth Low Energy (BLE) service, the first device sends a second message to the second device, wherein the second message comprises a second telephone number; the second device dials the second phone number in response to the second message;

when the first device does not support HFP service and BLE service and supports simple parallel SPP service, the first device sends a third message to the second device, wherein the third message comprises a third telephone number; the second device dials the third phone number in response to the third message;

the first device meeting a first preset condition comprises:

the first equipment detects that gesture operation of a user meets preset gesture operation, and the preset gesture operation is used for indicating the first equipment to make a call;

or the first device detects that the physiological characteristics of the user meet preset physiological characteristics, and the preset physiological characteristics are used for indicating the first device to make a call;

the method further comprises the following steps:

when the first device meets the first preset condition and the first device does not support HFP service, BLE service and SPP service, the first device displays prompt information, and the prompt information is used for prompting a user of emergency.

2. The method of claim 1, wherein the first message is an automatic dialing (ATD) command, and wherein the ATD command comprises the first telephone number.

3. The method of claim 1, wherein the second message is a generic attribute profile (GATT) command, the GATT command comprising the second phone number;

or, the second message is a broadcast, and the broadcast includes the second phone number.

4. The method of claim 1, wherein the third message is a Radio Frequency Communication (RFCOMM) command, wherein the RFCOMM command comprises the third phone number.

5. The method of claim 1, further comprising:

the second equipment starts a play-out function; the play-out function is used for amplifying the sound output by the second device.

6. An emergency call method, comprising:

the first equipment and the second equipment establish Bluetooth connection;

when the first device meets a first preset condition and supports the hands-free call HFP service, the first device sends a first message to the second device, wherein the first message comprises a first telephone number;

when the first device does not support the HFP service and the first device supports the Bluetooth Low Energy (BLE) service, the first device sends a second message to the second device, wherein the second message comprises a second telephone number;

when the first device does not support HFP service and BLE service and supports simple parallel SPP service, the first device sends a third message to the second device, wherein the third message comprises a third telephone number;

the first device meeting a first preset condition comprises:

the method comprises the steps that the first equipment detects that gesture operation of a user meets preset gesture operation, and the preset gesture operation is used for indicating the first equipment to make a call;

or the first device detects that the physiological characteristics of the user meet preset physiological characteristics, wherein the preset physiological characteristics are used for indicating the first device to make a call;

the method further comprises the following steps:

7. The method of claim 6, wherein the first message is an automatic dialing (ATD) command, and wherein the ATD command comprises the first telephone number.

8. The method of claim 6, wherein the second message is a generic Attribute Profile (GATT) command, the GATT command comprising the second phone number;

9. The method of claim 6, wherein the third message is a Radio Frequency Communication (RFCOMM) command, and wherein the RFCOMM command comprises the third phone number.

10. An intelligence wearing equipment which characterized in that includes: a processor and a memory;

the memory stores computer-executable instructions;

the processor executing the computer-executable instructions stored by the memory causes the processor to perform the method of any of claims 6-9.

11. A bracelet, comprising: a processor and a memory;

the memory stores computer-executable instructions;

12. A computer-readable storage medium, in which a computer program or instructions are stored which, when executed, implement the method of any one of claims 6-9.