WO2018094677A1 - 低功耗蓝牙ble设备、数据更新系统及方法 - Google Patents

低功耗蓝牙ble设备、数据更新系统及方法 Download PDF

Info

Publication number
WO2018094677A1
WO2018094677A1 PCT/CN2016/107201 CN2016107201W WO2018094677A1 WO 2018094677 A1 WO2018094677 A1 WO 2018094677A1 CN 2016107201 W CN2016107201 W CN 2016107201W WO 2018094677 A1 WO2018094677 A1 WO 2018094677A1
Authority
WO
WIPO (PCT)
Prior art keywords
ble
data
update data
update
ble device
Prior art date
Application number
PCT/CN2016/107201
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 EP16909741.7A priority Critical patent/EP3352525B1/en
Priority to PCT/CN2016/107201 priority patent/WO2018094677A1/zh
Priority to KR1020187003485A priority patent/KR102001792B1/ko
Priority to CN201680001565.9A priority patent/CN107041171B/zh
Priority to US15/879,769 priority patent/US20180150291A1/en
Publication of WO2018094677A1 publication Critical patent/WO2018094677A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/22—Processing or transfer of terminal data, e.g. status or physical capabilities
    • H04W8/24—Transfer of terminal data
    • H04W8/245—Transfer of terminal data from a network towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W84/00—Network topologies
    • H04W84/18—Self-organising networks, e.g. ad-hoc networks or sensor networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M1/00—Substation equipment, e.g. for use by subscribers
    • H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724—User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72406—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by software upgrading or downloading
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M2250/00—Details of telephonic subscriber devices
    • H04M2250/02—Details of telephonic subscriber devices including a Bluetooth interface
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to the field of wireless communications, and in particular, to a low power Bluetooth BLE device, a data update system, and a method.
  • OTA Over-the-Air Technology
  • OTA over-the-air
  • the object of the embodiments of the present invention is to provide a low-power Bluetooth BLE device, a data update system and a method, and automatically transmit the update data in the BLE network without manual intervention, without requiring manual intervention, so that the system update of the device in the BLE network is more simple.
  • an embodiment of the present invention provides a low-power Bluetooth BLE device, including a processor and a BLE communication module, where the processor is configured to trigger the BLE communication module when the BLE device acquires update data. Pass the updated data to the surrounding BLE via the BLE link And the device until the peripheral BLE device detects that the update data is obtained; wherein the peripheral BLE device is a device capable of performing end-to-end BLE communication with the BLE device that obtains the update data.
  • Embodiments of the present invention also provide a data update system including a plurality of the above-described Bluetooth low energy BLE devices.
  • An embodiment of the present invention further provides a data update method, including: after the BLE device acquires the update data, transmitting the update data to the neighboring BLE device through the BLE link until the peripheral BLE device is detected to be obtained. And the updating the data; wherein the peripheral BLE device is a device capable of performing end-to-end BLE communication with the BLE device that obtains the update data.
  • the embodiment of the present invention transmits the update data to the surrounding BLE device by using the BLE device with BLE wireless transmission capability when the update data is acquired, without manual intervention, without a specific background server, and automatically in the BLE network.
  • the update data is passed in, making system updates of devices in the BLE network easier.
  • FIG. 2 is a schematic structural diagram of a low power Bluetooth BLE device according to a first embodiment of the present invention
  • FIG. 3 is a schematic structural diagram of a low power consumption Bluetooth BLE device including an encryption module according to a second embodiment of the present invention
  • FIG. 4 is a schematic structural diagram of a Bluetooth low energy BLE device including a decryption module according to a second embodiment of the present invention
  • FIG. 5 is a schematic structural diagram of a low power Bluetooth BLE device according to a third embodiment of the present invention.
  • FIG. 6 is a schematic diagram showing the operation of a data updating system according to a fourth embodiment of the present invention.
  • FIG. 7 is a schematic diagram showing the operation of a data updating system according to a fifth embodiment of the present invention.
  • FIG. 8 is a schematic flowchart diagram of a data updating method according to a sixth embodiment of the present invention.
  • FIG. 9 is a schematic flow chart of a data updating method according to a seventh embodiment of the present invention.
  • FIG. 10 is a schematic flowchart diagram of a data updating method according to an eighth embodiment of the present invention.
  • FIG. 11 is a schematic flowchart of an execution of an update publishing device in a data updating method according to a ninth embodiment of the present invention.
  • FIG. 12 is a schematic flowchart of execution of a device other than an update publishing device in a data updating method according to a ninth embodiment of the present invention.
  • FIG. 13 is a schematic flowchart of an execution of an update publishing device in a data updating method according to a tenth embodiment of the present invention.
  • FIG. 14 is a schematic flowchart of execution of a device other than an update publishing device in a data updating method according to a tenth embodiment of the present invention.
  • Figure 15 is a flow chart showing a data updating method according to an eleventh embodiment of the present invention.
  • a first embodiment of the present invention relates to a low power Bluetooth BLE device.
  • the Bluetooth low energy device (BLE) device 100 of the present embodiment is a device with Bluetooth communication capability, as shown in FIG. 2, which includes, but is not limited to, a processor 101, a memory 102, and a BLE communication module 103. And the antenna 104 and the like.
  • the processor 101 is configured to run system software in the memory 102 and trigger the BLE communication module 103 to complete communication with other BLE devices.
  • Processors in the present invention may use, but are not limited to, ARM, MIPS, or other MCU processors.
  • the processor of the embodiment may be separately established, or a component unit having a processor function may be integrated in one module.
  • the memory 102 is mainly used to store system software and update data, and can store one or more different versions of update data.
  • the initiator is transferred, the update data is taken out of the memory 102, and transmitted to the recipient via the BLE link.
  • the recipient then stores the update data in the memory 102 of the device.
  • the deposit policy includes but is not limited to: only one update data space, directly overwrite the old version; or save space with multiple update data, alternate coverage, and so on.
  • the memory 102 can use, but is not limited to, sram, norflash, nandflash, eeprom, etc., erasable and rewritten memory types.
  • the update data mentioned here includes, but is not limited to, update data of an application, update data of a BLE communication protocol stack, system configuration data, and the like.
  • the processor 101 triggers the BLE communication module 103 to transmit the update data to the neighboring BLE device through the BLE link until it detects that the neighboring BLE devices obtain the update data.
  • the peripheral BLE device is a device capable of performing end-to-end BLE communication with the BLE device that obtains the updated data.
  • the low-power Bluetooth BLE device can be a smart device (such as a smart phone), a wearable device (such as a wristband), and various types of sensors.
  • the BLE device implements the BLE communication protocol stack function through the BLE communication module 103.
  • the BLE communication module 103 and the antenna 104 together establish a BLE communication channel for the low power BLE device, and the low power BLE device can initiate a communication connection.
  • the acquired update data can be transmitted to other devices through the BLE link, and the low-power device automatic update system is completed.
  • the device A can establish a communication connection through the BLE communication module, that is, device A and device B, Device B and device C, and device A and device C can perform BLE communication separately.
  • the device A can deliver the update data to the device B and the device C capable of performing BLE communication with itself.
  • the device A detects that both B and C have obtained the update data, the device A no longer transmits the update data.
  • device B can deliver the update data to device A and device C capable of performing BLE communication with itself, and device B detects that both A and C have received the update data, and no longer transmits the update. data.
  • the BLE device can obtain update data through the outside world, for example, the user sends the update data to the update publishing device.
  • the BLE device can also obtain update data by receiving update data delivered by other devices. Regardless of how the BLE device obtains the updated data, it transmits the update data to its surrounding BLE device. Through this method of updating the data transfer, the multi-level transfer can automatically transfer the update data to any BLE in the network. The device thus enables automatic transfer of updated data in the BLE network.
  • the present embodiment transmits the update data to the surrounding BLE device by using the BLE device with BLE wireless transmission capability when the update data is acquired, without manual intervention, and does not need a specific background server to automatically transmit the update data in the BLE network. This makes system updates for devices in the BLE network easier.
  • a second embodiment of the present invention relates to a low power Bluetooth BLE device.
  • the second embodiment is further improved on the basis of the first embodiment.
  • the main improvement is that in the second embodiment, the BLE device ensures the security of the device update process by performing specific security policy processing on the update data.
  • the Bluetooth low energy BLE device may further include an encryption module 105.
  • the encryption module is configured to perform security processing on the update data when the BLE device is used as an update publishing device to form encrypted update data.
  • the BLE communication module is also used to pass encrypted update data to the surrounding BLE device.
  • the Bluetooth low energy BLE device may further include a decryption module 106.
  • the decryption module 106 is configured to perform security verification on the received update data when the BLE device is used as the update data receiver, and trigger the BLE device to perform system update when the verification succeeds; when the verification fails, the received update is received. Data is passed to the surrounding BLE device via the BLE communication module.
  • the BLE device transmits the received update data to the surrounding BLE device through the BLE communication module. That is to say, when the BLE device receives the update data, the update data can be directly transmitted without performing security verification on the update data.
  • the BLE device In the network, there are some BLE devices that are only passed as update data. The transfer device exists.
  • the security verification used by the security processing and decryption module 106 employed by the encryption module 105 should correspond.
  • the encryption module 105 and the decryption module 106 may exist separately, configure an encryption module for a BLE device (eg, an update distribution device) that needs to perform security processing on the update data, and a BLE device that receives update data (for example, a device to be updated or Relay device) Configure the decryption module.
  • the encryption module 105 and the decryption module 106 can also be bundled together as a module to invoke the execution of related functions when encryption or decryption is required.
  • the existing forms of the encryption module 105 and the decryption module 106 can be applied to the present application, and are not enumerated here.
  • the security policy may be determined by a specific implementation, and may be a policy that only negotiates both the update publishing device and the device to be updated. For example, extracting feature information of the update publishing device and/or the device to be updated, and mixing the updated data according to the negotiated security policy.
  • the encryption module 105 includes an extraction sub-module and a hybrid sub-module.
  • the extraction sub-module is used to extract device features.
  • the hybrid submodule is used to mix the extracted device features with the update data according to a preset rule, and the mixed data is used as encrypted update data.
  • the decryption module 106 includes a parsing sub-module and a matching sub-module.
  • the parsing submodule is configured to parse the device feature from the received update data.
  • the matching sub-module is used to match the parsed device features with the features of the BLE device, and when the matching is successful, the verification is successful; when the matching fails, the verification fails.
  • the extraction sub-module in the encryption module 105 extracts features of the BLE device.
  • the device features include, but are not limited to, updating the publishing device address, updating the publishing device location, the type of the device to be updated, the location of the device to be updated, the updated publishing device number, the number of the device to be updated, and the like.
  • the update publishing device address is the identity of the update publishing device and is fully network unique. Updating the publishing device location is to update the location information of the publishing device.
  • the type of device to be updated is the unique identifier of a class of products.
  • the location of the device to be updated is the device identifier of a certain address area. Update the release device number.
  • the number of the device to be updated is the number of the device on the network.
  • the hybrid sub-module 1052 extracts the features extracted from the sub-module and The new data is mixed according to preset rules to form encrypted updated data.
  • the BLE device implements security processing of the updated data.
  • the BLE device then passes the encrypted update data to the surrounding BLE device via the BLE communication module 103.
  • the parsing sub-module in the decryption module 106 parses the device feature in the received update data; the matching sub-module matches the parsed device feature with the feature of the device, and the matching is successful. That is, the verification is successful; if the matching fails, that is, the verification fails, and the BLE device completes the security verification of the updated data.
  • feature extraction of the version publishing device and the device to be updated may also be integrated into the system update data, and then transmitted to the device to be updated by the BLE network.
  • the device to be updated extracts feature values in the system update data, checks the rights of the version release device, and checks the features of the device, and then performs system update to ensure the security of the device update process.
  • the encryption module 105 may further perform encryption processing on the update data according to the key shared by the update publishing device and the device to be updated to form encrypted update data.
  • the decryption module 106 decrypts the received update data according to the key shared by the update publishing device and the device to be updated, and obtains decrypted data; and verifies the decryption.
  • the correctness of the data when the verification is correct, the verification is successful; when the verification fails, the verification fails.
  • the key is shared between the update publishing device and the device to be updated, for example, the key is shared between the update publishing device and the device to be updated in advance by other means.
  • the encryption module 105 encrypts the update data together with the key to form encrypted update data.
  • the BLE communication module 103 passes the encrypted update data to the surrounding BLE device.
  • the decryption module 106 decrypts the encrypted data using the shared key to obtain decrypted data.
  • the decryption module 106 verifies the correctness of the obtained decrypted data. When the verification is correct, the determination is successful, and the device performs system update. When the verification fails, it is determined that the verification fails, the device does not perform device update and transmits the encrypted data to the surrounding BLE device.
  • the low-power Bluetooth BLE device provided in this embodiment can prohibit unauthorized devices from issuing updates and update the specified devices, thereby ensuring the security of the BLE device when delivering updated data.
  • a third embodiment of the present invention relates to a low power Bluetooth BLE device.
  • the third embodiment is further improved on the basis of the first or second embodiment, and the main improvement is that in the third embodiment, the BLE device has the capability of automatically feeding back the updated device, and realizing the situation of the updated device. Collection statistics.
  • the Bluetooth low energy BLE device further includes a source address recording module 107.
  • the source address recording module 107 is configured to record the source device address when receiving the update data when the BLE device is the update data receiver; wherein the source device address is the address of the BLE device that delivers the update data to the BLE device.
  • the BLE communication module is further configured to: when the BLE device completes the system update, transfer the device information to the source device; or the BLE communication module is further configured to: when the BLE device receives the device information of the updated device, transmit the device information to the source device Device information of the received updated device.
  • the device address of the BLE device is the identifier of the device and has network-wide uniqueness.
  • the source address recording module 106 records the device address of the BLE device that sent the update data to the device.
  • BLE device A delivers update data to the surroundings
  • BLE device B receives the update data sent by device A
  • device B records the device address of device A through the source address module.
  • device B completes the system update
  • device B's own device information will be delivered to device A according to the recorded device address.
  • the device B receives the device information sent by the updated device, the device B transmits the device information of the received updated device to the device A according to the recorded device address.
  • the BLE device that receives the update data will record the device address of the source of the update data. After the system update of the device is completed, the device information of the device is sent to the source of the update data, and the update data is delivered to the next device. If the device does not need to be updated, continue to pass the update data to the next device.
  • BLE devices all have the ability to pass device information of updated devices from other devices to the source of the updated data.
  • the device information mentioned here includes but not Limited to device address, device location, device type, etc.
  • a BLE device can be connected to multiple other BLE wireless devices to form a network.
  • the BLE device may be referred to as an update publishing device.
  • Any device can be an update publishing device.
  • the update publishing device can perform multi-level delivery by means of the above-mentioned update data delivery, and automatically transmit the update data to any BLE device on the network.
  • each device sends the device information of the updated device according to the recorded source address of the updated data of the previous level, until all the device information is fed back to the update publishing device of the updated data release, and then the update publishing device counts. Updated device status, such as quantity, device distribution, etc.
  • the source address recording module can be a single module or a part of the memory. Only the address of the source device can be recorded, and the device information can be accurately fed back according to the recorded address.
  • the application should not be limited by the record form of the source address, and any way of recording the source address should be within the scope of this application.
  • the low-power Bluetooth BLE device provided in this embodiment can quickly count the updated device situation, such as the number and distribution of updated devices, optimize the update data according to the statistical situation, and provide more perfect system update data to the user.
  • a fourth embodiment of the present invention relates to a data update system.
  • the data update system includes a low power Bluetooth BLE device mentioned in any one of the above-described first to third embodiments.
  • the data update system includes five BLE devices as an example. As shown in FIG. 6, it is assumed that the BLE device 1 is selected as the update publishing device, and the BLE device 5 is used as the device to be updated, and the process of updating the data in the network is:
  • the update data is transmitted to the BLE device 2 as shown in S61 of FIG.
  • the BLE device 2 When the BLE device 2 receives the update data, it transmits the received update data to its neighboring BLE device, and the peripheral devices of the BLE device 2 have the BLE device 3 and the BLE device 4, and therefore, the BLE device
  • the backup 2 delivers update data to the BLE device 3 and the BLE device 4, respectively, as shown in S62 and S63 of FIG.
  • the BLE device 3 When the BLE device 3 receives the update data, since there is only the BLE device 2 in its periphery, the BLE device 3 does not further transmit the update data.
  • the BLE device 4 When the BLE device 4 receives the update data, it transmits the update data to its peripheral device.
  • the peripheral device of the BLE device 3 has the BLE device 2 and the BLE device 5, and the BLE device 3 delivers the update data to the BLE device 5, as shown in S64 of FIG. .
  • the BLE device 5 After the BLE device 5 receives the update data, it performs system data update.
  • the link of BLE communication is end-to-end.
  • the device at one end of the link queries the other end device for the existence of the update data. If the version of the data is not present or the version of the updated data is low, the update data is transmitted; When the update data version is high, the update data is read and stored in the memory.
  • the timing of the device inquiring the updated data information of the other end device may be that after receiving the complete update data, the peer device may notify the device to query after receiving the complete update data.
  • the way to send and read updated data between devices includes, but is not limited to, file subcontracting, breakpoint retransmission, etc., to ensure the quality of the version delivery, and as far as possible does not affect the normal use of data transmission.
  • the data update system provided in this embodiment can realize that the BLE device under the system autonomously performs system update of the device without a server and without human intervention, thereby providing a simpler and faster update system for the user.
  • the present embodiment is a system embodiment corresponding to the first embodiment, and the present embodiment can be implemented in cooperation with the first embodiment.
  • the related technical details mentioned in the first embodiment are still effective in the present embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related art details mentioned in the present embodiment can also be applied to the first embodiment.
  • a fifth embodiment of the present invention relates to a data update system.
  • the fifth embodiment is further improved on the basis of the fourth embodiment, and the specific improvement is: in the fifth embodiment, the number
  • the update system can collect updates on statistical devices.
  • any one of the BLE devices in the data update system transmits its own device information to the source device when the BLE device completes the system update.
  • the BLE device receives the device information of the updated device, the BLE device transmits the device information of the received updated device to the source device until the update publishing device acquires all the updated devices.
  • the source device is a BLE device that delivers update data to the BLE device.
  • any one BLE device has the ability to transfer the device information of the updated device transmitted from other devices to the source of the updated data.
  • An update case collection statistic is performed after the update data is transmitted in the five BLE devices exemplified in the fourth embodiment as an example:
  • the BLE device 5 After the BLE device 5 completes the data update, it feeds back its own device information to the BLE device 4, as shown by S71 in FIG.
  • the BLE device 4 Upon receiving the device information fed back by the BLE device 5, the BLE device 4 feeds back the device information of the BLE device 5 to the BLE device 2, as shown in S72 of FIG.
  • the BLE device 2 Upon receiving the device information fed back by the BLE device 5, the BLE device 2 feeds back the device information of the BLE device 5 to the BLE device 1, as shown in S73 of FIG.
  • the BLE device 1 collects statistics on the received device information.
  • the data update system provided in this embodiment can quickly count the updated devices in the system, such as the number and distribution of updated devices, optimize update data according to statistical conditions, and provide users with more perfect system updates. data.
  • the present embodiment is a system embodiment corresponding to the third embodiment, and the present embodiment can be implemented in cooperation with the third embodiment.
  • the related technical details mentioned in the third embodiment are still effective in the present embodiment, and are not described herein again in order to reduce repetition. Accordingly, the related art details mentioned in the present embodiment can also be applied to the third embodiment.
  • a sixth embodiment of the present invention relates to a data updating method.
  • the data update method is based on the low power Bluetooth BLE device described in the first embodiment.
  • the specific process of the data update method is as shown in FIG. 8, which includes:
  • step S81 the update data is acquired.
  • the BLE device is used as an update publishing device to obtain update data from the outside world; and the second method is to update data transmitted from other BLE devices.
  • Step S82 the acquired update data is delivered to one of the surrounding BLE devices.
  • step S83 it is determined whether all the peripheral BLE devices have acquired the update data. If not, the process returns to step S82; if so, the process ends.
  • the BLE device after acquiring the update data, the BLE device will autonomously transfer the BLE device update data to the surroundings, and if the surrounding BLE devices have obtained the update data, stop transmitting the update data to the surrounding BLE device.
  • the low-power Bluetooth BLE device realizes autonomous transfer of update data without a server and without human intervention until the peripheral BLE devices obtain updated data.
  • the low-power Bluetooth BLE device system update is no longer dependent on the server, and the system can be updated autonomously for user's convenience.
  • a seventh embodiment of the present invention relates to a data updating method.
  • the seventh embodiment is further improved on the basis of the sixth embodiment, and is improved in that, in the seventh embodiment, A BLE device is used as a method of transferring update data from a device to a surrounding BLE device.
  • the BLE device After the BLE device obtains the update data from the device, it initiates a broadcast. After establishing a communication connection with any of the peripheral BLE devices, the update data stored by the device is transmitted. Repeat the above steps until the surrounding BLE devices get updated data.
  • the broadcast carries version information of the updated data.
  • the surrounding BLE device listens to the broadcast. After listening to the broadcast, the version information of the update data carried in the broadcast is read. The read version information is compared with the updated data version information stored by the device. When the two are inconsistent, a communication request is initiated. After the communication connection is established, the update data is received.
  • step S91 the BLE device 1 that obtains the update data initiates a broadcast, wherein the broadcast carries the version information of the update data.
  • the broadcast information includes version information of one or more update data that has been stored by the device.
  • step S92 the BLE device 2 listens to the broadcast. After listening to the broadcast, the version information of the update data carried in the broadcast is read. The read version information is compared with the updated data version information stored by the device. If the two are inconsistent, step S93 is performed; otherwise, the monitoring continues.
  • step S93 the BLE device 2 initiates a communication request to the BLE device 1.
  • Step S94 after establishing the communication connection, the BLE device 1 and the BLE device 2 deliver the update data.
  • An eighth embodiment of the present invention relates to a data updating method.
  • the eighth embodiment is further improved on the basis of the sixth embodiment, and is improved in that, in the eighth embodiment, a method in which a BLE device is used as a master device to transmit update data to a peripheral BLE device is provided.
  • the BLE device queries the version information of the existing update data of the communication peer end; and sends the version information obtained by the query to the version information of the update data stored by the device. Update data stored by this device.
  • step S101 the BLE device 1 establishes a communication connection with the BLE device 2.
  • the process of establishing a communication connection mentioned here is similar to the process of establishing a communication connection between Bluetooth devices in the prior art, and details are not described herein again.
  • step S102 the BLE device 1 queries the version information of the existing update data of the BLE device 2.
  • Step S103 when the BLE device 1 determines that the version information obtained by the query is inconsistent with the version information of the update data stored by the device, step S104 is performed; otherwise, the connection is disconnected.
  • step S104 the BLE device 1 transmits the update data stored by the device to the BLE device 2.
  • a ninth embodiment of the present invention relates to a data updating method.
  • the ninth embodiment is further improved on the basis of the sixth embodiment, and the improvement is that, in the ninth embodiment, the data update method ensures the security of the device update process by performing specific security policy processing on the update data. .
  • the BLE device obtains update data as an update publishing device. After the update data is acquired, the acquired update data is subjected to security processing to form encrypted update data. The encrypted update data is passed to the surrounding BLE device when the update data is delivered to the surrounding BLE device.
  • the BLE device receives the update data from the sender as the update data receiver to obtain the update data. After receiving the update data, security verification is performed on the received update data. When the verification is successful, the BLE device is triggered to perform system update; when the verification fails, the received update data is delivered to the surrounding BLE device.
  • the BLE device can also transmit the received update data to the surrounding BLE device regardless of whether the verification is successful or not. That is to say, when the BLE device receives the update data, the update data can be directly transmitted without performing security verification on the update data.
  • the BLE device In the network, there are some BLE devices that exist only as relay devices that update data delivery.
  • the policy for performing security processing may be agreed according to specific conditions, for example, the feature information of the extracted update publishing device and/or the device to be updated is mixed with the updated data according to the negotiated security policy.
  • the specific process of updating the publishing device is shown in Figure 11, which includes:
  • step S111 the update data is acquired.
  • Step S112 extracting device features.
  • Step S113 mixing the extracted device features with the update data according to a preset rule, and using the mixed data as the encrypted update data.
  • Step S114 the encrypted update data is delivered to the peripheral BLE device.
  • FIG. 12 The specific process performed by the device other than the update publishing device is as shown in FIG. 12, which includes:
  • Step S121 receiving update data.
  • Step S122 parsing the device feature from the received update data.
  • step S123 it is determined whether the parsed device feature matches the feature of the BLE device.
  • step S124 it is determined that the verification is successful, and step S124 is performed; when the matching fails, the verification is failed, and step S126 is performed.
  • step S124 it is determined whether system update is required; if yes, step S125 is performed; if not, step S126 is performed.
  • Step S125 performing system update using the received update data.
  • Step S126 the encrypted update data is delivered to the peripheral BLE device.
  • a tenth embodiment of the present invention relates to a data updating method.
  • the tenth embodiment is substantially the same as the ninth embodiment, and the main difference is that, in the ninth embodiment, the manner in which the feature information of the update issuing device and/or the device to be updated is mixed with the updated data is performed for security processing; In the tenth embodiment, security processing is performed using a general encryption method.
  • the key is shared between the update publishing device and the device to be updated, for example, the key is shared between the update publishing device and the device to be updated in advance by other means.
  • Figure 13 The specific process of updating the publishing device is shown in Figure 13, which includes:
  • Step S131 obtaining update data.
  • Step S132 Encrypt the update data according to the key shared by the update publishing device and the device to be updated to form encrypted update data.
  • Step S133 the encrypted update data is delivered to the peripheral BLE device.
  • FIG. 14 The specific process performed by the device other than the update publishing device is as shown in FIG. 14, which includes:
  • Step S141 receiving update data.
  • Step S142 decrypting the received update data by using a key shared by the update publishing device and the device to be updated, to obtain decrypted data.
  • Step S143 verifying the correctness of the decrypted data, and when the verification is correct, determining that the verification is successful, Step 144; when the verification fails, it is determined that the verification has failed, and step S146 is performed.
  • step S144 it is determined whether system update is required; if yes, step S145 is performed; if not, step S146 is performed.
  • Step S145 performing system update using the received update data.
  • Step S146 the encrypted update data is delivered to the peripheral BLE device.
  • An eleventh embodiment of the present invention relates to a data updating method.
  • the eleventh embodiment is further improved on the basis of the sixth embodiment, and is improved in that, in the eleventh embodiment, information for counting the updated device can be collected.
  • the BLE device receives the update data from the sender as the update data receiver, and obtains the update data. After the BLE device receives the update data, the specific process is performed as shown in FIG. 15, which includes:
  • step S151 the source device address is recorded.
  • the source device address is an address of a BLE device that delivers update data to the BLE device.
  • Step S152 it is determined whether the BLE device completes the system update, and if yes, step S153 is performed; otherwise, step S154 is performed.
  • Step S153 transmitting the device information of the device to the source device.
  • Step S154 determining whether the BLE device receives the device information of the updated device, and if yes, executing step S155; otherwise, ending the process.
  • Step S155 the device information of the received updated device is delivered to the source device.
  • each module involved in the implementation of the present application may be a logic module.
  • a logical unit may be a physical unit, or may be part of a physical unit, and may also be more A combination of physical units.
  • the present embodiment does not introduce a unit that is not closely related to solving the technical problem proposed by the present invention, but this does not mean that there are no other units in the present embodiment.
  • a program instructing related hardware may be completed by a program instructing related hardware, and the program is stored in a storage medium, and includes a plurality of instructions for making a device (which may be a single chip microcomputer). , a chip, etc. or a processor performs all or part of the steps of the methods described in various embodiments of the present application.
  • the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Human Computer Interaction (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

本发明涉及无线通讯领域，公开了一种低功耗蓝牙BLE设备、数据更新系统及方法。低功耗蓝牙BLE设备包括处理器和BLE通讯模块，该处理器用于在BLE设备获取到更新数据时，触发BLE通讯模块将更新数据通过BLE链路传递给周边BLE设备，直到检测到周边BLE设备均获得更新数据为止；其中，周边BLE设备为能够与获取到更新数据的BLE设备进行端到端BLE通讯的设备。本发明还公开了一种数据更新系统和方法。本发明在获取到更新数据时，通过采用具有BLE无线传输能力的BLE设备向周边BLE设备传递更新数据，无需人工干预，无需特定后台服务器，自动在BLE网络中传递更新数据，使得BLE网络中设备的系统更新更简单。

Description

低功耗蓝牙BLE设备、数据更新系统及方法 技术领域
本发明涉及无线通讯领域，特别涉及低功耗蓝牙BLE设备、数据更新系统及方法。
背景技术
目前短距离无线通讯技术，例如低功耗蓝牙(BLE),紫峰(ZigBee)技术，经典蓝牙(class bluetooth)等，在众多电子设备，如智能手机、手环、可穿戴设备、传感器等中得到了广泛的应用。这些电子设备支持空中下载技术(Over－the－Air Technology，简称“OTA”)，利用无线传输空中通道，传输更新数据包，完成系统自动更新功能。当电子设备的系统出现故障，或者需要利用系统资源扩充应用，或版本更新时，使用OTA功能，为用户提供了便利。
发明人在实现本发明的过程中发现，现在具有无线传输能力的设备虽然有很多空中下载技术(OTA)方案，但都需要服务器，人工操作，且版本不可传播。在这些方案中电子设备的系统更新依赖于服务器，当服务器与电子设备无法建立连接时，电子设备就不能更新系统；当大批量设备需要更新系统时，会加重服务器的负载，影响系统更新。
发明内容
本发明实施方式的目的在于提供一种低功耗蓝牙BLE设备、数据更新系统及方法，无需人工干预，无需特定后台服务器，自动在BLE网络中传递更新数据，使得BLE网络中设备的系统更新更简单。
为解决上述技术问题，本发明的实施方式提供了一种低功耗蓝牙BLE设备，包括处理器和BLE通讯模块，所述处理器用于在BLE设备获取到更新数据时，触发所述BLE通讯模块将更新数据通过BLE链路传递给周边BLE 设备，直到检测到所述周边BLE设备均获得上述更新数据为止；其中，上述周边BLE设备为能够与所述获取到更新数据的BLE设备进行端到端BLE通讯的设备。
本发明的实施方式还提供了一种数据更新系统，包括若干个上述低功耗蓝牙BLE设备。
本发明的实施方式还提供了一种数据更新方法，包括：在BLE设备获取到更新数据之后，将所述更新数据通过BLE链路传递给周边BLE设备，直到检测到所述周边BLE设备均获得所述更新数据为止；其中，上述周边BLE设备为能够与上述获取到更新数据的BLE设备进行端到端BLE通讯的设备。
本发明实施方式相对于现有技术而言，在获取到更新数据时，通过采用具有BLE无线传输能力的BLE设备向周边BLE设备传递更新数据，无需人工干预，无需特定后台服务器，自动在BLE网络中传递更新数据，使得BLE网络中设备的系统更新更简单。
附图说明
图1是根据现有技术的固件版本更新示意图；
图2是根据本发明第一实施方式的低功耗蓝牙BLE设备的结构示意图；
图3是根据本发明第二实施方式的低功耗蓝牙BLE设备包含加密模块的结构示意图；
图4是根据本发明第二实施方式的低功耗蓝牙BLE设备包含解密模块的结构示意图；
图5是根据本发明第三实施方式的低功耗蓝牙BLE设备的结构示意图；
图6是根据本发明第四实施方式的数据更新系统的工作示意图；
图7是根据本发明第五实施方式的数据更新系统的工作示意图；
图8是根据本发明第六实施方式的数据更新方法的流程示意图；
图9是根据本发明第七实施方式的数据更新方法的流程示意图；
图10是根据本发明第八实施方式的数据更新方法的流程示意图；
图11是根据本发明第九实施方式的数据更新方法中更新发布设备执行的流程示意图；
图12是根据本发明第九实施方式的数据更新方法中除更新发布设备之外的设备执行的流程示意图；
图13是根据本发明第十实施方式的数据更新方法中更新发布设备执行的流程示意图；
图14是根据本发明第十实施方式的数据更新方法中除更新发布设备之外的设备执行的流程示意图；
图15是根据本发明第十一实施方式的数据更新方法的流程示意图。
具体实施方式
为使本发明的目的、技术方案和优点更加清楚，下面将结合附图对本发明的各实施方式进行详细的阐述。然而，本领域的普通技术人员可以理解，在本发明各实施方式中，为了使读者更好地理解本申请而提出了许多技术细节。但是，即使没有这些技术细节和基于以下各实施方式的种种变化和修改，也可以实现本申请所要求保护的技术方案。
本发明的第一实施方式涉及一种低功耗蓝牙BLE设备。本实施方式的低功耗蓝牙BLE(bluetooth low energy)设备100是一种具有蓝牙通讯能力的设备，具体如图2所示，其包括但不限于：处理器101、存储器102、BLE通讯模块103和天线104等。
处理器101用于运行存储器102中的系统软件，并触发BLE通讯模块103，完成与其它BLE设备的通讯。本发明中的处理器可以使用但不限于ARM、MIPS、或其它MCU处理器。此外，需要说明的是，本实施方式的处理器可以是单独设立的，也可以是在某一个模块中集成有具有处理器功能的部件单元。
存储器102主要是用来存放系统软件和更新数据，可以存放一份或多份不同版本的更新数据。在进行BLE设备间版本传递时，传递发起方，把更新数据从存储器102中取出，通过BLE链路传递给接收方。接收方则将更新数据存入本设备的存储器102中。存入策略包含但不限于：只有一份更新数据空间，直接覆盖旧版本；或着存有多份更新数据的空间，交替覆盖等。存储器102可以使用但不限于：sram,norflash，nandflash，eeprom等可擦除改写的存储器类型。另外，这里所说的更新数据包含但不限于：应用程序的更新数据，BLE通讯协议栈的更新数据，系统配置数据等。
处理器101在BLE设备获取到更新数据时，触发BLE通讯模块103将更新数据通过BLE链路传递给周边BLE设备，直到检测到周边BLE设备均获得更新数据为止。其中，周边BLE设备为能够与获取到更新数据的BLE设备进行端到端BLE通讯的设备。
具体的，低功耗蓝牙BLE设备可以为智能设备(如智能手机)，可穿戴设备(如手环)，以及各种类型的传感器等。BLE设备通过BLE通讯模块103实现BLE通讯协议栈功能，BLE通讯模块103和天线104一起为低功耗BLE设备建立BLE通讯通道，此时低功耗BLE设备间可以发起通讯连接。当BLE设备间处在连接状态时，可以将获取到的更新数据通过BLE链路传递给其它设备，完成低功耗设备自动更新系统。例如，现在有三台低功耗蓝牙BLE设备分别为设备A，设备B，设备C，三台低功耗蓝牙设备之间可通过BLE通讯模块建立通讯连接，也就是说，设备A与设备B，设备B与设备C，设备A与设备C之间可分别进行BLE通讯。当设备A获取到更新数据时，设备A可以向能够与自身进行BLE通讯的设备B和设备C传递更新数据，设备A检测到B和C都获得了更新数据时，不再传递更新数据。同理，当设备B获取到更新数据时，设备B可以向能够与自身进行BLE通讯的设备A和设备C传递更新数据，设备B检测到A和C都获得了更新数据时，不再传递更新数据。
此外，值得说明的是，BLE设备可以通过外界获取到更新数据，比如，用户将更新数据下发到更新发布设备。或者，BLE设备也可以通过接收其它设备传递的更新数据以获取到更新数据。无论BLE设备以何种方式获取到更新数据，均向其周边BLE设备传递更新数据，通过这种更新数据传递的方式，进行多层次的传递，可以将更新数据自动传递给网络内任何一台BLE设备，从而实现更新数据在BLE网络中的自动传递。
相对现有技术，本实施方式在获取到更新数据时，通过采用具有BLE无线传输能力的BLE设备向周边BLE设备传递更新数据，无需人工干预，无需特定后台服务器，自动在BLE网络中传递更新数据，使得BLE网络中设备的系统更新更简单。
本发明的第二实施方式涉及一种低功耗蓝牙BLE设备。第二实施方式在第一实施方式基础上作了进一步改进，主要改进之处在于：在第二实施方式中，BLE设备通过对更新数据进行特定的安全策略处理，保证设备更新过程的安全性。
具体地说，如图3所示，低功耗蓝牙BLE设备还可以包括加密模块105。该加密模块用于在BLE设备作为更新发布设备时，对更新数据进行安全性处理，以形成加密的更新数据。相应地，BLE通讯模块还用于将加密的更新数据传递给周边BLE设备。
请参见图4所示，低功耗蓝牙BLE设备还可以包括解密模块106。该解密模块106用于在BLE设备作为更新数据接收方时，对接收到的更新数据进行安全性验证，并在验证成功时，触发BLE设备进行系统更新；在验证失败时，将接收到的更新数据通过BLE通讯模块传递给周边BLE设备。
另外，需要说明的是，还可以设定无论解密模块是否验证成功，BLE设备均将接收到的更新数据通过BLE通讯模块传递给周边BLE设备。也就是说，当BLE设备接收到更新数据时，可以直接将更新数据传递出去，而不对更新数据进行安全性验证。在网络中，有一些BLE设备仅作为更新数据传递 的中转设备存在。
值得一提的是，加密模块105所采用的安全性处理和解密模块106所采用的安全性验证应当相对应。另外，加密模块105和解密模块106可以单独存在，对需要对更新数据进行安全性处理的BLE设备(比如，更新发布设备)配置加密模块，对接收更新数据的BLE设备(比如，待更新设备或者中转设备)配置解密模块。加密模块105和解密模块106也可以绑定在一起作为一个模块，在需要加密或解密时调用执行相关功能即可。现有的加密模块105和解密模块106的存在形式均可适用于本申请，在此不一一列举。
值得说明的是，安全策略可视具体实现而定，可以是只有更新发布设备和待更新设备两者协商好的策略。比如，提取更新发布设备和/或待更新设备的特征信息，按照已协商安全策略，与更新数据混合。
具体地说，加密模块105包括提取子模块和混合子模。其中，提取子模块用于提取设备特征。混合子模用于按照预设规则将提取的设备特征与更新数据混合，将混合后的数据作为加密的更新数据。
解密模块106包括解析子模块和匹配子模块。其中，解析子模块用于从接收到的更新数据中解析出设备特征。匹配子模块用于解析出的设备特征与本BLE设备的特征进行匹配，并在匹配成功时，判定验证成功；在匹配失败时，判定验证失败。
当BLE设备作为更新发布设备时，加密模块105中的提取子模块提取BLE设备的特征。其中，设备特征包括但不限于：更新发布设备地址、更新发布设备位置、待更新设备的类型、待更新设备的位置、更新发布设备编号、待更新设备的编号等。更新发布设备地址是更新发布设备的标识，具有全网络唯一性。更新发布设备位置是更新发布设备的位置信息。待更新设备的类型是一类产品的唯一标识。待更新设备的位置是某一地址区域的设备标识。更新发布设备编号，待更新设备的编号是对网络中设备的编号。
设备特征提取完毕后，混合子模块1052将提取子模块提取的特征和更 新数据按照预设的规则混合，形成加密的更新的数据。此时，BLE设备实现对更新数据的安全性处理。然后，BLE设备通过BLE通讯模块103将加密的更新数据传递给周围的BLE设备。周围的BLE设备接收到加密的更新数据时，解密模块106中的解析子模块解析接收到的更新数据中的设备特征；匹配子模块将解析出的设备特征与本设备的特征进行匹配，匹配成功，即判定验证成功；匹配失败，即判定验证失败，此时BLE设备完成更新数据的安全性验证。
另外，在更新发布前，也可对版本发布设备和待更新设备的特征提取，集成到系统更新数据中，再由BLE网络传递到待更新设备上。待更新设备提取系统更新数据中的特征值，对版本发布设备的权限检查和自身特征检查，符合条件，再进行系统更新，保证设备更新过程的安全性。
另外，还可以采用一些通用加密方式作为安全策略。具体地说，加密模块105在对更新数据进行安全性处理时，还可以依据更新发布设备和待更新设备共享的密钥对更新数据进行加密处理，以形成加密的更新数据。解密模块106在对解密模块在对接收到的更新数据进行安全性验证时，采用依据更新发布设备和待更新设备共享的密钥对接收到的更新数据进行解密，得到解密数据；并校验解密数据的正确性；在校验正确时，判定验证成功；在校验失败时，判定验证失败。其中，密钥在更新发布设备和待更新设备之间共享，比如，通过其它方式预先在更新发布设备和待更新设备之间共享密钥。
具体的说，BLE作为发布设备时，加密模块105将更新数据和密钥一同进行加密处理，形成加密的更新数据。BLE通讯模块103将加密的更新数据传递给周围的BLE设备。周围的BLE设备在接收到加密的更新数据时，解密模块106使用共享的密钥对加密数据进行解密，得到解密数据。解密模块106验证得到的解密数据的正确性，校验正确时，判定成功，设备进行系统更新在校验失败时，判定验证失败，设备不进行设备更新并将加密数据传递给周围的BLE设备。
通过本实施例提供的低功耗蓝牙BLE设备，可以禁止未授权的设备发布更新，对指定的设备进行更新，确保了BLE设备在传递更新数据时的安全性。
本发明的第三实施方式涉及一种低功耗蓝牙BLE设备。第三实施方式在第一或第二实施方式基础上作了进一步改进，主要改进之处在于：在第三实施方式中，BLE设备具备自动反馈已更新设备情况的能力，实现对已更新设备情况的收集统计。
具体地说，如图5所示，低功耗蓝牙BLE设备还包括源地址记录模块107。该源地址记录模块107用于BLE设备作为更新数据接收方时，在接收到更新数据时记录源设备地址；其中，源设备地址为向本BLE设备传递更新数据的BLE设备的地址。BLE通讯模块还用于在本BLE设备完成系统更新时，向源设备传递自身的设备信息；或者，BLE通讯模块还用于在本BLE设备接收到已更新设备的设备信息时，向源设备传递接收到的已更新设备的设备信息。
举例来说，BLE设备的设备地址是设备的标识，具有全网唯一性。当BLE设备作为接收方接收到更新数据时，源地址记录模块106记录向本设备发送更新数据的BLE设备的设备地址。例如，BLE设备A向周围传递更新数据，BLE设备B接收到设备A发送的更新数据，设备B通过源地址模块记录设备A的设备地址。当设备B完成系统更新时，将根据记录的设备地址向设备A传递设备B自身的设备信息。当设备B收到已更新设备发送的来的设备信息时，设备B根据记录的设备地址向设备A传递接收到的已更新设备的设备信息。
也就是说，接收到更新数据的BLE设备会将更新数据来源方的设备地址记录下来。若在本设备系统更新完成后，将本设备的设备信息发送给更新数据来源方，同时传递更新数据到下一个设备。若在本设备不需要更新，则继续传递更新数据到下一个设备。BLE设备都具有将其它设备传来的已更新设备的设备信息传递给更新数据来源方的能力。这里所说的设备信息包括但不 限于设备地址，设备位置，设备类型等。
BLE设备可以与多个其它BLE无线设备连接，从而构成一个网络。在网络中，若一台BLE设备需要发布更新数据，则该BLE设备可称为更新发布设备。任何一个设备都可以成为更新发布设备。更新发布设备可以通过上述更新数据传递的方式，进行多层次的传递，将更新数据自动传递给网络上任何一台BLE设备。同时每个设备根据已记录的上一级的更新数据来源方地址，将已更新设备的设备信息发送过去，直到所有设备信息都反馈到更新数据发布的更新发布设备上，再由更新发布设备统计已更新的设备情况，如数量，设备分布情况等。
本领域技术人员应当了解，源地址记录模块可以是一个单独的模块，也可以是存储器的一部分，只需要能都记录源设备的地址，后续能根据该记录的地址准确反馈设备信息即可，本申请不应以源地址的记录形式为限制，任何记录源地址的方式都应该在本申请的保护范围之内。
本实施例提供的低功耗蓝牙BLE设备，能快速的统计已更新的设备情况，如已更新设备的数量、分布等，根据统计的情况优化更新数据，向用户提供更加完美的系统更新数据。
本发明的第四实施方式涉及一种数据更新系统。该数据更新系统包括若干个上述第一至第三实施方式中任意一个提及的低功耗蓝牙BLE设备。
BLE网络中任何一个设备都可作为更新发布设备，更新数据包通过BLE网络传递到网络中任何一台设备中。以数据更新系统包括5台BLE设备为例进行说明。如图6所示，假设现选择BLE设备1作为更新发布设备，BLE设备5作为待更新设备，更新数据在网络中的传递过程为：
BLE设备1在从外界获取到更新数据时，向BLE设备2传递更新数据如图6中S61所示。
BLE设备2接收到更新数据时，向其周边BLE设备传递接收到的更新数据，BLE设备2的周边设备有BLE设备3和BLE设备4，因此，BLE设 备2向BLE设备3和BLE设备4分别传递更新数据，如图6中S62和S63所示。
BLE设备3接收到更新数据时，由于其周边只有BLE设备2，因此BLE设备3不再进一步传递更新数据。
BLE设备4接收到更新数据时，向其周边设备传递更新数据，BLE设备3的周边设备有BLE设备2和BLE设备5，BLE设备3向BLE设备5传递更新数据，如图6中S64所示。
BLE设备5接收到更新数据之后，进行系统数据更新。
值得说明的是，BLE通讯的链路是端到端的方式。链路的一端设备通过其它BLE链路接收到更新数据并存储在存储器后，会去查询另一端设备是否存在该更新数据，若不存在或更新输数据版本低，则传递更新数据；若对端更新数据版本高，则读取更新数据，再存放在存储器。设备查询另一端设备的更新数据信息的时机可以是接收到完整的更新数据后，也可以是对端设备接收到完整的更新数据后，再通知本设备来查询。
另外，设备间发送和读取更新数据的方式包含但不限于文件分包，断点续传等方式，以保证版本传递的质量，和尽可能的不影响正常用途的数据传输。
本实施例提供的数据更新系统，可以实现在该系统下的BLE设备在没有服务器，无人工干预的情况下自主的进行设备的系统更新，为用户提供了更加简单快捷的更新系统。
不难发现，本实施方式为与第一实施方式相对应的系统实施例，本实施方式可与第一实施方式互相配合实施。第一实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第一实施方式中。
本发明的第五实施方式涉及一种数据更新系统。第五实施方式在第四实施方式基础上作了进一步改进，具体改进之处在于：在第五实施方式中，数 据更新系统可以收集统计设备的更新情况。
具体地说，数据更新系统中任意一个BLE设备在本BLE设备完成系统更新时，向源设备传递自身的设备信息。或者，数据更新系统中的任意一个BLE设备在本BLE设备接收到已更新设备的设备信息时，向源设备传递接收到的已更新设备的设备信息，直到更新发布设备获取到所有已更新设备的设备信息为止。其中，源设备为向本BLE设备传递更新数据的BLE设备。
在数据更新系统中，任意一个BLE设备都具有将其它设备传来的已更新设备的设备信息传递给更新数据来源方的能力。以第四实施方式中所例举的5台BLE设备中的更新数据传递之后进行更新情况收集统计为例进行说明：
在BLE设备5完成数据更新之后，向BLE设备4反馈自身的设备信息，如图7中S71所示。
BLE设备4在接收到BLE设备5反馈的设备信息时，将BLE设备5的设备信息反馈到BLE设备2,如图7中S72所示。
BLE设备2在接收到BLE设备5反馈的设备信息时，将BLE设备5的设备信息反馈到BLE设备1,如图7中S73所示。
BLE设备1对接收到的设备信息进行收集统计。
通过本实施例提供的数据更新系统，能快速的统计在该系统下已更新的设备情况，如已更新设备的数量、分布等，根据统计的情况优化更新数据，向用户提供更加完美的系统更新数据。
不难发现，本实施方式为与第三实施方式相对应的系统实施例，本实施方式可与第三实施方式互相配合实施。第三实施方式中提到的相关技术细节在本实施方式中依然有效，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第三实施方式中。
本发明的第六实施方式涉及一种数据更新方法。该数据更新方法基于第一实施方式所描述的低功耗蓝牙BLE设备。该数据更新方法的具体流程如图8所示，其包括：
步骤S81，获取更新数据。
具体的说，BLE设备获取更新数据有两种方式，方式一，BLE设备作为更新发布设备，从外界获取更新数据；方式二，从其它BLE设备传递的更新数据。
步骤S82，向周围BLE设备中的一个传递获取到的更新数据。
步骤S83，判断是否所有周边BLE设备均已获取到更新数据，若否，则返回执行步骤S82；若是，则结束本流程。
也就是说，BLE设备在获取更新数据后，会自主向周围传递BLE设备更新数据，如果周围的BLE设备均已经获得了更新数据，则停止向周围BLE设备传递更新数据。
本实施方式的数据更新方法，低功耗蓝牙BLE设备实现了在没有服务器，无人工干预的情况下自主传递更新数据，直到周边BLE设备均获得更新数据为止。使低功耗蓝牙BLE设备系统更新不再依赖于服务器，能自主的更新系统，方便用户的使用。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
不难发现，本实施方式与第一实施方式相互对应，因此本实施方式可与第一实施方式互相配合实施。第一实施方式中提到的相关技术细节在本实施方式中依然有效，在第一实施方式中所能达到的技术效果在本实施方式中也同样可以实现，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第一实施方式中。
本发明的第七实施方式涉及一种数据更新方法。第七实施方式在第六实施方式基础上作了进一步改进，其改进之处在于：在第七实施方式中，提供 了一种BLE设备作为从设备向周围BLE设备传递更新数据的方法。
BLE设备作为从设备获取到更新数据之后，发起广播。在与周边BLE设备中任意一个建立通讯连接之后，发送本设备存储的更新数据。重复上述步骤，直到周边BLE设备均获得更新数据为止。其中，广播中携带有更新数据的版本信息。
而周边BLE设备监听广播。在监听到广播之后，读取广播中携带的更新数据的版本信息。并将读取到的版本信息与本设备存储的更新数据版本信息进行比较。在两者不一致时，发起通讯请求。在建立通讯连接之后，接收更新数据。
具体流程如图9所示，其包括：
步骤S91，获得更新数据的BLE设备1发起广播，其中，广播中携带有更新数据的版本信息。具体地说，广播信息中包含本设备已存放的一份或多份更新数据的版本信息。
步骤S92，BLE设备2监听广播。在监听到广播之后，读取广播中携带的更新数据的版本信息。将读取到的版本信息与本设备存储的更新数据版本信息进行比较。若两者不一致，则执行步骤S93；否则，继续监听。
步骤S93，BLE设备2向BLE设备1发起通讯请求。
步骤S94，在建立通讯连接之后，BLE设备1和BLE设备2传递更新数据。
这里所说的建立通讯连接的过程与现有技术中蓝牙设备之间建立通讯连接的过程类似，在此不再赘述。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本发明的第八实施方式涉及一种数据更新方法。第八实施方式在第六实施方式基础上作了进一步改进，其改进之处在于：在第八实施方式中，提供了一种BLE设备作为主设备向周边BLE设备传递更新数据的方法。
具体地说，BLE设备与周边BLE设备中任意一个建立通讯连接之后，查询通讯对端的已存在更新数据的版本信息；在查询得到的版本信息与本设备存储的更新数据的版本信息不一致时，发送本设备存储的更新数据。
具体流程如图10所示，其包括：
步骤S101，BLE设备1与BLE设备2建立通讯连接。这里所说的建立通讯连接的过程与现有技术中蓝牙设备之间建立通讯连接的过程类似，在此不再赘述。
步骤S102，BLE设备1查询BLE设备2的已存在更新数据的版本信息。
步骤S103，BLE设备1判断查询得到的版本信息与本设备存储的更新数据的版本信息不一致时，执行步骤S104；否则，断开连接。
步骤S104，BLE设备1向BLE设备2发送本设备存储的更新数据。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
本发明的第九实施方式涉及一种数据更新方法。第九实施方式在第六实施方式基础上作了进一步改进，其改进之处在于：在第九实施方式中，数据更新方法通过对更新数据进行特定的安全策略处理，保证设备更新过程的安全性。
BLE设备作为更新发布设备获取到更新数据。在获取到更新数据之后，对获取到的更新数据进行安全性处理，以形成加密的更新数据。在向周边BLE设备传递更新数据时，将加密的更新数据传递给周边BLE设备。
BLE设备作为更新数据接收方，从发送方接收更新数据从而获取到更新数据。在接收到更新数据之后，对接收到的更新数据进行安全性验证。在验证成功时，触发BLE设备进行系统更新；在验证失败时，将接收到的更新数据传递给周边BLE设备。
另外，需要说明的是，还可以设定无论是否验证成功，BLE设备均将接收到的更新数据传递给周边BLE设备。也就是说，当BLE设备接收到更新数据时，可以直接将更新数据传递出去，而不对更新数据进行安全性验证。在网络中，有一些BLE设备仅作为更新数据传递的中转设备存在。
进行安全性处理的策略可根据具体情况商定，比如，按照已协商安全策略，将提取的更新发布设备和/或待更新设备的特征信息，与更新数据混合。更新发布设备执行的具体流程如图11所示，其包括：
步骤S111，获取更新数据。
步骤S112，提取设备特征。
步骤S113，按照预设规则将提取的设备特征与更新数据混合，将混合后的数据作为加密的更新数据。
步骤S114，向周边BLE设备传递加密的更新数据。
除更新发布设备之外的设备执行的具体流程如图12所示，其包括：
步骤S121，接收更新数据。
步骤S122，从接收到的更新数据中解析出设备特征。
步骤S123，判断解析出的设备特征与本BLE设备的特征是否匹配，在匹配成功时，判定验证成功，执行步骤S124；在匹配失败时，判定验证失败，执行步骤S126。
步骤S124，判断是否需要进行系统更新；若是，则执行步骤S125；若否，则执行步骤S126。
步骤S125，使用接收到的更新数据进行系统更新。
步骤S126，向周边BLE设备传递加密的更新数据。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系，都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
不难发现，本实施方式与第二实施方式相互对应，因此本实施方式可与第二实施方式互相配合实施。第二实施方式中提到的相关技术细节在本实施方式中依然有效，在第二实施方式中所能达到的技术效果在本实施方式中也同样可以实现，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第二实施方式中。
本发明的第十实施方式涉及一种数据更新方法。第十实施方式与第九实施方式大致相同，主要区别之处在于，在第九实施方式中，提取更新发布设备和/或待更新设备的特征信息与更新数据混合的方式进行安全性处理；在第十实施方式中，采用通用加密方式进行安全性处理。密钥在更新发布设备和待更新设备之间共享，比如，通过其它方式预先在更新发布设备和待更新设备之间共享密钥。
更新发布设备执行的具体流程如图13所示，其包括：
步骤S131，获取更新数据。
步骤S132，依据更新发布设备和待更新设备共享的密钥对更新数据进行加密处理，以形成加密的更新数据。
步骤S133，向周边BLE设备传递加密的更新数据。
除更新发布设备之外的设备执行的具体流程如图14所示，其包括：
步骤S141，接收更新数据。
步骤S142，采用更新发布设备和待更新设备共享的密钥对接收到的更新数据进行解密，得到解密数据。
步骤S143，校验解密数据的正确性，在校验正确时，判定验证成功，执 行步骤144；在校验失败时，判定验证失败，执行步骤S146。
步骤S144，判断是否需要进行系统更新；若是，则执行步骤S145；若否，则执行步骤S146。
步骤S145，使用接收到的更新数据进行系统更新。
步骤S146，向周边BLE设备传递加密的更新数据。
不难发现，本实施方式与第二实施方式相互对应，因此本实施方式可与第二实施方式互相配合实施。第二实施方式中提到的相关技术细节在本实施方式中依然有效，在第二实施方式中所能达到的技术效果在本实施方式中也同样可以实现，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第二实施方式中。
本发明的第十一实施方式涉及一种数据更新方法。第十一实施方式在第六实施方式基础上作了进一步改进，其改进之处在于：在第十一实施方式中，可以收集统计已更新设备的信息。
BLE设备作为更新数据接收方，从发送方接收更新数据从而获取到更新数据，在BLE设备接收到更新数据之后，执行的具体流程如图15所示，其包括：
步骤S151，记录源设备地址。其中，源设备地址为向本BLE设备传递更新数据的BLE设备的地址。
步骤S152，判断本BLE设备是否完成系统更新，若是，则执行步骤S153；否则，执行步骤S154。
步骤S153，向源设备传递自身的设备信息。
步骤S154，判断本BLE设备是否接收到已更新设备的设备信息，若是，则执行步骤S155，否则，结束本流程。
步骤S155，向源设备传递接收到的已更新设备的设备信息。
上面各种方法的步骤划分，只是为了描述清楚，实现时可以合并为一个步骤或者对某些步骤进行拆分，分解为多个步骤，只要包括相同的逻辑关系， 都在本专利的保护范围内；对算法中或者流程中添加无关紧要的修改或者引入无关紧要的设计，但不改变其算法和流程的核心设计都在该专利的保护范围内。
不难发现，本实施方式与第三实施方式相互对应，因此本实施方式可与第三实施方式互相配合实施。第三实施方式中提到的相关技术细节在本实施方式中依然有效，在第三实施方式中所能达到的技术效果在本实施方式中也同样可以实现，为了减少重复，这里不再赘述。相应地，本实施方式中提到的相关技术细节也可应用在第三实施方式中。
值得一提的是，本申请的实施方式中所涉及到的各模块可以为逻辑模块，在实际应用中，一个逻辑单元可以是一个物理单元，也可以是一个物理单元的一部分，还可以以多个物理单元的组合实现。此外，为了突出本发明的创新部分，本实施方式中并没有将与解决本发明所提出的技术问题关系不太密切的单元引入，但这并不表明本实施方式中不存在其它的单元。
本领域技术人员可以理解实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序存储在一个存储介质中，包括若干指令用以使得一个设备(可以是单片机，芯片等)或处理器(processor)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。
本领域的普通技术人员可以理解，上述各实施方式是实现本发明的具体实施例，而在实际应用中，可以在形式上和细节上对其作各种改变，而不偏离本发明的精神和范围。

Claims (20)

  1. 一种低功耗蓝牙BLE设备，其特征在于，包括处理器和BLE通讯模块；
    所述处理器用于在BLE设备获取到更新数据时，触发所述BLE通讯模块将所述更新数据通过BLE链路传递给周边BLE设备，直到检测到所述周边BLE设备均获得所述更新数据为止；
    其中，所述周边BLE设备为能够与所述获取到更新数据的BLE设备进行端到端BLE通讯的设备。
  2. 根据权利要求1所述的BLE设备，其特征在于，所述BLE设备还包括加密模块；
    所述加密模块用于在BLE设备作为更新发布设备时，对更新数据进行安全性处理，以形成加密的更新数据；
    所述BLE通讯模块还用于将所述加密的更新数据传递给周边BLE设备。
  3. 根据权利要求2所述的BLE设备，其特征在于，所述加密模块包括提取子模块和混合子模块；
    所述提取子模块，用于提取设备特征；
    所述混合子模块，用于按照预设规则将提取的所述设备特征与所述更新数据混合，将混合后的数据作为所述加密的更新数据；
    其中，所述设备特征包括：更新发布设备和/或待更新设备的特征。
  4. 根据权利要求2所述的BLE设备，其特征在于，所述加密模块在对更新数据进行安全性处理时，依据更新发布设备和待更新设备共享的密钥对更新数据进行加密处理，以形成加密的更新数据。
  5. 根据权利要求1至4任意一项所述的BLE设备，其特征在于，所述BLE设备还包括解密模块；
    所述解密模块用于在BLE设备作为更新数据接收方时，对接收到的更 新数据进行安全性验证，并在验证成功时，触发所述BLE设备进行系统更新；在验证失败时，将所述接收到的更新数据通过BLE通讯模块传递给所述周边BLE设备。
  6. 根据权利要求5所述的BLE设备，其特征在于，所述解密模块包括解析子模块和匹配子模块；
    所述解析子模块用于从接收到的更新数据中解析出设备特征；
    所述匹配子模块用于将解析出的设备特征与本BLE设备的特征进行匹配，并在匹配成功时，判定验证成功；在匹配失败时，判定验证失败；
    其中，所述设备特征包括：更新发布设备和/或待更新设备的特征。
  7. 根据权利要求5所述的BLE设备，其特征在于，所述解密模块在对接收到的更新数据进行安全性验证时，采用更新发布设备和待更新设备共享的密钥对接收到的更新数据进行解密，得到解密数据；并校验所述解密数据的正确性；在校验正确时，判定验证成功；在校验失败时，判定验证失败。
  8. 根据权利要求1所述的BLE设备，其特征在于，所述BLE设备还包括源地址记录模块；
    所述源地址记录模块用于BLE设备作为更新数据接收方时，在接收到更新数据时记录源设备地址；其中，所述源设备地址为向本BLE设备传递所述更新数据的BLE设备的地址；
    所述BLE通讯模块还用于在本BLE设备完成系统更新时，向源设备传递自身的设备信息；
    所述BLE通讯模块还用于在本BLE设备接收到已更新设备的设备信息时，向源设备传递接收到的已更新设备的设备信息。
  9. 一种数据更新系统，其特征在于，所述数据更新系统包括若干个权利要求1至8中任一项所述的低功耗蓝牙BLE设备。
  10. 一种数据更新方法，其特征在于，包括：
    在BLE设备获取到更新数据时，将所述更新数据通过BLE链路传递给 周边BLE设备，直到检测到所述周边BLE设备均获得所述更新数据为止；
    其中，所述周边BLE设备为能够与所述获取到更新数据的BLE设备进行端到端BLE通讯的设备。
  11. 根据权利要求10所述的数据更新方法，其特征在于，所述向周边BLE设备传递所述更新数据，具体包括：
    发起广播，其中，所述广播中携带有更新数据的版本信息；
    在与所述周边BLE设备中任意一个建立通讯连接之后，发送本设备存储的更新数据；
    重复上述步骤，直到所述周边BLE设备均获得所述更新数据为止。
  12. 根据权利要求11所述的数据更新方法，其特征在于，所述向周边BLE设备传递所述更新数据，具体还包括：
    监听到广播之后，读取广播中携带有更新数据的版本信息，与本设备存储的更新数据的版本信息进行比较；
    在读取到的版本信息与本设备存储的更新数据的版本信息不一致时，发起通讯连接请求；
    在建立通讯连接之后，接收更新数据。
  13. 根据权利要求10所述的数据更新方法，其特征在于，所述向周边BLE设备传递所述更新数据，具体包括：
    在与所述周边BLE设备中任意一个建立通讯连接之后，查询通讯对端的已存在更新数据的版本信息；
    在查询得到的版本信息与本设备存储的更新数据的版本信息不一致时，发送本设备存储的更新数据。
  14. 根据权利要求10所述的数据更新方法，其特征在于，BLE设备作为更新发布设备获取到更新数据；
    在获取到更新数据之后，在向周边BLE设备传递所述更新数据之前，所述数据更新方法还包括：
    对获取到的更新数据进行安全性处理，以形成加密的更新数据；
    在向周边BLE设备传递所述更新数据时，将所述加密的更新数据传递给周边BLE设备。
  15. 根据权利要求14所述的数据更新方法，其特征在于，对获取到的更新数据进行安全性处理，形成加密的更新数据，具体包括：
    提取设备特征；
    按照预设规则将提取的所述设备特征与所述更新数据混合，将混合后的数据作为所述加密的更新数据。
  16. 根据权利要求14所述的数据更新方法，其特征在于，对获取到的更新数据进行安全性处理时，依据更新发布设备和待更新设备共享的密钥对更新数据进行加密处理。
  17. 根据权利要求10至16任意一项所述的数据更新方法，其特征在于，BLE设备作为更新数据接收方，从发送方接收更新数据从而获取到更新数据；
    在接收到更新数据之后，所述数据更新方法还包括：
    对接收到的更新数据进行安全性验证；
    在验证成功时，触发所述BLE设备进行系统更新；
    在验证失败时，将所述接收到的更新数据传递给所述周边BLE设备。
  18. 根据权利要求17所述的数据更新方法，其特征在于，对接收到的更新数据进行安全性验证，具体包括：
    从接收到的更新数据中解析出设备特征；
    将解析出的设备特征与本BLE设备的特征进行匹配；
    在匹配成功时，判定验证成功；
    在匹配失败时，判定验证失败；
    其中，所述设备特征包括：更新发布设备和/或待更新设备的特征。
  19. 根据权利要求17所述的数据更新方法，其特征在于，对接收到的 更新数据进行安全性验证，具体包括：
    采用更新发布设备和待更新设备共享的密钥对接收到的更新数据进行解密，得到解密数据；
    校验所述解密数据的正确性；
    在校验正确时，判定验证成功；
    在校验失败时，判定验证失败。
  20. 根据权利要求10所述的数据更新方法，其特征在于，BLE设备作为更新数据接收方，从发送方接收更新数据从而获取到更新数据；
    在接收到更新数据之后，所述数据更新方法还包括：
    记录源设备地址；其中，所述源设备地址为向本BLE设备传递所述更新数据的BLE设备的地址；
    在本BLE设备完成系统更新时，向源设备传递自身的设备信息；
    在接收到已更新设备的设备信息时，向源设备传递接收到的已更新设备的设备信息。
PCT/CN2016/107201 2016-11-25 2016-11-25 低功耗蓝牙ble设备、数据更新系统及方法 WO2018094677A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
EP16909741.7A EP3352525B1 (en) 2016-11-25 2016-11-25 Bluetooth low energy (ble) device, and data update system and method
PCT/CN2016/107201 WO2018094677A1 (zh) 2016-11-25 2016-11-25 低功耗蓝牙ble设备、数据更新系统及方法
KR1020187003485A KR102001792B1 (ko) 2016-11-25 2016-11-25 저전력 블루투스 ble 기기, 데이터 업데이트 시스템 및 방법
CN201680001565.9A CN107041171B (zh) 2016-11-25 2016-11-25 低功耗蓝牙ble设备、数据更新系统及方法
US15/879,769 US20180150291A1 (en) 2016-11-25 2018-01-25 Bluetooth low energy device, and data update system and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2016/107201 WO2018094677A1 (zh) 2016-11-25 2016-11-25 低功耗蓝牙ble设备、数据更新系统及方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/879,769 Continuation US20180150291A1 (en) 2016-11-25 2018-01-25 Bluetooth low energy device, and data update system and method

Publications (1)

Publication Number Publication Date
WO2018094677A1 true WO2018094677A1 (zh) 2018-05-31

Family

ID=59530814

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/107201 WO2018094677A1 (zh) 2016-11-25 2016-11-25 低功耗蓝牙ble设备、数据更新系统及方法

Country Status (5)

Country Link
US (1) US20180150291A1 (zh)
EP (1) EP3352525B1 (zh)
KR (1) KR102001792B1 (zh)
CN (1) CN107041171B (zh)
WO (1) WO2018094677A1 (zh)

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108600892B (zh) * 2018-06-15 2020-05-22 歌尔科技有限公司 一种升级方法、装置、无线耳机、tws耳机及充电盒
CN109150969B (zh) * 2018-07-13 2022-04-19 北京旷视科技有限公司 数据传输方法、分发机、终端机和数据传输系统
CN108650676A (zh) * 2018-08-13 2018-10-12 青岛海信电器股份有限公司 一种蓝牙自组网中的密钥更新方法及装置
WO2020056558A1 (zh) 2018-09-17 2020-03-26 深圳市汇顶科技股份有限公司 一种蓝牙集群在线升级方法及装置
CN109445806B (zh) * 2018-12-20 2022-05-06 歌尔科技有限公司 基于Ble的多设备升级方法、装置、系统及终端
CN110166922A (zh) * 2019-05-30 2019-08-23 深圳市安特信技术有限公司 基于蓝牙耳机的测试通信系统及方法
CN110958162A (zh) * 2019-12-06 2020-04-03 广东博智林机器人有限公司 一种ble级联网络及其链路检测方法、设备和终端
WO2021155482A1 (zh) * 2020-02-03 2021-08-12 深圳市汇顶科技股份有限公司 数据传输的方法和ble设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103957607A (zh) * 2014-03-18 2014-07-30 南京志纯信息科技有限公司 一种基于蓝牙技术的单芯片多通道并行推送方法
CN104820611A (zh) * 2015-05-22 2015-08-05 中国科学院上海高等研究院 一种基于蓝牙的设备软件升级方法及升级装置
WO2015154636A1 (zh) * 2014-04-11 2015-10-15 比亚迪股份有限公司 对车辆的车身控制模块进行更新的方法、装置、系统及计算机可读存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101621737A (zh) * 2008-06-30 2010-01-06 北京腾瑞万里科技有限公司 数据更新方法及系统
US20110191764A1 (en) * 2010-02-04 2011-08-04 Nokia Corporation Systems, methods, and apparatuses for facilitating distribution of firmware updates
US20120054734A1 (en) * 2010-08-31 2012-03-01 Apple Inc. Device software upgrade using a dynamically sized partition
US9307347B2 (en) * 2012-06-01 2016-04-05 Nokia Technologies Oy Wireless programming
EP2704053B1 (en) * 2012-08-27 2016-09-21 Giesecke & Devrient GmbH Method and system for updating a firmware of a security module
WO2014070188A2 (en) * 2012-11-01 2014-05-08 Cooper Technologies Company Distribution of software updates in wireless multihop networks
US9722781B2 (en) * 2014-07-09 2017-08-01 Livio, Inc. Vehicle software update verification
US20160085538A1 (en) * 2014-09-22 2016-03-24 Qualcomm Technologies International, Ltd. Over-the-air updates for ble devices

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103957607A (zh) * 2014-03-18 2014-07-30 南京志纯信息科技有限公司 一种基于蓝牙技术的单芯片多通道并行推送方法
WO2015154636A1 (zh) * 2014-04-11 2015-10-15 比亚迪股份有限公司 对车辆的车身控制模块进行更新的方法、装置、系统及计算机可读存储介质
CN104820611A (zh) * 2015-05-22 2015-08-05 中国科学院上海高等研究院 一种基于蓝牙的设备软件升级方法及升级装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3352525A4 *

Also Published As

Publication number Publication date
EP3352525A1 (en) 2018-07-25
KR20180079285A (ko) 2018-07-10
KR102001792B1 (ko) 2019-07-18
US20180150291A1 (en) 2018-05-31
EP3352525B1 (en) 2021-03-24
EP3352525A4 (en) 2018-09-26
CN107041171A (zh) 2017-08-11
CN107041171B (zh) 2021-01-29

Similar Documents

Publication Publication Date Title
WO2018094677A1 (zh) 低功耗蓝牙ble设备、数据更新系统及方法
KR102275802B1 (ko) 단거리 무선 데이터 전송을 위한 시스템 및 방법
CN107231627B (zh) 一种蓝牙网络及配网方法
CN108632056B (zh) 一种智能设备网络配置方法与系统
CN113271579B (zh) 蓝牙设备控制方法、客户端、计算机设备和可读存储介质
KR101038153B1 (ko) 레거시 디바이스 등록 방법, 데이터 전송 방법 및 레거시디바이스 인증 방법
US20140028438A1 (en) Systems and methods for locking device management
US20220276855A1 (en) Method and apparatus for processing upgrade package of vehicle
CN108738017A (zh) 网络接入点中的安全通信
EP2986045B1 (en) Method, device and system for configuring wireless terminal
EP3940989A1 (en) Communication method and communication device
CN110708164B (zh) 一种物联网设备的控制方法、装置、存储介质及电子装置
CN110249585B (zh) 用于信息请求和/或信息供应的装置和方法
CN109996229B (zh) 基于dht网络的数据传输方法、装置、电子设备和存储介质
WO2019019853A1 (zh) 处理数据的方法、终端设备和网络设备
CN112737902A (zh) 网络配置方法和装置、存储介质及电子设备
CN105119900A (zh) 信息安全传输方法、联网接入方法及相应的终端
WO2021155482A1 (zh) 数据传输的方法和ble设备
EP2930962B1 (en) Encryption/decryption method, system and device
JP6804026B2 (ja) 暗号化通信システム
Ortiz-Yepes Balsa: Bluetooth low energy application layer security add-on
CN112559251B (zh) 一种电力物联网的配置数据管理方法及装置
WO2018076242A1 (zh) 一种信息传输方法及设备
CN111490880B (zh) 文件的接收方法及装置
CN115967511A (zh) 加解密方法、装置及计算机可读存储介质

Legal Events

Date Code Title Description
ENP Entry into the national phase

Ref document number: 20187003485

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE