CN110177357B - Bluetooth management method, mobile terminal and computer storage medium - Google Patents

Abstract

The present application discloses a Bluetooth management method, a mobile terminal and a computer storage medium. The Bluetooth management method includes: when the mobile terminal starts Bluetooth, the service classes corresponding to all application protocols are enabled; and the target application protocol supported by the target peripheral device is determined; The target peripheral device is one or more peripheral devices that perform Bluetooth communication with the mobile terminal; the service classes corresponding to application protocols other than the target application protocol are closed. In the above manner, the power consumption and memory occupation of the Bluetooth application can be reduced.

Description

A Bluetooth management method, mobile terminal and computer storage medium

technical field

The present application relates to the field of Bluetooth technology, and in particular, to a Bluetooth management method, a mobile terminal and a computer storage medium.

Background technique

Bluetooth is a widely used short-range communication technology. Based on Bluetooth technology, a variety of different functions can be implemented, such as hands-free calling, audio streaming, file transfer, etc. These so-called functions are called Bluetooth profiles (application protocols). For example, the three functions mentioned above correspond to The profiles are HFP (Hands-Free Protocol), A2DP (Audio Transmission Protocol), and OPP (Object Push Protocol). Although all profiles are implemented based on Bluetooth L2CAP (Logical Link Control Adaptation Protocol, which is the basic protocol of Bluetooth), each profile has its own completely different logic.

SUMMARY OF THE INVENTION

A technical solution adopted in the present application is to provide a Bluetooth management method, the method includes: when the mobile terminal starts Bluetooth, enabling service classes corresponding to all application protocols; determining the target application protocol supported by the target peripheral device; wherein, The target peripheral device is one or more peripheral devices that perform Bluetooth communication with the mobile terminal; the service classes corresponding to application protocols other than the target application protocol are closed.

Another technical solution adopted in the present application is to provide a mobile terminal, the mobile terminal includes a processor, a Bluetooth module connected to the processor, and a memory; wherein the Bluetooth module is used for pairing with peripheral devices for Bluetooth communication, and the memory It is used to store program data, and the processor is used to execute the program data to realize the following method: when the mobile terminal starts Bluetooth, the service classes corresponding to all application protocols are opened; the target application protocol supported by the target peripheral device is determined; wherein, the target peripheral device is One or more peripheral devices that perform Bluetooth communication with the mobile terminal; close the service classes corresponding to application protocols other than the target application protocol.

Another technical solution adopted in the present application is to provide a computer storage medium, in which program data is stored, and when the program data is executed by the processor, the following method is implemented: when the mobile terminal starts Bluetooth, the Service classes corresponding to all application protocols; determine the target application protocols supported by the target peripheral device; wherein, the target peripheral device is one or more peripheral devices that perform Bluetooth communication with the mobile terminal; close all application protocols except the target application protocol. the corresponding service class.

The Bluetooth management method provided by the present application includes: when the mobile terminal starts Bluetooth, the service classes corresponding to all application protocols are enabled; the target application protocol supported by the target peripheral device is determined; wherein, the target peripheral device is a device that performs Bluetooth communication with the mobile terminal. or multiple peripheral devices; close the service class corresponding to the application protocol other than the target application protocol. Through the above method, according to the application protocol supported by the paired peripheral device, dynamically switch the Service class corresponding to the profile in the Bluetooth application program to avoid high power consumption and high memory occupation when all Service classes are turned on. The problem can reduce the power consumption and memory usage of the Bluetooth application.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the drawings that are used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can also be obtained from these drawings without creative effort. in:

FIG. 1 is a first schematic flowchart of a Bluetooth management method provided by an embodiment of the present application;

2 is a schematic flowchart of determining a target application protocol provided by an embodiment of the present application;

3 is a second schematic flowchart of a Bluetooth management method provided by an embodiment of the present application;

4 is a schematic diagram of pairing a mobile terminal and a peripheral device provided by an embodiment of the present application;

5 is a third schematic flowchart of a Bluetooth management method provided by an embodiment of the present application;

6 is a schematic structural diagram of a mobile terminal provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a computer storage medium provided by an embodiment of the present application.

Detailed ways

Referring to FIG. 1, FIG. 1 is a first schematic flowchart of a Bluetooth management method provided by an embodiment of the present application, and the method includes:

Step 101 : when the mobile terminal starts the Bluetooth, the service classes corresponding to all the application protocols are started.

Bluetooth (Bluetooth) is a wireless technology standard that can realize short-distance data exchange between fixed devices, mobile devices and building personal area networks (UHF radio waves in the ISM band of 2.4-2.485GHz).

The L2CAP (Logical Link Control and Adaptation Protocol) protocol in Bluetooth is also called the Logical Link Control and Adaptation Protocol. It is the core protocol in the Bluetooth system and is responsible for adapting the upper layer protocol in the baseband.

The upper-layer application protocols of Bluetooth are listed in the following table:

HFP hands-free protocol Hands Free Protocol A2DP audio transmission protocol Advanced Audio Distribution Profile OPP target push protocol Object Push Protocol AVRCP Audio and video remote control protocol Audio Video Remote Control Protocol GATT Common Attribute Protocol Generic Attribute PAN Personal Area Local Area Network Protocol Personal Area Network PBAP Phone Book Access Agreement Phone Book Access Protocol HID Human Input Device Protocol Human Input Device

In the Android (Android) system, the Bluetooth function is integrated into a Bluetooth application (Bluetooth.apk), and the logic of each profile is implemented in Bluetooth.apk through a Service class (service class) (these Service classes are all Inherited from the android.app.Service class).

When the Bluetooth function is enabled, the Bluetooth.apk will parse a configuration file to obtain the Bluetooth profile currently supported by the current mobile phone, and open all the corresponding Service classes according to the supported profile. The correspondence between the commonly used Bluetooth profiles and their corresponding Service classes in Bluetooth.apk is shown in the following table:

When the Service classes corresponding to these profiles are enabled, each profile is available. When the Bluetooth function is turned off, the above Services will be turned off.

Step 102: Determine the target application protocol supported by the target peripheral device; wherein, the target peripheral device is one or more peripheral devices that perform Bluetooth communication with the mobile terminal.

In some embodiments, the peripheral device may be a Bluetooth functional device such as a Bluetooth headset, a Bluetooth speaker, or a Bluetooth walkie-talkie, or other mobile terminals, such as a mobile phone, a tablet computer, a wearable device, and the like.

In some embodiments, it can be assumed that the mobile terminal supports all application protocols by default. Then, it can be considered that as long as the application protocols supported by the peripheral device are supported by the mobile terminal, the mobile terminal also supports. Therefore, the application protocol supported by the target peripheral device can be directly obtained as the target application protocol.

Understandably, if a certain application protocol supported by the target peripheral device is not supported by the mobile terminal, then there is no meaning of establishing a Bluetooth connection between the mobile terminal and the peripheral device.

In other embodiments, as shown in FIG. 2 , which is a schematic flowchart of determining a target application protocol provided by an embodiment of the present application, step 101 may specifically include:

Step 1021: Determine the first application protocol supported by the mobile terminal, and determine the second application protocol supported by the target peripheral device.

Wherein, the first application protocol supported by the mobile terminal itself can be easily obtained, which will not be repeated here, and the following methods may be specifically adopted to determine the second application protocol supported by the target peripheral device: using the Service Discovery Protocol (SDP, Service Discovery Protocol). ) to obtain the second application protocol supported by the target peripheral device.

The SDP protocol allows mobile terminals to discover the services provided by paired peripherals and the attributes of those services. SDP only provides a mechanism for discovering services, not a method for using these services. Every bluetooth device needs an SDP protocol. Each Service in the SDP protocol is represented by a ServiceRecord (with a unique 32-bit Handle), each ServiceRecord is composed of several ServiceAttributes, and the ServiceAttribute is composed of two parts: Attribute ID and Attribute Valuel. These records can be accessed through the SDP request to obtain the service information of the peripheral device, so as to obtain the application protocol supported by the peripheral device.

Step 1022: Determine the intersection of the first application protocol and the second application protocol as the target application protocol.

Generally speaking, the number of the first application protocol supported by the mobile terminal is much larger than the number of the second application protocol supported by the peripheral device.

For example, the first application protocol supported by the mobile terminal includes HFP protocol, A2DP protocol, OPP protocol, AVRCP (Controller) protocol, GATT protocol, PAN protocol, PBAP protocol, and HID protocol. Assuming that the peripheral device is a Bluetooth headset, it supports The second application protocol includes the HFP protocol and the A2DP protocol. Then, the target application protocol of the intersection of the first application protocol and the second application protocol includes the HFP protocol and the A2DP protocol.

Step 103: Close the service classes corresponding to the application protocols other than the target application protocol.

In some embodiments, when the target peripheral device and the mobile terminal cancel the Bluetooth pairing, the state of the second service class corresponding to the application protocol other than the target application protocol is queried; if the second service class is on, the second service class is turned off. Service class; if the second service class is closed, keep it closed.

Taking the above example to illustrate, the first application protocol includes HFP protocol, A2DP protocol, OPP protocol, AVRCP (Controller) protocol, GATT protocol, PAN protocol, PBAP protocol, HID protocol, assuming that the peripheral device is a Bluetooth headset, it supports The second application protocol includes the HFP protocol and the A2DP protocol. Then, the target application protocol of the intersection of the first application protocol and the second application protocol includes the HFP protocol and the A2DP protocol. Then, the open server is the server class corresponding to the HFP protocol and A2DP protocol, and the closed service class is the service class corresponding to the OPP protocol, AVRCP (Controller) protocol, GATT protocol, PAN protocol, PBAP protocol, and HID protocol.

In addition, after step 103, it may further include: enabling the service class corresponding to the target application protocol.

It is understandable that in general, after the mobile terminal turns on Bluetooth, the server classes corresponding to all supported application protocols will be turned on by default. In the case of the device, some service classes are closed, so in some application scenarios, the closed service classes are also opened.

In some embodiments, when a new peripheral device establishes a Bluetooth pairing with the mobile terminal, the target application protocol supported by the target peripheral device is re-determined; or when a target peripheral device that has been paired with the mobile terminal, cancels the Bluetooth connection with the mobile terminal When pairing, re-determine the target application protocol supported by the target peripheral.

For example, the service class corresponding to the HFP application protocol supported by the target peripheral device is the HeadsetService service class. When the mobile terminal initially turns on Bluetooth, all service classes (including the HeadsetService service class) are turned on, then the HeadsetService service class corresponding to the HFP application protocol supported by the target peripheral device is obtained, and other service classes except the HeadsetService service class are turned off. If the target peripheral device cancels the Bluetooth connection with the mobile terminal, the HeadsetService service class is turned off, and if the target peripheral device establishes the Bluetooth connection with the mobile terminal again, the HeadsetService service class is turned on.

The Bluetooth management method provided by this embodiment includes: when the mobile terminal starts Bluetooth, the service classes corresponding to all application protocols are enabled; the target application protocol supported by the target peripheral device is determined; wherein, the target peripheral device is a device that performs Bluetooth communication with the mobile terminal. Peripheral device; closes the service class corresponding to the application protocol other than the target application protocol. Through the above method, according to the application protocol supported by the paired peripheral device, dynamically switch the Service class corresponding to the profile in the Bluetooth.apk, which avoids high power consumption and high memory usage when all Service classes are turned on. The problem can reduce the power consumption and memory usage of Bluetooth.apk.

In some embodiments, during the use of Bluetooth, a new peripheral device may establish a Bluetooth connection with the mobile terminal, and a peripheral device that has established a Bluetooth connection with the mobile terminal may cancel the Bluetooth connection with the mobile terminal. In the specific application process, it is relatively cumbersome to detect the target application protocol jointly supported by the mobile terminal and the target peripheral device each time. It can be understood that, among the multiple peripheral devices connected with the mobile terminal, there may be two devices of the same model, and the two devices support the same application protocol. In this embodiment, whether to re-determine the target application protocol jointly supported by the mobile terminal and the target peripheral device can be determined by judging whether there are devices of the same model.

Specifically, when a first peripheral device establishes a Bluetooth pairing with the mobile terminal, the model of the first peripheral device is obtained; if there is a second peripheral device in one or more first peripheral devices, the second peripheral device and the target peripheral device The model of each peripheral device is different, then re-determine the target application protocol supported by the target peripheral device.

For example, after a first peripheral device establishes a Bluetooth connection with the mobile terminal, if device A exists in the first peripheral device, and the model of each device in the target peripheral device is different, the target peripheral device supported by the target peripheral device is re-determined. application protocol. If all the devices in the first peripheral device have a device of the same model in the target device, it is not necessary to determine the target application protocol supported by the target peripheral device again.

Specifically, when the third peripheral device in the target peripheral device that has been paired with the mobile terminal cancels the Bluetooth pairing with the mobile terminal, the model of the third peripheral device is obtained; if there is a fourth peripheral device in one or more third peripheral devices device, the fourth peripheral device and the target peripheral device have different models of each peripheral device that maintains Bluetooth pairing, and the target application protocol supported by the target peripheral device is re-determined.

For example, when the third peripheral device in the target peripheral device that has been paired with the mobile terminal cancels the Bluetooth pairing with the mobile terminal, if there is Device B in one or more third peripheral devices, the device B remains paired with the target peripheral device. The model of each peripheral device is different, then re-determine the target application protocol supported by the target peripheral device. If all the devices in the third peripheral device have a device of the same model in the target device, there is no need to determine the target application protocol supported by the target peripheral device again.

Referring to FIG. 3, FIG. 3 is a second schematic flowchart of a Bluetooth management method provided by an embodiment of the present application. The method includes:

Step 301 : when the mobile terminal starts the Bluetooth, the service classes corresponding to all application protocols are started.

Step 302: Establish a corresponding counter for each application protocol.

The value of the counter identifies the number of peripheral devices that have been paired with the mobile terminal and support the corresponding application protocol, and the initial value of the counter is 0.

It can be understood that a mobile terminal can generally form a Bluetooth pairing with multiple peripheral devices, as shown in FIG. 4 , which is a schematic diagram of pairing between a mobile terminal and a peripheral device provided by an embodiment of the present application, wherein the mobile terminal 41 is respectively paired with the first peripheral device. The device 42, the second peripheral device 43 and the third peripheral device 44 form a pair.

Referring to the table below, the table below shows the application protocols supported by the mobile terminal 41 and the first peripheral device 42 , the second peripheral device 43 and the third peripheral device 44 respectively, and the corresponding counter values.

mobile terminal first peripheral second peripheral third peripheral counter HFP HFP 1 A2DP A2DP A2DP A2DP 3 OPP OPP OPP 2 AVRCP AVRCP 1 GATT 0 PAN 0 PBAP PBAP 1 HID HID 1

Step 303: Determine the target application protocol supported by the target peripheral device.

Step 304: Add 1 to the counter corresponding to the target application protocol.

Understandably, for the newly paired peripheral device, the SDP protocol can be used to obtain the application protocol it supports, and then the value of the corresponding counter in the above table is increased. Then the value of the corresponding counter in the above table is decreased.

After step 304, step 305 and step 308 are performed, respectively.

Step 305: Query the status of the first service class corresponding to application protocols other than the target application protocol.

Step 306 : if the first service class is in an open state and the value of the counter corresponding to the target application protocol is 0, then close the first service class.

If the target application protocol does not include the PAN protocol, according to the value of the counter shown in the above table, it is detected whether the Service class corresponding to the PAN protocol is in the open state. If it is in the open state, the Service class corresponding to the PAN protocol is closed.

If the target application protocol does not include the PAN protocol, the value of the counter shown in the above table is 0, and at the same time, it is detected whether the Service class corresponding to the PAN protocol is in the open state, and if it is in the closed state, the closed state is maintained.

Step 307: If the first service class is in the closed state, keep the closed state.

Step 308: Query the status of the second service class corresponding to the target application protocol.

Step 309: If the second service class is in the open state, keep the open state.

If the target application protocol includes the A2DP protocol, according to the value of the counter shown in the above table, add 1 to 3, and check whether the Service class corresponding to the A2DP protocol is in the open state. If it is in the open state, keep it in the open state. .

Step 310: If the second service class is in an off state, enable the second service class.

If the target application protocol includes the GATT protocol, according to the value of the counter shown in the above table, add 1 to 0, and at the same time check whether the Service class corresponding to the GATT protocol is in the open state, if it is in the closed state, then open the GATT protocol The corresponding Service class.

Referring to FIG. 5, FIG. 5 is a third schematic flowchart of a Bluetooth management method for a mobile terminal provided by an embodiment of the present application. The method includes:

Step 501 : when the mobile terminal starts the Bluetooth, the service classes corresponding to all the application protocols are started.

Step 502: Establish a corresponding counter for each application protocol.

The value of the counter identifies the number of peripheral devices that have been paired with the mobile terminal and support the corresponding application protocol, and the initial value of the counter is 0.

Step 503: Determine the target application protocol supported by the target peripheral device.

Step 504: Add 1 to the counter corresponding to the target application protocol.

Step 505: If the Bluetooth pairing with the target peripheral device is released, obtain the second application protocol supported by the target peripheral device.

Step 506: Decrement the value of the counter corresponding to the second application protocol by 1.

Continuing to refer to the following table, the table below shows the application protocols supported by the mobile terminal and the first peripheral device, the second peripheral device and the third peripheral device respectively, and the corresponding counter values.

If the mobile terminal releases the Bluetooth pairing with the third peripheral device, the value of the counter corresponding to the A2DP protocol and the HID protocol is decremented by 1, as follows:

mobile terminal first peripheral second peripheral counter HFP HFP 1 A2DP A2DP A2DP 3-1=2 OPP OPP OPP 2 AVRCP AVRCP 1 GATT 0 PAN 0 PBAP PBAP 1 HID 1-1=0

Step 507: Detect whether the value of the counter corresponding to the second application protocol is 0.

Wherein, it is detected whether the value of the counter corresponding to the A2DP protocol and the HID protocol is 0.

Step 508: Close the service class corresponding to the second application protocol.

If it is detected that the value of the counter corresponding to the HID protocol is 0, then the Service class corresponding to the HID protocol is closed.

In addition, in the above-mentioned embodiment, if the mobile terminal turns off the Bluetooth, all service classes are turned off at the same time, and the values of the counters corresponding to all service classes are cleared to zero.

Referring to FIG. 6 , FIG. 6 is a schematic structural diagram of a mobile terminal provided by an embodiment of the present application. The mobile terminal 60 includes a processor 61 , a Bluetooth module 62 connected to the processor 61 , and a memory 63 .

The Bluetooth module 62 is also called a Bluetooth module, and is generally composed of a chip, a Printed Circuit Board (PCB), and peripheral devices.

Understandably, the mobile terminal 60 may be a mobile phone, a tablet computer, a wearable device and a smart device.

Wherein, the memory 63 is used to store the program data, and the processor 61 is used to execute the program data to realize the following method:

When the mobile terminal starts Bluetooth, the service classes corresponding to all application protocols are enabled; the target application protocol supported by the target peripheral device is determined; wherein, the target peripheral device is one or more peripheral devices that perform Bluetooth communication with the mobile terminal; Service classes corresponding to application protocols other than application protocols.

In some embodiments, the processor 61 is further configured to execute the program data to implement the method of determining the target application protocol supported by the target peripheral device using the service discovery protocol.

In some embodiments, the processor 61 is further configured to execute the program data to implement the following method: when a new peripheral device establishes a Bluetooth pairing with the mobile terminal, re-determine the target application protocol supported by the target peripheral device; or when a new peripheral device establishes a Bluetooth pairing with the mobile terminal; When the target peripheral device that is paired with the mobile terminal cancels the Bluetooth pairing with the mobile terminal, the target application protocol supported by the target peripheral device is re-determined.

In some embodiments, the processor 61 is further configured to execute the program data to implement the following method: when a first peripheral device establishes a Bluetooth pairing with the mobile terminal, obtain the model of the first peripheral device; There is a second peripheral device in the peripheral device, and the model of each peripheral device in the second peripheral device and the target peripheral device is different, then re-determine the target application protocol supported by the target peripheral device

In some embodiments, the processor 61 is further configured to execute the program data to implement the following method: when the third peripheral device in the target peripheral device that has been paired with the mobile terminal cancels the Bluetooth pairing with the mobile terminal, obtain the third peripheral device The model of the device; if there is a fourth peripheral in one or more third peripherals, and the model of each peripheral that maintains Bluetooth pairing in the fourth peripheral is different from that of the target peripheral, then re-determine the type of the target peripheral. Supported target application protocols.

In some embodiments, the processor 61 is further configured to execute the program data to implement the following method: when the target peripheral device and the mobile terminal cancel the Bluetooth pairing, query the first service class corresponding to the application protocol other than the target application protocol. state; if the first service class is in the open state, the first service class is closed; if the first service class is in the closed state, the closed state is maintained.

In some embodiments, the processor 61 is further configured to execute the program data to implement the following method: when a new peripheral device establishes a Bluetooth pairing with the mobile terminal, query the state of the second service class corresponding to the target application protocol; If the second service class is in the open state, the open state is maintained; if the second service class is in the closed state, the second service class is opened.

In some embodiments, the processor 61 is further configured to execute program data to implement the following method: after a set period of time when Bluetooth is enabled, if no peripheral device communicates with the mobile terminal via Bluetooth, close all application protocols corresponding to the service class.

Referring to FIG. 7, FIG. 7 is a schematic structural diagram of a computer storage medium provided by an embodiment of the present application. The computer storage medium 70 stores program data 71, and when the program data 71 is executed by the processor, it is used to implement the following method:

When the mobile terminal starts Bluetooth, the service classes corresponding to all application protocols are turned on; the target application protocol supported by the target peripheral device is determined; wherein, the target peripheral device is a peripheral device that performs Bluetooth communication with the mobile terminal; The service class corresponding to the application protocol.

In some embodiments, the program data 71, when executed by the processor, is also used to implement the following method: using the service discovery protocol to determine the target application protocol supported by the target peripheral device.

In some embodiments, when executed by the processor, the program data 71 is further used to implement the following method: when a new peripheral device establishes a Bluetooth pairing with the mobile terminal, re-determining the target application protocol supported by the target peripheral device; Or when the target peripheral device that has been paired with the mobile terminal cancels the Bluetooth pairing with the mobile terminal, the target application protocol supported by the target peripheral device is re-determined.

In some embodiments, when the program data 71 is executed by the processor, it is also used to implement the following method: when a first peripheral device establishes a Bluetooth pairing with the mobile terminal, obtain the model of the first peripheral device; if one or more There is a second peripheral device in each of the first peripheral devices, and the models of the second peripheral device and each peripheral device in the target peripheral device are different, and the target application protocol supported by the target peripheral device is re-determined.

In some embodiments, when the program data 71 is executed by the processor, it is further used to implement the following method: when the third peripheral device in the target peripheral device that has been paired with the mobile terminal cancels the Bluetooth pairing with the mobile terminal, obtain The model of the third peripheral device; if there is a fourth peripheral device in one or more third peripheral devices, and the model of each peripheral device that maintains Bluetooth pairing in the fourth peripheral device and the target peripheral device is different, then re-determine the target The target application protocol supported by the peripheral device.

In some embodiments, the program data 71, when executed by the processor, is further used to implement the following method: when the target peripheral device cancels the Bluetooth pairing with the mobile terminal, query the first application protocol corresponding to the application protocol other than the target application protocol. The state of the service class; if the first service class is in the open state, the first service class is closed; if the first service class is in the closed state, the closed state is maintained.

In some embodiments, when executed by the processor, the program data 71 is further used to implement the following method: when a new peripheral device establishes a Bluetooth pairing with the mobile terminal, query the state of the second service class corresponding to the target application protocol ; If the second service class is in the open state, keep the open state; if the second service class is in the closed state, open the second service class.

In some embodiments, when the program data 71 is executed by the processor, it is also used to implement the following method: after a set period of time when Bluetooth is enabled, if no peripheral device communicates with the mobile terminal via Bluetooth, all application protocols are closed. the corresponding service class.

In the several embodiments provided in this application, it should be understood that the disclosed method and device may be implemented in other manners. For example, the device implementations described above are only illustrative. For example, the division of the modules or units is only a logical function division. In actual implementation, there may be other divisions. For example, multiple units or components may be Incorporation may either be integrated into another system, or some features may be omitted, or not implemented.

The units described as separate components may or may not be physically separated, and components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this implementation manner.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit. The above-mentioned integrated units may be implemented in the form of hardware, or may be implemented in the form of software functional units.

If the integrated units in the other embodiments described above are implemented in the form of software functional units and sold or used as independent products, they may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor (processor) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes.

The above description is only an embodiment of the present application, and is not intended to limit the scope of the patent of the present application. Any equivalent structure or equivalent process transformation made by using the contents of the description and drawings of the present application, or directly or indirectly applied to other related technologies Fields are similarly included within the scope of patent protection of this application.

Claims (6)

1. A bluetooth management method, comprising:

when the mobile terminal starts the Bluetooth, starting service classes corresponding to all application protocols;

establishing a corresponding counter for each application protocol;

determining a first application protocol supported by the mobile terminal, and determining a second application protocol supported by a target peripheral device by adopting a service discovery protocol; the target peripheral equipment is one or more peripheral equipment which carries out Bluetooth communication with the mobile terminal;

determining an intersection of the first application protocol and the second application protocol as a target application protocol; when a new peripheral device establishes Bluetooth pairing with the mobile terminal, re-determining a target application protocol supported by the target peripheral device; or when the target peripheral equipment which is paired with the mobile terminal is cancelled with the mobile terminal, the target application protocol supported by the target peripheral equipment is determined again;

adding 1 to a counter corresponding to the target application protocol;

inquiring the state of a first service class corresponding to the application protocol except the target application protocol;

if the first service class is in an open state and the value of a counter corresponding to the target application protocol is a preset threshold value, closing the first service class, and if the first service class is in a closed state, keeping the closed state;

querying the state of a second service class corresponding to the target application protocol;

if the second service class is in an open state, the second service class is kept in the open state, and if the second service class is in a closed state, the second service class is opened;

if the Bluetooth pairing with the target peripheral equipment is released, acquiring a second application protocol supported by the target peripheral equipment and subtracting 1 from the value of a counter corresponding to the second application protocol;

and when the value of the counter corresponding to the second application protocol is a preset threshold value, closing the service class corresponding to the second application protocol.

2. The method of claim 1,

the step of re-determining the target application protocol supported by the target peripheral device when the new peripheral device establishes bluetooth pairing with the mobile terminal includes:

when a first peripheral device establishes Bluetooth pairing with the mobile terminal, acquiring the model of the first peripheral device;

and if a second peripheral device exists in one or more first peripheral devices, and the model of each peripheral device in the second peripheral device is different from that of each peripheral device in the target peripheral device, re-determining the target application protocol supported by the target peripheral device.

3. The method of claim 1,

the step of re-determining the target application protocol supported by the target peripheral device when the target peripheral device paired with the mobile terminal cancels bluetooth pairing with the mobile terminal comprises:

when the Bluetooth pairing between a third peripheral device which is paired with the mobile terminal in the target peripheral device and the mobile terminal is cancelled, acquiring the model of the third peripheral device;

and if a fourth peripheral device exists in one or more third peripheral devices, and the model of each peripheral device which is paired with the target peripheral device by the Bluetooth is different from that of each peripheral device which is paired with the target peripheral device, re-determining the target application protocol supported by the target peripheral device.

4. The method of claim 1,

when the mobile terminal starts the bluetooth, after the step of starting the service classes corresponding to all the application protocols, the method further comprises the following steps:

and after the first preset time of starting the Bluetooth, if no peripheral equipment performs Bluetooth communication with the mobile terminal, closing the service classes corresponding to all application protocols.

5. A mobile terminal is characterized by comprising a processor, a Bluetooth module and a memory, wherein the Bluetooth module and the memory are connected with the processor;

wherein the bluetooth module is for bluetooth communication with a peripheral device pair, the memory is for storing program data, and the processor is for executing the program data to implement the method of any one of claims 1-4.

6. A computer storage medium, characterized in that program data are stored in the computer storage medium, which program data, when being executed by a processor, are adapted to carry out the method of any one of claims 1-4.

Images