WO2019218548A1 - 连接请求处理方法、装置、蓝牙耳机、穿戴设备、系统及存储介质 - Google Patents

连接请求处理方法、装置、蓝牙耳机、穿戴设备、系统及存储介质 Download PDF

Info

Publication number
WO2019218548A1
WO2019218548A1 PCT/CN2018/105041 CN2018105041W WO2019218548A1 WO 2019218548 A1 WO2019218548 A1 WO 2019218548A1 CN 2018105041 W CN2018105041 W CN 2018105041W WO 2019218548 A1 WO2019218548 A1 WO 2019218548A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal device
bluetooth headset
connection request
a2dp connection
a2dp
Prior art date
Application number
PCT/CN2018/105041
Other languages
English (en)
French (fr)
Inventor
王雪梅
Original Assignee
歌尔科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 歌尔科技有限公司 filed Critical 歌尔科技有限公司
Priority to US16/959,969 priority Critical patent/US11178707B2/en
Publication of WO2019218548A1 publication Critical patent/WO2019218548A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01D—MEASURING NOT SPECIALLY ADAPTED FOR A SPECIFIC VARIABLE; ARRANGEMENTS FOR MEASURING TWO OR MORE VARIABLES NOT COVERED IN A SINGLE OTHER SUBCLASS; TARIFF METERING APPARATUS; MEASURING OR TESTING NOT OTHERWISE PROVIDED FOR
    • G01D5/00—Mechanical means for transferring the output of a sensing member; Means for converting the output of a sensing member to another variable where the form or nature of the sensing member does not constrain the means for converting; Transducers not specially adapted for a specific variable
    • G01D5/12—Mechanical means for transferring the output of a sensing member; Means for converting the output of a sensing member to another variable where the form or nature of the sensing member does not constrain the means for converting; Transducers not specially adapted for a specific variable using electric or magnetic means
    • G01D5/14—Mechanical means for transferring the output of a sensing member; Means for converting the output of a sensing member to another variable where the form or nature of the sensing member does not constrain the means for converting; Transducers not specially adapted for a specific variable using electric or magnetic means influencing the magnitude of a current or voltage
    • G01D5/142—Mechanical means for transferring the output of a sensing member; Means for converting the output of a sensing member to another variable where the form or nature of the sensing member does not constrain the means for converting; Transducers not specially adapted for a specific variable using electric or magnetic means influencing the magnitude of a current or voltage using Hall-effect devices
    • G01D5/145—Mechanical means for transferring the output of a sensing member; Means for converting the output of a sensing member to another variable where the form or nature of the sensing member does not constrain the means for converting; Transducers not specially adapted for a specific variable using electric or magnetic means influencing the magnitude of a current or voltage using Hall-effect devices influenced by the relative movement between the Hall device and magnetic fields
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01J—MEASUREMENT OF INTENSITY, VELOCITY, SPECTRAL CONTENT, POLARISATION, PHASE OR PULSE CHARACTERISTICS OF INFRARED, VISIBLE OR ULTRAVIOLET LIGHT; COLORIMETRY; RADIATION PYROMETRY
    • G01J5/00—Radiation pyrometry, e.g. infrared or optical thermometry
    • G01J5/0003—Radiation pyrometry, e.g. infrared or optical thermometry for sensing the radiant heat transfer of samples, e.g. emittance meter
    • G01J5/0011—Ear thermometers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
    • H04R1/00—Details of transducers, loudspeakers or microphones
    • H04R1/10—Earpieces; Attachments therefor ; Earphones; Monophonic headphones
    • H04R1/1041—Mechanical or electronic switches, or control elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/25—Maintenance of established connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
    • H04R1/00—Details of transducers, loudspeakers or microphones
    • H04R1/10—Earpieces; Attachments therefor ; Earphones; Monophonic headphones
    • H04R1/1016—Earpieces of the intra-aural type
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
    • H04R2420/00—Details of connection covered by H04R, not provided for in its groups
    • H04R2420/07—Applications of wireless loudspeakers or wireless microphones
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04R—LOUDSPEAKERS, MICROPHONES, GRAMOPHONE PICK-UPS OR LIKE ACOUSTIC ELECTROMECHANICAL TRANSDUCERS; DEAF-AID SETS; PUBLIC ADDRESS SYSTEMS
    • H04R2460/00—Details of hearing devices, i.e. of ear- or headphones covered by H04R1/10 or H04R5/033 but not provided for in any of their subgroups, or of hearing aids covered by H04R25/00 but not provided for in any of its subgroups
    • H04R2460/03—Aspects of the reduction of energy consumption in hearing devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present application relates to the field of wireless communications technologies, and in particular, to a connection request processing method and apparatus, a Bluetooth headset, a wearable device, a system, and a storage medium.
  • Bluetooth devices have gradually entered people's daily lives, bringing great convenience to people's lives.
  • Bluetooth headsets use Bluetooth technology on hands-free headsets, allowing users to avoid the annoying wires and easily talk or listen to music in a variety of ways.
  • the terminal device performs Bluetooth connection with the Bluetooth headset through a Hands-Free Profile (HFP) protocol and an Advanced Audio Distribution Profile (A2DP) protocol, respectively.
  • HFP Hands-Free Profile
  • A2DP Advanced Audio Distribution Profile
  • the Bluetooth headset can control telephone transactions on the terminal device, such as answering, hanging up, rejecting, voice dialing, etc.
  • A2DP Advanced Audio Distribution Profile
  • the Bluetooth headset can receive high quality audio and video data transmitted by the terminal device.
  • the existing Bluetooth connection method makes the Bluetooth headset consume more power.
  • aspects of the present application provide a connection processing method, apparatus, Bluetooth headset, wearable device, system, and storage medium to save power consumption of a Bluetooth headset.
  • connection request processing method which is applicable to a Bluetooth headset, and the method includes:
  • the A2DP connection request is processed in a manner compatible with the category of the terminal device to maintain a non-A2DP connection state with the terminal device.
  • the embodiment of the present application further provides a Bluetooth headset, including: a memory, a processor, and a communication component;
  • the memory for storing a computer program
  • the communication component is configured to receive an A2DP connection request and other connection request sent by the terminal device;
  • the processor is configured to execute the computer program for:
  • the communication component When the communication component receives the A2DP connection request sent by the terminal device, determining, according to the current state information of the Bluetooth headset, that the A2DP connection is not required to be maintained with the terminal device;
  • the A2DP connection request is processed in a manner compatible with the category of the terminal device to maintain a non-A2DP connection state with the terminal device.
  • the embodiment of the present application further provides a wearable device, including: a wearable device body and the above-mentioned Bluetooth headset; the Bluetooth headset is detachable from the wearable device body.
  • the wearable device is a smart wristband
  • the smart wristband includes a wristband
  • the Bluetooth headset is installed in the wristband
  • the Bluetooth headset can be separated from the wristband.
  • connection request processing apparatus including: a determining module, an identifying module, and a processing module;
  • the determining module is configured to: when receiving the A2DP connection request sent by the terminal device, determine, according to the current state information of the Bluetooth headset, that the Bluetooth headset does not need to maintain an A2DP connection with the terminal device;
  • the identifying module is configured to identify a category of the terminal device according to a situation that the other connection request sent by the terminal device is received before receiving the A2DP connection request;
  • the processing module is configured to process the A2DP connection request in a manner compatible with a category of the terminal device to maintain a non-A2DP connection state with the terminal device.
  • the embodiment of the present application further provides a connection request processing system, where the system includes the foregoing Bluetooth headset and a terminal device;
  • the terminal device is configured to send an A2DP connection request and other connection requests to the Bluetooth headset.
  • the Bluetooth headset is disposed on the wearable device and is detachable from the wearable device.
  • the embodiment of the present application further provides a computer readable storage medium storing a computer program, wherein the steps of the foregoing method are implemented when the computer program is executed by one or more processors.
  • the Bluetooth headset when receiving the A2DP connection request sent by the terminal device, determining whether the Bluetooth headset needs to maintain an A2DP connection with the terminal device; when determining that the Bluetooth headset does not need to maintain the A2DP connection with the terminal device, according to receiving the A2DP
  • the connection request is received before receiving the other connection request sent by the terminal device to identify the category of the terminal device; and the A2DP connection request is processed in a manner compatible with the category of the terminal device, so that the Bluetooth headset and the terminal device maintain the non-A2DP connection state.
  • the A2DP connection request can be processed in a manner compatible with the terminal device, thereby preventing the terminal device from displaying an error message or continuously reconnecting the status; and the Bluetooth headset can be maintained without the terminal device.
  • the A2DP is connected to a non-A2DP connection state, saving power consumption of the Bluetooth headset.
  • FIG. 1 is a schematic structural diagram of a connection request processing system according to an exemplary embodiment of the present application
  • connection request processing system is a schematic structural diagram of another connection request processing system according to an exemplary embodiment of the present application.
  • FIG. 2b is a schematic structural diagram of a wearable device (smart wristband) according to an embodiment of the present disclosure
  • FIG. 3 is a schematic flowchart of a connection request processing method according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a connection request processing apparatus according to another embodiment of the present disclosure.
  • FIG. 5 is a schematic structural diagram of a Bluetooth headset according to another embodiment of the present disclosure.
  • the present invention provides a solution to the technical problem that the Bluetooth headset consumes a large amount of power when the terminal device is connected to the Bluetooth headset.
  • the basic idea is: when it is determined that the Bluetooth headset does not need to maintain the A2DP connection with the terminal device. Identifying the category of the terminal device according to the situation of receiving other connection requests sent by the terminal device before receiving the A2DP connection request; and processing the A2DP connection request in a manner compatible with the category of the terminal device to enable the Bluetooth headset Maintain non-A2DP connection status with the terminal device.
  • the processing method of the A2DP connection request sent by the terminal device is processed in a manner compatible with the terminal device to prevent the terminal device from displaying an error message or a misoperation, and the Bluetooth headset can be omitted.
  • the device is in a non-A2DP connection state, which saves power consumption of the Bluetooth headset.
  • FIG. 1 is a schematic structural diagram of a connection request processing system according to an exemplary embodiment of the present application.
  • the system 10 includes a Bluetooth headset 10a and a terminal device 10b.
  • the implementation forms of the Bluetooth headset 10a and the terminal device 10b presented in FIG. 1 are merely exemplary and are not limited to the implementation forms of the two.
  • the Bluetooth headset 10a is communicably connected to the terminal device 10b via a Bluetooth method.
  • the terminal device 10b refers to a computer device used by the user to meet the needs of the user for communication, audio and video appreciation, and the like, for example, but not limited to: a smart phone, a tablet computer, an MP3, an MP4, and a phone watch. Wearable devices such as smart bracelets.
  • the terminal device 10b typically includes at least one processing unit and at least one memory. The number of processing units and memories depends on the configuration and type of the terminal device 10b.
  • the memory may include volatile, such as RAM, and may also include non-volatile, such as Read-Only Memory (ROM), flash memory, etc., or both.
  • an operating system (OS), one or more application software, such as application software corresponding to the Bluetooth headset 10a, and program data and the like may be stored in the memory.
  • the terminal device 10b also includes a basic configuration of a network card chip, an IO bus, an audio and video component, and the like.
  • the terminal device 10b may also include some peripheral devices, such as a keyboard, a mouse, a stylus, a printer, and the like. These peripheral devices are well known in the art and will not be described here.
  • the user turns on the Bluetooth function of the terminal device, and sends a Bluetooth connection request to the Bluetooth headset; the Bluetooth headset receives and responds to the Bluetooth connection request, and establishes a Bluetooth connection with the terminal device.
  • the Bluetooth connection process between the terminal device and the Bluetooth headset includes: a process of establishing an HFP connection based on the HFP protocol and a process of establishing an A2DP connection based on the A2DP protocol.
  • the user can use the Bluetooth headset to control the telephone transaction on the terminal device, such as answering, hanging up, rejecting, voice dialing, etc.; and based on the terminal device and the Bluetooth headset
  • the A2DP connection allows the user to listen to high-quality audio and video transmitted by the terminal device through the Bluetooth headset. Since the Bluetooth headset needs to maintain both the HFP connection and the A2DP connection, this makes the Bluetooth headset consume more power.
  • the user wants to know the telephone transaction of the terminal device 10b in real time, such as an incoming call, a short message, etc.
  • the Bluetooth headset 10a needs to monitor the telephone transaction of the terminal device 10b in real time, and the Bluetooth headset 10a and the terminal device 10b can The HFP connection is maintained at all times to prevent the user from listening to the telephone or the like of the terminal device 10b.
  • the user generally listens to the audio and video played by the terminal device 10b during the leisure time or some suitable period of time, and therefore, the A2DP connection between the Bluetooth headset 10a and the terminal device 10b does not need to be maintained for a long time.
  • the Bluetooth headset 10a identifies and distinguishes the Bluetooth connection request sent by the terminal device 10b, and when the audio and video played by the terminal device 10b needs to be listened to, the Bluetooth headset 10a and the terminal are maintained.
  • the terminal device 10b sends an A2DP connection request to the Bluetooth headset 10a
  • the Bluetooth headset 10a receives the A2DP connection request sent by the terminal device 10b, and according to the current state information of the Bluetooth headset 10a when receiving the A2DP connection request, It is determined whether it is necessary to maintain an A2DP connection with the terminal device 10b.
  • the non-A2DP connection can be maintained with the terminal device 10b in a certain manner.
  • the Bluetooth headset can reject the A2DP connection request sent by the terminal device, thereby maintaining a non-A2DP connection state with the terminal device 10b.
  • the Bluetooth headset 10a of the present embodiment can support multiple types of terminal devices.
  • the category of the terminal device is classified according to the operating system it adopts.
  • the terminal device adopts an iPhone operating system (IOS), which is called an IOS device; for example, the terminal device adopts an Android operating system, which is called an Android device; for example, the terminal device adopts a Windows operating system. It is called a Windows device.
  • IOS iPhone operating system
  • Android Android operating system
  • Windows operating system a terminal device that uses a non-IOS operating system
  • a non-IOS device is uniformly defined as a non-IOS device.
  • the inventors of the present application have found that different types of terminal devices may react differently to Bluetooth headsets rejecting A2DP connection requests. If the Bluetooth headset 10a sends an A2DP connection request to the IOS device and the non-IOS device to directly reject the A2DP connection request, then for the IOS device, the IOS device will display "The connection is unsuccessful, please be sure that XX has The error message in the communication range is opened, where "XX" can be the model number, IP address, etc. of the Bluetooth headset 10a.
  • the Bluetooth headset 10a further receives other connections sent by the terminal device 10b according to the A2DP connection request.
  • the category of the terminal device 10b is identified, and the A2DP connection request is processed in a manner compatible with the category of the terminal device 10b, thereby maintaining the non-A2DP connection state with the terminal device 10b. In this way, it is possible to avoid processing the A2DP connection request in a manner that is not adapted to the category of the terminal device, and the terminal device displays an error message or a misoperation.
  • the Bluetooth headset when determining that the A2DP connection is not required to be maintained with the terminal device, the Bluetooth headset receives another connection request sent by the terminal device before receiving the A2DP connection request sent by the terminal device, The category of the terminal device is identified, and the A2DP connection request is processed in a manner compatible with the category of the terminal device to maintain a non-A2DP connection state with the terminal device.
  • the Bluetooth headset in the connection request processing system is in a non-A2DP connection state when there is no need to maintain an A2DP connection with the terminal device, thereby saving power consumption of the Bluetooth headset.
  • the Bluetooth headset 10a can determine whether an A2DP connection with the terminal device 10b needs to be established based on its current location state and/or state of charge.
  • a sensor can be provided on the Bluetooth headset 10a that can capture the current location information of the Bluetooth headset 10a.
  • the sensor may be a position sensor such as a human ear sensor, an infrared sensor or the like. Determining whether the Bluetooth headset 10a is out of the ear of the corresponding user according to the location data collected by the location sensor; in order to prevent the Bluetooth headset 10a from needing to maintain the A2DP connection with the terminal device 10b due to the situation in which the Bluetooth headset 10a slips off the user's ear When it is determined that the Bluetooth headset 10a has been detached from the ear of the corresponding user, it is further determined whether the length of time that the Bluetooth headset 10a is detached from the user's ear exceeds a preset duration threshold.
  • the preset duration threshold is defined as A preset duration threshold, when the duration of the Bluetooth headset 10a is off the user's ear exceeds the first preset duration threshold, indicating that the user does not need to use the Bluetooth headset to listen to the audio and video transmitted by the terminal device, and the A2DP connection is not necessary, then the Bluetooth is determined.
  • the earphone 10a does not need to maintain an A2DP connection with the terminal device 10b.
  • it is determined that the Bluetooth headset 10a is not detached from the ear of the corresponding user it is determined that the Bluetooth headset 10a needs to maintain an A2DP connection with the terminal device 10b, so that the user can listen to the audio and video transmitted by the terminal device through the Bluetooth headset.
  • the Bluetooth headset 10a can be attached to a wearable device that includes a Bluetooth headset 10a and a wearable device body.
  • the wearable device can be a smart bracelet, a smart watch, or the like.
  • the Bluetooth headset 10a is mounted on the wearable device body, and the Bluetooth headset 10a can be separated from the wearable device body.
  • the Bluetooth headset 10a When the user mounts the Bluetooth headset 10a on the wearable device body, it is indicated that the user does not need to receive the audio and video transmitted by the terminal device 10b by using the Bluetooth headset 10a. Based on this, the current location information of the Bluetooth headset 10a can be acquired using the sensor on the Bluetooth headset 10a.
  • the sensor may be a position sensor such as a Hall sensor or the like.
  • the Bluetooth headset 10a Based on the relative position data of the Bluetooth headset 10a and the wearable device body collected by the position sensor, it is determined whether the Bluetooth headset 10a is out of the attached wearable device. When it is determined that the Bluetooth headset 10a is not detached from the attached wearable device, that is, mounted on the wearable device body, it is determined that the Bluetooth headset 10a does not need to maintain an A2DP connection with the terminal device 10b. However, when it is determined that the Bluetooth headset 10a is detached from the attached wearable device, it may be impossible to determine that the Bluetooth headset 10a needs to maintain an A2DP connection with the terminal device 10b, and further judgment may be made according to other conditions. For example, the judgment is made according to the current state of charge of the Bluetooth headset 10a.
  • the above position sensor may also be disposed on the wearable device body of the wearable device.
  • the Bluetooth headset 10a is attached to the wearable device, whether the Bluetooth headset 10a is separated from the user's ear and the Bluetooth headset 10b is removed from the attached wearable device according to the first sensor and the second sensor on the Bluetooth headset. It is determined whether it needs to maintain an A2DP connection with the terminal device 10b.
  • the first sensor may be a human ear sensor, an infrared sensor, or the like, and the second sensor may be a Hall sensor or the like.
  • the Bluetooth headset 10a determines that the length of time from the user's ear exceeds the first preset duration threshold according to the location information collected by the first sensor, it may be determined that the Bluetooth headset 10a does not need to maintain an A2DP connection with the terminal device 10b, and may The location information collected by the second sensor determines whether the Bluetooth headset 10a is out of the attached wearable device for further determination. That is, when the duration of the Bluetooth headset 10a from the user's ear exceeds the first preset duration threshold, and the Bluetooth headset 10a does not leave the attached wearable device, it is determined that the Bluetooth headset 10a does not need to maintain an A2DP connection with the terminal device 10b.
  • the Bluetooth headset 10a determines that the length of time from the user's ear exceeds the first preset duration threshold according to the location information collected by the first sensor, it may be determined that the Bluetooth headset 10a does not need to maintain an A2DP connection with the terminal device 10b, and may The location information collected by the second sensor determines whether the Bluetooth headset 10a is out of the attached
  • the Bluetooth headset 10a can have a built-in rechargeable battery, and in order to maintain the battery life of the Bluetooth headset 10a, it is necessary to charge the Bluetooth headset 10a in time.
  • the Bluetooth headset 10a when the Bluetooth headset 10a is in a charging state, the user generally does not receive the audio and video transmitted by the terminal device 10b through the Bluetooth headset 10a. Based on this, it can be detected whether the external power port of the Bluetooth headset 10a has an external power source. When it is detected that there is an external power source, it is determined that the Bluetooth headset 10a does not need to establish an A2DP connection with the terminal device 10b.
  • the Bluetooth headset 10a when it is determined that the external power source of the Bluetooth headset 10a does not have an external power source, it may be determined that the Bluetooth headset 10a needs to maintain an A2DP connection with the terminal device 10b, and may further determine according to the current location state of the Bluetooth headset 10a. Whether an A2DP connection needs to be established with the terminal device 10b.
  • the external power port of the Bluetooth headset 10a may be, but not limited to, a USB interface.
  • the user can turn on the Bluetooth function in the setting bar of the terminal device 10b, and the terminal device 10b sends a Bluetooth connection request to the Bluetooth headset 10a in response to the user's operation to turn on the Bluetooth function.
  • the terminal device 10b For the terminal device 10b, the HFP connection request and the A2DP connection request are sequentially transmitted to the Bluetooth headset 10a in a serial communication manner in accordance with the order of adaptation with the device type. The order in which the different types of terminal devices transmit the HFP connection request and the A2DP connection request to the Bluetooth headset 10a is different.
  • an IOS device when a Bluetooth connection request is sent to the Bluetooth headset 10a, an A2DP connection request is sent first, and then an HFP connection request is sent; for other non-IOS devices such as Android, an HFP connection request is sent first, and then A2DP is sent. Connection request.
  • the Bluetooth headset 10a can determine whether the terminal device 10b is an IOS device according to whether or not the HFP connection request is received before receiving the A2DP connection request. If the Bluetooth headset 10a does not receive the HFP connection request sent by the terminal device 10b before receiving the A2DP connection request sent by the terminal device 10b, it is determined that the terminal device 10b is an IOS device; if the Bluetooth headset 10a receives the A2DP sent by the terminal device 10b Upon receiving the HFP connection request sent by the terminal device 10b before the connection request, it is determined that the terminal device 10b is a non-IOS device.
  • an application (App) corresponding to the Bluetooth headset 10a is installed on the terminal device 10b.
  • the Bluetooth headset 10a needs to perform data communication with the corresponding App
  • the user opens the corresponding App
  • the terminal device 10b transmits a connection request under the corresponding data communication protocol to the Bluetooth headset 10a in response to the user's operation of opening the App.
  • the Bluetooth headset 10a receives the connection request under the data communication protocol, thereby establishing a data communication connection with the terminal device 10b, and transmitting the corresponding data to the App on the terminal device through the data communication connection.
  • the unique iPod Accessory Protocol IAP
  • IAP unique iPod Accessory Protocol
  • the terminal device 10b is an IOS device by determining whether the IAP connection request sent by the terminal device 10b is received before the Bluetooth headset 10a receives the A2DP connection request sent by the terminal device 10b. If the Bluetooth headset 10a receives the IAP connection request sent by the terminal device 10b before receiving the A2DP connection request sent by the terminal device 10b, it determines that the terminal device 10b is an IOS device. Optionally, if the Bluetooth headset 10a does not receive the foregoing IAP connection request before receiving the A2DP connection request, the category of the terminal device 10b may be further performed according to the sequence in which the Bluetooth headset 10a receives the A2DP connection request and the HFP connection request. Judge.
  • the Bluetooth headset 10a Based on the category of the terminal device 10b, the Bluetooth headset 10a processes the A2DP connection request sent by the terminal device 10b in a manner compatible with the category of the terminal device 10b, thereby maintaining a non-A2DP connection state with the terminal device 10b to save the Bluetooth headset 10a. Power consumption.
  • the Bluetooth headset 10a directly rejects the connection request sent by the terminal device 10b, and can maintain a non-A2DP connection state with the terminal device 10b.
  • the Bluetooth headset 10a first establishes an A2DP connection with the terminal device 10b in response to the A2DP connection request sent by the terminal device 10b; and disconnects the terminal when the duration of the A2DP connection is longer than a preset duration threshold.
  • the A2DP connection of the device 10b in turn, maintains a non-A2DP connection state with the terminal device 10b.
  • the preset duration threshold is defined as a second preset duration threshold.
  • the Bluetooth headset 10a processes the A2DP connection request sent by the terminal device 10b in two different ways, because the Bluetooth headset 10a sends A2DP connection requests to the IOS device and the non-IOS device.
  • the error message indicating "The connection is unsuccessful, please be sure that XX is open within the communication range" is displayed on the IOS device, where "XX" can be The model number, IP address, etc. of the Bluetooth headset 10a.
  • the non-IOS device will continuously send to the Bluetooth.
  • the earphone 10a sends an A2DP connection request, causing the Bluetooth headset 10a to continuously perform A2DP connection with the non-IOS device and continuously disconnect, which affects the service life of the Bluetooth headset 10a and the terminal device 10b.
  • the Bluetooth headset 10a processes the A2DP connection request in a manner compatible with the type of the terminal device 10b to maintain the non-A2DP connection state with the terminal device 10b, thereby avoiding the occurrence of the above two situations and enhancing the user experience, and The service life of the Bluetooth headset 10a and the terminal device 10b is extended.
  • the second preset duration threshold may be set according to the configuration of the terminal device 10b, and the size of the duration threshold is not limited, as long as the Bluetooth headset 10a can be disconnected from the terminal device 10b, the terminal device is 10b will not continue to send A2DP connection requests.
  • the Bluetooth headset 10a can also monitor its own state information, and determine, according to the monitored state information, whether it is necessary to continue to maintain the A2DP connection with the terminal device 10b; When the Bluetooth headset 10a determines that it is not necessary to continue to maintain the A2DP connection with the terminal device 10b, regardless of the category device of the terminal device 10b, the A2DP connection is directly disconnected, saving the power of the Bluetooth headset and not affecting the terminal device 10b. .
  • the Bluetooth headset may be a stand-alone Bluetooth headset, or may be dependent on a wearable device, such as a smart bracelet, an AR or VR headset display device, and the like.
  • FIG. 2 is a schematic structural diagram of the connection request processing system 20.
  • the system 20 includes a wearable device 20a and a terminal device 20b; and the wearable device 20a is a Bluetooth headset 20a1 and a wearable device body 20a2.
  • the implementation forms of the wearable device 20a, the Bluetooth headset 20a1, the wearable device body 20a2, and the terminal device 10b presented in FIG. 2a are merely exemplary descriptions, and the implementation forms of the two are not limited.
  • the terminal device 20b may perform a Bluetooth connection with the Bluetooth headset 20a1 on the wearable device 20a; or may use a wireless or wired connection with the wearable device 20a.
  • the wearable device 20a can communicate with the terminal device 20b through a mobile network.
  • the network format of the mobile network can be 2G (GSM), 2.5G (GPRS), 3G (WCDMA, TD-SCDMA, CDMA2000, UTMS). ), 4G (LTE), 4G+ (LTE+), WiMax, and the like.
  • the wearable device 20a can also be communicably connected to the terminal device 20b by means of Bluetooth, WiFi, infrared, or the like. It is worth noting that the wearable device 20a may not be connected to the terminal device 20b. Whether or not it is connected to the terminal device 20b depends on the function and needs of the wearable device 20a.
  • the Bluetooth headset 20a1 when the terminal device 20b sends an A2DP connection request to the Bluetooth headset 20a1, the Bluetooth headset 20a1 receives the A2DP connection request sent by the terminal device 20b, and according to the current status of the Bluetooth headset 20a1 when receiving the A2DP connection request. The information determines whether it needs to maintain an A2DP connection with the terminal device 20b.
  • the Bluetooth headset 10a may further identify the category of the terminal device 20b according to the situation of receiving other connection requests sent by the terminal device 20b before receiving the A2DP connection request, and adopting the terminal device
  • the category of 20b is adapted to handle the above A2DP connection request, thereby maintaining its own non-A2DP connection state with the terminal device 20b. In this way, it is possible to avoid processing the A2DP connection request in a manner that is not adapted to the category of the terminal device, and the terminal device displays an error message or a misoperation.
  • the wearable device 20a can be a smart wristband.
  • FIG. 2b a schematic structural diagram of a smart wristband according to an embodiment of the present application is shown.
  • the smart bracelet 20c includes a wristband 20c1 and a Bluetooth headset 20c2, wherein the Bluetooth headset 20c2 is mounted in the wristband 20c1, and the Bluetooth headset 20c2 is separated from the wristband 20c1, that is, the Bluetooth headset 20c2 is detachable.
  • the Bluetooth headset when determining that the A2DP connection is not required to be maintained with the terminal device, the Bluetooth headset receives another connection request sent by the terminal device before receiving the A2DP connection request sent by the terminal device, The category of the terminal device is identified, and the A2DP connection request is processed in a manner compatible with the category of the terminal device to maintain a non-A2DP connection state with the terminal device.
  • the Bluetooth headset in the connection request processing system is in a non-A2DP connection state when it is not required to maintain an A2DP connection with the terminal device, thereby saving power consumption of the Bluetooth headset, that is, saving power consumption of the wearable device.
  • the present application also provides some method embodiments, which describe the processing procedure of the A2DP connection request sent by the terminal device from the perspective of the Bluetooth headset, respectively.
  • FIG. 3 is a schematic flowchart of a connection request processing method according to an embodiment of the present application. As shown in Figure 3, it includes:
  • the Bluetooth headset when receiving the A2DP connection request sent by the terminal device, the Bluetooth headset can determine whether it needs to be maintained with the terminal device according to the current state of the Bluetooth headset. A2DP connection; when it is determined that the terminal device does not need to maintain the A2DP connection, the A2DP connection request is processed, and the non-A2DP connection state is maintained with the terminal device.
  • the terminal device may display an error message or appear. Continue to reconnect and other failures.
  • the category of the terminal device is further identified according to the case of receiving other connection requests sent by the terminal device before receiving the A2DP connection request.
  • the A2DP connection request sent by the terminal device is processed in a manner compatible with the category of the terminal device, so that the Bluetooth headset and the terminal device maintain the non-A2DP connection state. This not only saves the power consumption of the Bluetooth headset, but also prevents the terminal device from displaying an error message or continuously performing A2DP connection.
  • the Bluetooth headset and the terminal device need to maintain an HFP connection to listen to the telephone service of the corresponding terminal device.
  • the Bluetooth headset when the user does not need to use the Bluetooth headset to receive audio and video transmitted by the terminal device, the Bluetooth headset does not need to maintain an A2DP connection with the terminal device. At this point, the user generally no longer wears the Bluetooth headset, but places the Bluetooth headset in certain locations.
  • the Bluetooth headset when the Bluetooth headset is charging, the user generally does not receive the audio and video transmitted by the terminal device. At this time, the Bluetooth headset does not need to maintain an A2DP connection with the terminal device.
  • an optional implementation manner of step 301 is: determining that the A2DP connection is not required to be maintained with the terminal device according to the current location state and/or the charging state of the Bluetooth headset.
  • the senor may be configured to collect the current location information of the Bluetooth headset on the Bluetooth headset.
  • the sensor may be a location sensor, such as a human ear. Inductive sensors, infrared sensors, etc.
  • the Bluetooth headset Determining whether the Bluetooth headset is out of the ear of the corresponding user according to the location data collected by the location sensor; in order to prevent the Bluetooth headset from being connected to the terminal device to cause A2DP connection due to the Bluetooth headset slipping off the user's ear, When it is determined that the Bluetooth headset has been detached from the ear of the corresponding user, it is further determined whether the length of the Bluetooth headset is out of the user's ear exceeds a preset duration threshold.
  • the preset duration threshold is defined as a first preset duration threshold. When the duration of the Bluetooth headset from the user's ear exceeds the first preset duration threshold, it is determined that there is no need to maintain an A2DP connection with the terminal device.
  • the Bluetooth headset when it is determined that the Bluetooth headset does not leave the ear of the corresponding user, it is determined that the Bluetooth headset needs to maintain an A2DP connection with the terminal device, so that the user can listen to the audio and video transmitted by the terminal device through the Bluetooth headset.
  • the Bluetooth headset can be attached to the wearable device, and the wearable device includes a Bluetooth headset and a wearable device body.
  • the wearable device can be a smart bracelet, a smart watch, etc.
  • the Bluetooth headset is mounted on the wearable device body, and the Bluetooth headset can be separated from the wearable device body.
  • the sensor can be a position sensor, such as a Hall sensor.
  • the Bluetooth headset According to the relative position data of the Bluetooth headset and the wearable device body collected by the position sensor, it is determined whether the Bluetooth headset is out of the attached wearable device. When it is determined that the Bluetooth headset is not disconnected from the attached wearable device, that is, mounted on the wearable device body, it is not necessary to maintain an A2DP connection with the terminal device. However, when it is determined that the Bluetooth headset is out of the attached wearable device, it may not be determined that the Bluetooth headset does not need to maintain an A2DP connection with the terminal device, and further judgment may be made according to other conditions. For example, judging based on the current state of charge of the Bluetooth headset.
  • the above position sensor can be disposed on the main body of the wearable device.
  • the Bluetooth headset in the case that the Bluetooth headset is attached to the wearable device, whether the Bluetooth headset is separated from the user's ear and the Bluetooth headset is separated from the attached wearable device according to the first sensor and the second sensor on the Bluetooth headset to determine whether it is An A2DP connection needs to be maintained with the terminal device.
  • the first sensor may be a human ear sensor, an infrared sensor, or the like
  • the second sensor may be a Hall sensor or the like.
  • the Bluetooth headset 10a determines that the length of time from the user's ear exceeds the first preset duration threshold according to the location information collected by the first sensor, it may be determined that the Bluetooth headset does not need to maintain an A2DP connection with the terminal device, which may be according to the second.
  • the location information collected by the sensor determines whether the Bluetooth headset is out of the attached wearable device for further determination. That is, when the duration of the Bluetooth headset from the user's ear exceeds the first preset duration threshold, and the Bluetooth headset does not leave the attached wearable device, it is determined that the Bluetooth headset does not need to maintain an A2DP connection with the terminal device.
  • the Bluetooth headset does not need to maintain an A2DP connection with the terminal device.
  • the external power port of the Bluetooth headset may be, but not limited to, a USB interface.
  • the user can enable the Bluetooth function in the setting bar of the terminal device, and the terminal device sends a Bluetooth connection request to the Bluetooth headset in response to the user's operation of turning on the Bluetooth function.
  • the HFP connection request and the A2DP connection request are sequentially sent to the Bluetooth headset by serial communication in the order of adaptation with the device type.
  • the order in which different types of terminal devices send HFP connection requests and A2DP connection requests to Bluetooth headsets is different. For example, for an IOS device, when a Bluetooth connection request is sent to a Bluetooth headset, an A2DP connection request is sent first, and then an HFP connection request is sent; for other non-IOS devices such as Android, a HFP connection request is sent first, and then Send an A2DP connection request.
  • an optional implementation manner of step 302 is to determine whether the terminal device is an IOS device according to whether an HFP connection request is received before receiving the A2DP connection request. If the HFP connection request sent by the terminal device is not received before receiving the A2DP connection request sent by the terminal device, determining that the terminal device is an IOS device; if receiving the HFP sent by the terminal device before receiving the A2DP connection request sent by the terminal device The connection request determines that the terminal device is a non-IOS device.
  • an App corresponding to the Bluetooth headset can be installed on the terminal device.
  • the Bluetooth headset needs to perform data communication with the corresponding App
  • the user opens the corresponding App
  • the terminal device sends a connection request under the corresponding data communication protocol to the Bluetooth headset in response to the operation of the user opening the App.
  • the Bluetooth headset receives the connection request under the data communication protocol, thereby establishing a data communication connection with the terminal device, and transmitting the corresponding data to the App on the terminal device through the data communication connection Bluetooth headset.
  • the unique IAP protocol can be used to communicate with the Bluetooth headset.
  • step 302 determines whether the terminal device is an IOS device by determining whether an IAP connection request sent by the terminal device is received before receiving the A2DP connection request sent by the terminal device. If the IAP connection request sent by the terminal device is received before receiving the A2DP connection request sent by the terminal device, it is determined that the terminal device is an IOS device. Optionally, if the foregoing IAP connection request is not received before receiving the A2DP connection request, the type of the terminal device may be further determined according to the sequence in which the Bluetooth headset receives the A2DP connection request and the HFP connection request, and the determining process is performed. See the related description above, and details are not described here.
  • the A2DP connection request sent by the terminal device is processed in a manner compatible with the category of the terminal device, thereby maintaining a non-A2DP connection state with the terminal device, so as to save power consumption of the Bluetooth headset.
  • the terminal device When the terminal device is a non-IOS device, the connection request sent by the terminal device is directly rejected, and the non-A2DP connection state can be maintained with the terminal device 10b.
  • the terminal device When the terminal device is an IOS device, the A2DP connection is initiated in response to the A2DP connection request sent by the terminal device, and the A2DP connection is established with the terminal device when the duration of the A2DP connection is longer than the preset duration threshold. Maintain non-A2DP connection status with the terminal device.
  • the preset duration threshold may be set according to the configuration of the terminal device, and the duration threshold is not limited. As long as the connection with the terminal device is disconnected, the terminal device does not continuously send the A2DP connection request. Just fine. For the reason for processing the A2DP connection request in the foregoing manner, refer to the related description in the system embodiment corresponding to FIG. 1 above, and details are not described herein again.
  • the Bluetooth headset can also monitor its own state information, and according to the monitored state information, determine whether it is necessary to continue to maintain the A2DP connection with the terminal device; when the Bluetooth headset determines When the A2DP connection is not required to be maintained with the terminal device, the A2DP connection is directly disconnected regardless of the category device of the terminal device, which saves the power of the Bluetooth headset and does not affect the terminal device.
  • FIG. 4 is a schematic structural diagram of a connection request processing apparatus according to another embodiment of the present application.
  • the connection request processing device can be implemented as a function module in the Bluetooth headset, or can be connected to the Bluetooth headset independently of the Bluetooth headset, and is responsible for processing the A2DP connection request sent by the terminal device to the Bluetooth headset.
  • the connection request processing device 40 includes a determination module 41, an identification module 42, and a processing module 43. among them,
  • the determining module 41 is configured to determine, according to the current state information of the Bluetooth headset, that the Bluetooth headset does not need to maintain an A2DP connection with the terminal device when receiving the A2DP connection request sent by the terminal device.
  • the identification module 42 identifies the category of the terminal device based on the case of receiving other connection requests sent by the terminal device before receiving the A2DP connection request.
  • the processing module 43 processes the A2DP connection request in a manner compatible with the category of the terminal device to maintain a non-A2DP connection state with the terminal device.
  • the determining module 41 determines that the Bluetooth headset does not need to maintain an A2DP connection with the terminal device according to the current state information of the Bluetooth headset, and is specifically configured to: according to the current location state and/or the charging state of the Bluetooth headset, Make sure the Bluetooth headset does not need to maintain an A2DP connection with the terminal device.
  • the determining module 41 determines that the Bluetooth headset is not detached from the corresponding user's ear according to the location data collected by the location sensor on the Bluetooth headset when determining that the A2DP connection is not required to be maintained with the terminal device according to the current state of the Bluetooth headset. Determining that the Bluetooth headset does not need to maintain an A2DP connection with the terminal device when the duration of the Bluetooth headset is off the ear of the user exceeds the first preset duration threshold; or the location data collected according to the location sensor on the Bluetooth headset Determine whether the Bluetooth headset is out of the wearable device attached to the Bluetooth headset. When the judgment result is no, it is determined that the Bluetooth headset does not need to maintain an A2DP connection with the terminal device.
  • the determining module 41 is specifically configured to: determine whether an external power source of the wearable device has an external power source, and when the determination result is , to determine that the Bluetooth headset does not need to establish an A2DP connection with the terminal device.
  • the identifying module 42 is configured to: when receiving the category of the terminal device according to the other connection request sent by the terminal device before the A2DP connection request, specifically: if the A2DP sent by the terminal device is received The HFP connection request sent by the terminal device is not received before the connection request, and the terminal device is determined to be an IOS device; if the IAP connection request sent by the terminal device is received before receiving the A2DP connection request sent by the terminal device, it is determined that the terminal device is an IOS device; If the HFP connection request sent by the terminal device is received before receiving the A2DP connection request sent by the terminal device, it is determined that the terminal device is a non-IOS device.
  • the processing module 43 processes the A2DP connection request in a manner compatible with the category of the terminal device to maintain the non-A2DP connection state with the terminal device, specifically for: when the terminal device is a non-IOS The device directly rejects the A2DP connection request to maintain the non-A2DP connection status with the terminal device; or when the terminal device is the IOS device, responds to the A2DP connection request to establish an A2DP connection with the terminal device, and the duration of the A2DP connection exceeds the pre- When the duration threshold is set, the A2DP connection with the terminal device is disconnected to maintain the non-A2DP connection state with the terminal device.
  • the connection request processing apparatus recognizes that the Bluetooth headset does not need to maintain an A2DP connection with the terminal device, and receives another connection request sent by the terminal device before receiving the A2DP connection request sent by the terminal device.
  • the category of the terminal device, and the A2DP connection request is processed in a manner compatible with the category of the terminal device, so that the Bluetooth headset and the terminal device maintain a non-A2DP connection state. This can save power consumption of the Bluetooth headset.
  • FIG. 5 is a schematic structural diagram of a Bluetooth headset according to another embodiment of the present disclosure. As shown in FIG. 5, the memory 50a, the communication component 50b, and the processor 50c are included. among them,
  • the memory 50a is for storing a computer program.
  • the communication component 50b is configured to receive an A2DP connection request and other connection request sent by the terminal device.
  • the processor 50c is configured to execute a computer program stored in the memory 50a, when the communication component 50b receives the A2DP connection request sent by the terminal device, and determines that the A2DP connection is not required to be maintained with the terminal device according to the current state information of the Bluetooth headset.
  • the type of the terminal device is identified according to the case where the other connection request sent by the terminal device is received before the A2DP connection request; the A2DP connection request is processed in a manner compatible with the category of the terminal device to maintain the non-A2DP connection state with the terminal device.
  • the Bluetooth headset can also include a power component 50d.
  • the power supply assembly 50d provides power to the Bluetooth headset.
  • the power component 50d can include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power for the devices to which the power components belong.
  • power supply assembly 50d includes a rechargeable battery.
  • the processor 50c is specifically configured to: determine, according to the current location state of the Bluetooth headset and/or the charging state of the power component 50d, Maintain an A2DP connection with the terminal device.
  • the processor 50c determines that the Bluetooth headset is off the ear of the corresponding user according to the location data collected by the location sensor on the Bluetooth headset when determining that the A2DP connection is not required to be maintained with the terminal device according to the current location state of the Bluetooth headset.
  • the duration of the Bluetooth headset from the ear of the user exceeds the first preset duration threshold, it is determined that there is no need to maintain an A2DP connection with the terminal device; or according to the location data collected by the location sensor on the Bluetooth headset, Whether the Bluetooth headset is out of the wearable device attached to the Bluetooth headset, and when the judgment result is no, it is determined that the A2DP connection is not required to be maintained with the terminal device.
  • the processor 50c is configured to determine whether the external power port in the power component 50d of the Bluetooth headset has an external connection when it is determined that the A2DP connection is not required to be maintained with the terminal device according to the current charging state of the power component 50d of the Bluetooth headset. The power supply exists. When the judgment result is present, it is determined that it is not necessary to establish an A2DP connection with the terminal device.
  • the processor 50c when the processor 50c identifies the category of the terminal device according to the other connection request sent by the terminal device before the A2DP connection request, the processor 50c is specifically configured to: if the communication component 50b is receiving the terminal device The received A2DP connection request does not receive the HFP connection request sent by the terminal device, and determines that the terminal device is an IOS device; if the communication component 50b receives the IAP connection request sent by the terminal device before receiving the A2DP connection request sent by the terminal device, determining The terminal device is an IOS device; if the communication component 50b receives the HFP connection request sent by the terminal device before receiving the A2DP connection request sent by the terminal device, it is determined that the terminal device is a non-IOS device.
  • the processor 50c processes the A2DP connection request in a manner compatible with the category of the terminal device to maintain the non-A2DP connection status with the terminal device, specifically, when the terminal device is a non-IOS
  • the device directly rejects the A2DP connection request to maintain the non-A2DP connection status with the terminal device; or when the terminal device is the IOS device, responds to the A2DP connection request to establish an A2DP connection with the terminal device, and the duration of the A2DP connection exceeds the pre- When the duration threshold is set, the A2DP connection with the terminal device is disconnected to maintain the non-A2DP connection state with the terminal device.
  • the Bluetooth headset may further include other components such as an audio component 50e. Only some of the components are schematically illustrated in FIG. 5, and it is not meant that the terminal device includes only the components shown in FIG.
  • the Bluetooth headset determines whether the Bluetooth headset needs to maintain an A2DP connection with the terminal device when receiving the A2DP connection request sent by the terminal device; when it is determined that the A2DP connection is not required to be maintained with the terminal device, the terminal device is received according to the terminal device. Before receiving the A2DP connection request, receiving the other connection request sent by the terminal device, identifying the category of the terminal device, and processing the A2DP connection request in a manner compatible with the category of the terminal device, so as to keep the terminal device non-terminally A2DP connection status.
  • the Bluetooth headset is in a non-A2DP connection state when it does not need to maintain an A2DP connection with the terminal device, thereby saving power consumption of the Bluetooth headset.
  • the Bluetooth headset provided by the embodiment of the present application may exist separately or may be attached to other devices, such as a wearable device.
  • the wearable device may be, but not limited to, a smart wristband, a smart watch, an AR, or VR headset display device, etc.
  • the embodiment of the present application further provides a wearable device.
  • the structure of the wearable device can be as shown in FIG. 2b, including the wearable device body and the Bluetooth headset, and the Bluetooth headset can be separated from the wearable device body.
  • the wearable device body is a wristband 20c2 and the Bluetooth headset 20c1 is mounted within the wristband 20c2.
  • the internal structure of the Bluetooth headset 20c1 refer to the structure diagram of the Bluetooth headset shown in FIG. 5, and details are not described herein again.
  • the Bluetooth headset in the wearable device provided by the embodiment of the present application can be used as a separate component or integrated with other parts of the wearable device as a component, for example, integrated in a smart wristband or a dial portion of a smart watch.
  • the wearable device may further include other components such as a display, an audio component, and the like, but is not limited thereto. among them,
  • the display may include a screen whose screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user.
  • the touch panel includes one or more touch sensors to sense touches, slides, and gestures on the touch panel. The touch sensor may sense not only the boundary of the touch or sliding action, but also the duration and pressure associated with the touch or slide operation.
  • An audio component configured to output and/or input an audio signal.
  • the audio component includes a microphone (MIC) that is configured to receive an external audio signal when the device to which the audio component belongs is in an operational mode, such as a call mode, a recording mode, and a voice recognition mode.
  • the received audio signal can be further stored in a memory or transmitted via a communication component.
  • the audio component further includes a speaker for outputting an audio signal.
  • the Bluetooth headset when determining that the A2DP connection is not required to be maintained with the terminal device, the Bluetooth headset recognizes that the other connection request sent by the terminal device is received before receiving the A2DP connection request sent by the terminal device.
  • the category of the terminal device, and the A2DP connection request is processed in a manner compatible with the category of the terminal device to maintain a non-A2DP connection state with the terminal device.
  • the Bluetooth headset in the wearable device is in a non-A2DP connection state when it is not required to maintain an A2DP connection with the terminal device, thereby saving power consumption of the Bluetooth headset, that is, saving power consumption of the wearable device.
  • the embodiment of the present application further provides a computer readable storage medium storing a computer program, which when executed, can implement various steps or operations that can be performed by a Bluetooth headset in the foregoing method embodiment.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • processors CPUs
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • the memory may include non-persistent memory, random access memory (RAM), and/or non-volatile memory in a computer readable medium, such as read only memory (ROM) or flash memory.
  • RAM random access memory
  • ROM read only memory
  • Memory is an example of a computer readable medium.
  • Computer readable media includes both permanent and non-persistent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • the information can be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory. (ROM), electrically erasable programmable read only memory (EEPROM), flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, Magnetic tape cartridges, magnetic tape storage or other magnetic storage devices or any other non-transportable media can be used to store information that can be accessed by a computing device.
  • computer readable media does not include temporary storage of computer readable media, such as modulated data signals and carrier waves.

Abstract

本申请实施例提供一种连接请求处理方法、蓝牙耳机、穿戴设备、系统及存储介质。在本申请实施例中，在接收到终端设备发送的A2DP连接请求时，确定蓝牙耳机是否需要与终端设备保持A2DP连接；当不需要时，根据在接收到A2DP连接请求之前接收终端设备发送的其它连接请求的情况，来识别终端设备的类别；并采用与终端设备的类别相适配的方式处理A2DP连接请求，以使蓝牙耳机与终端设备保持非A2DP连接状态。本申请实施例采用与终端设备相适配的方式处理A2DP连接请求，可避免终端设备显示错误提示信息或不断回连的状况；而且可使蓝牙耳机在无需与终端设备保持A2DP连接时处于非A2DP连接状态，节省蓝牙耳机的功耗。

Description

连接请求处理方法、装置、蓝牙耳机、穿戴设备、系统及存储介质
交叉引用
本申请引用于2018年5月17日递交的名称为“连接处理方法、蓝牙耳机、穿戴设备及系统”的第201810474442.8号中国专利申请，其通过引用被全部并入本申请。
技术领域
本申请涉及无线通信技术领域，尤其涉及一种连接请求处理方法、装置、蓝牙耳机、穿戴设备、系统及存储介质。
背景技术
随着蓝牙技术的发展，蓝牙设备逐渐进入人们的日常生活，给人们的生活带来极大的便利。尤其是蓝牙耳机，将蓝牙技术应用在免持耳机上，让使用者可以免除恼人电线的牵绊，自在地以各种方式轻松通话或聆听音乐。
在现有技术中，终端设备通过免提模型(Hands-free Profile，HFP)协议和蓝牙音频传输模型(Advanced Audio Distribution Profile，A2DP)协议分别与蓝牙耳机进行蓝牙连接。其中，基于HFP连接，蓝牙耳机可以控制终端设备上的电话事务，如接听、挂断、拒接、语音拨号等；基于A2DP连接，蓝牙耳机可以接收终端设备传输的高品质的音视频数据。但是，现有这种蓝牙连接方式使得蓝牙耳机功耗较大。
发明内容
本申请的多个方面提供一种连接处理方法、装置、蓝牙耳机、穿戴设备、系统及存储介质，用以节省蓝牙耳机功耗。
本申请实施例提供连接请求处理方法，适用于蓝牙耳机，该方法包括：
在接收到终端设备发送的A2DP连接请求时，根据所述蓝牙耳机当前的状态信息，确定不需要与所述终端设备保持A2DP连接；
根据在所述A2DP连接请求之前接收所述终端设备发送的其它连接请求的情况，识别所述终端设备的类别；
采用与所述终端设备的类别相适配的方式处理所述A2DP连接请求，以 与所述终端设备保持非A2DP连接状态。
本申请实施例还提供一种蓝牙耳机，包括：存储器、处理器和通信组件；
所述存储器，用于存储计算机程序；
所述通信组件，用于接收终端设备发送的A2DP连接请求和其它连接请求；
所述处理器，用于执行所述计算机程序，以用于：
在所述通信组件接收到终端设备发送的A2DP连接请求时，根据所述蓝牙耳机当前的状态信息，确定不需要与所述终端设备保持A2DP连接；
根据所述通信组件在所述A2DP连接请求之前接收所述终端设备发送的其它连接请求的情况，识别所述终端设备的类别；
采用与所述终端设备的类别相适配的方式处理所述A2DP连接请求，以与所述终端设备保持非A2DP连接状态。
本申请实施例还提供一种穿戴设备，包括：穿戴设备主体和上述蓝牙耳机；所述蓝牙耳机与所述穿戴设备主体可分离。
在一可选实施方式中，上述穿戴设备为智能手环，所述智能手环包括腕带，所述蓝牙耳机安装在所述腕带内，且所述蓝牙耳机可与所述腕带分离。
本申请实施例还提供一种连接请求处理装置，其特征在于，包括：确定模块、识别模块和处理模块；其中，
所述确定模块，用于在接收到终端设备发送的A2DP连接请求时，根据蓝牙耳机当前的状态信息，确定所述蓝牙耳机不需要与所述终端设备保持A2DP连接；
所述识别模块，用于根据在接收到所述A2DP连接请求之前接收所述终端设备发送的其它连接请求的情况，识别所述终端设备的类别；
所述处理模块，用于采用与所述终端设备的类别相适配的方式处理所述所述A2DP连接请求，以与所述终端设备保持非A2DP连接状态。
本申请实施例还提供一种连接请求处理系统，该系统包括上述蓝牙耳机和终端设备；
所述终端设备，用于向所述蓝牙耳机发送A2DP连接请求以及其它连接请求。
在一可选实施方式中，所述蓝牙耳机设置于穿戴设备上，且与所述穿戴设备可分离。
本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，其特征在于，所述计算机程序被一个或多个处理器执行时，可实现上述方法的步骤。
在本申请实施例中，在接收到终端设备发送的A2DP连接请求时，确定 蓝牙耳机是否需要与终端设备保持A2DP连接；当确定蓝牙耳机不需要与终端设备保持A2DP连接时，根据在接收到A2DP连接请求之前接收终端设备发送的其它连接请求的情况，来识别终端设备的类别；并采用与终端设备的类别相适配的方式处理A2DP连接请求，以使蓝牙耳机与终端设备保持非A2DP连接状态。这种处理A2DP连接请求的方式，可采用与终端设备相适配的方式处理A2DP连接请求，进而避免终端设备显示错误提示信息或不断回连的状况；而且可使蓝牙耳机在无需与终端设备保持A2DP连接时处于非A2DP连接状态，节省蓝牙耳机的功耗。
附图说明
此处所说明的附图用来提供对本申请的进一步理解，构成本申请的一部分，本申请的示意性实施例及其说明用于解释本申请，并不构成对本申请的不当限定。在附图中：
图1为本申请一示例性实施例提供的一种连接请求处理系统的结构示意图；
图2a为本申请一示例性实施例提供的另一种连接请求处理系统的结构示意图；
图2b为本申请一实施例提供的一种穿戴设备(智能手环)的结构示意图；
图3为本申请一实施例提供的一种连接请求处理方法的流程示意图；
图4为本申请另一实施例提供的一种连接请求处理装置的结构示意图；
图5为本申请又一实施例提供的一种蓝牙耳机的结构示意图。
具体实施方式
为使本申请的目的、技术方案和优点更加清楚，下面将结合本申请具体实施例及相应的附图对本申请技术方案进行清楚、完整地描述。显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
针对现有在终端设备与蓝牙耳机连接的情况下蓝牙耳机功耗较大的技术问题，本申请实施例提供一种解决方案，基本思路是：当确定蓝牙耳机不需要与终端设备保持A2DP连接时，根据在接收到A2DP连接请求之前接收终端设备发送的其它连接请求的情况，来识别终端设备的类别；并采用与终端设备的类别相适配的方式处理所述A2DP连接请求，以使蓝牙耳机与终端设备保持非A2DP连接状态。这种对于终端设备发送的A2DP连接请求的处理 方式，采用与终端设备相适配的方式处理A2DP连接请求，可避免终端设备显示错误提示信息或出现误操作等状况；而且可使蓝牙耳机在无需与终端设备保持A2DP连接时处于非A2DP连接状态，节省蓝牙耳机的功耗。
以下结合附图，详细说明本申请各实施例提供的技术方案。
图1为本申请一示例性实施例提供的一种连接请求处理系统的结构示意图。如图1所示，该系统10包括：蓝牙耳机10a和终端设备10b。图1中所呈现的蓝牙耳机10a和终端设备10b的实现形式只是示例性说明，并不对二者的实现形式做限定。其中，在本申请实施例中，蓝牙耳机10a通过蓝牙方式和终端设备10b通信连接。
在本实施例中，终端设备10b是指用户使用的，能够满足用户所需通信、音视频欣赏等需求的计算机设备，例如可以是但不限于：智能手机、平板电脑、MP3、MP4以及电话手表、智能手环等可穿戴设备。终端设备10b通常包括至少一个处理单元和至少一个存储器。处理单元和存储器的数量取决于终端设备10b的配置和类型。存储器可以包括易失性的，例如RAM，也可以包括非易失性的，例如只读存储器(Read-Only Memory，ROM)、闪存等，或者也可以同时包括两种类型的。存储器内通常存储有操作系统(Operating System，OS)、一个或多个应用软件，例如与蓝牙耳机10a对应的应用软件，也可以存储有程序数据等。除了处理单元和存储器之外，终端设备10b也会包括网卡芯片、IO总线、音视频组件等基本配置。可选地，根据终端设备10b的实现形式，终端设备10b也可以包括一些外围设备，例如键盘、鼠标、输入笔、打印机等。这些外围设备在本领域中是众所周知的，在此不做赘述。
在现有技术中，用户打开终端设备端的蓝牙功能，向蓝牙耳机发送蓝牙连接请求；蓝牙耳机接收并响应该蓝牙连接请求，与终端设备建立蓝牙连接。其中，终端设备与蓝牙耳机之间的蓝牙连接过程包括：基于HFP协议建立HFP连接的过程和基于A2DP协议建立A2DP连接的过程。之后，基于终端设备与蓝牙耳机之间的HFP连接，用户便可使用蓝牙耳机控制终端设备上的电话事务，如接听、挂断、拒接、语音拨号等；而基于终端设备与蓝牙耳机之间的A2DP连接，用户可以通过蓝牙耳机聆听终端设备传输的高品质的音视频。由于蓝牙耳机需要同时保持HFP连接和A2DP连接，这使得蓝牙耳机功耗较大。
一般来说，用户希望能够实时了解终端设备10b的电话事务，例如来电、短信等，在这种情况下，蓝牙耳机10a需实时监听终端设备10b的电话事务，则蓝牙耳机10a与终端设备10b可时刻保持HFP连接，以防止用户漏听终端设备10b的电话等。然而，用户一般在闲暇时间或某些合适的时间段，才会聆听终端设备10b播放的音视频，因此，蓝牙耳机10a与终端设备10b之间 的A2DP连接不需要长期保持。基于此，在本实施例提供的连接请求处理系统10中，蓝牙耳机10a对终端设备10b发送的蓝牙连接请求进行识别区分，当需要收听终端设备10b播放的音视频时，保持蓝牙耳机10a与终端设备10b得的A2DP连接；当用户不需要收听终端设备10b播放的音视频时，蓝牙耳机10a与终端设备10b保持非A2DP连接状态，进而节省蓝牙耳机10a的功耗。
在本实施例中，终端设备10b向蓝牙耳机10a发送A2DP连接请求，蓝牙耳机10a接收终端设备10b发送的A2DP连接请求，并在接收到该A2DP连接请求时，根据蓝牙耳机10a当前的状态信息，确定自身是否需要与终端设备10b保持A2DP连接。当确定不需要与终端设备10b保持A2DP连接时，可以采用一定方式与终端设备10b保持非A2DP连接。例如，蓝牙耳机可以拒绝终端设备发送的A2DP连接请求，从而与终端设备10b保持非A2DP连接状态。
为了通用性，本实施例的蓝牙耳机10a可以支持多种类型的终端设备。其中，终端设备的类别是根据其采用的操作系统进行分类的。例如，终端设备采用苹果操作系统(iPhone operating system，IOS)，则称之为IOS设备；再例如，终端设备采用Android操作系统，则称之为Android设备；再例如，终端设备采用Windows操作系统，则称之为Windows设备。为了描述方便，在本申请实施例中，将采用非IOS操作系统的终端设备，统一定义为非IOS设备。
经过实践，本申请发明人发现：不同类型的终端设备对蓝牙耳机拒绝A2DP连接请求的反应会有所不同。若蓝牙耳机10a对IOS设备和非IOS设备发送的A2DP连接请求都采用直接拒绝该A2DP连接请求的方式，则对于IOS设备来说，在IOS设备上则会显示“连接不成功，请确信XX已打开在通信范围内”的错误提示信息，其中“XX”可为蓝牙耳机10a的型号、IP地址等。
针对上述问题，在本实施例提供的连接请求处理系统10中，在确定不需要与终端设备保持A2DP连接的情况下，蓝牙耳机10a进一步根据接收到A2DP连接请求之前接收终端设备10b发送的其它连接请求的情况，识别终端设备10b的类别，并采用与终端设备10b的类别相适配的方式处理上述A2DP连接请求，进而使得自身与终端设备10b保持非A2DP连接状态。这样，可避免因采用与终端设备的类别不适配的方式处理A2DP连接请求，而导致终端设备显示错误提示信息或出现误操作等状况。
在本实施例提供的连接请求处理系统中，蓝牙耳机在确定不需要与终端设备保持A2DP连接时，根据在接收到终端设备发送的A2DP连接请求之前接收该终端设备发送的其它连接请求的情况，识别出终端设备的类别，并采 用与该终端设备的类别相适配的方式处理A2DP连接请求，使其与终端设备保持非A2DP连接状态。该连接请求处理系统中蓝牙耳机在无需与终端设备保持A2DP连接时处于非A2DP连接状态，从而节省蓝牙耳机的功耗。
在一可选实施例中，蓝牙耳机10a可以根据自身当前的位置状态和/或充电状态，确定是否需要与终端设备10b建立A2DP连接。
可选地，可以在蓝牙耳机10a上设置传感器，该传感器可采集蓝牙耳机10a当前的位置信息。可选地，传感器可以为位置传感器，例如人耳感应传感器、红外传感器等。根据该位置传感器采集到的位置数据，判断蓝牙耳机10a是否脱离对应用户的耳部；为了防止因蓝牙耳机10a滑脱用户耳部的情况而对蓝牙耳机10a是否需要与终端设备10b保持A2DP连接造成误判，则当确定蓝牙耳机10a已脱离对应用户的耳部时，进一步确定蓝牙耳机10a脱离用户耳部的时长是否超过预设的时长阈值，为了描述方便，将该预设的时长阈值定义为第一预设时长阈值，当蓝牙耳机10a脱离用户耳部的时长超过第一预设时长阈值时，说明用户不需要使用蓝牙耳机聆听终端设备传输的音视频，此时A2DP连接没有必要，则确定蓝牙耳机10a不需要与终端设备10b保持A2DP连接。可选地，当确定蓝牙耳机10a未脱离对应用户的耳部时，则确定蓝牙耳机10a需要与终端设备10b保持A2DP连接，以便于用户可以通过蓝牙耳机聆听终端设备传输的音视频。
在另一可选实施例中，蓝牙耳机10a可依附于穿戴设备，穿戴设备包括蓝牙耳机10a和穿戴设备主体。该穿戴设备可为智能手环、智能手表等。蓝牙耳机10a安装在穿戴设备主体上，且蓝牙耳机10a可与穿戴设备主体分离。当用户将蓝牙耳机10a安装在穿戴设备主体上时，说明该用户不需要利用蓝牙耳机10a接收终端设备10b传输的音视频。基于此，可以利用蓝牙耳机10a上的传感器采集蓝牙耳机10a当前的位置信息。可选地，该传感器可以为位置传感器，例如霍尔传感器等。根据该位置传感器采集到的蓝牙耳机10a与穿戴设备主体的相对位置数据，判断蓝牙耳机10a是否脱离所依附的穿戴设备。当确定出蓝牙耳机10a未脱离所依附的穿戴设备，即安装在穿戴设备主体上时，确定蓝牙耳机10a不需要与终端设备10b保持A2DP连接。然而，当确定出蓝牙耳机10a脱离所依附的穿戴设备时，可能无法确定蓝牙耳机10a需要与终端设备10b保持A2DP连接，可以根据其他条件做进一步判断。例如，根据蓝牙耳机10a当前的充电状态进行判断等。
值得说明的是，上述位置传感器也可设置于穿戴设备的穿戴设备主体上。
可选地，对于蓝牙耳机10a依附于穿戴设备的情况，可以根据蓝牙耳机上的第一传感器和第二传感器，判断蓝牙耳机10a是否脱离用户耳部和蓝牙耳机10b是否脱离所依附的穿戴设备来确定其是否需要与终端设备10b保持 A2DP连接。其中，第一传感器可以是人耳感应传感器、红外传感器等，第二传感器可以为霍尔传感器等。然而，当蓝牙耳机10a根据第一传感器采集的位置信息，确定其脱离用户耳部的时长超过第一预设时长阈值时，可能无法确定蓝牙耳机10a不需要与终端设备10b保持A2DP连接，可以根据第二传感器采集的位置信息，判断蓝牙耳机10a是否脱离所依附的穿戴设备进行进一步判定。即当蓝牙耳机10a脱离用户耳部的时长超过第一预设时长阈值，且蓝牙耳机10a未脱离所依附的穿戴设备时，确定蓝牙耳机10a不需要与终端设备10b保持A2DP连接。具体判断过程可参见上述所述，此处不再赘述。
在又一可选实施例中，蓝牙耳机10a可内置充电电池，为了能保持蓝牙耳机10a的续航时间，需要及时为蓝牙耳机10a进行充电。为了增强用户的体验，当蓝牙耳机10a处于充电状态时，用户一般不会通过蓝牙耳机10a接收终端设备10b传输的音视频。基于此，可以检测蓝牙耳机10a的外接电源端口是否有外接电源存在，当检测到有外接电源存在时，确定蓝牙耳机10a不需要与终端设备10b建立A2DP连接。然而，可选地，当判断出蓝牙耳机10a的外接电源端口不存在外接电源时，可能无法确定蓝牙耳机10a需要与终端设备10b保持A2DP连接，可以进一步根据上述蓝牙耳机10a当前的位置状态来确定是否需要与终端设备10b建立A2DP连接。可选地，蓝牙耳机10a的外接电源端口可以是但不局限于：USB接口。
在上述或下述实施例中，用户可以在终端设备10b的设置栏中开启蓝牙功能，终端设备10b响应用户开启蓝牙功能的操作，向蓝牙耳机10a发送蓝牙连接请求。对终端设备10b来说，会按照与设备类型适配的先后顺序采用串行通信的方式依次将HFP连接请求和A2DP连接请求发送给蓝牙耳机10a。不同类别的终端设备向蓝牙耳机10a发送HFP连接请求和A2DP连接请求的顺序不同。例如，对IOS设备来说，在向蓝牙耳机10a发送蓝牙连接请求时会先发送A2DP连接请求，再发送HFP连接请求；对Android等其他非IOS设备，则会先发送HFP连接请求，再发送A2DP连接请求。
基于上述，蓝牙耳机10a可根据在接收到A2DP连接请求前是否接收到HFP连接请求来确定终端设备10b是否为IOS设备。若蓝牙耳机10a在接收到终端设备10b发送的A2DP连接请求之前未接收到终端设备10b发送的HFP连接请求，则确定终端设备10b为IOS设备；若蓝牙耳机10a在接收到终端设备10b发送的A2DP连接请求之前接收到终端设备10b发送的HFP连接请求，则确定终端设备10b为非IOS设备。
可选地，终端设备10b上安装有蓝牙耳机10a对应的应用程序(Application，App)。当蓝牙耳机10a需要与对应的App进行数据通信时，用户打开对应的App，终端设备10b响应用户打开App的操作，向蓝牙耳机 10a发送相应的数据通信协议下的连接请求。蓝牙耳机10a接收该数据通信协议下的连接请求，进而与终端设备10b建立数据通信连接，并通过该数据通信连接将对应的数据发送给终端设备上的App。对IOS设备来说，可采用特有的iPod附件协议(iPod Accessory Protocol，IAP)与蓝牙耳机10a进行数据通信。
基于此，可通过判断在蓝牙耳机10a接收到终端设备10b发送的A2DP连接请求之前，是否接收到该终端设备10b发送的IAP连接请求来确定终端设备10b是否为IOS设备。若蓝牙耳机10a在接收到终端设备10b发送的A2DP连接请求之前接收到该终端设备10b发送的IAP连接请求，则确定该终端设备10b为IOS设备。可选地，若蓝牙耳机10a在接收到A2DP连接请求之前未接收到上述IAP连接请求，则可根据上述蓝牙耳机10a接收A2DP连接请求和HFP连接请求的先后顺序，对终端设备10b的类别进行进一步判断。
基于上述终端设备10b的类别，蓝牙耳机10a采用与终端设备10b的类别相适配的方式处理终端设备10b发送的A2DP连接请求，进而与终端设备10b保持非A2DP连接状态，以节省蓝牙耳机10a的功耗。
当终端设备10b为非IOS设备时，蓝牙耳机10a直接拒绝终端设备10b发送的连接请求，可以与终端设备10b保持非A2DP连接状态。当终端设备10b为IOS设备时，蓝牙耳机10a先响应终端设备10b发送的A2DP连接请求，与终端设备10b建立A2DP连接；在该A2DP连接的保持时长超过预设的时长阈值时，断开与终端设备10b的A2DP连接，进而与终端设备10b保持非A2DP连接状态。为描述方便，将该预设时长阈值定义为第二预设时长阈值。
对IOS设备和非IOS设备，蓝牙耳机10a采用两种不同的方式对终端设备10b发送的A2DP连接请求进行处理，其原因是：若蓝牙耳机10a对IOS设备和非IOS设备发送的A2DP连接请求都采用直接拒绝该A2DP连接请求的方式，则对于IOS设备来说，在IOS设备上则会显示“连接不成功，请确信XX已打开在通信范围内”的错误提示信息，其中“XX”可为蓝牙耳机10a的型号、IP地址等。若蓝牙耳机10a对IOS设备和非IOS设备发送的A2DP连接请求都采用上述先响应该A2DP连接请求，并在A2DP连接保持一定时间后再断开的方式进行处理，则非IOS设备会不断向蓝牙耳机10a发送A2DP连接请求，导致蓝牙耳机10a不断与该非IOS设备不断进行A2DP回连，并不断断开，这会影响蓝牙耳机10a和终端设备10b的使用寿命。因此，蓝牙耳机10a采用与终端设备10b的类型相适配的方式对A2DP连接请求进行处理，来保持与终端设备10b的非A2DP连接状态，可避免上述两种情况的发生，增强用户体验，并延长蓝牙耳机10a和终端设备10b的使用寿命。
需要说明的是，上述第二预设时长阈值可根据终端设备10b的配置进行 设定，对时长阈值的大小不做限定，只要能保证蓝牙耳机10a断开与终端设备10b的连接后，终端设备10b不会再不断发送A2DP连接请求即可。
可选地，对于蓝牙耳机10a与终端设备10b在已经保持A2DP连接的情况，蓝牙耳机10a也可以监控自身的状态信息，并根据监控到的状态信息判断是否需要继续与终端设备10b保持A2DP连接；当蓝牙耳机10a确定不需要与终端设备10b继续保持该A2DP连接时，无论终端设备10b属于哪种类别设备，均直接断开A2DP连接，节约蓝牙耳机的电量，而且对终端设备10b不会造成影响。
值得说明的是，在上述或下述实施例中，蓝牙耳机可为独立的蓝牙耳机，也可依赖于穿戴设备，例如智能手环、AR或VR头戴显示设备等。基于此，本申请一实施例还提供另一种连接请求处理系统，图2为该连接请求处理系统20的结构示意图。如图2a所示，该系统20包括穿戴设备20a和终端设备20b；且穿戴设备20a蓝牙耳机20a1和穿戴设备主体20a2。图2a中所呈现的穿戴设备20a、蓝牙耳机20a1、穿戴设备主体20a2以及终端设备10b的实现形式只是示例性说明，并不对二者的实现形式做限定。
其中，在本实施例中，终端设备20b可以和穿戴设备20a上的蓝牙耳机20a1进行蓝牙连接；也可以和穿戴设备20a采用无线或有线连接。可选地，穿戴设备20a可以通过移动网络和终端设备20b通信连接，相应地，移动网络的网络制式可以为2G(GSM)、2.5G(GPRS)、3G(WCDMA、TD-SCDMA、CDMA2000、UTMS)、4G(LTE)、4G+(LTE+)、WiMax等中的任意一种。可选地，穿戴设备20a也可以通过蓝牙、WiFi、红外线等方式和终端设备20b通信连接。值得说明的是，穿戴设备20a也可以不与终端设备20b连接。是否与终端设备20b连接，可视穿戴设备20a的功能和需求而定。
在本实施例中，当终端设备20b向蓝牙耳机20a1发送A2DP连接请求时，蓝牙耳机20a1接收终端设备20b发送的A2DP连接请求，并在接收到该A2DP连接请求时，根据蓝牙耳机20a1当前的状态信息，确定自身是否需要与终端设备20b保持A2DP连接。当确定自身不需要与终端设备20b保持A2DP连接之后，蓝牙耳机10a可进一步根据接收到A2DP连接请求之前接收终端设备20b发送的其它连接请求的情况，识别终端设备20b的类别，并采用与终端设备20b的类别相适配的方式处理上述A2DP连接请求，进而使得自身与终端设备20b保持非A2DP连接状态。这样，可避免因采用与终端设备的类别不适配的方式处理A2DP连接请求，而导致终端设备显示错误提示信息或出现误操作等状况。
在一可选实施方式中，穿戴设备20a可以为智能手环，如图2b所示为本申请一实施例提供的一种智能手环的结构示意图。智能手环20c包括腕带20c1 和蓝牙耳机20c2，其中，蓝牙耳机20c2安装在腕带20c1内，且蓝牙耳机20c2与腕带20c1分离，即蓝牙耳机20c2为可拆卸的。
对于图2a和图2b中的蓝牙耳机对A2DP连接请求进行处理的详细描述，可参见上述实施例中对图1中的相应描述，此处不再赘述。
在本实施例提供的连接请求处理系统中，蓝牙耳机在确定不需要与终端设备保持A2DP连接时，根据在接收到终端设备发送的A2DP连接请求之前接收该终端设备发送的其它连接请求的情况，识别出终端设备的类别，并采用与该终端设备的类别相适配的方式处理A2DP连接请求，使其与终端设备保持非A2DP连接状态。该连接请求处理系统中蓝牙耳机在无需与终端设备保持A2DP连接时处于非A2DP连接状态，从而节省蓝牙耳机的功耗，即节省穿戴设备的功耗。
除上述系统实施例之外，本申请还提供了一些方法实施例，这些方法实施例分别从蓝牙耳机的角度描述了对终端设备发送的A2DP连接请求的处理过程。下面将结合附图对这些方法实施例进行详细说明。
图3为本申请一实施例提供的一种连接请求处理方法的流程示意图。如图3所示，包括：
301、在接收到终端设备发送的A2DP连接请求时，根据蓝牙耳机当前的状态信息，确定不需要与终端设备保持A2DP连接。
302、根据在接收到A2DP连接请求之前接收终端设备发送的其它连接请求的情况，识别终端设备的类别。
303、采用与终端设备的类别相适配的方式处理A2DP连接请求，以与终端设备保持非A2DP连接状态。
在本实施例中，为了提高蓝牙耳机的运行速度，节约蓝牙耳机的功耗，蓝牙耳机在接收到终端设备发送的A2DP连接请求时，可根据蓝牙耳机当前的状态，确定是否需要与终端设备保持A2DP连接；在确定不需要与终端设备不需要保持A2DP连接时，对该A2DP连接请求进行处理，进而与终端设备保持非A2DP连接状态。
又因为终端设备具有多种类别，若采用同一种方式处理A2DP连接请求，则当所采用的处理A2DP连接请求的方式与终端设备的类别不适配时，终端设备则会出现错误的提示信息或者出现不断回连等故障。基于此，在本实施例中，在确定不需要与终端设备不需要保持A2DP连接之后，进一步根据在接收到A2DP连接请求之前接收终端设备发送的其它连接请求的情况，识别出该终端设备的类别；之后，再采用与终端设备的类别相适配的方式处理终端设备发送的A2DP连接请求，进而使蓝牙耳机与终端设备保持非A2DP连接状态。这样不仅节省蓝牙耳机的功耗，而且可以避免终端设备显示错误提 示信息或不断进行A2DP回连的状况。
需要说明的是，在上述或下述实施例中，为了防止用户漏听电话，蓝牙耳机与终端设备需要保持HFP连接，以监听对应的终端设备的电话业务。
在一些应用场景中，当用户无需利用蓝牙耳机来接收终端设备传输的音视频时，蓝牙耳机不需要与终端设备保持A2DP连接。此时，用户一般不再佩戴该蓝牙耳机，而将蓝牙耳机置于某些位置。
在另一些应用场景下，为了用户使用方便，蓝牙耳机在进行充电时，用户一般不会用来接收终端设备传输的音视频，此时，蓝牙耳机不需要与终端设备保持A2DP连接。
基于上述应用场景，步骤301的一种可选实施方式为：根据蓝牙耳机当前的位置状态和/或充电状态，确定不需要与终端设备保持A2DP连接。
进一步，当根据蓝牙耳机当前的位置状态，确定不需要与终端设备保持A2DP连接时，可以在蓝牙耳机上设置传感器采集蓝牙耳机当前的位置信息，可选地，传感器可以为位置传感器，例如人耳感应传感器、红外传感器等。根据该位置传感器采集到的位置数据，判断蓝牙耳机是否脱离对应用户的耳部；为了防止因蓝牙耳机滑脱用户耳部的情况而对蓝牙耳机是否需要与终端设备保持A2DP连接造成误判，则当确定蓝牙耳机已脱离对应用户的耳部时，进一步确定蓝牙耳机脱离用户耳部的时长是否超过预设的时长阈值，为了描述方便，将该预设的时长阈值定义为第一预设时长阈值，当蓝牙耳机脱离用户耳部的时长超过第一预设时长阈值时，则确定不需要与终端设备保持A2DP连接。可选地，当确定蓝牙耳机未脱离对应用户的耳部时，则确定蓝牙耳机需要与终端设备保持A2DP连接，以便于用户可以通过蓝牙耳机聆听终端设备传输的音视频。
可选地，蓝牙耳机可依附于穿戴设备，穿戴设备包括蓝牙耳机和穿戴设备主体。该穿戴设备可为智能手环、智能手表等，蓝牙耳机安装在穿戴设备主体上，且蓝牙耳机可与穿戴设备主体分离。当用户将蓝牙耳机安装在穿戴设备主体上时，说明该用户不需要利用蓝牙耳机接收终端设备传输的音视频。基于此，可以利用蓝牙耳机上的传感器采集蓝牙耳机当前的位置信息，可选地，传感器可以为位置传感器，例如霍尔传感器等。根据该位置传感器采集到的蓝牙耳机与穿戴设备主体的相对位置数据，判断蓝牙耳机是否脱离所依附的穿戴设备。当确定出蓝牙耳机未脱离所依附的穿戴设备，即安装在穿戴设备主体上时，确不需要与终端设备保持A2DP连接。然而，当确定出蓝牙耳机脱离所依附的穿戴设备时，可能无法确定蓝牙耳机不需要与终端设备保持A2DP连接，可以根据根据其他条件做进一步判断。例如，根据蓝牙耳机当前的充电状态进行判断等。
值得说明的是，上述位置传感器可设置于穿戴设备的主体上。
可选地，对于蓝牙耳机依附于穿戴设备的情况，可以根据蓝牙耳机上的第一传感器和第二传感器，判断蓝牙耳机是否脱离用户耳部和蓝牙耳机是否脱离所依附的穿戴设备来确定其是否需要与终端设备保持A2DP连接。其中，第一传感器可以是人耳感应传感器、红外传感器等，第二传感器可以为霍尔传感器等。然而，当蓝牙耳机10a根据第一传感器采集的位置信息，确定其脱离用户耳部的时长超过第一预设时长阈值时，可能无法确定蓝牙耳机不需要与终端设备保持A2DP连接，可以根据第二传感器采集的位置信息，判断蓝牙耳机是否脱离所依附的穿戴设备进行进一步判定。即当蓝牙耳机脱离用户耳部的时长超过第一预设时长阈值，且蓝牙耳机未脱离所依附的穿戴设备时，确定蓝牙耳机不需要与终端设备保持A2DP连接。具体判断过程可参见上述所述，此处不再赘述。
进一步，当根据蓝牙耳机当前的充电状态，确定不需要与终端设备保持A2DP连接请求时，可以检测蓝牙耳机的外接电源端口是否有外接电源存在，当检测到有外接电源存在时，确定不需要与终端设备建立A2DP连接。然而，当判断出蓝牙耳机的外接电源端口不存在外接电源时，可能无法确定蓝牙耳机不需要与终端设备保持A2DP连接，可以根据其他条件做进一步判断。可选地，可以进一步根据上述蓝牙耳机当前的位置状态来确定是否需要与终端设备保持A2DP连接。可选地，蓝牙耳机的外接电源端口可以是但不局限于：USB接口。
在一可选实施例中，用户可以在终端设备的设置栏中开启蓝牙功能，终端设备响应用户开启蓝牙功能的操作，向蓝牙耳机发送蓝牙连接请求。对终端设备来说，会按照与设备类型适配的先后顺序采用串行通信的方式将HFP连接请求和A2DP连接请求依次发送于蓝牙耳机。不同类别的终端设备向蓝牙耳机发送HFP连接请求和A2DP连接请求的顺序不同。例如，对IOS设备来说，在向蓝牙耳机发送蓝牙连接请求时会先发送A2DP连接请求，再发送HFP连接请求；对于Android等其他非IOS设备来说，则会先向发送HFP连接请求，再发送A2DP连接请求。基于此，步骤302的一种可选实施方式为：根据在接收到A2DP连接请求前是否接收到HFP连接请求来确定终端设备是否为IOS设备。若在接收到终端设备发送的A2DP连接请求之前未接收到终端设备发送的HFP连接请求，则确定终端设备为IOS设备；若在接收到终端设备发送的A2DP连接请求之前接收到终端设备发送的HFP连接请求，则确定终端设备为非IOS设备。
可选地，终端设备上可安装与蓝牙耳机对应的App。当蓝牙耳机需要与对应的App进行数据通信时，用户打开对应的App，终端设备响应用户打开 App的操作，向蓝牙耳机发送相应的数据通信协议下的连接请求。蓝牙耳机接收该数据通信协议下的连接请求，进而与终端设备建立数据通信连接，并通过该数据通信连接蓝牙耳机将对应的数据发送于终端设备上的App。对IOS设备来说，可采用特有的IAP协议来实现与与蓝牙耳机进行数据通信。基于此，步骤302的另一种可选实施方式为：通过判断在接收到终端设备发送的A2DP连接请求之前，是否接收到该终端设备发送的IAP连接请求来确定终端设备是否为IOS设备。若在接收到终端设备发送的A2DP连接请求之前接收到该终端设备发送的IAP连接请求，则确定该终端设备为IOS设备。可选地，若在接收到A2DP连接请求之前未接收到上述IAP连接请求，则可根据上述蓝牙耳机接收A2DP连接请求和HFP连接请求的先后顺序，对终端设备的类别进行进一步判断，其判断过程可参见上述相关描述，此处不再赘述。
基于上述确定出的终端设备的类别，采用与终端设备的类别相适配的方式处理终端设备发送的A2DP连接请求，进而与终端设备保持非A2DP连接状态，以节省蓝牙耳机的功耗。
当终端设备为非IOS设备时，直接拒绝终端设备发送的连接请求，可以与终端设备10b保持非A2DP连接状态。当终端设备为IOS设备时，先响应终端设备发送的A2DP连接请求，与终端设备建立A2DP连接；在该A2DP连接的保持时长超过预设的时长阈值时，断开与终端设备的A2DP连接，进而与终端设备保持非A2DP连接状态。可选地，预设的时长阈值可根据终端设备的配置进行设定，对时长阈值的大小不做限定，只要能保证断开与终端设备的连接后，终端设备不会再不断发送A2DP连接请求即可。对于采用上述方式对A2DP连接请求进行处理的原因，可参见上述图1所对应的系统实施例中对的相关描述，此处不再赘述。
可选地，对于蓝牙耳机与终端设备在已经保持A2DP连接的情况，蓝牙耳机也可以监控自身的状态信息，并根据监控到的状态信息判断是否需要继续与终端设备保持A2DP连接；当蓝牙耳机确定不需要与终端设备保持该A2DP连接时，无论终端设备属于哪种类别设备，均直接断开A2DP连接，节约蓝牙耳机的电量，而且对终端设备不会造成影响。
图4为本申请另一实施例提供的一种连接请求处理装置的结构示意图。该连接请求处理装置可作为蓝牙耳机中的功能模块实现，或者也可以独立于蓝牙耳机但与蓝牙耳机通信连接，以负责对终端设备发送给蓝牙耳机的A2DP连接请求进行处理。如图4所示，该连接请求处理装置40包括：确定模块41、识别模块42以及处理模块43。其中，
确定模块41，用于在接收到终端设备发送的A2DP连接请求时，根据蓝牙耳机当前的状态信息，确定蓝牙耳机不需要与终端设备保持A2DP连接。
识别模块42，根据在接收到A2DP连接请求之前接收终端设备发送的其它连接请求的情况，识别终端设备的类别。
处理模块43，采用与终端设备的类别相适配的方式处理A2DP连接请求，以与终端设备保持非A2DP连接状态。
在一可选实施例中，确定模块41在根据蓝牙耳机当前的状态信息，确定蓝牙耳机不需要与终端设备保持A2DP连接时，具体用于：根据蓝牙耳机当前的位置状态和/或充电状态，确定蓝牙耳机不需要与终端设备保持A2DP连接。
进一步，确定模块41在根据蓝牙耳机当前的位置状态，确定不需要与终端设备保持A2DP连接时，具体用于：根据蓝牙耳机上的位置传感器采集到的位置数据，确定蓝牙耳机脱离对应用户的耳部；当所述蓝牙耳机脱离所述用户的耳部的时长超过第一预设时长阈值时，确定蓝牙耳机不需要与终端设备保持A2DP连接；或者根据蓝牙耳机上的位置传感器采集到的位置数据，判断蓝牙耳机是否脱离蓝牙耳机依附的穿戴设备，当判断结果为否时，确定蓝牙耳机不需要与终端设备保持A2DP连接。
可选地，确定模块41在根据蓝牙耳机当前的充电状态，确定不需要与终端设备保持A2DP连接时，具体用于：判断穿戴设备的外接电源端口是否有外接电源存在，当判断结果为存在时，确定蓝牙耳机不需要与终端设备建立A2DP连接。
在另一可选实施例中，识别模块42在根据在A2DP连接请求之前接收终端设备发送的其它连接请求的情况，识别终端设备的类别时，具体用于：若在接收到终端设备发送的A2DP连接请求之前未接收到终端设备发送的HFP连接请求，确定终端设备为IOS设备；若在接收到终端设备发送的A2DP连接请求之前接收到终端设备发送的IAP连接请求，确定终端设备为IOS设备；若在接收到终端设备发送的A2DP连接请求之前接收到终端设备发送的HFP连接请求，确定终端设备为非IOS设备。
在又一可选实施例中，处理模块43在采用与终端设备的类别相适配的方式处理A2DP连接请求，以与终端设备保持非A2DP连接状态时，具体用于：当终端设备为非IOS设备时，直接拒绝A2DP连接请求，以与终端设备保持非A2DP连接状态；或者当终端设备为IOS设备时，响应A2DP连接请求，以与终端设备建立A2DP连接，并在A2DP连接的保持时长超过预设的时长阈值时，断开与终端设备的A2DP连接，以与终端设备保持非A2DP连接状态。
本实施例提供的连接请求处理装置，在确定蓝牙耳机不需要与终端设备保持A2DP连接时，根据在接收到终端设备发送的A2DP连接请求之前接收 该终端设备发送的其它连接请求的情况，识别出终端设备的类别，并采用与该终端设备的类别相适配的方式处理A2DP连接请求，使蓝牙耳机与终端设备保持非A2DP连接状态。这可以节省蓝牙耳机的功耗。
图5为本申请又一实施例提供的一种蓝牙耳机的结构示意图。如图5所示，包括：存储器50a、通信组件50b以及处理器50c。其中，
存储器50a，用于存储计算机程序。
通信组件50b，用于接收终端设备发送的A2DP连接请求和其它连接请求。
处理器50c，用于执行存储器50a存储的计算机程序，以用于：在通信组件50b接收到终端设备发送的A2DP连接请求时，根据蓝牙耳机当前的状态信息，确定不需要与终端设备保持A2DP连接；根据在A2DP连接请求之前接收终端设备发送的其它连接请求的情况，识别终端设备的类别；采用与终端设备的类别相适配的方式处理A2DP连接请求，以与终端设备保持非A2DP连接状态。
在一可选实施例中，蓝牙耳机还可包括电源组件50d。电源组件50d为蓝牙耳机提供电力。电源组件50d可以包括电源管理系统，一个或多个电源，及其他与为电源组件所属设备生成、管理和分配电力相关联的组件。可选地，电源组件50d包括可充电电池。
相应地，处理器50c在根据蓝牙耳机当前的状态信息，确定不需要与终端设备保持A2DP连接时，具体用于：根据蓝牙耳机当前的位置状态和/或电源组件50d的充电状态，确定不需要与终端设备保持A2DP连接。
进一步，处理器50c在根据蓝牙耳机当前的位置状态，确定不需要与终端设备保持A2DP连接时，具体用于：根据蓝牙耳机上的位置传感器采集到的位置数据，确定蓝牙耳机脱离对应用户的耳部；当所述蓝牙耳机脱离所述用户的耳部的时长超过第一预设时长阈值时，确定不需要与终端设备保持A2DP连接；或者根据蓝牙耳机上的位置传感器采集到的位置数据，判断蓝牙耳机是否脱离蓝牙耳机依附的穿戴设备，当判断结果为否时，确定不需要与终端设备保持A2DP连接。
可选地，处理器50c在根据蓝牙耳机的电源组件50d当前的充电状态，确定不需要与终端设备保持A2DP连接时，具体用于：判断蓝牙耳机的电源组件50d中的外接电源端口是否有外接电源存在，当判断结果为存在时，确定不需要与终端设备建立A2DP连接。
在另一可选实施例中，处理器50c在根据在A2DP连接请求之前接收终端设备发送的其它连接请求的情况，识别终端设备的类别时，具体用于：若通信组件50b在接收到终端设备发送的A2DP连接请求之前未接收到终端设备发送的HFP连接请求，确定终端设备为IOS设备；若通信组件50b在接收 到终端设备发送的A2DP连接请求之前接收到终端设备发送的IAP连接请求，确定终端设备为IOS设备；若通信组件50b在接收到终端设备发送的A2DP连接请求之前接收到终端设备发送的HFP连接请求，确定终端设备为非IOS设备。
在又一可选实施例中，处理器50c在采用与终端设备的类别相适配的方式处理A2DP连接请求，以与终端设备保持非A2DP连接状态时，具体用于：当终端设备为非IOS设备时，直接拒绝A2DP连接请求，以与终端设备保持非A2DP连接状态；或者当终端设备为IOS设备时，响应A2DP连接请求，以与终端设备建立A2DP连接，并在A2DP连接的保持时长超过预设的时长阈值时，断开与终端设备的A2DP连接，以与终端设备保持非A2DP连接状态。
可选地，如图5所示，蓝牙耳机还可包括：音频组件50e等其它组件。图5中仅示意性给出部分组件，并不意味着终端设备只包括图5所示组件。
本实施例提供的蓝牙耳机，在接收到终端设备发送的A2DP连接请求时，确定蓝牙耳机是否需要与终端设备保持A2DP连接；当确定不需要与终端设备保持A2DP连接时，根据在接收到终端设备发送的A2DP连接请求之前接收该终端设备发送的其它连接请求的情况，识别出终端设备的类别，并采用与该终端设备的类别相适配的方式处理A2DP连接请求，使其与终端设备保持非A2DP连接状态。该蓝牙耳机在无需与终端设备保持A2DP连接时处于非A2DP连接状态，从而节省蓝牙耳机的功耗。
值得说明的是，本申请实施例所提供的蓝牙耳机可单独存在，也可依附于其他设备，例如穿戴设备，可选地，穿戴设备可以是但不局限于智能手环、智能手表、AR或VR头戴显示设备等。基于此，本申请实施例还提供一种穿戴设备，穿戴设备的结构示意图可如图2b所示，包括穿戴设备主体和蓝牙耳机，蓝牙耳机与穿戴设备主体可分离。对于图2b所呈现的穿戴设备的实现形式，穿戴设备主体为腕带20c2，蓝牙耳机20c1安装在腕带20c2内。对于蓝牙耳机20c1的内部结构可参见图5所示的蓝牙耳机的结构示意图，此处不再赘述。
需要说明的是，本申请实施例提供的穿戴设备中的蓝牙耳机可作为一个独立的部分，也可与穿戴设备的其它部分集成为一个部件，例如集成在智能手环或智能手表的表盘部分。
还需要说明的是，本申请实施例提供的穿戴设备，还可包括：显示器、音频组件等其它组件，但不限于此。其中，
显示器，可以包括屏幕，其屏幕可以包括液晶显示器(LCD)和触摸面板(TP)。如果屏幕包括触摸面板，屏幕可以被实现为触摸屏，以接收来自用 户的输入信号。触摸面板包括一个或多个触摸传感器以感测触摸、滑动和触摸面板上的手势。所述触摸传感器可以不仅感测触摸或滑动动作的边界，而且还检测与所述触摸或滑动操作相关的持续时间和压力。
音频组件，被配置为输出和/或输入音频信号。例如，音频组件包括一个麦克风(MIC)，当音频组件所属设备处于操作模式，如呼叫模式、记录模式和语音识别模式时，麦克风被配置为接收外部音频信号。所接收的音频信号可以被进一步存储在存储器或经由通信组件发送。在一些实施例中，音频组件还包括一个扬声器，用于输出音频信号。
在本实施例提供的穿戴设备中，蓝牙耳机在确定不需要与终端设备保持A2DP连接时，根据在接收到终端设备发送的A2DP连接请求之前接收该终端设备发送的其它连接请求的情况，识别出终端设备的类别，并采用与该终端设备的类别相适配的方式处理A2DP连接请求，使其与终端设备保持非A2DP连接状态。该穿戴设备中蓝牙耳机在无需与终端设备保持A2DP连接时处于非A2DP连接状态，从而节省蓝牙耳机的功耗，即节省穿戴设备的功耗。
相应地，本申请实施例还提供一种存储有计算机程序的计算机可读存储介质，该计算机程序被执行时能够实现上述方法实施例中可由蓝牙耳机执行的各步骤或操作。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上， 使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。
内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。
计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
以上所述仅为本申请的实施例而已，并不用于限制本申请。对于本领域技术人员来说，本申请可以有各种更改和变化。凡在本申请的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本申请的权利要求范围之内。

Claims (15)

  1. 一种连接请求处理方法，适用于蓝牙耳机，其特征在于，所述方法包括：
    在接收到终端设备发送的A2DP连接请求时，根据所述蓝牙耳机当前的状态信息，确定不需要与所述终端设备保持A2DP连接；
    根据在接收到所述A2DP连接请求之前接收所述终端设备发送的其它连接请求的情况，识别所述终端设备的类别；
    采用与所述终端设备的类别相适配的方式处理所述A2DP连接请求，以与所述终端设备保持非A2DP连接状态。
  2. 根据权利要求1所述的方法，其特征在于，所述根据所述蓝牙耳机当前的状态信息，确定不需要与所述终端设备保持A2DP连接，包括：
    根据所述蓝牙耳机当前的位置状态和/或充电状态，确定不需要与所述终端设备保持A2DP连接。
  3. 根据权利要求2所述的方法，其特征在于，根据所述蓝牙耳机当前的位置状态，确定不需要与所述终端设备保持A2DP连接，包括：
    根据所述蓝牙耳机上的位置传感器采集到的位置数据，确定所述蓝牙耳机脱离对应用户的耳部；
    当所述蓝牙耳机脱离所述用户的耳部的时长超过第一预设时长阈值时，确定不需要与所述终端设备保持A2DP连接；和/或
    根据所述蓝牙耳机上的位置传感器采集到的位置数据，判断所述蓝牙耳机是否脱离所述蓝牙耳机依附的穿戴设备，当判断结果为否时，确定不需要与所述终端设备保持A2DP连接。
  4. 根据权利要求2所述的方法，其特征在于，所述根据所述蓝牙耳机当前的充电状态，确定不需要与所述终端设备保持A2DP连接，包括：
    判断所述蓝牙设备的外接电源端口是否有外接电源存在，当判断结果为存在时，确定不需要与所述终端设备保持A2DP连接。
  5. 根据权利要求1所述的方法，其特征在于，所述根据在接收到所述A2DP连接请求之前接收所述终端设备发送的其它连接请求的情况，识别所述终端设备的类别，包括：
    若在接收到所述终端设备发送的A2DP连接请求之前未接收到所述终端设备发送的HFP连接请求，确定所述终端设备为IOS设备；
    若在接收到所述终端设备发送的A2DP连接请求之前接收到所述终端设备发送的iPod附件协议连接请求，确定所述终端设备为IOS设备；
    若在接收到所述终端设备发送的A2DP连接请求之前接收到所述终端设 备发送的HFP连接请求，确定所述终端设备为非IOS设备。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述采用与所述终端设备的类别相适配的方式处理所述A2DP连接请求，以与所述终端设备保持非A2DP连接状态，包括：
    当所述终端设备为非IOS设备时，直接拒绝所述A2DP连接请求，以与所述终端设备保持非A2DP连接状态；或者
    当所述终端设备为IOS设备时，响应所述A2DP连接请求，以与所述终端设备建立A2DP连接，并在所述A2DP连接的保持时长超过第二预设时长阈值时，断开与所述终端设备的A2DP连接，以与所述终端设备保持非A2DP连接状态。
  7. 一种蓝牙耳机，其特征在于，包括：存储器、处理器和通信组件；
    所述存储器，用于存储计算机程序；
    所述通信组件，用于接收终端设备发送的A2DP连接请求和其它连接请求；
    所述处理器，用于执行所述计算机程序，以用于：
    在所述通信组件接收到终端设备发送的A2DP连接请求时，根据所述蓝牙耳机当前的状态信息，确定不需要与所述终端设备保持A2DP连接；
    根据所述通信组件在接收到所述A2DP连接请求之前接收所述终端设备发送的其它连接请求的情况，识别所述终端设备的类别；
    采用与所述终端设备的类别相适配的方式处理所述A2DP连接请求，以与所述终端设备保持非A2DP连接状态。
  8. 根据权利要求7所述的蓝牙耳机，其特征在于，所述处理器在确定不需要与所述终端设备保持A2DP连接时，具体用于：
    根据所述蓝牙耳机当前的位置状态和/或充电状态，确定不需要与所述终端设备保持A2DP连接。
  9. 根据权利要求7所述的蓝牙耳机，其特征在于，所述处理器在识别所述终端设备的类别时，具体用于：
    若所述通信组件在接收到所述终端设备发送的A2DP连接请求之前未接收到所述终端设备发送的HFP连接请求，确定所述终端设备为IOS设备；
    若所述通信组件在接收到所述终端设备发送的A2DP连接请求之前接收到所述终端设备发送的iPod附件协议连接请求，确定所述终端设备为IOS设备；
    若所述通信组件在接收到所述终端设备发送的A2DP连接请求之前接收到所述终端设备发送的HFP连接请求，确定所述终端设备为非IOS设备。
  10. 一种穿戴设备，其特征在于，包括：穿戴设备主体和权利要求7-9 任一项所述的蓝牙耳机；所述蓝牙耳机与所述穿戴设备主体可分离。
  11. 根据权利要求10所述的穿戴设备，其特征在于，所述穿戴设备为智能手环，所述智能手环包括腕带，所述蓝牙耳机安装在所述腕带内。
  12. 一种连接请求处理装置，其特征在于，包括：确定模块、识别模块和处理模块；其中，
    所述确定模块，用于在接收到终端设备发送的A2DP连接请求时，根据蓝牙耳机当前的状态信息，确定所述蓝牙耳机不需要与所述终端设备保持A2DP连接；
    所述识别模块，用于根据在接收到所述A2DP连接请求之前接收所述终端设备发送的其它连接请求的情况，识别所述终端设备的类别；
    所述处理模块，用于采用与所述终端设备的类别相适配的方式处理所述所述A2DP连接请求，以与所述终端设备保持非A2DP连接状态。
  13. 一种连接请求处理系统，其特征在于，包括：权利要求7-9任一项所述的蓝牙耳机和终端设备；
    所述终端设备，用于向所述蓝牙耳机发送A2DP连接请求以及其它连接请求。
  14. 根据权利13所述的系统，其特征在于，所述蓝牙耳机设置于穿戴设备上，所述穿戴设备包括所述蓝牙耳机和穿戴设备主体，所述蓝牙耳机与所述穿戴设备主体可分离。
  15. 一种存储有计算机程序的计算机可读存储介质，其特征在于，所述计算机程序被一个或多个处理器执行时，可实现权利要求1-6任一项所述的方法的步骤。
PCT/CN2018/105041 2018-05-17 2018-09-11 连接请求处理方法、装置、蓝牙耳机、穿戴设备、系统及存储介质 WO2019218548A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/959,969 US11178707B2 (en) 2018-05-17 2018-09-11 Connection request processing method and apparatus, bluetooth earphone, wearable device, system and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810474442.8 2018-05-17
CN201810474442.8A CN108650668B (zh) 2018-05-17 2018-05-17 连接请求处理方法、蓝牙耳机及穿戴设备

Publications (1)

Publication Number Publication Date
WO2019218548A1 true WO2019218548A1 (zh) 2019-11-21

Family

ID=63756513

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/105041 WO2019218548A1 (zh) 2018-05-17 2018-09-11 连接请求处理方法、装置、蓝牙耳机、穿戴设备、系统及存储介质

Country Status (3)

Country Link
US (1) US11178707B2 (zh)
CN (1) CN108650668B (zh)
WO (1) WO2019218548A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112272373A (zh) * 2020-10-14 2021-01-26 海信视像科技股份有限公司 一种蓝牙设备类型切换方法及显示设备
US11019960B1 (en) 2020-02-03 2021-06-01 Roboburger Enterprises Apparatus and method for preparing cooked food
CN113518336A (zh) * 2021-07-16 2021-10-19 Oppo广东移动通信有限公司 蓝牙连接的提示方法、装置、终端及存储介质

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112823530A (zh) * 2018-10-15 2021-05-18 深圳市欢太科技有限公司 耳机断开连接的方法、相关设备及计算机可读存储介质
CN109495871B (zh) * 2018-12-20 2022-02-18 Oppo广东移动通信有限公司 蓝牙连接控制方法、电子装置及计算机可读存储介质
CN110784846B (zh) * 2019-10-10 2023-06-27 RealMe重庆移动通信有限公司 车载蓝牙设备识别方法、装置、电子设备及存储介质
CN110972022B (zh) 2019-12-25 2020-12-18 歌尔股份有限公司 一种tws耳机及其降低耳机能耗的方法、装置和介质
CN113127190A (zh) 2019-12-31 2021-07-16 华为技术有限公司 占用设备的方法以及电子设备
CN111132117B (zh) * 2020-02-24 2023-04-25 中国第一汽车股份有限公司 一种蓝牙连接方法、装置、车辆及存储介质
CN112995965B (zh) * 2021-01-29 2023-03-28 广东思派康电子科技有限公司 一种蓝牙耳机充电时的控制方法、计算机存储介质、蓝牙耳机
CN113179505B (zh) * 2021-03-10 2023-04-28 歌尔科技有限公司 蓝牙播放装置重启回连方法、蓝牙播放装置和电子设备
CN113473432A (zh) * 2021-07-01 2021-10-01 浙江强脑科技有限公司 智能终端与智能穿戴设备的通信方法、装置、终端及介质
CN114501678B (zh) * 2022-02-24 2023-11-21 喀斯玛汇智(无锡)科技有限公司 通信处理方法及装置

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102331727A (zh) * 2011-08-24 2012-01-25 华为软件技术有限公司 一种蓝牙媒体播放控制方法和相关装置
US20120135686A1 (en) * 2009-08-13 2012-05-31 Zte Corporation Method and system for orderly connection of a bluetooth headset controlled by terminal
CN106488383A (zh) * 2015-08-28 2017-03-08 宇龙计算机通信科技(深圳)有限公司 一种连接蓝牙设备的方法及装置
CN106851530A (zh) * 2016-12-14 2017-06-13 青岛海信电器股份有限公司 一种蓝牙设备自动回连的方法及蓝牙设备
WO2018082335A1 (zh) * 2016-11-07 2018-05-11 中兴通讯股份有限公司 连接蓝牙设备的方法、装置、系统及设备

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9820323B1 (en) * 2016-11-22 2017-11-14 Bose Corporation Wireless audio tethering system

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120135686A1 (en) * 2009-08-13 2012-05-31 Zte Corporation Method and system for orderly connection of a bluetooth headset controlled by terminal
CN102331727A (zh) * 2011-08-24 2012-01-25 华为软件技术有限公司 一种蓝牙媒体播放控制方法和相关装置
CN106488383A (zh) * 2015-08-28 2017-03-08 宇龙计算机通信科技(深圳)有限公司 一种连接蓝牙设备的方法及装置
WO2018082335A1 (zh) * 2016-11-07 2018-05-11 中兴通讯股份有限公司 连接蓝牙设备的方法、装置、系统及设备
CN106851530A (zh) * 2016-12-14 2017-06-13 青岛海信电器股份有限公司 一种蓝牙设备自动回连的方法及蓝牙设备

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11019960B1 (en) 2020-02-03 2021-06-01 Roboburger Enterprises Apparatus and method for preparing cooked food
CN112272373A (zh) * 2020-10-14 2021-01-26 海信视像科技股份有限公司 一种蓝牙设备类型切换方法及显示设备
CN112272373B (zh) * 2020-10-14 2022-03-25 海信视像科技股份有限公司 一种蓝牙设备类型切换方法及显示设备
CN113518336A (zh) * 2021-07-16 2021-10-19 Oppo广东移动通信有限公司 蓝牙连接的提示方法、装置、终端及存储介质

Also Published As

Publication number Publication date
CN108650668B (zh) 2020-02-07
US20210136839A1 (en) 2021-05-06
CN108650668A (zh) 2018-10-12
US11178707B2 (en) 2021-11-16

Similar Documents

Publication Publication Date Title
WO2019218548A1 (zh) 连接请求处理方法、装置、蓝牙耳机、穿戴设备、系统及存储介质
US20210294565A1 (en) Changing companion communication device behavior based on status of wearable device
KR102505264B1 (ko) 무선 오디오 출력 디바이스
US10771908B2 (en) Swapping roles between untethered wirelessly connected devices
US10609198B2 (en) Personal media system including base station and wireless earbud
US10204624B1 (en) False positive wake word
US11178280B2 (en) Input during conversational session
US20170078464A1 (en) System for sound capture and generation via nasal vibration
US20190050195A1 (en) Output provision based on gaze detection
WO2017071159A1 (zh) 一种移动终端的消息提醒方法及系统
US20190019505A1 (en) Sustaining conversational session
US20160253996A1 (en) Activating voice processing for associated speaker
TWI661808B (zh) 生理偵測系統、方法及其穿戴式裝置
CN104216503A (zh) 一种信息处理方法及电子设备
US20200178328A1 (en) Wireless connection establishment between devices
WO2018132948A1 (zh) 一种无线耳机的控制方法和无线耳机

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18918476

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18918476

Country of ref document: EP

Kind code of ref document: A1