WO2017070854A1 - 一种数据同步方法、移动终端及智能穿戴设备 - Google Patents

一种数据同步方法、移动终端及智能穿戴设备 Download PDF

Info

Publication number
WO2017070854A1
WO2017070854A1 PCT/CN2015/092996 CN2015092996W WO2017070854A1 WO 2017070854 A1 WO2017070854 A1 WO 2017070854A1 CN 2015092996 W CN2015092996 W CN 2015092996W WO 2017070854 A1 WO2017070854 A1 WO 2017070854A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
wearable device
mobile terminal
smart wearable
bluetooth
Prior art date
Application number
PCT/CN2015/092996
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 PCT/CN2015/092996 priority Critical patent/WO2017070854A1/zh
Priority to CN201580002060.XA priority patent/CN105917677A/zh
Publication of WO2017070854A1 publication Critical patent/WO2017070854A1/zh

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/06Protocols specially adapted for file transfer, e.g. file transfer protocol [FTP]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/01Protocols
    • H04L67/10Protocols in which an application is distributed across nodes in the network
    • H04L67/1095Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W52/00Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02Power saving arrangements
    • H04W52/0209Power saving arrangements in terminal devices
    • H04W52/0225Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0248Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal dependent on the time of the day, e.g. according to expected transmission activity
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/18Management of setup rejection or failure
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/19Connection re-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W76/00Connection management
    • H04W76/10Connection setup
    • H04W76/14Direct-mode setup
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE 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/00Reducing energy consumption in communication networks
    • Y02D30/70Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a data synchronization method, a mobile terminal, and a smart wearable device.
  • Smart wearable devices such as smart watches and smart wristbands, and smart wearable devices have received extensive attention.
  • Smart wearable devices generally connect and communicate with Bluetooth built into mobile terminals such as mobile phones through built-in Bluetooth.
  • the mobile terminal needs to synchronize data with the smart wearable device, if the Bluetooth is abnormally disconnected, the data synchronization will fail. After that, the mobile terminal will reconnect the smart wearable device through Bluetooth until the data synchronization is successful.
  • the Bluetooth has been in an abnormally disconnected state, the mobile terminal continues to perform Bluetooth reconnection due to data synchronization failure, resulting in faster consumption of the smart wearable device.
  • the embodiments of the present invention provide a data synchronization method, a mobile terminal, and a smart wearable device, which can save power of the smart wearable device.
  • a data synchronization method including:
  • the mobile terminal sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data to the mobile terminal;
  • the mobile terminal when the mobile terminal detects that the data synchronization fails, the mobile terminal records a data tag of the synchronized data in the data, and reconnects the Bluetooth;
  • the mobile terminal sends the data tag to the smart wearable device
  • the mobile terminal determines that the mobile terminal fails to connect with the smart wearable device.
  • the mobile terminal wears smart
  • the device sends a data request command, so that the smart wearable device synchronizes data with the mobile terminal, including:
  • the mobile terminal sends a data request instruction to the smart wearable device and starts counting, so that the smart wearable device returns a data request confirmation command in response to the data request instruction;
  • the mobile terminal determines whether the data request confirmation instruction returned by the smart wearable device is received within a preset length
  • the mobile terminal sends a data synchronization instruction to the smart wearable device, so that the smart wearing device synchronizes data with the mobile terminal;
  • the mobile terminal determines that the data request confirmation is exceeded, and performs the step of sending a data request instruction to the smart wearable device and starting to calculate;
  • the mobile terminal determines that the data request confirmation fails.
  • the mobile terminal when the data synchronization failure is detected, the mobile terminal records the data tag of the synchronized data in the data, and the method further includes:
  • the mobile terminal detects whether the data sent by the smart wearable device is received
  • the mobile terminal confirms that the data synchronization fails.
  • the mobile terminal After detecting the data synchronization failure, the mobile terminal records the data tag of the synchronized data in the data, and after reconnecting the Bluetooth, the method further includes:
  • the mobile terminal determines whether the data is important data
  • the mobile terminal is configured to send the data tag to the smart wearable device, so that the smart wearable device continues to synchronize the data according to the data tag.
  • a data synchronization method including: [0026] the smart wearable device receives a data request instruction sent by the mobile terminal, and synchronizes data with the mobile terminal;
  • the smart wearable device when the smart wearable device detects that the data synchronization fails, the smart wearable device records a data mark of the unsynchronized data in the data, and reconnects the Bluetooth;
  • the smart wearable device when the Bluetooth connection is successfully connected, the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark;
  • the smart wearable device when the Bluetooth connection fails, the smart wearable device performs the step of reconnecting the Bluetooth; [0030] when detecting that the number of failed reconnections of the Bluetooth exceeds a first preset number of times, the smart wearer The device determines that the mobile terminal fails to connect to the smart wearable device.
  • a third aspect of the embodiments of the present invention provides a mobile terminal, including:
  • a first sending unit configured to send a data request instruction to the smart wearable device, to enable the smart wearable device to synchronize data to the mobile terminal;
  • a reconnection unit configured to: when detecting the data synchronization failure, record a data tag of the synchronized data in the data, and reconnect the Bluetooth;
  • a second sending unit configured to send the data tag to the smart wearable device when the reconnecting unit reconnects to the Bluetooth successfully, so that the smart wearable device continues to synchronize according to the data tag. Unsynchronized data in the data;
  • a first triggering unit configured to trigger the reconnecting unit to reconnect the Bluetooth when the reconnecting unit fails to reconnect the Bluetooth
  • the first determining unit is configured to determine that the mobile terminal fails to connect to the smart wearable device when detecting that the number of failed reconnections of the Bluetooth exceeds a first preset number of times.
  • the first sending unit includes
  • a first sending subunit configured to send a data request instruction to the smart wearable device and start counting, so that the smart wearable device returns a data request confirmation command in response to the data request instruction;
  • a determining subunit configured to determine whether the data request confirmation instruction returned by the smart wearable device is received within a preset length
  • a second sending subunit configured to: when the determining subunit determines that the result is yes, Sending a data synchronization instruction to enable the smart wearable device to synchronize data with the mobile terminal;
  • a first determining subunit configured to: when the determining subunit determines that the result is negative, determining that the data request confirmation is over, triggering the first sending unit to send a data request instruction to the smart wearable device and starting Count
  • the second determining subunit is configured to determine that the data request confirmation fails when it is determined that the number of times the data request confirmation is exceeded exceeds a second preset number.
  • the mobile terminal further includes:
  • a detecting unit configured to detect whether the data sent by the smart wearable device is received
  • a second determining unit configured to: when the detection unit detects that the result is negative, confirm that the data synchronization fails
  • the mobile terminal further includes:
  • a determining unit configured to determine whether the data is important data
  • a second triggering unit configured to: when the determining unit determines that the result is ⁇ , and when the reconnecting Bluetooth succeeds, triggering the second sending unit to send the data mark to the smart wearable device, So that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark;
  • a third triggering unit configured to: when the determining unit determines that the result is ⁇ , and when the reconnecting Bluetooth fails, triggering the reconnecting unit to reconnect the Bluetooth until the reconnecting unit is successfully connected; .
  • a fourth aspect of the embodiments of the present invention provides a smart wearable device, including:
  • a receiving unit configured to receive a data request instruction sent by the mobile terminal, and synchronize data with the mobile terminal
  • a reconnection unit configured to: when the smart wearable device detects that the data synchronization fails, record a data mark of the unsynchronized data in the data, and reconnect the Bluetooth;
  • a synchronization unit configured to continue to synchronize the unsynchronized data in the data according to the data mark when the Bluetooth is successfully reconnected;
  • a triggering unit configured to trigger the reconnect unit to restart when the reconnect unit fails to reconnect the Bluetooth Connect to Bluetooth
  • the determining unit is configured to determine that the mobile terminal fails to connect to the smart wearable device when detecting that the number of failed reconnections of the Bluetooth exceeds a first preset number of times.
  • a fifth aspect of the embodiments of the present invention provides a mobile terminal, including a Bluetooth module, a processor, and a memory, where the processor performs the following steps:
  • the processor sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal, including :
  • the method further includes:
  • the method further includes:
  • the Bluetooth device when the smart wearable device fails to synchronize data with the mobile terminal, the Bluetooth device is reconnected.
  • the Bluetooth connection fails, continue to connect to Bluetooth.
  • the Bluetooth connection is no longer reconnected, and the connection between the mobile terminal and the smart wearable device is determined to be unsuccessful. Since reconnecting the Bluetooth greatly consumes the power in the smart wearable device, when the Bluetooth connection fails due to objective reasons (for example, the distance between the mobile terminal and the smart wearable device exceeds the Bluetooth transmission distance ⁇ ), the embodiment of the present invention is implemented. , can save the power of smart wearable devices.
  • FIG. 1 is a schematic diagram of a network architecture of an embodiment of the present invention.
  • FIG. 2 is a flowchart of a data synchronization method according to an embodiment of the present invention.
  • FIG. 3 is a flowchart of another data synchronization method according to an embodiment of the present invention.
  • 5 is a flowchart of another data synchronization method disclosed in an embodiment of the present invention.
  • 6 is a schematic structural diagram of a mobile terminal according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention.
  • FIG. 10 is a schematic structural diagram of a smart wearable device according to an embodiment of the present invention.
  • FIG. 11 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention.
  • the embodiment of the invention provides a data synchronization method, a mobile terminal and a smart wearable device, which can save power of the smart wearable device. The details are described below separately.
  • FIG. 1 is a schematic diagram of a network architecture disclosed in the embodiment of the present invention.
  • a mobile terminal and a smart wearable device may be included, wherein the mobile terminal may be connected to the smart wearable device via Bluetooth.
  • the mobile terminal may include a mobile phone, a tablet, a personal digital assistant (PDA), and a mobile internet device (Mobile Internet Device).
  • PDA personal digital assistant
  • Mobile Internet Device Mobile Internet Device
  • the smart wearable device may include various types of wearable devices, such as a smart wristband, a smart watch, and smart glasses, which are not limited in the embodiment of the present invention.
  • a smart wristband such as a smart wristband, a smart watch, and smart glasses, which are not limited in the embodiment of the present invention.
  • the power of the smart wearable device can be saved.
  • the embodiment of the present invention discloses a data synchronization method, as shown in FIG. 2
  • FIG. 2 is a flowchart of a data synchronization method according to an embodiment of the present invention. As shown in FIG. 2, the data synchronization method described in this embodiment includes:
  • Step S201 The mobile terminal sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal.
  • the mobile terminal when the mobile terminal needs to synchronize data in the smart wearable device, the mobile terminal sends a data request instruction to the smart wearable device, and the smart wearable device responds to the data request command to synchronize data with the mobile terminal.
  • the mobile terminal and the smart wearable device need to connect through Bluetooth.
  • step S201 may include:
  • the mobile terminal sends a data request instruction to the smart wearable device and starts counting, so that the smart wearable device responds to the data request instruction and returns a data request confirmation command;
  • the mobile terminal determines whether the data request confirmation command returned by the smart wearable device is received within the preset length; [0098] if yes, the mobile terminal sends a data synchronization instruction to the smart wearable device to synchronize the smart wearable device with the mobile terminal Data
  • the mobile terminal determines that the data request confirmation is exceeded, and performs a step of transmitting a data request command to the smart wearable device and starting the counting;
  • the mobile wear device after the mobile terminal sends a data request instruction to the smart wearable device, the mobile wear device starts to calculate, and if the smart wear device receives the data request command, the smart wearable device moves to the mobile terminal within the preset length.
  • the terminal returns a data request confirmation command; if the smart wear device does not receive the data request command, the smart wearable device cannot return a data request confirmation command to the mobile terminal within a preset length.
  • the mobile terminal If the mobile terminal receives the data request confirmation command returned by the smart wearable device within the preset length, the mobile terminal sends a data synchronization instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal; if the mobile terminal is preset If the data request confirmation command returned by the smart wearable device is not received within the length, the mobile terminal determines that the data request confirmation is exceeded, and the mobile terminal continues to send a data request command to the smart wearable device and starts counting.
  • the preset length can be any length, for example: 100ms, 200ms, 300ms, 400ms, 500ms, etc. Preferably, the preset length is 300ms.
  • the mobile terminal determines that the data request confirmation fails.
  • the second preset number can be set to any number of times, for example, 1 time, 2 times, 3 times, 4 times, 5 times, 6 times, 7 times, 8 times, 9 times, 10 times, etc., preferably, The second preset number is set to 6 times.
  • the mobile terminal determines that the data request confirmation fails.
  • the mobile terminal when detecting that the number of times the data request confirmation is exceeded exceeds the second preset number, the mobile terminal no longer sends a data request instruction to the smart wearable device, and the mobile terminal determines that the data request confirmation fails, and avoids detecting when After the data request confirmation command returned by the smart wearable device is not received within the preset length, the mobile terminal continuously sends a data request command to the smart wearable device and starts counting, thereby causing great consumption of power in the smart wearable device, thereby It can save the power of smart wearable devices.
  • Step S202 When the mobile terminal detects that the data synchronization fails, the mobile terminal records the data tag of the synchronized data in the data, and reconnects the Bluetooth.
  • the mobile terminal after the smart wearable device synchronizes data with the mobile terminal, if the mobile terminal detects that the data synchronization fails, the mobile terminal records the data mark of the synchronized data in the data, and reconnects the Bluetooth.
  • the data that the smart wearable device synchronizes with the mobile terminal may include multiple pieces of data, each of which carries a unique data mark.
  • the mobile terminal When the mobile terminal detects that the data synchronization fails, the mobile terminal records the data mark of the synchronized data in the plurality of pieces of data. And reconnect Bluetooth.
  • Step S203 After reconnecting the Bluetooth successfully, the mobile terminal sends a data mark to the smart wearable device, so that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark.
  • the mobile terminal when the Bluetooth connection is successfully re-established, the mobile terminal sends the data tag of the synchronized data to the smart wearable device, and the smart wearable device continues to synchronize the unsynchronized data in the data according to the data tag of the synchronized data.
  • Step S204 When the Bluetooth connection reconnection fails, step S202 is performed.
  • the mobile terminal when the Bluetooth connection fails, the mobile terminal records the data tag of the synchronized data in the data, and reconnects the Bluetooth.
  • Step S205 When it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the mobile terminal determines that the connection between the mobile terminal and the smart wearable device fails.
  • the mobile terminal counts the number of times the Bluetooth connection fails to be reconnected.
  • the mobile terminal determines that the mobile terminal fails to connect with the smart wearable device.
  • the first preset number of times may be preset by the user, and the first preset number of times may be set to any number of times, for example, 1 time, 2 times, 3 times, 4 times, 5 times, etc., preferably, the first preset number of times Set to 3 times, when it is detected that the number of times of reconnecting Bluetooth fails more than 3 times, the mobile terminal determines that the mobile terminal fails to connect with the smart wearable device.
  • Embodiments of the present invention when the number of failed attempts to reconnect Bluetooth is detected After the first preset number of times, the mobile terminal no longer reconnects to the Bluetooth, and determines that the mobile terminal fails to connect with the smart wearable device, thereby avoiding the failure of the mobile terminal to continuously reconnect the Bluetooth after detecting the failure to reconnect the Bluetooth. Wear power in the device, which saves smart wearable devices
  • the mobile terminal sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal; when the mobile terminal detects that the data synchronization fails, the mobile terminal records the synchronized data in the data.
  • Data tag reconnect Bluetooth; when reconnecting Bluetooth successfully, the mobile terminal sends a data tag to the smart wearable device, so that the smart wear device continues to synchronize the unsynchronized data in the data according to the data tag; when the Bluetooth connection fails, the mobile terminal performs The step of reconnecting the Bluetooth; when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the mobile terminal determines that the connection between the mobile terminal and the smart wearable device fails.
  • the mobile terminal when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the mobile terminal does not reconnect the Bluetooth, and determines that the connection between the mobile terminal and the smart wearable device fails, thereby avoiding failure to detect reconnection of the Bluetooth. ⁇ , the continuous reconnection of the mobile terminal by the mobile terminal greatly consumes the power in the smart wearable device, thereby saving the power of the smart wearable device.
  • FIG. 3 is a flowchart of another data synchronization method according to an embodiment of the present invention.
  • the data synchronization method described in this embodiment includes:
  • Step S301 The mobile terminal sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal.
  • step S301 may include:
  • the mobile terminal sends a data request instruction to the smart wearable device and starts counting, so that the smart wearable device responds to the data request instruction and returns a data request confirmation command;
  • the mobile terminal determines whether a data request confirmation command returned by the smart wearable device is received within the preset length; [0116] if yes, the mobile terminal sends a data synchronization instruction to the smart wearable device to synchronize the smart wearable device with the mobile terminal Data
  • the mobile terminal determines that the data request confirmation is exceeded, and performs a step of sending a data synchronization instruction to the smart wearable device and starting to calculate; [0118] When it is detected that the number of times the determination data request confirmation is exceeded exceeds the second preset number of times, the mobile terminal determines that the data request confirmation fails.
  • Step S302 the mobile terminal detects whether the data sent by the smart wearable device is received, and if yes, the mobile terminal confirms that the data synchronization is successful; if not, the mobile terminal confirms that the data synchronization fails, step S303 is performed.
  • the smart wear device after the mobile terminal sends the data request instruction to the smart wearable device, if the smart wear device receives the data request instruction, the smart wear device synchronizes the data with the mobile terminal in response to the data request instruction, when the data is synchronized. Upon completion, the mobile terminal confirms that the data synchronization is successful. When the data is not synchronized, the mobile terminal records the data tag of the synchronized data in the data, and reconnects the Bluetooth.
  • the mobile terminal detects whether the data sent by the smart wearable device is received within a preset length (eg, 300 ms), and if yes, the mobile terminal confirms that the data synchronization is successful; if not, the mobile terminal confirms that the data synchronization fails, step S303 is performed. .
  • whether the data synchronization is successful is determined by the mobile terminal detecting whether the data sent by the smart wearable device is received.
  • Step S303 The mobile terminal records the data tag of the synchronized data in the data, and reconnects the Bluetooth.
  • Step S304 After reconnecting the Bluetooth successfully, the mobile terminal sends a data mark to the smart wearable device, so that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark.
  • Step S305 When the Bluetooth connection fails, step S303 is performed.
  • Step S306 When it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the mobile terminal determines that the connection between the mobile terminal and the smart wearable device fails.
  • the mobile terminal sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal; and the mobile terminal detects whether the data sent by the smart wearable device is received.
  • the mobile terminal confirms that the data synchronization is successful; if not, the mobile terminal confirms that the data synchronization fails, the mobile terminal records the data tag of the synchronized data in the data, and reconnects the Bluetooth; when the Bluetooth is successfully reconnected, the mobile terminal goes to the smart wearable device Sending a data tag to enable the smart wearable device to continue synchronizing the unsynchronized data in the data according to the data tag; when the reconnecting of the Bluetooth fails, the mobile terminal performs the step of reconnecting the Bluetooth; when detecting that the number of failed Bluetooth reconnections exceeds the first preset The number of times, the mobile terminal determines that the mobile terminal fails to connect with the smart wearable device.
  • the mobile terminal when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the mobile terminal does not reconnect the Bluetooth. It is determined that the connection between the mobile terminal and the smart wearable device fails, and when the failure to reconnect the Bluetooth is detected, the mobile terminal continuously reconnects the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the smart wearable device power.
  • FIG. 4 is a flowchart of another data synchronization method according to an embodiment of the present invention.
  • the data synchronization method described in this embodiment includes:
  • Step S401 The mobile terminal sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal.
  • step S401 may include:
  • the mobile terminal sends a data request instruction to the smart wearable device and starts counting, so that the smart wearable device responds to the data request instruction and returns a data request confirmation command;
  • the mobile terminal determines whether a data request confirmation command returned by the smart wearable device is received within the preset length; [0131] if yes, the mobile terminal sends a data synchronization instruction to the smart wearable device to synchronize the smart wearable device with the mobile terminal Data
  • the mobile terminal determines that the data request confirmation is exceeded, and performs a step of transmitting a data synchronization instruction to the smart wearable device and starting the counting;
  • the mobile terminal determines that the data request confirmation has failed.
  • Step S402 the mobile terminal detects whether the data sent by the smart wearable device is received, and if yes, the mobile terminal confirms that the data synchronization is successful; if not, the mobile terminal confirms that the data synchronization fails, step S403 is performed.
  • Step S403 The mobile terminal records the data tag of the synchronized data in the data, and reconnects the Bluetooth.
  • Step S404 The mobile terminal determines whether the data is important data. If yes, step S405 is performed, and if no, step S406 is performed.
  • Step S405 When the Bluetooth connection fails, the mobile terminal reconnects the Bluetooth until the Bluetooth connection succeeds; when the Bluetooth connection is successfully completed, step S406 is performed.
  • the important data may be an important data type preset by the user.
  • the data is determined to be important data.
  • Important data can be heart rate data (eg, when the user wearing the smart wearable device is a heart disease patient, heart rate data can be set as important data), body temperature data, and the like.
  • the mobile terminal determines that the data is important data, if the Bluetooth connection is successful, the mobile terminal sends a data mark to the smart wearable device, so that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark; if the Bluetooth connection fails, the mobile terminal fails. Reconnect Bluetooth until the Bluetooth connection is successful.
  • the number of times of reconnecting the Bluetooth may not be limited, and the important data in the smart wearable device is synchronized to the mobile terminal as soon as possible, and the important data in the smart wearable device is synchronized to the mobile device. In the terminal.
  • Step S406 After reconnecting the Bluetooth successfully, the mobile terminal sends a data mark to the smart wearable device, so that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark.
  • Step S407 When the Bluetooth connection fails, step S403 is performed.
  • Step S408 When it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the mobile terminal determines that the connection between the mobile terminal and the smart wearable device fails.
  • the mobile terminal sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal; and the mobile terminal detects whether the data sent by the smart wearable device is received.
  • the mobile terminal determines whether the data is important data, and if so, when re After the connection to the Bluetooth fails, the mobile terminal reconnects the Bluetooth until the Bluetooth connection is successful; when the Bluetooth connection is successfully connected, the mobile terminal sends a data mark to the smart wearable device, so that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark; When the reconnection of the Bluetooth fails, the mobile terminal performs the step of reconnecting the Bluetooth; when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the mobile terminal determines that the connection of the mobile terminal with the smart wearable device fails.
  • the mobile terminal when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the mobile terminal does not reconnect the Bluetooth, and determines that the connection between the mobile terminal and the smart wearable device fails, thereby avoiding failure to detect reconnection of the Bluetooth. ⁇ , the mobile terminal continuously reconnects to the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the power of the smart wearable device.
  • the mobile terminal judges that the data is important data, if the Bluetooth connection fails, the mobile terminal fails. Reconnect Bluetooth repeatedly until the Bluetooth connection is successful, ensuring important data and defects in the smart wearable device Sync to the mobile terminal.
  • FIG. 5 is a flowchart of another data synchronization method according to an embodiment of the present invention.
  • the data synchronization method described in this embodiment includes:
  • Step S501 The smart wearable device receives a data request instruction sent by the mobile terminal, and synchronizes data with the mobile terminal.
  • the mobile terminal when the mobile terminal needs to synchronize the data in the smart wearable device, the mobile terminal sends a data request instruction to the smart wearable device, and the smart wearable device synchronizes the data with the data request instruction to the mobile terminal.
  • the smart wearable device Before the smart wearable device receives the data request command sent by the mobile terminal, the mobile terminal and the smart wearable device need to connect through Bluetooth.
  • Step S502 When the smart wearable device detects that the data synchronization fails, the smart wearable device records the data tag of the unsynchronized data in the data, and reconnects the Bluetooth.
  • the smart wearable device after the smart wearable device synchronizes data with the mobile terminal, when the smart wearable device detects that the data synchronization fails, the smart wearable device records the data mark of the unsynchronized data in the data, and reconnects the Bluetooth.
  • the data that the smart wearable device synchronizes with the mobile terminal may include multiple pieces of data, each of which carries a unique data tag.
  • the mobile terminal records the data tag of the unsynchronized data in the plurality of pieces of data. , and reconnect Bluetooth.
  • Step S503 When the Bluetooth connection is successfully re-established, the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark.
  • the smart wearable device when the Bluetooth connection is successfully re-connected, the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark of the unsynchronized data in the data.
  • Step S504 When the Bluetooth connection fails, step S502 is performed.
  • the smart wearable device when the Bluetooth connection fails, the smart wearable device records the data tag of the unsynchronized data in the data, and reconnects the Bluetooth.
  • Step S505 When it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the smart wearable device determines that the connection between the mobile terminal and the smart wearable device fails.
  • the smart wearable device counts the number of times that the Bluetooth connection fails to be reconnected. When it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number, the smart wearable device determines the mobile terminal and the smart device. The wearable device connection failed.
  • the first preset number of times may be preset by the user, and the first preset number of times may be set to any number of times, for example, 1 time, 2 times, 3 times, 4 times, 5 times, etc., preferably, the first preset number of times Set to 3 times, when it is detected that the number of times of reconnecting Bluetooth fails more than 3 times, the smart wearable device determines that the mobile terminal fails to connect with the smart wearable device.
  • the smart wearable device when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the smart wearable device does not reconnect the Bluetooth, determining that the mobile terminal fails to connect with the smart wearable device, and avoids detecting that the Bluetooth is reconnected. After the failure, the smart wearable device continuously reconnects to the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the smart wearable device power.
  • the smart wearable device receives the data request command sent by the mobile terminal, and synchronizes the data with the mobile terminal; when the smart wear device detects the data synchronization failure, the smart wearable device records the data mark of the unsynchronized data in the data.
  • Reconnect Bluetooth when the Bluetooth connection is successfully connected, the smart wearable device continues to synchronize the unsynchronized data in the data according to the data tag; when the Bluetooth connection fails, the smart wearable device performs the step of reconnecting the Bluetooth; when detecting the reconnection of the Bluetooth failed After the number of times exceeds the first preset number, the smart wearable device determines that the mobile terminal fails to connect with the smart wearable device.
  • the smart wearable device when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the smart wearable device does not reconnect the Bluetooth, determining that the mobile terminal fails to connect with the smart wearable device, and avoids detecting that the Bluetooth is reconnected. After the failure, the smart wearable device continuously reconnects to the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the smart wearable device power.
  • the embodiment of the present invention discloses a mobile terminal, as shown in FIG.
  • FIG. 6 is a schematic structural diagram of a mobile terminal disclosed in the embodiment of the present invention. As shown in FIG. 6, the mobile terminal described in this embodiment includes a first sending unit 601, a reconnecting unit 602, a second sending unit 603, a first triggering unit 604, and a first determining unit 605, where:
  • the first sending unit 601 is configured to send a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal.
  • FIG. 7 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention.
  • the first sending unit 601 may include:
  • the first sending subunit 6101 is configured to send a data request instruction to the smart wearable device and start counting, so that the smart wearable device returns a data request confirmation command in response to the data request instruction;
  • the determining subunit 6102 is configured to determine whether a data request confirmation instruction returned by the smart wearable device is received within the preset length
  • the second sending subunit 6103 is configured to: when the determining subunit 6102 determines that the result is yes, send a data synchronization instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal;
  • the first determining subunit 6104 is configured to: when the determining subunit 6102 determines that the result is negative, determining that the data request acknowledges the super buffer, triggering the first sending subunit 6101 to send a data request instruction to the smart wearable device, and starting to calculate ;
  • the second determining subunit 6105 is configured to determine that the data request confirmation fails when it is detected that the number of times the data request confirmation is exceeded exceeds the second preset number.
  • the determining subunit 6102 determines whether the data returned by the smart wearable device is received within the preset length. Requesting a confirmation command, if the smart wearable device receives the data request command, the smart wearable device returns a data request confirmation command to the mobile terminal within a preset length; if the smart wear device does not receive the data request command, Within a long period of time, the smart wearable device cannot return a data request confirmation command to the mobile terminal.
  • the second sending subunit 6103 sends a data synchronization instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal; If the terminal does not receive the data request confirmation command returned by the smart wearable device within the preset length, the first determining subunit 6104 determines that the data request confirmation is exceeded, and the mobile terminal continues to send the data request command to the smart wearable device and starts counting.
  • the preset length can be any length, for example: 100ms, 200ms, 300ms, 400ms, 500ms, etc. Preferably, the preset length is 300ms.
  • the second determining subunit 6105 determines that the data request confirmation has failed.
  • the second preset number can be set to any number of times, for example, 1 time, 2 times, 3 times, 4 times, 5 times, 6 times, 7 times, 8 times, 9 times, 10 times, etc., preferably, The second preset number is set to 6 times, when the number of times the data request confirmation is exceeded is detected. After 6 times, the second determination subunit 6105 determines that the data request confirmation has failed.
  • the first sending subunit 610 1 when it is detected that the number of times the data request confirmation is exceeded exceeds the second preset number, the first sending subunit 610 1 no longer sends a data request instruction to the smart wearable device, and the second determining subunit 6105 determines The data request confirmation fails, and when the data request confirmation command returned by the smart wearable device is not received within the preset length, the first sending subunit 6101 continuously sends a data request command to the smart wearable device and starts counting ⁇ Lost the consumption of power in the smart wearable device, thus saving the smart wearable device
  • the reconnection unit 602 is configured to: when the data synchronization failure is detected, record the data tag of the synchronized data in the data, and reconnect the Bluetooth.
  • the reconnection unit 602 After the smart wearable device synchronizes data with the mobile terminal, if the mobile terminal detects that the data synchronization fails, the reconnection unit 602 records the data tag of the synchronized data in the data, and reconnects the Bluetooth.
  • the data synchronized by the smart wearable device to the mobile terminal may include a plurality of pieces of data, each of which carries a unique data tag.
  • the reconnection unit 602 records the data of the synchronized data in the plurality of pieces of data. Mark, and reconnect Bluetooth.
  • the second sending unit 603 is further configured to: when the reconnecting unit 602 reconnects the Bluetooth successfully, send a data tag to the smart wearable device, so that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data tag.
  • the second sending unit 603 sends the data tag of the synchronized data to the smart wearable device, and the smart wear device continues to synchronize the data according to the data tag of the synchronized data.
  • the data is not synchronized.
  • the first triggering unit 604 is configured to trigger the reconnection unit 60 2 to reconnect the Bluetooth when the reconnection unit 602 fails to reconnect the Bluetooth.
  • the reconnection unit 602 when the reconnection unit 602 fails to reconnect the Bluetooth, the reconnection unit 602 is triggered to record the data tag of the synchronized data in the data, and the Bluetooth is reconnected.
  • the first determining unit 605 is configured to determine that the mobile terminal fails to connect to the smart wearable device when detecting that the reconnection unit 602 fails to reconnect the Bluetooth for more than the first preset number of times.
  • the mobile terminal counts the number of times the Bluetooth connection fails to be reconnected.
  • the first determining unit 605 determines that the mobile terminal and the smart wearer Wearing a device connection failed.
  • the first preset number of times may be preset by the user, and the first preset number of times may be set to any number of times, for example, 1 time, 2 times, 3 times, 4 times, 5 times, etc., preferably, the first preset number of times
  • the first determining unit 605 determines that the mobile terminal fails to connect with the smart wearable device.
  • the reconnection unit 602 when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the reconnection unit 602 does not reconnect the Bluetooth, and the first determining unit 605 determines that the connection between the mobile terminal and the smart wearable device fails, thereby avoiding When it is detected that the reconnection of the Bluetooth fails, the reconnection unit 602 continuously reconnects the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the smart wearable device power.
  • the first sending unit 601 sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal; when the mobile terminal detects that the data synchronization fails, the reconnect unit 602 records the data.
  • the data tag of the synchronized data is reconnected to the Bluetooth; when the Bluetooth is successfully reconnected, the second sending unit 603 sends a data tag to the smart wearable device, so that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data tag;
  • the first trigger unit 604 triggers the reconnection unit 602 to reconnect the Bluetooth; when it detects that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the first determining unit 605 determines that the mobile terminal is connected to the smart wearable device. failure.
  • the reconnection unit 602 when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the reconnection unit 602 does not reconnect the Bluetooth, and the first determining unit 605 determines that the connection between the mobile terminal and the smart wearable device fails, thereby avoiding When it is detected that the reconnection of the Bluetooth fails, the reconnection unit 602 continuously reconnects the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the smart wearable device power.
  • FIG. 8 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention.
  • the mobile terminal described in this embodiment includes a first sending unit 601, a reconnecting unit 602, a second sending unit 603, a first triggering unit 604, and a first determining unit, which are described in FIG.
  • a detection unit 606 and a second determination unit 607 are further included, wherein:
  • the detecting unit 606 is configured to detect whether data sent by the smart wearable device is received.
  • the second determining unit 607 is configured to confirm that the data synchronization fails when the detection unit 606 detects that the result is negative.
  • the detecting unit 606 detects whether the data sent by the smart wearable device is received, and if not, the second determining unit 60 7 Confirm that the data synchronization failed.
  • the detecting unit 606 detects whether the data sent by the smart wearable device is received within a preset length (eg, 300 ms), and if yes, the second determining unit 607 confirms that the data synchronization is successful; if not, the second determining unit 607 confirms the data. If the synchronization fails, the trigger reconnection unit 602 records the data tag of the synchronized data in the data, and reconnects the Bluetooth.
  • the embodiment of the present invention can detect whether the data synchronization is successful by detecting whether the data sent by the smart wearable device is received by the detecting unit 060.
  • the first sending unit 601 sends a data request instruction to the smart wearable device, so that the smart wearable device synchronizes data with the mobile terminal; the detecting unit 606 detects whether the data sent by the smart wearable device is received, and if so, Then, the second determining unit 607 confirms that the data synchronization is successful; if not, the second determining unit 607 confirms that the data synchronization has failed, and when the second determining unit 607 confirms that the data synchronization has failed, the reconnection unit 620 records the data tag of the synchronized data in the data.
  • the second sending unit 603 sends a data mark to the smart wearable device, so that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark; when the Bluetooth connection fails, the first The triggering unit 604 triggers the reconnection unit 602 to reconnect the Bluetooth; when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the first determining unit 605 determines that the mobile terminal fails to connect with the smart wearable device.
  • the reconnection unit 602 when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the reconnection unit 602 does not reconnect the Bluetooth, and the first determining unit 605 determines that the connection between the mobile terminal and the smart wearable device fails, and avoids When it is detected that the reconnection of the Bluetooth fails, the reconnection unit 602 continuously reconnects the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the smart wearable device power.
  • FIG. 9 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention.
  • the mobile terminal described in this embodiment includes the first sending unit 601, the reconnecting unit 602, the second sending unit 603, the first triggering unit 604, and the first determining unit, which are described in FIG. 605.
  • the detecting unit 606 and the second determining unit 607 further include a determining unit 608, a second triggering unit 609, and a third triggering unit 610, where:
  • the determining unit 608 is configured to determine whether the data is important data.
  • the second triggering unit 609 is configured to: when the determining unit 608 determines that the result is ⁇ , and when the Bluetooth connection is successfully connected, triggering the second sending unit 603 to send the data mark to the smart wearable device, so that the smart wearable device according to the data The tag continues to synchronize unsynchronized data in the data.
  • the third triggering unit 610 is configured to: when the determining unit 608 determines that the result is ⁇ , and when the Bluetooth connection fails, the trigger reconnection unit 602 reconnects the Bluetooth until the reconnection unit 602 is successfully connected.
  • the important data may be an important data type preset by the user, when the determining unit
  • the 608 determines the data type attribution and the important data type, and determines the data as important data.
  • the important data may be heart rate data (for example, when the user wearing the smart wearable device is a heart patient, the heart rate data may be set. For important data), body temperature data, etc.
  • the second triggering unit 609 triggers the second sending unit 603 to send a data mark to the smart wearable device, so that the smart wearable device continues to synchronize the data according to the data mark.
  • the third trigger unit 610 triggers the reconnection unit 602 to reconnect the Bluetooth until the reconnection unit 602 is successfully connected.
  • the number of times of reconnecting the Bluetooth may not be limited, and the important data in the smart wearable device is synchronized to the mobile terminal as soon as possible, and the important data in the smart wearable device is synchronized to the mobile device. In the terminal.
  • the first sending unit 601 sends a data request instruction to the smart wearable device to enable the smart wearable device to synchronize data with the mobile terminal; the detecting unit 606 detects whether the data sent by the smart wearable device is received, and if so, Then, the second determining unit 607 confirms that the data synchronization is successful; if not, the second determining unit 607 confirms that the data synchronization has failed, and when the second determining unit 607 confirms that the data synchronization has failed, the reconnection unit 620 records the data tag of the synchronized data in the data. Re-connecting the Bluetooth; the determining unit 608 determines whether the data is important data.
  • the third triggering unit 610 triggers the reconnecting unit 602 to reconnect the Bluetooth until the Bluetooth connection is successful; when the Bluetooth connection is successfully restored ⁇
  • the second sending unit 603 sends a data mark to the smart wearable device, so that the smart wearable device continues to synchronize the unsynchronized data in the data according to the data mark; when the Bluetooth connection fails, the first trigger unit 604 triggers the reconnect unit 602 to reconnect the Bluetooth.
  • the first determination unit 605 determines that the mobile device and the smart wearable device connection failure.
  • the reconnection unit 602 when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the reconnection unit 602 does not reconnect the Bluetooth, and the first determining unit 605 determines that the connection between the mobile terminal and the smart wearable device fails, thereby avoiding When it is detected that the reconnection of the Bluetooth fails, the reconnection unit 602 continuously reconnects the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the smart wearable device power.
  • FIG. 10 is a schematic structural diagram of a smart wearable device disclosed in an embodiment of the present invention.
  • the smart wearable device described in this embodiment includes a receiving unit 1001, a reconnecting unit 1002, a synchronizing unit 1003, a triggering unit 1004, and a determining unit 1005, where:
  • the receiving unit 1001 is configured to receive a data request instruction sent by the mobile terminal, and synchronize data with the mobile terminal.
  • the mobile terminal when the mobile terminal needs to synchronize the data in the smart wearable device, the mobile terminal sends a data request instruction to the smart wearable device, and the receiving unit 1001 receives the data request command sent by the mobile terminal, and synchronizes the data with the mobile terminal. . Before the receiving unit 1001 receives the data request command sent by the mobile terminal, the mobile terminal and the smart wearable device need to be connected through Bluetooth.
  • the reconnection unit 1002 is configured to: when the smart wearable device detects that the data synchronization fails, record the data tag of the unsynchronized data in the data, and reconnect the Bluetooth.
  • the reconnect unit 1002 records the data mark of the unsynchronized data in the data, and reconnects the Bluetooth.
  • the data that the smart wearable device synchronizes with the mobile terminal may include multiple pieces of data, each of which carries a unique data tag.
  • the reconnection unit 1002 records the unsynchronized data in the plurality of pieces of data. Data tag, and reconnect Bluetooth.
  • the synchronization unit 1003 is configured to continue to synchronize the unsynchronized data in the data according to the data mark when the Bluetooth connection is successfully re-established.
  • the synchronization unit 1003 when the Bluetooth connection is successfully re-established, the synchronization unit 1003 continues to synchronize the unsynchronized data in the data according to the data tag of the unsynchronized data in the data.
  • the trigger unit 1004 is configured to trigger the reconnection unit 1002 to reconnect the Bluetooth when the reconnection unit 1002 fails to reconnect the Bluetooth.
  • the reconnection unit 1002 when the reconnection unit 1002 fails to reconnect the Bluetooth, the reconnection unit 1002 is triggered to record the data tag of the unsynchronized data in the data, and the Bluetooth is reconnected.
  • the determining unit 1005 is configured to determine that the connection between the mobile terminal and the smart wearable device fails when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times.
  • the smart wearable device counts the number of times the Bluetooth connection fails to be reconnected.
  • the determining unit 1005 determines the mobile terminal and the smart device.
  • the first preset number of times may be preset by the user, and the first preset number of times may be set to any number of times, for example, 1 time, 2 times, 3 times, 4 times, 5 times, etc., preferably, the first preset number of times Set to 3 times, when it is detected that the number of times of reconnecting Bluetooth fails more than 3 times, the determining unit 1005 determines that the mobile terminal fails to connect with the smart wearable device.
  • the reconnection unit 1002 when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the reconnection unit 1002 does not reconnect the Bluetooth, and the determining unit 1005 determines that the connection between the mobile terminal and the smart wearable device fails, and avoids detecting After the failure to reconnect the Bluetooth, the reconnection unit 1002 continuously reconnects the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the power of the smart wearable device.
  • the receiving unit 1001 receives the data request instruction sent by the mobile terminal, and synchronizes data with the mobile terminal.
  • the reconnection unit 1002 records the data of the unsynchronized data in the data. Mark, reconnect Bluetooth; when reconnecting Bluetooth successfully, sync unit 1 003 continues to synchronize unsynchronized data in data according to data mark; when reconnecting Bluetooth fails, trigger unit 1004 triggers reconnect unit 1002 to reconnect Bluetooth; when detected When the number of times of reconnecting the Bluetooth fails more than the first preset number of times, the determining unit 1005 determines that the connection of the mobile terminal with the smart wearable device fails.
  • the reconnection unit 1002 when it is detected that the number of failed reconnections of the Bluetooth exceeds the first preset number of times, the reconnection unit 1002 does not reconnect the Bluetooth, and the determining unit 1005 determines that the connection between the mobile terminal and the smart wearable device fails, and avoids detecting After the failure to reconnect the Bluetooth, the reconnection unit 1002 continuously reconnects the Bluetooth, which greatly consumes the power in the smart wearable device, thereby saving the power of the smart wearable device.
  • FIG. 11 is a schematic structural diagram of another mobile terminal according to an embodiment of the present invention. As shown
  • the mobile terminal includes a Bluetooth module 2001, a processor 2002, and a storage device 2003, wherein the processor 2002 respectively connects the memory 2003 and the Bluetooth module 2001 through a bus, wherein the memory 2003 is used to store a data synchronization program, and the processor 2002 is used to read the data synchronization program stored in the memory 2003 to perform the following operations:
  • the data tag is sent to the smart wearable device to make the smart wearable device root According to the data tag, the unsynchronized data in the data is continuously synchronized;
  • the processor 2002 sends a data request instruction to the smart wearable device to enable the smart wearable device to synchronize data with the mobile terminal, including:
  • the processor 2002 when the processor 2002 detects that the data synchronization has failed, the data tag of the synchronized data in the data is recorded, and before the Bluetooth is reconnected, the following operations are also performed:
  • the processor 2002 when the processor 2002 detects that the data synchronization has failed, the data tag of the synchronized data in the data is recorded, and after reconnecting the Bluetooth, the following operations are also performed:
  • a program to instruct related hardware can be completed by a program to instruct related hardware, and the program can be stored in a computer readable storage medium, the storage medium.
  • a computer readable storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or a compact disc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephone Function (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明实施例公开了一种数据同步方法、移动终端及智能穿戴设备,该方法包括:移动终端向智能穿戴设备发送数据请求指令,以使智能穿戴设备向移动终端同步数据;当移动终端检测到数据同步失败时,移动终端记录数据中已同步数据的数据标记,重新连接蓝牙;当重新连接蓝牙成功时,移动终端向智能穿戴设备发送数据标记,以使智能穿戴设备根据数据标记继续同步数据中未同步数据;当重新连接蓝牙失败时,移动终端执行重新连接蓝牙的步骤;当检测到重新连接蓝牙失败的次数超过第一预设次数时,移动终端确定移动终端与智能穿戴设备连接失败。实施本发明实施例,可以节省智能穿戴设备电量。

Description

一种数据同步方法、 移动终端及智能穿戴设备
[0001] 技术领域
[0002] 本发明涉及通信技术领域, 具体涉及一种数据同步方法、 移动终端及智能穿戴 设备。
[0003] 背景技术
[0004] 近年来, 越来越多的用户使用智能手表、 智能手环等智能穿戴设备, 智能穿戴 设备得到了广泛的关注。 智能穿戴设备一般通过内置的蓝牙与手机等移动终端 内置的蓝牙进行连接和通信。 当移动终端需要与智能穿戴设备同步数据吋, 若 蓝牙异常断幵吋, 会导致数据同步失败, 此吋, 移动终端会通过蓝牙重新连接 智能穿戴设备, 直至数据同步成功为止。 当蓝牙一直处于异常断幵状态吋, 由 于数据同步失败, 移动终端会持续进行蓝牙重连, 导致智能穿戴设备电量消耗 较快。
[0005] 发明内容
[0006] 本发明实施例提供一种数据同步方法、 移动终端及智能穿戴设备, 可以节省智 能穿戴设备电量。
[0007] 本发明实施例第一方面, 提供了一种数据同步方法, 包括:
[0008] 移动终端向智能穿戴设备发送数据请求指令, 以使所述智能穿戴设备向所述移 动终端同步数据;
[0009] 当所述移动终端检测到所述数据同步失败吋, 所述移动终端记录所述数据中已 同步数据的数据标记, 重新连接蓝牙;
[0010] 当重新连接蓝牙成功吋, 所述移动终端向所述智能穿戴设备发送所述数据标记
, 以使所述智能穿戴设备根据所述数据标记继续同步所述数据中未同步数据;
[0011] 当重新连接蓝牙失败吋, 所述移动终端执行所述重新连接蓝牙的步骤;
[0012] 当检测到所述重新连接蓝牙失败的次数超过第一预设次数吋, 所述移动终端确 定所述移动终端与所述智能穿戴设备连接失败。
[0013] 在本发明实施例第一方面的第一种可能的实现方式中, 所述移动终端向智能穿 戴设备发送数据请求指令, 以使所述智能穿戴设备向所述移动终端同步数据, 包括:
[0014] 所述移动终端向智能穿戴设备发送数据请求指令并幵始计吋, 以使所述智能穿 戴设备响应所述数据请求指令返回数据请求确认指令;
[0015] 所述移动终端判断在预设吋长内是否收到所述智能穿戴设备返回的所述数据请 求确认指令;
[0016] 若是, 所述移动终端向所述智能穿戴设备发送数据同步指令, 以使所述智能穿 戴设备向移动终端同步数据;
[0017] 若否, 所述移动终端确定所述数据请求确认超吋, 执行所述向智能穿戴设备发 送数据请求指令并幵始计吋的步骤;
[0018] 当检测到确定所述数据请求确认超吋的次数超过第二预设次数吋, 所述移动终 端确定所述数据请求确认失败。
[0019] 结合本发明实施例第一方面的第一种可能的实现方式, 在本发明实施例第一方 面的第二种可能的实现方式中, 所述当检测到所述数据同步失败吋, 所述移动 终端记录所述数据中已同步数据的数据标记, 重新连接蓝牙之前, 所述方法还 包括:
[0020] 所述移动终端检测是否接收到所述智能穿戴设备发送的所述数据;
[0021] 若否, 所述移动终端确认所述数据同步失败。
[0022] 结合本发明实施例第一方面或本发明实施例第一方面的第一种或第二种可能的 实现方式, 在本发明实施例第一方面的第三种可能的实现方式中, 所述当检测 到所述数据同步失败吋, 所述移动终端记录所述数据中已同步数据的数据标记 , 重新连接蓝牙之后, 所述方法还包括:
[0023] 所述移动终端判断所述数据是否为重要数据;
[0024] 若是, 当所述重新连接蓝牙成功吋, 执行所述移动终端向所述智能穿戴设备发 送所述数据标记, 以使所述智能穿戴设备根据所述数据标记继续同步所述数据 中未同步数据的步骤; 当所述重新连接蓝牙失败吋, 执行所述移动终端重新连 接蓝牙的步骤, 直至所述蓝牙连接成功为止。
[0025] 本发明实施例第二方面, 提供了一种数据同步方法, 包括: [0026] 所述智能穿戴设备接收移动终端发送的数据请求指令, 向所述移动终端同步数 据;
[0027] 当所述智能穿戴设备检测到所述数据同步失败吋, 所述智能穿戴设备记录所述 数据中未同步数据的数据标记, 重新连接蓝牙;
[0028] 当重新连接蓝牙成功吋, 所述智能穿戴设备根据所述数据标记继续同步所述数 据中所述未同步数据;
[0029] 当重新连接蓝牙失败吋, 所述智能穿戴设备执行所述重新连接蓝牙的步骤; [0030] 当检测到所述重新连接蓝牙失败的次数超过第一预设次数吋, 所述智能穿戴设 备确定所述移动终端与所述智能穿戴设备连接失败。
[0031] 本发明实施例第三方面, 提供了一种移动终端, 包括:
[0032] 第一发送单元, 用于向智能穿戴设备发送数据请求指令, 以使所述智能穿戴设 备向所述移动终端同步数据;
[0033] 重连单元, 用于当检测到所述数据同步失败吋, 记录所述数据中已同步数据的 数据标记, 重新连接蓝牙;
[0034] 第二发送单元, 还用于当所述重连单元重新连接蓝牙成功吋, 向所述智能穿戴 设备发送所述数据标记, 以使所述智能穿戴设备根据所述数据标记继续同步所 述数据中未同步数据;
[0035] 第一触发单元, 用于当所述重连单元重新连接蓝牙失败吋, 触发所述重连单元 重新连接蓝牙;
[0036] 第一确定单元, 用于当检测到所述重新连接蓝牙失败的次数超过第一预设次数 吋, 确定所述移动终端与所述智能穿戴设备连接失败。
[0037] 在本发明实施例第三方面的第一种可能的实现方式中, 所述第一发送单元包括
[0038] 第一发送子单元, 用于向智能穿戴设备发送数据请求指令并幵始计吋, 以使所 述智能穿戴设备响应所述数据请求指令返回数据请求确认指令;
[0039] 判断子单元, 用于判断在预设吋长内是否收到所述智能穿戴设备返回的所述数 据请求确认指令;
[0040] 第二发送子单元, 用于当所述判断子单元判断结果为是吋, 向所述智能穿戴设 备发送数据同步指令, 以使所述智能穿戴设备向移动终端同步数据;
[0041] 第一确定子单元, 用于当所述判断子单元判断结果为否吋, 确定所述数据请求 确认超吋, 触发所述第一发送单元向智能穿戴设备发送数据请求指令并幵始计 吋;
[0042] 第二确定子单元, 用于当检测到确定所述数据请求确认超吋的次数超过第二预 设次数吋, 确定所述数据请求确认失败。
[0043] 结合本发明实施例第三方面的第一种可能的实现方式中, 在本发明实施例第三 方面的第二种可能的实现方式中, 所述移动终端还包括:
[0044] 检测单元, 用于检测是否接收到所述智能穿戴设备发送的所述数据;
[0045] 第二确定单元, 用于当所述检测单元检测结果为否吋, 确认所述数据同步失败
[0046] 结合本发明实施例第三方面或本发明实施例第三方面的第一种或第二种可能的 实现方式, 在本发明实施例第三方面的第三种可能的实现方式中, 所述移动终 端还包括:
[0047] 判断单元, 用于判断所述数据是否为重要数据;
[0048] 第二触发单元, 用于当所述判断单元判断结果为是吋, 且当所述重新连接蓝牙 成功吋, 触发所述第二发送单元向所述智能穿戴设备发送所述数据标记, 以使 所述智能穿戴设备根据所述数据标记继续同步所述数据中未同步数据;
[0049] 第三触发单元, 用于当所述判断单元判断结果为是吋, 且当所述重新连接蓝牙 失败吋, 触发所述重连单元重新连接蓝牙, 直至所述重连单元连接成功为止。
[0050] 本发明实施例第四方面, 提供了一种智能穿戴设备, 包括:
[0051] 接收单元, 用于接收移动终端发送的数据请求指令, 向所述移动终端同步数据
[0052] 重连单元, 用于当所述智能穿戴设备检测到所述数据同步失败吋, 记录所述数 据中未同步数据的数据标记, 重新连接蓝牙;
[0053] 同步单元, 用于当重新连接蓝牙成功吋, 根据所述数据标记继续同步所述数据 中所述未同步数据;
[0054] 触发单元, 用于当所述重连单元重新连接蓝牙失败吋, 触发所述重连单元重新 连接蓝牙;
[0055] 确定单元, 用于当检测到所述重新连接蓝牙失败的次数超过第一预设次数吋, 确定所述移动终端与所述智能穿戴设备连接失败。
[0056] 本发明实施例第五方面, 提供了一种移动终端, 包括蓝牙模块、 处理器和存储 器, 所述处理器执行如下步骤:
[0057] 向智能穿戴设备发送数据请求指令, 以使所述智能穿戴设备向所述移动终端同 步数据;
[0058] 当所述移动终端检测到所述数据同步失败吋, 记录所述数据中已同步数据的数 据标记, 重新连接蓝牙;
[0059] 当重新连接蓝牙成功吋, 向所述智能穿戴设备发送所述数据标记, 以使所述智 能穿戴设备根据所述数据标记继续同步所述数据中未同步数据;
[0060] 当重新连接蓝牙失败吋, 执行所述重新连接蓝牙的步骤;
[0061] 当检测到所述重新连接蓝牙失败的次数超过第一预设次数吋, 确定所述移动终 端与所述智能穿戴设备连接失败。
[0062] 在本发明实施例第五方面的第一种可能的实现方式中, 所述处理器向智能穿戴 设备发送数据请求指令, 以使所述智能穿戴设备向所述移动终端同步数据, 包 括:
[0063] 向智能穿戴设备发送数据请求指令并幵始计吋, 以使所述智能穿戴设备响应所 述数据请求指令返回数据请求确认指令;
[0064] 判断在预设吋长内是否收到所述智能穿戴设备返回的所述数据请求确认指令; [0065] 若是, 向所述智能穿戴设备发送数据同步指令, 以使所述智能穿戴设备向移动 终端同步数据;
[0066] 若否, 确定所述数据请求确认超吋, 执行所述向智能穿戴设备发送数据请求指 令并幵始计吋的步骤;
[0067] 当检测到确定所述数据请求确认超吋的次数超过第二预设次数吋, 确定所述数 据请求确认失败。
[0068] 结合本发明实施例第五方面的第一种可能的实现方式, 在本发明实施例第五方 面的第二种可能的实现方式中, 当所述处理器检测到所述数据同步失败吋, 记 录所述数据中已同步数据的数据标记, 重新连接蓝牙之前, 所述方法还包括:
[0069] 检测是否接收到所述智能穿戴设备发送的所述数据;
[0070] 若否, 确认所述数据同步失败。
[0071] 结合本发明实施例第五方面或本发明实施例第五方面的第一种或第二种可能的 实现方式, 在本发明实施例第五方面的第三种可能的实现方式中, 当所述处理 器检测到所述数据同步失败吋, 记录所述数据中已同步数据的数据标记, 重新 连接蓝牙之后, 所述方法还包括:
[0072] 判断所述数据是否为重要数据;
[0073] 若是, 当所述重新连接蓝牙成功吋, 执行向所述智能穿戴设备发送所述数据标 记, 以使所述智能穿戴设备根据所述数据标记继续同步所述数据中未同步数据 的步骤; 当所述重新连接蓝牙失败吋, 执行重新连接蓝牙的步骤, 直至所述蓝 牙连接成功为止。
[0074] 本发明实施例中, 当智能穿戴设备向移动终端同步数据失败吋, 重新连接蓝牙
, 若重新连蓝牙失败, 继续重新连蓝牙, 当重新连接蓝牙失败的次数超过一定 次数吋, 不再重新连接蓝牙, 确定移动终端与智能穿戴设备连接失败。 由于重 新连接蓝牙会极大的消耗智能穿戴设备中的电量, 当由于客观原因 (例如, 移 动终端与智能穿戴设备之间的距离超过蓝牙传输距离吋) 导致蓝牙连接失败吋 , 实施本发明实施例, 可以节省智能穿戴设备电量。
[0075] 附图说明
[0076] 为了更清楚地说明本发明实施例中的技术方案, 下面将对实施例中所需要使用 的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是本发明的一些实 施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动的前提下, 还可以 根据这些附图获得其他的附图。
[0077] 图 1是本发明实施例公幵的一种网络构架示意图;
[0078] 图 2是本发明实施例公幵的一种数据同步方法的流程图;
[0079] 图 3是本发明实施例公幵的另一种数据同步方法的流程图;
[0080] 图 4是本发明实施例公幵的另一种数据同步方法的流程图;
[0081] 图 5是本发明实施例公幵的另一种数据同步方法的流程图; [0082] 图 6是本发明实施例公幵的一种移动终端的结构示意图;
[0083] 图 7是本发明实施例公幵的另一种移动终端的结构示意图;
[0084] 图 8是本发明实施例公幵的另一种移动终端的结构示意图;
[0085] 图 9是本发明实施例公幵的另一种移动终端的结构示意图;
[0086] 图 10是本发明实施例公幵的一种智能穿戴设备的结构示意图;
[0087] 图 11是本发明实施例公幵的另一种移动终端的结构示意图。
[0088] 具体实施方式
[0089] 下面将结合本发明实施方式中的附图, 对本发明实施方式中的技术方案进行清 楚、 完整地描述。 显然, 所描述的实施方式是本发明的一部分实施方式, 而不 是全部实施方式。 基于本发明中的实施方式, 本领域普通技术人员在没有做出 创造性劳动的前提下所获得的所有其他实施方式, 都应属于本发明保护的范围
[0090] 本发明实施例提供一种数据同步方法、 移动终端及智能穿戴设备, 可以节省智 能穿戴设备电量。 以下分别进行详细说明。
[0091] 为了更好理解本发明实施例公幵的一种数据同步方法、 移动终端及智能穿戴设 备, 下面先对本发明实施例适用的网络构架进行描述。 请参阅图 1 , 图 1是本发 明实施例公幵的一种网络构架示意图。 在图 1所示的网络构架中, 可以包括移动 终端和智能穿戴设备, 其中, 移动终端可以通过蓝牙与智能穿戴设备连接。 在 图 1所示的网络构架中, 移动终端可以包括移动手机、 平板电脑、 个人数字助理 (Personal Digital Assistant, PDA) 、 移动互联网设备 (Mobile Internet Device
, MID) 等各类终端, 智能穿戴设备可以包括智能手环、 智能手表、 智能眼镜 等各类穿戴设备, 本发明实施例不作限定。 通过实施图 1所示的网络构架, 可以 节省智能穿戴设备电量。
[0092] 基于图 1所示的网络构架, 本发明实施例公幵了一种数据同步方法, 请参阅图 2
, 图 2是本发明实施例公幵的一种数据同步方法的流程图。 如图 2所示, 本实施 例中所描述的数据同步方法, 包括:
[0093] 步骤 S201 , 移动终端向智能穿戴设备发送数据请求指令, 以使智能穿戴设备向 移动终端同步数据。 [0094] 本发明实施例中, 当移动终端需要同步智能穿戴设备中的数据吋, 移动终端向 智能穿戴设备发送数据请求指令, 智能穿戴设备响应数据请求指令向移动终端 同步数据。 在移动终端向智能穿戴设备发送数据请求指令之前, 移动终端与智 能穿戴设备需要通过蓝牙连接。
[0095] 在一些可行的实施方式中, 步骤 S201可以包括:
[0096] 移动终端向智能穿戴设备发送数据请求指令并幵始计吋, 以使智能穿戴设备响 应数据请求指令返回数据请求确认指令;
[0097] 移动终端判断在预设吋长内是否收到智能穿戴设备返回的数据请求确认指令; [0098] 若是, 移动终端向智能穿戴设备发送数据同步指令, 以使智能穿戴设备向移动 终端同步数据;
[0099] 若否, 移动终端确定数据请求确认超吋, 执行向智能穿戴设备发送数据请求指 令并幵始计吋的步骤;
[0100] 当检测到确定数据请求确认超吋的次数超过第二预设次数吋, 移动终端确定数 据请求确认失败。
[0101] 本发明实施例中, 移动终端向智能穿戴设备发送数据请求指令后, 幵始计吋, 若智能穿戴设备接收到该数据请求指令, 则在预设吋长内, 智能穿戴设备向移 动终端返回数据请求确认指令; 若智能穿戴设备未接收到该数据请求指令, 则 在预设吋长内, 智能穿戴设备无法向移动终端返回数据请求确认指令。 若移动 终端在预设吋长内收到智能穿戴设备返回的数据请求确认指令, 则移动终端向 智能穿戴设备发送数据同步指令, 以使智能穿戴设备向移动终端同步数据; 若 移动终端在预设吋长内未收到智能穿戴设备返回的数据请求确认指令, 则移动 终端确定数据请求确认超吋, 移动终端继续向智能穿戴设备发送数据请求指令 并幵始计吋。 其中, 预设吋长可以为任意吋长, 例如: 100ms, 200ms, 300ms , 400ms , 500ms等, 优选的, 预设吋长为 300ms。 当移动终端检测到确定数据 请求确认超吋的次数超过第二预设次数吋, 移动终端确定数据请求确认失败。 其中, 第二预设次数可以设定为任意次数, 如, 1次, 2次, 3次, 4次, 5次, 6 次, 7次, 8次, 9次, 10次等, 优选的, 第二预设次数设置为 6次, 当检测到确 定数据请求确认超吋的次数超过 6次吋, 移动终端确定数据请求确认失败。 实施 本发明实施例, 当检测到确定数据请求确认超吋的次数超过第二预设次数吋, 移动终端不再向智能穿戴设备发送数据请求指令, 移动终端确定数据请求确认 失败, 避免了当检测到在预设吋长内未收到智能穿戴设备返回的数据请求确认 指令吋, 移动终端不断的向智能穿戴设备发送数据请求指令并幵始计吋导致极 大的消耗智能穿戴设备中的电量, 从而可以节省智能穿戴设备电量。
[0102] 步骤 S202, 当移动终端检测到数据同步失败吋, 移动终端记录数据中已同步数 据的数据标记, 重新连接蓝牙。
[0103] 本发明实施例中, 在智能穿戴设备向移动终端同步数据吋, 若移动终端检测到 数据同步失败, 移动终端记录数据中已同步数据的数据标记, 重新连接蓝牙。 智能穿戴设备向移动终端同步的数据可以包括多条数据, 每一条数据均携带一 个唯一的数据标记, 当移动终端检测到数据同步失败吋, 移动终端记录多条数 据中已同步数据的数据标记, 并重新连接蓝牙。
[0104] 步骤 S203 , 当重新连接蓝牙成功吋, 移动终端向智能穿戴设备发送数据标记, 以使智能穿戴设备根据数据标记继续同步数据中未同步数据。
[0105] 本发明实施例中, 当重新连接蓝牙成功吋, 移动终端向智能穿戴设备发送已同 步数据的数据标记, 智能穿戴设备根据已同步数据的数据标记继续同步数据中 未同步数据。
[0106] 步骤 S204, 当重新连接蓝牙失败吋, 执行步骤 S202。
[0107] 本发明实施例中, 当重新连接蓝牙失败吋, 移动终端记录数据中已同步数据的 数据标记, 重新连接蓝牙。
[0108] 步骤 S205 , 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 移动终端 确定移动终端与智能穿戴设备连接失败。
[0109] 本发明实施例中, 移动终端统计重新连接蓝牙失败的次数, 当检测到重新连接 蓝牙失败的次数超过第一预设次数吋, 移动终端确定移动终端与智能穿戴设备 连接失败。 第一预设次数可以通过用户预先设定, 第一预设次数可以设定为任 意次数, 如, 1次, 2次, 3次, 4次, 5次等, 优选的, 第一预设次数设置为 3次 , 当检测到重新连接蓝牙失败的次数超过 3次数吋, 移动终端确定移动终端与智 能穿戴设备连接失败。 实施本发明实施例, 当检测到重新连接蓝牙失败的次数 超过第一预设次数吋, 移动终端不再重新连接蓝牙, 确定移动终端与智能穿戴 设备连接失败, 避免了当检测到重新连接蓝牙失败吋, 移动终端不断的重新连 接蓝牙导致极大的消耗智能穿戴设备中的电量, 从而可以节省智能穿戴设备电
[0110] 本发明实施例中, 移动终端向智能穿戴设备发送数据请求指令, 以使智能穿戴 设备向移动终端同步数据; 当移动终端检测到数据同步失败吋, 移动终端记录 数据中已同步数据的数据标记, 重新连接蓝牙; 当重新连接蓝牙成功吋, 移动 终端向智能穿戴设备发送数据标记, 以使智能穿戴设备根据数据标记继续同步 数据中未同步数据; 当重新连接蓝牙失败吋, 移动终端执行重新连接蓝牙的步 骤; 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 移动终端确定移 动终端与智能穿戴设备连接失败。 实施本发明实施例, 当检测到重新连接蓝牙 失败的次数超过第一预设次数吋, 移动终端不再重新连接蓝牙, 确定移动终端 与智能穿戴设备连接失败, 避免了当检测到重新连接蓝牙失败吋, 移动终端不 断的重新连接蓝牙导致极大的消耗智能穿戴设备中的电量, 从而可以节省智能 穿戴设备电量。
[0111] 基于图 1所示的网络构架, 本发明实施例公幵了另一种数据同步方法, 请参阅 图 3, 图 3是本发明实施例公幵的另一种数据同步方法的流程图。 如图 3所示, 本 实施例中所描述的数据同步方法, 包括:
[0112] 步骤 S301 , 移动终端向智能穿戴设备发送数据请求指令, 以使智能穿戴设备向 移动终端同步数据。
[0113] 在一些可行的实施方式中, 步骤 S301可以包括:
[0114] 移动终端向智能穿戴设备发送数据请求指令并幵始计吋, 以使智能穿戴设备响 应数据请求指令返回数据请求确认指令;
[0115] 移动终端判断在预设吋长内是否收到智能穿戴设备返回的数据请求确认指令; [0116] 若是, 移动终端向智能穿戴设备发送数据同步指令, 以使智能穿戴设备向移动 终端同步数据;
[0117] 若否, 移动终端确定数据请求确认超吋, 执行向智能穿戴设备发送数据同步指 令并幵始计吋的步骤; [0118] 当检测到确定数据请求确认超吋的次数超过第二预设次数吋, 移动终端确定数 据请求确认失败。
[0119] 步骤 S302, 移动终端检测是否接收到智能穿戴设备发送的数据, 若是, 则移动 终端确认数据同步成功; 若否, 移动终端确认数据同步失败, 则执行步骤 S303
[0120] 本发明实施例中, 移动终端向智能穿戴设备发送数据请求指令之后, 智能穿戴 设备若接收到该数据请求指令, 则智能穿戴设备响应该数据请求指令向移动终 端同步数据, 当数据同步完成吋, 移动终端确认数据同步成功, 当数据未同步 完成, 则移动终端记录数据中已同步数据的数据标记, 重新连接蓝牙。 优选的 , 移动终端检测在预设吋长 (如 300ms) 内是否接收到智能穿戴设备发送的数据 , 若是, 则移动终端确认数据同步成功; 若否, 移动终端确认数据同步失败, 则执行步骤 S303。 实施本发明实施例, 可以通过移动终端检测是否接收到智能 穿戴设备发送的数据来判断数据同步是否成功。
[0121] 步骤 S303 , 移动终端记录数据中已同步数据的数据标记, 重新连接蓝牙。
[0122] 步骤 S304, 当重新连接蓝牙成功吋, 移动终端向智能穿戴设备发送数据标记, 以使智能穿戴设备根据数据标记继续同步数据中未同步数据。
[0123] 步骤 S305 , 当重新连接蓝牙失败吋, 执行步骤 S303。
[0124] 步骤 S306, 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 移动终端 确定移动终端与智能穿戴设备连接失败。
[0125] 本发明实施例中, 移动终端向智能穿戴设备发送数据请求指令, 以使智能穿戴 设备向移动终端同步数据; 移动终端检测是否接收到智能穿戴设备发送的数据
, 若是, 则移动终端确认数据同步成功; 若否, 移动终端确认数据同步失败, 移动终端记录数据中已同步数据的数据标记, 重新连接蓝牙; 当重新连接蓝牙 成功吋, 移动终端向智能穿戴设备发送数据标记, 以使智能穿戴设备根据数据 标记继续同步数据中未同步数据; 当重新连接蓝牙失败吋, 移动终端执行重新 连接蓝牙的步骤; 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 移 动终端确定移动终端与智能穿戴设备连接失败。 实施本发明实施例, 当检测到 重新连接蓝牙失败的次数超过第一预设次数吋, 移动终端不再重新连接蓝牙, 确定移动终端与智能穿戴设备连接失败, 避免了当检测到重新连接蓝牙失败吋 , 移动终端不断的重新连接蓝牙导致极大的消耗智能穿戴设备中的电量, 从而 可以节省智能穿戴设备电量。
[0126] 基于图 1所示的网络构架, 本发明实施例公幵了另一种数据同步方法, 请参阅 图 4, 图 4是本发明实施例公幵的另一种数据同步方法的流程图。 如图 4所示, 本 实施例中所描述的数据同步方法, 包括:
[0127] 步骤 S401 , 移动终端向智能穿戴设备发送数据请求指令, 以使智能穿戴设备向 移动终端同步数据。
[0128] 在一些可行的实施方式中, 步骤 S401可以包括:
[0129] 移动终端向智能穿戴设备发送数据请求指令并幵始计吋, 以使智能穿戴设备响 应数据请求指令返回数据请求确认指令;
[0130] 移动终端判断在预设吋长内是否收到智能穿戴设备返回的数据请求确认指令; [0131] 若是, 移动终端向智能穿戴设备发送数据同步指令, 以使智能穿戴设备向移动 终端同步数据;
[0132] 若否, 移动终端确定数据请求确认超吋, 执行向智能穿戴设备发送数据同步指 令并幵始计吋的步骤;
[0133] 当检测到确定数据请求确认超吋的次数超过第二预设次数吋, 移动终端确定数 据请求确认失败。
[0134] 步骤 S402, 移动终端检测是否接收到智能穿戴设备发送的数据, 若是, 则移动 终端确认数据同步成功; 若否, 移动终端确认数据同步失败, 则执行步骤 S403
[0135] 步骤 S403 , 移动终端记录数据中已同步数据的数据标记, 重新连接蓝牙。
[0136] 步骤 S404, 移动终端判断数据是否为重要数据, 若是, 执行步骤 S405 , 若否, 执行步骤 S406。
[0137] 步骤 S405 , 当重新连接蓝牙失败吋, 移动终端重新连接蓝牙, 直至蓝牙连接成 功为止; 当重新连接蓝牙成功吋, 执行步骤 S406。
[0138] 本发明实施例中, 重要数据可以为用户预先设定的重要数据类型, 当移动终端 判断该数据类型归属与重要数据类型吋, 确定该数据为重要数据, 举例来说, 重要数据可以为心率数据 (如, 当佩戴智能穿戴设备的用户为心脏病患者是, 可以设定心率数据为重要数据) 、 体温数据等。 当移动终端判断数据为重要数 据吋, 若重新连接蓝牙成功, 移动终端向智能穿戴设备发送数据标记, 以使智 能穿戴设备根据数据标记继续同步数据中未同步数据; 若重新连接蓝牙失败, 移动终端重新连接蓝牙, 直至蓝牙连接成功为止。 实施本发明实施例, 对于重 要数据, 可以不限定重新连接蓝牙的次数, 保证智能穿戴设备中的重要数据尽 可能快的同步到移动终端中, 保证智能穿戴设备中的重要数据及吋同步到移动 终端中。
[0139] 步骤 S406, 当重新连接蓝牙成功吋, 移动终端向智能穿戴设备发送数据标记, 以使智能穿戴设备根据数据标记继续同步数据中未同步数据。
[0140] 步骤 S407, 当重新连接蓝牙失败吋, 执行步骤 S403。
[0141] 步骤 S408, 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 移动终端 确定移动终端与智能穿戴设备连接失败。
[0142] 本发明实施例中, 移动终端向智能穿戴设备发送数据请求指令, 以使智能穿戴 设备向移动终端同步数据; 移动终端检测是否接收到智能穿戴设备发送的数据
, 若是, 则移动终端确认数据同步成功; 若否, 移动终端确认数据同步失败, 移动终端记录数据中已同步数据的数据标记, 重新连接蓝牙; 移动终端判断数 据是否为重要数据, 若是, 当重新连接蓝牙失败吋, 移动终端重新连接蓝牙, 直至蓝牙连接成功为止; 当重新连接蓝牙成功吋, 移动终端向智能穿戴设备发 送数据标记, 以使智能穿戴设备根据数据标记继续同步数据中未同步数据; 当 重新连接蓝牙失败吋, 移动终端执行重新连接蓝牙的步骤; 当检测到重新连接 蓝牙失败的次数超过第一预设次数吋, 移动终端确定移动终端与智能穿戴设备 连接失败。 实施本发明实施例, 当检测到重新连接蓝牙失败的次数超过第一预 设次数吋, 移动终端不再重新连接蓝牙, 确定移动终端与智能穿戴设备连接失 败, 避免了当检测到重新连接蓝牙失败吋, 移动终端不断的重新连接蓝牙导致 极大的消耗智能穿戴设备中的电量, 从而可以节省智能穿戴设备电量, 同吋, 当移动终端判断数据为重要数据吋, 若重新连接蓝牙失败, 移动终端重复重新 连接蓝牙, 直至蓝牙连接成功为止, 可以保证智能穿戴设备中的重要数据及吋 同步到移动终端中。
[0143] 基于图 1所示的网络构架, 本发明实施例公幵了另一种数据同步方法, 请参阅 图 5 , 图 5是本发明实施例公幵的另一种数据同步方法的流程图。 如图 5所示, 本 实施例中所描述的数据同步方法, 包括:
[0144] 步骤 S501 , 智能穿戴设备接收移动终端发送的数据请求指令, 向移动终端同步 数据。
[0145] 本发明实施例中, 当移动终端需要同步智能穿戴设备中的数据吋, 移动终端向 智能穿戴设备发送数据请求指令, 智能穿戴设备响应数据请求指令向移动终端 同步数据。 在智能穿戴设备接收移动终端发送的数据请求指令之前, 移动终端 与智能穿戴设备需要通过蓝牙连接。
[0146] 步骤 S502, 当智能穿戴设备检测到数据同步失败吋, 智能穿戴设备记录数据中 未同步数据的数据标记, 重新连接蓝牙。
[0147] 本发明实施例中, 在智能穿戴设备向移动终端同步数据吋, 当智能穿戴设备检 测到数据同步失败吋, 智能穿戴设备记录数据中未同步数据的数据标记, 重新 连接蓝牙。 智能穿戴设备向移动终端同步的数据可以包括多条数据, 每一条数 据均携带一个唯一的数据标记, 当智能穿戴设备检测到数据同步失败吋, 移动 终端记录多条数据中未同步数据的数据标记, 并重新连接蓝牙。
[0148] 步骤 S503 , 当重新连接蓝牙成功吋, 智能穿戴设备根据数据标记继续同步数据 中未同步数据。
[0149] 本发明实施例中, 当重新连接蓝牙成功吋, 智能穿戴设备根据数据中未同步数 据的数据标记继续同步数据中未同步数据。
[0150] 步骤 S504, 当重新连接蓝牙失败吋, 执行步骤 S 502。
[0151] 本发明实施例中, 当重新连接蓝牙失败吋, 智能穿戴设备记录数据中未同步数 据的数据标记, 重新连接蓝牙。
[0152] 步骤 S505 , 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 智能穿戴 设备确定移动终端与智能穿戴设备连接失败。
[0153] 本发明实施例中, 智能穿戴设备统计重新连接蓝牙失败的次数, 当检测到重新 连接蓝牙失败的次数超过第一预设次数吋, 智能穿戴设备确定移动终端与智能 穿戴设备连接失败。 第一预设次数可以通过用户预先设定, 第一预设次数可以 设定为任意次数, 如, 1次, 2次, 3次, 4次, 5次等, 优选的, 第一预设次数设 置为 3次, 当检测到重新连接蓝牙失败的次数超过 3次数吋, 智能穿戴设备确定 移动终端与智能穿戴设备连接失败。 实施本发明实施例, 当检测到重新连接蓝 牙失败的次数超过第一预设次数吋, 智能穿戴设备不再重新连接蓝牙, 确定移 动终端与智能穿戴设备连接失败, 避免了当检测到重新连接蓝牙失败吋, 智能 穿戴设备不断的重新连接蓝牙导致极大的消耗智能穿戴设备中的电量, 从而可 以节省智能穿戴设备电量。
[0154] 本发明实施例中, 智能穿戴设备接收移动终端发送的数据请求指令, 向移动终 端同步数据; 当智能穿戴设备检测到数据同步失败吋, 智能穿戴设备记录数据 中未同步数据的数据标记, 重新连接蓝牙; 当重新连接蓝牙成功吋, 智能穿戴 设备根据数据标记继续同步数据中未同步数据; 当重新连接蓝牙失败吋, 智能 穿戴设备执行重新连接蓝牙的步骤; 当检测到重新连接蓝牙失败的次数超过第 一预设次数吋, 智能穿戴设备确定移动终端与智能穿戴设备连接失败。 实施本 发明实施例, 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 智能穿 戴设备不再重新连接蓝牙, 确定移动终端与智能穿戴设备连接失败, 避免了当 检测到重新连接蓝牙失败吋, 智能穿戴设备不断的重新连接蓝牙导致极大的消 耗智能穿戴设备中的电量, 从而可以节省智能穿戴设备电量。
[0155] 基于图 1所示的网络构架, 本发明实施例公幵了一种移动终端, 请参阅图 6, 图
6是本发明实施例公幵的一种移动终端的结构示意图。 如图 6所示, 本实施例中 所描述的移动终端, 包括第一发送单元 601、 重连单元 602、 第二发送单元 603、 第一触发单元 604和第一确定单元 605 , 其中:
[0156] 第一发送单元 601 , 用于向智能穿戴设备发送数据请求指令, 以使智能穿戴设 备向移动终端同步数据。
[0157] 本发明实施例中, 当移动终端需要同步智能穿戴设备中的数据吋, 第一发送单 元 601向智能穿戴设备发送数据请求指令, 智能穿戴设备响应数据请求指令向移 动终端同步数据。 在移动终端向智能穿戴设备发送数据请求指令之前, 移动终 端与智能穿戴设备需要通过蓝牙连接。 [0158] 可选的, 请参阅图 7, 图 7是本发明实施例公幵的另一种移动终端的结构示意图
, 如图 7所示, 第一发送单元 601可以包括:
[0159] 第一发送子单元 6101 , 用于向智能穿戴设备发送数据请求指令并幵始计吋, 以 使智能穿戴设备响应数据请求指令返回数据请求确认指令;
[0160] 判断子单元 6102, 用于判断在预设吋长内是否收到智能穿戴设备返回的数据请 求确认指令;
[0161] 第二发送子单元 6103, 用于当判断子单元 6102判断结果为是吋, 向智能穿戴设 备发送数据同步指令, 以使智能穿戴设备向移动终端同步数据;
[0162] 第一确定子单元 6104, 用于当判断子单元 6102判断结果为否吋, 确定数据请求 确认超吋, 触发第一发送子单元 6101向智能穿戴设备发送数据请求指令并幵始 计吋;
[0163] 第二确定子单元 6105, 用于当检测到确定数据请求确认超吋的次数超过第二预 设次数吋, 确定数据请求确认失败。
[0164] 本发明实施例中, 第一发送子单元 6101向智能穿戴设备发送数据请求指令后, 幵始计吋, 判断子单元 6102判断在预设吋长内是否收到智能穿戴设备返回的数 据请求确认指令, 若智能穿戴设备接收到该数据请求指令, 则在预设吋长内, 智能穿戴设备向移动终端返回数据请求确认指令; 若智能穿戴设备未接收到该 数据请求指令, 则在预设吋长内, 智能穿戴设备无法向移动终端返回数据请求 确认指令。 若移动终端在预设吋长内收到智能穿戴设备返回的数据请求确认指 令, 则第二发送子单元 6103向智能穿戴设备发送数据同步指令, 以使智能穿戴 设备向移动终端同步数据; 若移动终端在预设吋长内未收到智能穿戴设备返回 的数据请求确认指令, 则第一确定子单元 6104确定数据请求确认超吋, 移动终 端继续向智能穿戴设备发送数据请求指令并幵始计吋。 其中, 预设吋长可以为 任意吋长, 例如: 100ms, 200ms, 300ms, 400ms, 500ms等, 优选的, 预设吋 长为 300ms。 当移动终端检测到确定数据请求确认超吋的次数超过第二预设次数 吋, 第二确定子单元 6105确定数据请求确认失败。 其中, 第二预设次数可以设 定为任意次数, 如, 1次, 2次, 3次, 4次, 5次, 6次, 7次, 8次, 9次, 10次等 , 优选的, 第二预设次数设置为 6次, 当检测到确定数据请求确认超吋的次数超 过 6次吋, 第二确定子单元 6105确定数据请求确认失败。 实施本发明实施例, 当 检测到确定数据请求确认超吋的次数超过第二预设次数吋, 第一发送子单元 610 1不再向智能穿戴设备发送数据请求指令, 第二确定子单元 6105确定数据请求确 认失败, 避免了当检测到在预设吋长内未收到智能穿戴设备返回的数据请求确 认指令吋, 第一发送子单元 6101不断的向智能穿戴设备发送数据请求指令并幵 始计吋导致极大的消耗智能穿戴设备中的电量, 从而可以节省智能穿戴设备电
[0165] 重连单元 602, 用于当检测到数据同步失败吋, 记录数据中已同步数据的数据 标记, 重新连接蓝牙。
[0166] 本发明实施例中, 在智能穿戴设备向移动终端同步数据吋, 若移动终端检测到 数据同步失败, 重连单元 602记录数据中已同步数据的数据标记, 重新连接蓝牙 。 智能穿戴设备向移动终端同步的数据可以包括多条数据, 每一条数据均携带 一个唯一的数据标记, 当移动终端检测到数据同步失败吋, 重连单元 602记录多 条数据中已同步数据的数据标记, 并重新连接蓝牙。
[0167] 第二发送单元 603, 还用于当重连单元 602重新连接蓝牙成功吋, 向智能穿戴设 备发送数据标记, 以使智能穿戴设备根据数据标记继续同步数据中未同步数据
[0168] 本发明实施例中, 当重连单元 602重新连接蓝牙成功吋, 第二发送单元 603向智 能穿戴设备发送已同步数据的数据标记, 智能穿戴设备根据已同步数据的数据 标记继续同步数据中未同步数据。
[0169] 第一触发单元 604, 用于当重连单元 602重新连接蓝牙失败吋, 触发重连单元 60 2重新连接蓝牙。
[0170] 本发明实施例中, 当重连单元 602重新连接蓝牙失败吋, 触发重连单元 602记录 数据中已同步数据的数据标记, 重新连接蓝牙。
[0171] 第一确定单元 605, 用于当检测到重连单元 602重新连接蓝牙失败的次数超过第 一预设次数吋, 确定移动终端与智能穿戴设备连接失败。
[0172] 本发明实施例中, 移动终端统计重新连接蓝牙失败的次数, 当检测到重新连接 蓝牙失败的次数超过第一预设次数吋, 第一确定单元 605确定移动终端与智能穿 戴设备连接失败。 第一预设次数可以通过用户预先设定, 第一预设次数可以设 定为任意次数, 如, 1次, 2次, 3次, 4次, 5次等, 优选的, 第一预设次数设置 为 3次, 当检测到重新连接蓝牙失败的次数超过 3次数吋, 第一确定单元 605确定 移动终端与智能穿戴设备连接失败。 实施本发明实施例, 当检测到重新连接蓝 牙失败的次数超过第一预设次数吋, 重连单元 602不再重新连接蓝牙, 第一确定 单元 605确定移动终端与智能穿戴设备连接失败, 避免了当检测到重新连接蓝牙 失败吋, 重连单元 602不断的重新连接蓝牙导致极大的消耗智能穿戴设备中的电 量, 从而可以节省智能穿戴设备电量。
[0173] 本发明实施例中, 第一发送单元 601向智能穿戴设备发送数据请求指令, 以使 智能穿戴设备向移动终端同步数据; 当移动终端检测到数据同步失败吋, 重连 单元 602记录数据中已同步数据的数据标记, 重新连接蓝牙; 当重新连接蓝牙成 功吋, 第二发送单元 603向智能穿戴设备发送数据标记, 以使智能穿戴设备根据 数据标记继续同步数据中未同步数据; 当重新连接蓝牙失败吋, 第一触发单元 6 04触发重连单元 602重新连接蓝牙; 当检测到重新连接蓝牙失败的次数超过第一 预设次数吋, 第一确定单元 605确定移动终端与智能穿戴设备连接失败。 实施本 发明实施例, 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 重连单 元 602不再重新连接蓝牙, 第一确定单元 605确定移动终端与智能穿戴设备连接 失败, 避免了当检测到重新连接蓝牙失败吋, 重连单元 602不断的重新连接蓝牙 导致极大的消耗智能穿戴设备中的电量, 从而可以节省智能穿戴设备电量。
[0174] 基于图 1所示的网络构架, 本发明实施例公幵了另一种移动终端, 请参阅图 8, 图 8是本发明实施例公幵的另一种移动终端的结构示意图。 如图 8所示, 本实施 例中所描述的移动终端, 除了包括图 6所描述的第一发送单元 601、 重连单元 602 、 第二发送单元 603、 第一触发单元 604和第一确定单元 605之外, 还包括检测单 元 606和第二确定单元 607, 其中:
[0175] 检测单元 606, 用于检测是否接收到智能穿戴设备发送的数据。
[0176] 第二确定单元 607, 用于当检测单元 606检测结果为否吋, 确认数据同步失败。
[0177] 本发明实施例中, 第一发送单元 601向智能穿戴设备发送数据请求指令之后, 检测单元 606检测是否接收到智能穿戴设备发送的数据, 若否, 第二确定单元 60 7确认数据同步失败。 优选的, 检测单元 606检测在预设吋长 (如 300ms) 内是否 接收到智能穿戴设备发送的数据, 若是, 则第二确定单元 607确认数据同步成功 ; 若否, 第二确定单元 607确认数据同步失败, 触发重连单元 602记录数据中已 同步数据的数据标记, 重新连接蓝牙。 实施本发明实施例, 可以通过检测单元 6 06检测是否接收到智能穿戴设备发送的数据来判断数据同步是否成功。
[0178] 本发明实施例中, 第一发送单元 601向智能穿戴设备发送数据请求指令, 以使 智能穿戴设备向移动终端同步数据; 检测单元 606检测是否接收到智能穿戴设备 发送的数据, 若是, 则第二确定单元 607确认数据同步成功; 若否, 第二确定单 元 607确认数据同步失败, 当第二确定单元 607确认数据同步失败吋, 重连单元 6 02记录数据中已同步数据的数据标记, 重新连接蓝牙; 当重新连接蓝牙成功吋 , 第二发送单元 603向智能穿戴设备发送数据标记, 以使智能穿戴设备根据数据 标记继续同步数据中未同步数据; 当重新连接蓝牙失败吋, 第一触发单元 604触 发重连单元 602重新连接蓝牙; 当检测到重新连接蓝牙失败的次数超过第一预设 次数吋, 第一确定单元 605确定移动终端与智能穿戴设备连接失败。 实施本发明 实施例, 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 重连单元 602 不再重新连接蓝牙, 第一确定单元 605确定移动终端与智能穿戴设备连接失败, 避免了当检测到重新连接蓝牙失败吋, 重连单元 602不断的重新连接蓝牙导致极 大的消耗智能穿戴设备中的电量, 从而可以节省智能穿戴设备电量。
[0179] 基于图 1所示的网络构架, 本发明实施例公幵了另一种移动终端, 请参阅图 9, 图 9是本发明实施例公幵的另一种移动终端的结构示意图。 如图 9所示, 本实施 例中所描述的移动终端, 除了包括图 6所描述的第一发送单元 601、 重连单元 602 、 第二发送单元 603、 第一触发单元 604、 第一确定单元 605、 检测单元 606和第 二确定单元 607之外, 还包括判断单元 608、 第二触发单元 609和第三触发单元 61 0, 其中:
[0180] 判断单元 608, 用于判断数据是否为重要数据。
[0181] 第二触发单元 609, 用于当判断单元 608判断结果为是吋, 且当重新连接蓝牙成 功吋, 触发第二发送单元 603向智能穿戴设备发送数据标记, 以使智能穿戴设备 根据数据标记继续同步数据中未同步数据。 [0182] 第三触发单元 610, 用于当判断单元 608判断结果为是吋, 且当重新连接蓝牙失 败吋, 触发重连单元 602重新连接蓝牙, 直至重连单元 602连接成功为止。
[0183] 本发明实施例中, 重要数据可以为用户预先设定的重要数据类型, 当判断单元
608判断该数据类型归属与重要数据类型吋, 确定该数据为重要数据, 举例来说 , 重要数据可以为心率数据 (如, 当佩戴智能穿戴设备的用户为心脏病患者是 , 可以设定心率数据为重要数据) 、 体温数据等。 当判断单元 608判断数据为重 要数据吋, 若重新连接蓝牙成功, 第二触发单元 609触发第二发送单元 603向智 能穿戴设备发送数据标记, 以使智能穿戴设备根据数据标记继续同步数据中未 同步数据; 若重新连接蓝牙失败, 第三触发单元 610触发重连单元 602重新连接 蓝牙, 直至重连单元 602连接成功为止。 实施本发明实施例, 对于重要数据, 可 以不限定重新连接蓝牙的次数, 保证智能穿戴设备中的重要数据尽可能快的同 步到移动终端中, 保证智能穿戴设备中的重要数据及吋同步到移动终端中。
[0184] 本发明实施例中, 第一发送单元 601向智能穿戴设备发送数据请求指令, 以使 智能穿戴设备向移动终端同步数据; 检测单元 606检测是否接收到智能穿戴设备 发送的数据, 若是, 则第二确定单元 607确认数据同步成功; 若否, 第二确定单 元 607确认数据同步失败, 当第二确定单元 607确认数据同步失败吋, 重连单元 6 02记录数据中已同步数据的数据标记, 重新连接蓝牙; 判断单元 608判断数据是 否为重要数据, 若是, 当重新连接蓝牙失败吋, 第三触发单元 610触发重连单元 602重新连接蓝牙, 直至蓝牙连接成功为止; 当重新连接蓝牙成功吋, 第二发送 单元 603向智能穿戴设备发送数据标记, 以使智能穿戴设备根据数据标记继续同 步数据中未同步数据; 当重新连接蓝牙失败吋, 第一触发单元 604触发重连单元 602重新连接蓝牙; 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 第 一确定单元 605确定移动终端与智能穿戴设备连接失败。 实施本发明实施例, 当 检测到重新连接蓝牙失败的次数超过第一预设次数吋, 重连单元 602不再重新连 接蓝牙, 第一确定单元 605确定移动终端与智能穿戴设备连接失败, 避免了当检 测到重新连接蓝牙失败吋, 重连单元 602不断的重新连接蓝牙导致极大的消耗智 能穿戴设备中的电量, 从而可以节省智能穿戴设备电量,
[0185] 基于图 1所示的网络构架, 本发明实施例公幵了一种智能穿戴设备, 请参阅图 1 0, 图 10是本发明实施例公幵的一种智能穿戴设备的结构示意图。 如图 10所示, 本实施例中所描述的智能穿戴设备, 包括接收单元 1001、 重连单元 1002、 同步 单元 1003、 触发单元 1004和确定单元 1005, 其中:
[0186] 接收单元 1001 , 用于接收移动终端发送的数据请求指令, 向移动终端同步数据
[0187] 本发明实施例中, 当移动终端需要同步智能穿戴设备中的数据吋, 移动终端向 智能穿戴设备发送数据请求指令, 接收单元 1001接收移动终端发送的数据请求 指令, 向移动终端同步数据。 在接收单元 1001接收移动终端发送的数据请求指 令之前, 移动终端与智能穿戴设备需要通过蓝牙连接。
[0188] 重连单元 1002, 用于当智能穿戴设备检测到数据同步失败吋, 记录数据中未同 步数据的数据标记, 重新连接蓝牙。
[0189] 本发明实施例中, 在智能穿戴设备向移动终端同步数据吋, 当智能穿戴设备检 测到数据同步失败吋, 重连单元 1002记录数据中未同步数据的数据标记, 重新 连接蓝牙。 智能穿戴设备向移动终端同步的数据可以包括多条数据, 每一条数 据均携带一个唯一的数据标记, 当智能穿戴设备检测到数据同步失败吋, 重连 单元 1002记录多条数据中未同步数据的数据标记, 并重新连接蓝牙。
[0190] 同步单元 1003, 用于当重新连接蓝牙成功吋, 根据数据标记继续同步数据中未 同步数据。
[0191] 本发明实施例中, 当重新连接蓝牙成功吋, 同步单元 1003根据数据中未同步数 据的数据标记继续同步数据中未同步数据。
[0192] 触发单元 1004, 用于当重连单元 1002重新连接蓝牙失败吋, 触发重连单元 1002 重新连接蓝牙。
[0193] 本发明实施例中, 当重连单元 1002重新连接蓝牙失败吋, 触发重连单元 1002记 录数据中未同步数据的数据标记, 重新连接蓝牙。
[0194] 确定单元 1005, 用于当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 确定移动终端与智能穿戴设备连接失败。
[0195] 本发明实施例中, 智能穿戴设备统计重新连接蓝牙失败的次数, 当检测到重新 连接蓝牙失败的次数超过第一预设次数吋, 确定单元 1005确定移动终端与智能 穿戴设备连接失败。 第一预设次数可以通过用户预先设定, 第一预设次数可以 设定为任意次数, 如, 1次, 2次, 3次, 4次, 5次等, 优选的, 第一预设次数设 置为 3次, 当检测到重新连接蓝牙失败的次数超过 3次数吋, 确定单元 1005确定 移动终端与智能穿戴设备连接失败。 实施本发明实施例, 当检测到重新连接蓝 牙失败的次数超过第一预设次数吋, 重连单元 1002不再重新连接蓝牙, 确定单 元 1005确定移动终端与智能穿戴设备连接失败, 避免了当检测到重新连接蓝牙 失败吋, 重连单元 1002不断的重新连接蓝牙导致极大的消耗智能穿戴设备中的 电量, 从而可以节省智能穿戴设备电量。
[0196] 本发明实施例中, 接收单元 1001接收移动终端发送的数据请求指令, 向移动终 端同步数据; 当智能穿戴设备检测到数据同步失败吋, 重连单元 1002记录数据 中未同步数据的数据标记, 重新连接蓝牙; 当重新连接蓝牙成功吋, 同步单元 1 003根据数据标记继续同步数据中未同步数据; 当重新连接蓝牙失败吋, 触发单 元 1004触发重连单元 1002重新连接蓝牙; 当检测到重新连接蓝牙失败的次数超 过第一预设次数吋, 确定单元 1005确定移动终端与智能穿戴设备连接失败。 实 施本发明实施例, 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 重 连单元 1002不再重新连接蓝牙, 确定单元 1005确定移动终端与智能穿戴设备连 接失败, 避免了当检测到重新连接蓝牙失败吋, 重连单元 1002不断的重新连接 蓝牙导致极大的消耗智能穿戴设备中的电量, 从而可以节省智能穿戴设备电量
[0197] 请参阅图 11 , 图 11是本发明实施例公幵的另一种移动终端的结构示意图。 如图
11所示, 该移动终端包括蓝牙模块 2001、 处理器 2002和储存器 2003, 其中, 处 理器 2002分别通过总线连接存储器 2003以及蓝牙模块 2001 , 其中, 存储器 2003 用于存储数据同步程序, 而处理器 2002用于读取存储器 2003存储的数据同步程 序以执行下述操作:
[0198] 向智能穿戴设备发送数据请求指令, 以使智能穿戴设备向移动终端同步数据; [0199] 当检测到数据同步失败吋, 记录数据中已同步数据的数据标记, 蓝牙模块 2001 重新连接蓝牙;
[0200] 当重新连接蓝牙成功吋, 向智能穿戴设备发送数据标记, 以使智能穿戴设备根 据数据标记继续同步数据中未同步数据;
[0201] 当重新连接蓝牙失败吋, 执行蓝牙模块 2001重新连接蓝牙的步骤;
[0202] 当检测到重新连接蓝牙失败的次数超过第一预设次数吋, 确定移动终端与智能 穿戴设备连接失败。
[0203] 本发明实施例中, 处理器 2002向智能穿戴设备发送数据请求指令, 以使智能穿 戴设备向移动终端同步数据, 包括:
[0204] 向智能穿戴设备发送数据请求指令并幵始计吋, 以使智能穿戴设备响应数据请 求指令返回数据请求确认指令;
[0205] 判断在预设吋长内是否收到智能穿戴设备返回的数据请求确认指令;
[0206] 若是, 向智能穿戴设备发送数据同步指令, 以使智能穿戴设备向移动终端同步 数据;
[0207] 若否, 确定数据请求确认超吋, 执行向智能穿戴设备发送数据同步指令并幵始 计吋的步骤;
[0208] 当检测到确定数据请求确认超吋的次数超过第二预设次数吋, 确定数据请求确 认失败。
[0209] 在一个实施例中, 当处理器 2002检测到数据同步失败吋, 记录数据中已同步数 据的数据标记, 重新连接蓝牙之前, 还执行以下操作:
[0210] 检测是否接收到智能穿戴设备发送的数据;
[0211] 若否, 确认数据同步失败。
[0212] 在一个实施例中, 当处理器 2002检测到数据同步失败吋, 记录数据中已同步数 据的数据标记, 重新连接蓝牙之后, 还执行以下操作:
[0213] 判断数据是否为重要数据;
[0214] 若是, 当重新连接蓝牙成功吋, 执行向智能穿戴设备发送数据标记, 以使智能 穿戴设备根据数据标记继续同步数据中未同步数据的步骤; 当重新连接蓝牙失 败吋, 执行重新连接蓝牙的步骤, 直至蓝牙连接成功为止。
[0215] 可见, 实施图 11所描述的移动终端, 当检测到重新连接蓝牙失败的次数超过第 一预设次数吋, 移动终端不再重新连接蓝牙, 确定移动终端与智能穿戴设备连 接失败, 避免了当检测到重新连接蓝牙失败吋, 移动终端不断的重新连接蓝牙 导致极大的消耗智能穿戴设备中的电量, 从而可以节省智能穿戴设备电量。
[0216] 本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可 以通过程序来指令相关的硬件来完成, 该程序可以存储于一计算机可读存储介 质中, 存储介质可以包括: 闪存盘、 只读存储器 (Read-Only Memory , ROM ) 、 随机存取器 (Random Access Memory, RAM) 、 磁盘或光盘等。
[0217] 以上对本发明实施例所提供的一种数据同步方法、 移动终端及智能穿戴设备进 行了详细介绍, 本文中应用了具体个例对本发明的原理及实施方式进行了阐述 , 以上实施例的说明只是用于帮助理解本发明的方法及其核心思想; 同吋, 对 于本领域的一般技术人员, 依据本发明的思想, 在具体实施方式及应用范围上 均会有改变之处, 综上所述, 本说明书内容不应理解为对本发明的限制。
技术问题
问题的解决方案
发明的有益效果

Claims

权利要求书
[权利要求 1] 一种数据同步方法, 其特征在于, 包括:
移动终端向智能穿戴设备发送数据请求指令, 以使所述智能穿戴设备 向所述移动终端同步数据;
当所述移动终端检测到所述数据同步失败吋, 所述移动终端记录所述 数据中已同步数据的数据标记, 重新连接蓝牙; 当重新连接蓝牙成功吋, 所述移动终端向所述智能穿戴设备发送所述 数据标记, 以使所述智能穿戴设备根据所述数据标记继续同步所述数 据中未同步数据;
当重新连接蓝牙失败吋, 所述移动终端执行所述重新连接蓝牙的步骤 当检测到所述重新连接蓝牙失败的次数超过第一预设次数吋, 所述移 动终端确定所述移动终端与所述智能穿戴设备连接失败。
[权利要求 2] 根据权利要求 1所述的方法, 其特征在于, 所述移动终端向智能穿戴 设备发送数据请求指令, 以使所述智能穿戴设备向所述移动终端同步 数据, 包括:
所述移动终端向智能穿戴设备发送数据请求指令并幵始计吋, 以使所 述智能穿戴设备响应所述数据请求指令返回数据请求确认指令; 所述移动终端判断在预设吋长内是否收到所述智能穿戴设备返回的所 述数据请求确认指令;
若是, 所述移动终端向所述智能穿戴设备发送数据同步指令, 以使所 述智能穿戴设备向移动终端同步数据;
若否, 所述移动终端确定所述数据请求确认超吋, 执行所述向智能穿 戴设备发送数据请求指令并幵始计吋的步骤;
当检测到确定所述数据请求确认超吋的次数超过第二预设次数吋, 所 述移动终端确定所述数据请求确认失败。
[权利要求 3] 根据权利要求 2所述的方法, 其特征在于, 所述当检测到所述数据同 步失败吋, 所述移动终端记录所述数据中已同步数据的数据标记, 重 新连接蓝牙之前, 所述方法还包括:
所述移动终端检测是否接收到所述智能穿戴设备发送的所述数据; 若否, 所述移动终端确认所述数据同步失败。
[权利要求 4] 根据权利要求 1~3任一项所述的方法, 其特征在于, 所述当检测到所 述数据同步失败吋, 所述移动终端记录所述数据中已同步数据的数据 标记, 重新连接蓝牙之后, 所述方法还包括:
所述移动终端判断所述数据是否为重要数据;
若是, 当所述重新连接蓝牙成功吋, 执行所述移动终端向所述智能穿 戴设备发送所述数据标记, 以使所述智能穿戴设备根据所述数据标记 继续同步所述数据中未同步数据的步骤; 当所述重新连接蓝牙失败吋 , 执行所述移动终端重新连接蓝牙的步骤, 直至所述蓝牙连接成功为 止。
[权利要求 5] —种数据同步方法, 其特征在于, 包括:
所述智能穿戴设备接收移动终端发送的数据请求指令, 向所述移动终 端同步数据;
当所述智能穿戴设备检测到所述数据同步失败吋, 所述智能穿戴设备 记录所述数据中未同步数据的数据标记, 重新连接蓝牙;
当重新连接蓝牙成功吋, 所述智能穿戴设备根据所述数据标记继续同 步所述数据中所述未同步数据;
当重新连接蓝牙失败吋, 所述智能穿戴设备执行所述重新连接蓝牙的 步骤;
当检测到所述重新连接蓝牙失败的次数超过第一预设次数吋, 所述智 能穿戴设备确定所述移动终端与所述智能穿戴设备连接失败。
[权利要求 6] —种移动终端, 其特征在于, 包括:
第一发送单元, 用于向智能穿戴设备发送数据请求指令, 以使所述智 能穿戴设备向所述移动终端同步数据;
重连单元, 用于当检测到所述数据同步失败吋, 记录所述数据中已同 步数据的数据标记, 重新连接蓝牙; 第二发送单元, 还用于当所述重连单元重新连接蓝牙成功吋, 向所述 智能穿戴设备发送所述数据标记, 以使所述智能穿戴设备根据所述数 据标记继续同步所述数据中未同步数据;
第一触发单元, 用于当所述重连单元重新连接蓝牙失败吋, 触发所述 重连单元重新连接蓝牙;
第一确定单元, 用于当检测到所述重新连接蓝牙失败的次数超过第一 预设次数吋, 确定所述移动终端与所述智能穿戴设备连接失败。
[权利要求 7] 根据权利要求 6所述的移动终端, 其特征在于, 所述第一发送单元包 括:
第一发送子单元, 用于向智能穿戴设备发送数据请求指令并幵始计吋 , 以使所述智能穿戴设备响应所述数据请求指令返回数据请求确认指 令;
判断子单元, 用于判断在预设吋长内是否收到所述智能穿戴设备返回 的所述数据请求确认指令;
第二发送子单元, 用于当所述判断子单元判断结果为是吋, 向所述智 能穿戴设备发送数据同步指令, 以使所述智能穿戴设备向移动终端同 步数据;
第一确定子单元, 用于当所述判断子单元判断结果为否吋, 确定所述 数据请求确认超吋, 触发所述第一发送子单元向智能穿戴设备发送数 据请求指令并幵始计吋;
第二确定子单元, 用于当检测到确定所述数据请求确认超吋的次数超 过第二预设次数吋, 确定所述数据请求确认失败。
[权利要求 8] 根据权利要求 7所述的移动终端, 其特征在于, 所述移动终端还包括 检测单元, 用于检测是否接收到所述智能穿戴设备发送的所述数据; 第二确定单元, 用于当所述检测单元检测结果为否吋, 确认所述数据 同步失败。
[权利要求 9] 根据权利要求 6~8任一项所述的移动终端, 其特征在于, 所述移动终 端还包括:
判断单元, 用于判断所述数据是否为重要数据; 第二触发单元, 用于当所述判断单元判断结果为是吋, 且当所述重新 连接蓝牙成功吋, 触发所述第二发送单元向所述智能穿戴设备发送所 述数据标记, 以使所述智能穿戴设备根据所述数据标记继续同步所述 数据中未同步数据;
第三触发单元, 用于当所述判断单元判断结果为是吋, 且当所述重新 连接蓝牙失败吋, 触发所述重连单元重新连接蓝牙, 直至所述重连单 元连接成功为止。
[权利要求 10] —种智能穿戴设备, 其特征在于, 包括:
接收单元, 用于接收移动终端发送的数据请求指令, 向所述移动终端 同步数据;
重连单元, 用于当所述智能穿戴设备检测到所述数据同步失败吋, 记 录所述数据中未同步数据的数据标记, 重新连接蓝牙;
同步单元, 用于当重新连接蓝牙成功吋, 根据所述数据标记继续同步 所述数据中所述未同步数据;
触发单元, 用于当所述重连单元重新连接蓝牙失败吋, 触发所述重连 单元重新连接蓝牙;
确定单元, 用于当检测到所述重新连接蓝牙失败的次数超过第一预设 次数吋, 确定所述移动终端与所述智能穿戴设备连接失败。
[权利要求 11] 一种移动终端, 其特征在于, 包括蓝牙模块、 处理器和存储器, 所述 处理器执行如下步骤:
向智能穿戴设备发送数据请求指令, 以使所述智能穿戴设备向所述移 动终端同步数据;
当所述移动终端检测到所述数据同步失败吋, 记录所述数据中已同步 数据的数据标记, 重新连接蓝牙;
当重新连接蓝牙成功吋, 向所述智能穿戴设备发送所述数据标记, 以 使所述智能穿戴设备根据所述数据标记继续同步所述数据中未同步数 据;
当重新连接蓝牙失败吋, 执行所述重新连接蓝牙的步骤;
当检测到所述重新连接蓝牙失败的次数超过第一预设次数吋, 确定所 述移动终端与所述智能穿戴设备连接失败。
[权利要求 12] 根据权利要求 11所述的方法, 其特征在于, 所述处理器向智能穿戴设 备发送数据请求指令, 以使所述智能穿戴设备向所述移动终端同步数 据, 包括:
向智能穿戴设备发送数据请求指令并幵始计吋, 以使所述智能穿戴设 备响应所述数据请求指令返回数据请求确认指令; 判断在预设吋长内是否收到所述智能穿戴设备返回的所述数据请求确 认指令;
若是, 向所述智能穿戴设备发送数据同步指令, 以使所述智能穿戴设 备向移动终端同步数据;
若否, 确定所述数据请求确认超吋, 执行所述向智能穿戴设备发送数 据请求指令并幵始计吋的步骤;
当检测到确定所述数据请求确认超吋的次数超过第二预设次数吋, 确 定所述数据请求确认失败。
[权利要求 13] 根据权利要求 12所述的移动终端, 其特征在于, 当所述处理器检测到 所述数据同步失败吋, 记录所述数据中已同步数据的数据标记, 重新 连接蓝牙之前, 所述方法还包括:
检测是否接收到所述智能穿戴设备发送的所述数据;
若否, 确认所述数据同步失败。
[权利要求 14] 根据权利要求 11~13任一项所述的移动终端, 其特征在于, 当所述处 理器检测到所述数据同步失败吋, 记录所述数据中已同步数据的数据 标记, 重新连接蓝牙之后, 所述方法还包括:
判断所述数据是否为重要数据;
若是, 当所述重新连接蓝牙成功吋, 执行向所述智能穿戴设备发送所 述数据标记, 以使所述智能穿戴设备根据所述数据标记继续同步所述 数据中未同步数据的步骤; 当所述重新连接蓝牙失败吋, 执行重新连 接蓝牙的步骤, 直至所述蓝牙连接成功为止。
PCT/CN2015/092996 2015-10-27 2015-10-27 一种数据同步方法、移动终端及智能穿戴设备 WO2017070854A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2015/092996 WO2017070854A1 (zh) 2015-10-27 2015-10-27 一种数据同步方法、移动终端及智能穿戴设备
CN201580002060.XA CN105917677A (zh) 2015-10-27 2015-10-27 一种数据同步方法、移动终端及智能穿戴设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2015/092996 WO2017070854A1 (zh) 2015-10-27 2015-10-27 一种数据同步方法、移动终端及智能穿戴设备

Publications (1)

Publication Number Publication Date
WO2017070854A1 true WO2017070854A1 (zh) 2017-05-04

Family

ID=56744387

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/092996 WO2017070854A1 (zh) 2015-10-27 2015-10-27 一种数据同步方法、移动终端及智能穿戴设备

Country Status (2)

Country Link
CN (1) CN105917677A (zh)
WO (1) WO2017070854A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107135474B (zh) * 2017-06-15 2019-12-20 北京一数科技有限公司 一种数据同步方法、装置及移动设备
CN107371224A (zh) * 2017-07-18 2017-11-21 深圳天珑无线科技有限公司 一种无线通信设备连接信号的方法、设备以及存储装置
CN109391927A (zh) * 2018-03-29 2019-02-26 展讯通信(上海)有限公司 Ble设备自动重连方法及装置
CN117350696B (zh) * 2023-12-05 2024-05-31 深圳市光速时代科技有限公司 一种智能手表对逾期任务数据的消除方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179302A (zh) * 2006-11-09 2008-05-14 中兴通讯股份有限公司 蓝牙电话终端设备实现蓝牙耳机应用的方法
CN103518418A (zh) * 2012-09-27 2014-01-15 华为终端有限公司 一种蓝牙设备之间连接的方法及设备
US8645772B2 (en) * 2010-08-25 2014-02-04 Itron, Inc. System and method for managing uncertain events for communication devices
CN103581421A (zh) * 2012-08-02 2014-02-12 北京千橡网景科技发展有限公司 一种移动终端的照片分享方法和装置
CN104993934A (zh) * 2015-06-30 2015-10-21 惠州Tcl移动通信有限公司 一种智能穿戴设备与移动终端连接处理方法及系统

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8155055B2 (en) * 2007-09-14 2012-04-10 Sony Ericsson Mobile Communications Ab Automatic re-connection of a previously lost connection in a frequency hopping communication system
CN101217295B (zh) * 2007-12-29 2011-10-26 华为终端有限公司 基于蓝牙技术的文件发送方法、接收方法及装置
CN101877604B (zh) * 2010-06-22 2015-01-28 中兴通讯股份有限公司 一种传输文件的方法及系统
CN101883144B (zh) * 2010-06-30 2013-02-20 北京神州泰岳软件股份有限公司 基于sip的文件断点续传方法
CN102694677A (zh) * 2012-04-11 2012-09-26 佳都新太科技股份有限公司 基于远程ip解析灾备数据中心的建设新方法
CN104219038A (zh) * 2014-08-27 2014-12-17 小米科技有限责任公司 一种同步数据的方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101179302A (zh) * 2006-11-09 2008-05-14 中兴通讯股份有限公司 蓝牙电话终端设备实现蓝牙耳机应用的方法
US8645772B2 (en) * 2010-08-25 2014-02-04 Itron, Inc. System and method for managing uncertain events for communication devices
CN103581421A (zh) * 2012-08-02 2014-02-12 北京千橡网景科技发展有限公司 一种移动终端的照片分享方法和装置
CN103518418A (zh) * 2012-09-27 2014-01-15 华为终端有限公司 一种蓝牙设备之间连接的方法及设备
CN104993934A (zh) * 2015-06-30 2015-10-21 惠州Tcl移动通信有限公司 一种智能穿戴设备与移动终端连接处理方法及系统

Also Published As

Publication number Publication date
CN105917677A (zh) 2016-08-31

Similar Documents

Publication Publication Date Title
US10057673B2 (en) Electronic device and operating method thereof
US20220086554A1 (en) Method of controlling charging level in audio device that is connectable to electronic device
WO2017070854A1 (zh) 一种数据同步方法、移动终端及智能穿戴设备
EP3462802B1 (en) Bluetooth connection method and terminal
US20200125580A1 (en) Data synchronization method, apparatus, and system
US9800718B2 (en) Method for controlling wearable electronic devices, central apparatus, and central device
US20180110021A1 (en) Method and device for measuring amount of user physical activity
KR101080359B1 (ko) Lte 네트워크의 긴급통화를 위한 rrc 연결 재구축 방법
CN105302284B (zh) 一种智能穿戴设备的控制方法、装置及系统
KR20200044505A (ko) 링크 공유를 지원하는 전자 장치 및 이를 위한 방법
US8942685B2 (en) Callback options via wireless device
WO2020156425A1 (zh) 信息传输方法、终端设备和网络侧设备
US20160286594A1 (en) Method for establishing communications between peer devices, wireless communication device using the same and computer-readable medium
EP3016359B1 (en) Data processing method, terminal, subscriber identity module card, and system
CN115811520B (zh) 分布式系统中主节点的选举方法、装置和电子设备
UA127950C2 (uk) Спосіб роботи у випадку втрати зв'язку та абонентське обладнання
CN114245362A (zh) 设备回连方法和蓝牙外设
KR101781271B1 (ko) 캐시 일관성을 위한 제어 시스템 및 방법
CN111448825B (zh) 一种传输控制方法及设备
WO2013091449A1 (en) Connecting wireless devices
CN114157677A (zh) 数据同步方法及相关产品
US11513765B2 (en) Bluetooth audio device, Bluetooth audio system and operating method thereof
CN115086828B (zh) 耳机控制方法及相关装置
WO2023197709A1 (zh) 器件识别方法和相关装置
EP3989215A1 (en) Synchronous display blinking

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: 15906920

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: 15906920

Country of ref document: EP

Kind code of ref document: A1