WO2019100704A1 - 用于多模IoT设备的启动方法、多模IoT设备及存储介质 - Google Patents

用于多模IoT设备的启动方法、多模IoT设备及存储介质 Download PDF

Info

Publication number
WO2019100704A1
WO2019100704A1 PCT/CN2018/091935 CN2018091935W WO2019100704A1 WO 2019100704 A1 WO2019100704 A1 WO 2019100704A1 CN 2018091935 W CN2018091935 W CN 2018091935W WO 2019100704 A1 WO2019100704 A1 WO 2019100704A1
Authority
WO
WIPO (PCT)
Prior art keywords
partition
communication mode
iot device
flag
code
Prior art date
Application number
PCT/CN2018/091935
Other languages
English (en)
French (fr)
Inventor
金海鹏
Original Assignee
泰凌微电子（上海）有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 泰凌微电子（上海）有限公司 filed Critical 泰凌微电子（上海）有限公司
Priority to US16/763,980 priority Critical patent/US11422823B2/en
Priority to EP18880374.6A priority patent/EP3719634A4/en
Publication of WO2019100704A1 publication Critical patent/WO2019100704A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • 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
    • 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
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/4401—Bootstrapping
    • G06F9/4406—Loading of operating system
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44—Arrangements for executing specific programs
    • G06F9/445—Program loading or initiating
    • G06F9/44568—Immediately runnable code
    • G06F9/44578—Preparing or optimising for loading
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • 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
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/06—Terminal devices adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
    • G—PHYSICS
    • G16—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR SPECIFIC APPLICATION FIELDS
    • G16Y—INFORMATION AND COMMUNICATION TECHNOLOGY SPECIALLY ADAPTED FOR THE INTERNET OF THINGS [IoT]
    • G16Y10/00—Economic sectors
    • G16Y10/75—Information technology; Communication
    • 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

Definitions

  • the present invention relates to multimode Internet of Things (IoT) technology, and more particularly to a booting method for a multimode IoT device, a multimode IoT device, and a computer storage medium.
  • IoT Internet of Things
  • Bluetooth Low Energy BLE
  • Bluetooth low energy Mesh self-organizing network Bluetooth
  • Zigbee Zigbee Protocol
  • Thread 6LoWPAN
  • 6LoWPAN 6LoWPAN
  • the current multi-mode IoT device supports multiple different IoT communication modes. Many different IoT communication modes run on the same firmware and share software/hardware resources on the same firmware. Therefore, each IoT communication mode cannot fully occupy the same firmware. Problems with software/hardware resources.
  • the present disclosure can effectively implement the startup of a multi-mode IoT device based on a specific storage area division, and enables the multi-mode IoT device to support multiple IoT communication modes while enabling the currently running IoT communication mode to use all software/hardware of the firmware alone. Resources, improve the communication response time of IoT devices, and reduce communication delays.
  • a method for booting a multimode IoT device comprising: receiving a boot operation for a multimode IoT device; in response to the booting operation, initiating a flag bit for a partition in a memory Performing detection, wherein the memory includes a plurality of first partitions respectively storing a communication mode startup code and including a partition start flag bit, and the partition start flag bit is set to be effective to indicate a corresponding
  • the partition is a bootable partition, and when the partition boot flag is set to be invalid, it is used to indicate that the corresponding partition is an unbootable partition; when a valid partition boot flag is detected, the valid partition start flag is executed.
  • a communication mode startup code in the corresponding first partition to enable the multi-mode IoT device to operate in a communication mode corresponding to the corresponding first partition.
  • the memory further includes a second partition, the second partition is used for updating of a communication mode startup code and includes a partition startup flag, the method further comprising: detecting the second partition a partition boot flag; if it is detected that the partition boot flag of the second partition is valid, running a communication mode boot code in the second partition to cause the multimode IoT device to operate with the The communication mode corresponding to the second partition.
  • the method further includes: downloading, in the second partition, an update code corresponding to a current communication mode of the multi-mode IoT device; and starting a partition start flag of the second partition The bit is set to valid, and the partition start flag of the first partition corresponding to the current communication mode is set to be invalid.
  • the method further includes: a communication mode startup code in the second partition Copying to a first partition corresponding to a communication mode corresponding to the second partition, and setting a partition start flag of the second partition to be invalid, corresponding to a communication mode corresponding to the second partition
  • the partition boot flag in the first partition is set to be valid.
  • the communication mode includes at least two of: BLE or BLE Mesh, Zigbee, Thread, HomeKit, ANT, and a private communication protocol.
  • a multimode IoT device comprising: a control unit; a memory, the memory including a plurality of first partitions, each of the plurality of first partitions storing a communication mode startup code And including a partition startup flag, the partition startup flag is set to be effective to indicate that the corresponding partition is a bootable partition, and the partition boot flag is set to be invalid to indicate that the corresponding partition is an unbootable partition; a radio frequency transceiver unit supporting a plurality of communication modes; wherein the control unit detects a partition start flag bit in the memory in response to a boot operation of the multi-mode IoT device, when a valid partition start flag is detected And running a communication mode startup code in the first partition corresponding to the valid partition start flag bit, so that the radio frequency transceiver unit operates in a communication mode corresponding to the corresponding first partition.
  • the memory further includes a second partition, the second partition is used for updating of a communication mode startup code and includes a partition start flag bit;
  • the control unit is further configured to: detect the a partition start flag of the second partition; if it is detected that the partition start flag of the second partition is valid, running a communication mode startup code in the second partition, so that the radio transceiver unit operates The communication mode corresponding to the second partition is described.
  • control unit is further configured to: download an update code corresponding to a current communication mode of the radio frequency transceiver unit in the second partition; start a partition of the second partition The flag bit is set to be valid, and the partition start flag bit of the first partition corresponding to the current communication mode is set to be invalid.
  • the control unit is further configured to: initiate a communication mode in the second partition Copying the code into the first partition corresponding to the communication mode corresponding to the second partition, and setting the partition start flag of the second partition to be invalid, corresponding to the communication mode corresponding to the second partition
  • the partition start flag in the first partition is set to be valid.
  • a multimode IoT device comprising: one or more processors; a memory; a computer program stored in the memory, the computer program being processed by the one or more The processor, when executed, causes the processor to perform the method of any of the above first aspects.
  • a computer readable storage medium storing a computer program, when executed by a processor, causing a processor to perform any of the above first aspects The method described in the item.
  • the present disclosure achieves software/hardware resources for the firmware to use firmware alone by selectively selecting an active communication mode during the IoT device startup phase.
  • FIG. 1 is a schematic flowchart showing an implementation process of a method for starting a multi-mode IoT device according to an embodiment of the present invention
  • FIG. 2 is a system architecture diagram of a multimode IoT radio system level chip according to an embodiment of the present invention
  • FIG. 3 is a diagram showing a storage space layout of a multimode IoT device according to an embodiment of the present invention.
  • FIG. 4 is a diagram showing a storage space layout of a multimode IoT device according to an embodiment of the present invention.
  • FIG. 5 is a diagram showing a storage space layout change diagram of a multi-mode IoT device according to an embodiment of the present invention
  • FIG. 6 is a diagram showing a storage space layout change diagram of a multi-mode IoT device according to an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a multimode IoT device according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram showing the implementation of a multi-mode IoT device according to an embodiment of the present invention.
  • FIG. 9 shows a schematic diagram of a computer readable storage medium storing a computer program implementing a boot method for a multimode IoT device in accordance with an embodiment of the present invention.
  • Fig. 1 is a flowchart showing an implementation flow of a method for starting a multimode IoT device according to an embodiment of the present invention.
  • an embodiment of the present invention provides a method for starting a multi-mode IoT device, the method comprising the following operations: operation 101, receiving a startup operation for a multi-mode IoT device, and operation 102, in response to the starting An operation of detecting a partition boot flag bit in the memory, wherein the memory includes a plurality of first partitions respectively storing a communication mode boot code and including a partition boot flag bit, the partition booting When the flag bit is set to be valid, it is used to indicate that the corresponding partition is a bootable partition, and when the partition start flag is set to be invalid, it is used to indicate that the corresponding partition is an unbootable partition; operation 103, when a valid partition start flag is detected And a communication mode startup code in the first partition corresponding to the valid partition initiation flag bit to operate the multimode IoT device in a communication mode corresponding to the corresponding first partition.
  • the communication mode includes at least two of BLE or BLE Mesh, Zigbee, Thread, HomeKit, ANT, and a private communication protocol.
  • a boot operation for a multimode IoT device may include a power up operation for a multimode IoT device; a boot operation for a multimode IoT device may also include a restart operation for a multimode IoT device.
  • a valid partition start flag when a valid partition start flag is detected, it indicates that the first partition corresponding to the valid partition start flag is detected as a bootable partition, and the valid partition can be directly operated. And a communication mode startup code in the first partition corresponding to the startup flag bit, so that the multi-mode IoT device operates in a communication mode corresponding to the corresponding first partition.
  • Step 1 divide the storage space to obtain N partitions.
  • the value of N is greater than or equal to 3; in step 2, the N partitions are functionally partitioned to obtain M partitions including partition start flag bits and NM user data partitions, and the value of M is greater than or equal to 2 and less than N.
  • the partition startup flag is set to be valid, it is used to indicate that the corresponding partition is a bootable partition, and when the partition startup flag is set to be invalid, it is used to indicate that the corresponding partition is an unbootable partition.
  • the manner of dividing the storage space mainly includes a static division manner and a dynamic division manner.
  • the static division mode may divide the storage area by a fixed byte interval to obtain a plurality of partitions; the dynamic division manner may be real-time dynamic storage area division on demand.
  • the manner of dividing the storage space is also related to the storage format of the memory itself.
  • the M partitions including the partition start flag may be refined into a plurality of first partitions respectively storing a communication mode startup code and an updated second partition for the communication mode startup code, such as over the air download.
  • OTA partition may be refined into a plurality of first partitions respectively storing a communication mode startup code and an updated second partition for the communication mode startup code, such as over the air download.
  • FIG. 2 is a system architecture diagram of a multimode IoT radio system level chip according to an embodiment of the present invention
  • FIG. 3 is a diagram showing a storage space layout of a multimode IoT device according to an embodiment of the present invention.
  • the multimode IoT radio system level chip includes a radio frequency transceiver (RF Transceiver) capable of supporting different IoT communication standards, a 32-bit or higher performance microcontroller (MCU) ), as well as different formats of storage space such as flash (Flash) and boot chip (BROM).
  • RF Transceiver radio frequency transceiver
  • MCU microcontroller
  • flash flash
  • BROM boot chip
  • FIG. 3 a memory space such as a flash memory or other format as shown in FIG. 2 may be divided into four partitions separated by, for example, 64K, 128K and 256K bytes thereof; further, the four partitions are functionalized.
  • the partition obtains a partition reserved for user data, that is, a User Data Area and three partitions including partition start flag bits F0, F1, and F2, respectively.
  • the #0 partition storing the binary code shown in FIG. 3 and the #1 partition storing the binary code are respectively the first partition storing a communication mode startup code, and the over-the-air OTA partition (OTA Area) is used for communication.
  • the updated second partition (that is, the shared area) of the mode boot code so that any first partition can be updated with the shared area when it needs code update.
  • FIG. 4 is a diagram showing a storage space layout of a multi-mode IoT device according to an embodiment of the present invention.
  • the first partitions #0 and #1 correspond to the BLE communication mode and the Zigbee communication mode, respectively.
  • the Zigbee startup code stored in the first partition #1 is run at startup to work in the Zigbee communication mode.
  • the BLE boot code stored in the first partition #0 is run to operate in the BLE communication mode.
  • the method may further include: detecting a partition initiation flag bit of the second partition; if the The partition start flag of the second partition is valid, and the communication mode startup code in the second partition is executed to enable the multi-mode IoT device to operate in a communication mode corresponding to the second partition.
  • the method further includes: downloading, in the second partition, an update code corresponding to a current communication mode of the multi-mode IoT device; starting a partition of the second partition The flag bit is set to be valid, and the partition start flag bit of the first partition corresponding to the current communication mode is set to be invalid.
  • the OTA partition is the second partition. In this way, when the multi-mode IoT device is restarted, it is checked that the partition boot flag of the second partition is valid, thereby running the updated communication mode startup code in the second partition to implement the communication of the multi-mode IoT device running the update. Mode startup code.
  • the second partition can be shared between the first partitions, that is, the communication mode startup code in any of the first partitions can be updated through the second partition.
  • This update method is that it does not affect the operation of the current communication mode of the multimode IoT device during the process of downloading the update code to the second partition.
  • FIG. 5 is a diagram showing a storage space layout change diagram of a multimode IoT device according to an embodiment of the present invention.
  • the multimode IoT device is currently running the Zigbee communication mode (ie, the current communication mode) in the #1 partition (ie, the first partition), and the current firmware corresponding to the Zigbee communication mode at this time.
  • the code needs to be upgraded.
  • the multimode IoT device can first wirelessly communicate with the upgrade device to cause the IoT device to download the updated firmware code (ie, the update code of the communication mode or the communication mode startup code therein) to the over-the-air OTA partition (That is, the second partition), in which, after the multi-mode IoT device downloads the complete updated firmware code, it first performs integrity check and authentication, and then stores it in the air to download the OTA partition; again, multi-mode IoT The device sets the partition start flag of the #1 partition to invalid, that is, sets F1 to “0”, and sets the partition start flag of the over-the-air OTA partition to be valid, that is, F2 is set to “1”; finally, The updated firmware code downloaded in the OTA partition is operated by restarting the multi-mode IoT device to cause the multi-mode IoT device to operate in a Zigbee communication mode corresponding to the updated firmware code.
  • the updated firmware code ie, the update code of the communication mode or the communication mode startup code therein
  • the method further includes: copying the communication mode startup code in the second partition to the second In the first partition corresponding to the communication mode corresponding to the partition, and setting the partition start flag of the second partition to be invalid, setting the partition start flag in the first partition corresponding to the communication mode corresponding to the second partition to effective.
  • FIG. 6 is a diagram showing a storage space layout change diagram of a multimode IoT device according to an embodiment of the present invention.
  • the multi-mode IoT device operates in the Zigbee communication mode (ie, the current communication mode), and the partition start flag of the corresponding #1 partition (ie, the first partition) is valid, that is, F1.
  • the partition start flag of the corresponding #1 partition ie, the first partition
  • F1 the partition start flag of the corresponding #1 partition
  • the multimode IoT device wirelessly communicates with the upgrade device to cause the IoT device to download the new firmware code to the over the air to download the OTA partition (ie, the second partition), wherein when the multimode IoT device is downloading the complete new After the firmware code, it is first checked for integrity and authenticated, and then the new firmware code is stored to download the OTA partition over the air; again, the multimode IoT device sets the partition start flag of the running #1 partition to invalid.
  • the multi-mode IoT device can be restarted after waiting for a specific length of time, or immediately.
  • the multimode IoT device downloads the OTA partition copy from the air
  • the new firmware code is to the partition corresponding to the BLE communication mode, that is, the #0 partition
  • the multi-mode IoT device sets the partition startup flag of the over-the-air OTA partition to be invalid.
  • Set F2 to "0” and set the partition start flag of #0 of the completed code update to be valid, that is, set F0 to "1", so it can be partitioned from #0 when the multimode IoT device is restarted. Start the updated BLE communication mode startup code.
  • the partition start flag of the corresponding #1 partition ie, the first partition
  • F1 is set to "1”
  • the multimode IoT device wirelessly communicates with the upgrade device to enable the multimode IoT device to download the new firmware code to control the download of the OTA partition (ie, the second partition), wherein when the multimode IoT device is downloading the complete new After the firmware code, it is first checked for integrity and authenticated, and then the new firmware code is stored to download the OTA partition over the air; again, the multimode IoT device sets the partition start flag of the running #1 partition to invalid. , that is, set F1 to “0”, and set the partition start flag of the over-the-air OTA partition to be valid, that is, set F2 to “1”; then, the latter can restart the multi-mode IoT device immediately after waiting for a certain length of time.
  • the multimode IoT device Triggering the multimode IoT device to run the downloaded new firmware code in the OTA partition to enable the multimode IoT device to operate in the Zigbee communication mode corresponding to the new firmware code; finally, the multimode IoT device downloads the OTA partition from the air Copy the new firmware code to the partition corresponding to the Zigbee communication mode, that is, the #1 partition, and the multi-mode IoT device sets the partition startup flag of the over-the-air OTA partition to none.
  • the embodiment of the present invention can effectively implement a startup code of a specific communication mode in a desired storage area when a multi-mode IoT device is started at a startup based on a specific storage area division, while running a multi-mode IoT device to support multiple IoT communication modes.
  • Improve the utilization of IoT device hardware resources by each communication mode supported by the IoT device effectively reduce the network delay caused by the IoT device hardware resource limitation, and thus improve the user experience of the IoT device.
  • the embodiment of the present invention can also implement the update and upgrade of the communication mode startup code by using the common control download OTA partition, and realize that the first partition does not replace the communication mode startup code stored in the partition before the communication mode startup code update and upgrade. A more secure and reliable update and upgrade process.
  • FIG. 7 is a schematic diagram showing the structure of a multimode IoT device according to an embodiment of the present invention.
  • an embodiment of the present invention provides a multi-mode IoT device, where the device 70 includes: a control unit 701; a memory 702, where the memory 702 includes a plurality of first partitions, and the plurality of first partitions are respectively stored.
  • the radio transceiver unit 703 supports a plurality of communication modes; wherein the control unit 701 detects a partition start flag in the memory 702 in response to a boot operation of the multimode IoT device, when When a valid partition start flag is detected, a communication mode start code in the first partition corresponding to the valid partition start flag is executed, so that the radio transceiver unit 703 operates to correspond to the corresponding first partition. Communication mode.
  • the communication mode includes Bluetooth low energy or Bluetooth low energy Mesh, Zigbee, Thread, HomeKit, ANT, and a private communication protocol.
  • the memory 702 further includes a second partition for updating the communication mode startup code and including a partition start flag bit; the control unit 701 is further configured to: detect a partition start flag of the second partition; if it is detected that the partition start flag of the second partition is valid, running a communication mode startup code in the second partition to enable the radio transceiver unit 703 to work And a communication mode corresponding to the second partition.
  • control unit 701 is further configured to: download an update code corresponding to a current communication mode of the radio frequency transceiver unit 703 in the second partition;
  • the partition start flag is set to be valid, and the partition start flag of the first partition corresponding to the current communication mode is set to be invalid.
  • the control unit 701 is further configured to: communicate in the second partition Copying the mode startup code to the first partition corresponding to the communication mode corresponding to the second partition, and setting the partition startup flag of the second partition to be invalid, and the communication mode corresponding to the second partition
  • the partition start flag bit in the corresponding first partition is set to be valid.
  • the multimode IoT device of the present invention can include at least one or more processors, and at least one memory.
  • the memory stores a computer program that, when executed by the processor, causes the processor to perform the various steps of the boot method for the multi-mode IoT device described in this specification, for example, the processor can execute as shown in FIG.
  • Operation 101 receiving a boot operation for a multimode IoT device; operation 102, detecting a partition boot flag in a memory in response to the boot operation, wherein the memory includes a plurality of first partitions, the plurality Each of the first partitions respectively stores a communication mode startup code and includes a partition startup flag, and when the partition startup flag is set to be valid, the corresponding partition is used as a bootable partition, and the partition startup flag is set to be invalid.
  • operation 103 when the corresponding partition is used to indicate that the corresponding partition is unbootable; operation 103, when a valid partition start flag is detected, running a communication mode startup code in the first partition corresponding to the valid partition start flag bit, so that The multimode IoT device operates in a communication mode corresponding to the corresponding first partition.
  • FIG. 8 shows an implementation diagram of a multi-mode IoT device according to an embodiment of the present invention.
  • a multimode IoT device 800 in accordance with such an embodiment of the present invention is described below with reference to FIG.
  • the multimode IoT device 800 shown in FIG. 8 is merely an example and should not impose any limitation on the function and scope of use of the embodiments of the present invention.
  • device 800 is shown in the form of a general purpose computing device, including but not limited to: at least one processor 810, at least one memory 820, and a bus connecting different system components (including memory 820 and processor 810). 860.
  • Bus 860 includes an address bus, a control bus, and a data bus.
  • Memory 820 can include volatile memory, such as random access memory (RAM) 821 and/or cache memory 822, and can further include read only memory (ROM) 823.
  • RAM random access memory
  • ROM read only memory
  • the memory 820 can also include a set (at least one) of program modules 824, including but not limited to: an operating system, one or more applications, other program modules, and program data, each of these examples. This combination may include the implementation of a network environment.
  • the multimode IoT device 800 can also communicate with one or more external devices 80 (eg, a keyboard, pointing device, Bluetooth device, etc.). This communication can be performed through an input/output (I/O) interface 840 and displayed on display unit 830. Also, the multimode IoT device 800 can communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) via the network adapter 850. As shown, network adapter 850 communicates with other modules in multimode IoT device 800 via bus 860.
  • LAN local area network
  • WAN wide area network
  • public network such as the Internet
  • multi-mode IoT device 800 may be utilized in conjunction with multi-mode IoT device 800, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems. , tape drives, and data backup storage systems.
  • aspects of the present invention may also be embodied in the form of a computer program product comprising program code for use in making the program code when executed by a processor
  • the processor performs various steps of the method described above, for example, the processor can perform operation 101 as shown in FIG.
  • operation 102 in response to the boot operation, to a memory The partition boot flag is detected, wherein the memory includes a plurality of first partitions, each of the plurality of first partitions respectively storing a communication mode startup code and including a partition start flag, and the partition start flag is set to When valid, it is used to indicate that the corresponding partition is a bootable partition, and when the partition start flag is set to be invalid, it is used to indicate that the corresponding partition is an unbootable partition; and operation 103, when a valid partition start flag is detected, the operation is performed. a communication mode startup code in the first partition corresponding to the valid partition initiation flag bit to cause the multimode
  • the IoT device operates in a communication mode corresponding to the corresponding first partition.
  • the computer program product can employ any combination of one or more readable media.
  • the readable medium can be a readable signal medium or a readable storage medium.
  • the readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive lists) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the foregoing.
  • FIG. 9 shows a schematic diagram of a computer readable storage medium storing a computer program implementing a boot method for a multimode IoT device in accordance with an embodiment of the present invention.
  • a program product 900 in accordance with an embodiment of the present invention can employ a portable compact disk read only memory (CD-ROM) and includes program code and can be run on a terminal or server.
  • CD-ROM portable compact disk read only memory
  • the program product of the present invention is not limited thereto, and in the present document, the readable storage medium may be any tangible medium containing or storing a program that can be used by or in connection with an instruction execution system, apparatus or device.
  • Program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C++, etc., including conventional procedural Programming language—such as the "C" language or a similar programming language.
  • the program code can be executed entirely on the user computing device, partly on the user device, partly on the user computing device, or entirely on the remote computing device or server.
  • the remote computing device can be connected to the user computing device via any kind of network, including a local area network (LAN) or wide area network (WAN), or can be connected to an external computing device (eg, utilizing Internet services)
  • the provider is connected via the Internet).

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • Stored Programmes (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明提供一种用于多模IoT设备的启动方法、多模IoT设备及计算机存储介质，其中，所述用于多模IoT设备的启动方法包括：接收针对多模IoT设备的启动操作；响应于所述启动操作，对存储器中的分区启动标志位进行检测，其中所述存储器包括多个第一分区，所述多个第一分区分别存储有一种通信模式启动代码并且包含分区启动标志位，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区；当检测到有效的分区启动标志位时，运行与所述有效的分区启动标志位对应的第一分区中的通信模式启动代码，以使所述多模IoT设备工作于与所对应的第一分区对应的通信模式。

Description

用于多模IoT设备的启动方法、多模IoT设备及存储介质 技术领域
本发明涉及多模物联网(IoT)技术，尤其涉及一种用于多模IoT设备的启动方法、多模IoT设备及计算机存储介质。
背景技术
目前，存在有多个可适用于2.4GHz IoT的通信标准或通信模式，如蓝牙低功耗(Bluetooth Low Energy，BLE)、蓝牙低功耗Mesh(自组网蓝牙)、Zigbee(紫蜂协议)、Thread、6LoWPAN等，这些通信模式在家庭、办公室和工业环境等应用领域中重叠或交叉覆盖。
当前市场上以泰凌微电子(上海)有效公司为例的公司可提供多模物联网射频系统级芯片(IoT RF SoC)以使单一设备能够在不同的IoT通信模式下工作。举例来说，只需将频率为2.4GHz的射频无线电集成到集成电路(IC)芯片，即可使得该IC芯片支持不同的IoT通信模式。
然而，目前多模IoT设备支持多种不同IoT通信模式的方式是多种不同IoT通信模式运行在同一固件上，共享同一固件上的软件/硬件资源，因此存在各IoT通信模式无法完全占用同一固件上的软件/硬件资源的问题。
发明内容
本公开能够基于特定的存储区域划分而有效实现多模IoT设备的启动，在允许多模IoT设备支持多种IoT通信模式的同时，使得当前运行的IoT通信模式能够单独使用固件的所有软件/硬件资源，提高IoT设备的通信响应时间，减少通信延时。
根据本公开的第一方面，提供一种用于多模IoT设备的启动方法，该方法包括：接收针对多模IoT设备的启动操作；响应于所述启动操作，对存储器中的分区启动标志位进行检测，其中所述存储器包括多个第一分区，所述多个第一分区分别存储有一种通信模式启动代码并且包含分区启 动标志位，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区；当检测到有效的分区启动标志位时，运行与所述有效的分区启动标志位对应的第一分区中的通信模式启动代码，以使所述多模IoT设备工作在与所对应的第一分区对应的通信模式。
根据本公开的一个实施方式，其中，所述存储器还包括第二分区，所述第二分区用于通信模式启动代码的更新并且包括分区启动标志位，该方法进一步包括：检测所述第二分区的分区启动标志位；如果检测到所述第二分区的分区启动标志位为有效，则运行所述第二分区中的通信模式启动代码，以使所述多模IoT设备工作于与所述第二分区对应的通信模式。
根据本公开的一个实施方式，其中，所述方法还包括：在所述第二分区中下载与所述多模IoT设备的当前通信模式对应的更新代码；将所述第二分区的分区启动标志位设置为有效，并将当前通信模式对应的第一分区的分区启动标志位设置为无效。
根据本公开的一个实施方式，其中，在使所述多模IoT设备工作于与所述第二分区对应的通信模式后，所述方法还包括：将所述第二分区中的通信模式启动代码复制到与所述第二分区对应的通信模式所对应的第一分区中，并将所述第二分区的分区启动标志位设置为无效，将与所述第二分区对应的通信模式所对应的第一分区中的分区启动标志位设置为有效。
根据本公开的一个实施方式，其中，所述通信模式包括以下中的至少两者：BLE或BLE Mesh，Zigbee，Thread，HomeKit，ANT，以及私有通信协议。
根据本公开的第二方面，提供一种多模IoT设备，该设备包括：控制单元；存储器，所述存储器包括多个第一分区，所述多个第一分区分别存储有一种通信模式启动代码并且包含分区启动标志位，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区；射频收发单元，支持多种通信模式；其中，所述控制单元响应于对所述多模IoT设备的启动操作而检测所述存储器中的分区启动标志位，当检测到有效的分区启动标志位时，运行与所述有效的分区启动标志位对应的第一分区中的通信模式 启动代码，以使所述射频收发单元工作于与所对应的第一分区对应的通信模式。
根据本公开的一个实施方式，其中，所述存储器还包括第二分区，所述第二分区用于通信模式启动代码的更新并且包括分区启动标志位；所述控制单元还用于：检测所述第二分区的分区启动标志位；如果检测到所述第二分区的分区启动标志位为有效，则运行所述第二分区中的通信模式启动代码，以使所述射频收发单元工作于与所述第二分区对应的通信模式。
根据本公开的一个实施方式，其中，所述控制单元还用于：在所述第二分区中下载与所述射频收发单元的当前通信模式对应的更新代码；将所述第二分区的分区启动标志位设置为有效，并将当前通信模式对应的第一分区的分区启动标志位设置为无效。
根据本公开的一个实施方式，其中，在使所述射频收发单元工作于与所述第二分区对应的通信模式后，所述控制单元还用于：将所述第二分区中的通信模式启动代码复制到与所述第二分区对应的通信模式所对应的第一分区中，并将所述第二分区的分区启动标志位设置为无效，将与所述第二分区对应的通信模式所对应的第一分区中的分区启动标志位设置为有效。
根据本公开的第三方面，提供一种多模IoT设备，包括：一个或者多个处理器；存储器；存储在所述存储器中的计算机程序，所述计算机程序在被所述一个或者多个处理器执行时使所述处理器执行上述第一方面中任一项所述的方法。
根据本公开的第四方面，提供一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序在被处理器执行时使得处理器执行上述第一方面中任一项所述的方法。
通过本公开的教导，能够基于特定的存储区域划分而有效实现多模IoT设备在启动时运行期望存储区域中的特定通信模式的启动代码，在运行多模IoT设备支持多种IoT通信模式的同时，使得当前运行的IoT通信模式能够单独使用固件的所有软件/硬件资源，提高IoT设备的通信响应时间，减少通信延时，从而提升多模IoT设备的用户体验。因此，本公开是通过在IoT设备启动阶段时择一选择有效的通信模式，实现该通信模式单 独使用固件的软件/硬件资源。
需要理解的是，本公开的教导并不需要实现上面所述的全部有益效果，而是特定的技术方案可以实现特定的技术效果，并且本公开的其他实施方式还能够实现上面未提到的有益效果。
附图说明
通过参考附图阅读下文的详细描述，本发明示例性实施方式的上述以及其他目的、特征和优点将变得易于理解。在附图中，以示例性而非限制性的方式示出了本发明的若干实施方式，其中：
在附图中，相同或对应的标号表示相同或对应的部分。
图1示出了本发明实施例用于多模IoT设备的启动方法的实现流程示意图；
图2示出了本发明实施例多模IoT射频系统级芯片的系统架构图；
图3示出了本发明实施例多模IoT设备的存储空间布局图；
图4示出了本发明实施例多模IoT设备的存储空间布局图；
图5示出了本发明实施例多模IoT设备的存储空间布局变化图；
图6示出了本发明实施例多模IoT设备的存储空间布局变化图；
图7示出了本发明实施例多模IoT设备的组成结构示意图；
图8示出了根据本发明实施方式的多模IoT设备的实现示意图；
图9示出了存储有实现根据本发明实施方式的用于多模IoT设备的启动方法的计算机程序的计算机可读存储介质的示意图。
具体实施方式
下面将参考若干示例性实施方式来描述本发明的原理和精神。应当理解，给出这些实施方式仅仅是为了使本领域技术人员能够更好地理解进而实现本发明，而并非以任何方式限制本发明的范围。相反，提供这些实施方式是为了使本公开更加透彻和完整，并且能够将本公开的范围完整地传达给本领域的技术人员。
下面结合附图对本发明的具体实施方式进行详细描述。
图1示出了本发明实施例用于多模IoT设备的启动方法的实现流程示 意图。
如图1所示，本发明实施例提供一种用于多模IoT设备的启动方法，该方法包括如下操作：操作101，接收针对多模IoT设备的启动操作；操作102，响应于所述启动操作，对存储器中的分区启动标志位进行检测，其中所述存储器包括多个第一分区，所述多个第一分区分别存储有一种通信模式启动代码并且包含分区启动标志位，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区；操作103，当检测到有效的分区启动标志位时，运行与所述有效的分区启动标志位对应的第一分区中的通信模式启动代码，以使所述多模IoT设备工作在与所对应的第一分区对应的通信模式。
其中，所述通信模式包括以下中的至少两者：BLE或BLE Mesh，Zigbee，Thread，HomeKit，ANT，以及私有通信协议。
在操作101，针对多模IoT设备的启动操作可以包括针对多模IoT设备的上电操作；针对多模IoT设备的启动操作还可以包括针对多模IoT设备的重启操作。
在操作103，当检测到有效的分区启动标志位时，即表明检测有所述有效的分区启动标志位所对应的第一分区为可启动的分区，也就可以直接运行与所述有效的分区启动标志位对应的第一分区中的通信模式启动代码，以使所述多模IoT设备工作于与所对应的第一分区对应的通信模式。
本发明实施例在通过操作101-103实现多模IoT设备的启动之前，需要预先对多模IoT设备的存储器进行存储区域划分，其操作流程如下：步骤1，划分存储空间，以得到N个分区，N的取值大于等于3；步骤2，将所述N个分区进行功能分区，得到M个包含分区启动标志位的分区和N-M个用户数据分区，M的取值大于等于2，且小于N。其中，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区。
在步骤1，所述划分存储空间的方式主要包括静态划分方式和动态划分方式。其中，静态划分方式可以是以固定字节为间隔进行存储区域划分以得到多个分区；动态划分方式可以是按需进行实时的动态存储区域划 分。当然，所述划分存储空间的方式的选取也会与存储器本身存储格式有关。
在步骤2，所述M个包含分区启动标志位的分区可以细化为多个分别存储有一种通信模式启动代码的第一分区和用于通信模式启动代码的更新的第二分区，如空中下载OTA分区。
图2示出了本发明实施例多模IoT射频系统级芯片的系统架构图；图3示出了本发明实施例多模IoT设备的存储空间布局图。
在一示例中，如图2所示，所述多模IoT射频系统级芯片包括有能够支持不同IoT通信标准的射频收发器(RF Transceiver)，一个32位或更高性能的微控制器(MCU)，以及诸如闪存(Flash)和启动芯片(BROM)等不同格式的存储空间。如图3所示，诸如如图2所示的闪存或其他格式的存储空间可以划分为以例如64K，128K及其256K字节为间隔的四个分区；进一步地，将该四个分区进行功能分区，得到被预留给用户数据的一个分区，即用户数据分区(User Data Area)和三个分别包括有分区启动标志位F0、F1、F2的分区。其中，图3所示的存储有二进制代码的#0分区、存储有二进制代码的#1分区分别为存储有一种通信模式启动代码的第一分区，空中下载OTA分区(OTA Area)为用于通信模式启动代码的更新的第二分区(也即共享区域)，这样任何第一分区需要代码更新时均可借助该共享区域加以更新。这里，若要将分区启动标志位设置为有效而使对应的分区可用于启动，则可将分区启动标志位的值设置为“1”；反之，若要将分区启动标志位设置为无效而使对应的分区不可用于启动，则将该分区启动标志位的值设置为“0”。举例来说，若F0＝0，F1＝1，F2＝0,…的情况下，则可确定所述#1分区为可启动分区。
图4示出了本发明实施例多模IoT设备的存储空间布局图。
在一示例中，如图4所示，其中第一分区#0和#1分别对应BLE通信模式和Zigbee通信模式。举例来说，对于F0＝0，F1＝1，F2＝0,…的情况下，则可检测到F1＝1，即确定对应的第一分区#1为可启动的分区，即多模IoT设备在启动时会运行第一分区#1中存储的Zigbee启动代码，以工作于Zigbee通信模式。又比如，对于F0＝1,F1＝x,F2＝x,…的情况下，则可检测到F0＝1，即确定对应第一分区#0为可启动的分区，即多模IoT设备在启 动时会运行第一分区#0中存储的BLE启动代码，以工作于BLE通信模式。
根据本公开的另一个实施方式，基于如图3所示的多模IoT设备的存储空间布局图，该方法还可以进一步包括：检测所述第二分区的分区启动标志位；如果检测到所述第二分区的分区启动标志位为有效，则运行所述第二分区中的通信模式启动代码，以使所述多模IoT设备工作于与所述第二分区对应的通信模式。
根据本公开的又一个实施方式，其中，所述方法还包括：在所述第二分区中下载与所述多模IoT设备的当前通信模式对应的更新代码；将所述第二分区的分区启动标志位设置为有效，并将当前通信模式对应的第一分区的分区启动标志位设置为无效。在图3所示实施方式中，OTA分区为第二分区。这样，在多模IoT设备重启时，会检查到该第二分区的分区启动标志位是有效的，从而运行该第二分区中的更新的通信模式启动代码，实现多模IoT设备运行更新的通信模式启动代码。在这里，第二分区可在第一分区之间共享，即，任何第一分区中的通信模式启动代码均可以通过第二分区进行更新。这种更新方式的优势还在于：在向第二分区下载更新代码的过程中，不会影响多模IoT设备当前通信模式的运行。
图5示出了本发明实施例多模IoT设备的存储空间布局变化图。
在一示例中，如图5所示，假设多模IoT设备当前正在运行#1分区(即第一分区)中的Zigbee通信模式(即当前通信模式)，且此时Zigbee通信模式对应的当前固件代码需要升级。为此，多模IoT设备首先可以与升级设备进行无线通信，以使所述IoT设备下载该更新的固件代码(即，通信模式的更新代码或其中含有通信模式启动代码)至空中下载OTA分区(即第二分区)，其中，当多模IoT设备下载了完整的更新的固件代码后，首先对其进行完整性检查和认证，通过之后才将其存储在空中下载OTA分区；再次，多模IoT设备将#1分区的分区启动标志位设置为无效，即将F1设置为“0”，并将所述空中下载OTA分区的分区启动标志位设置为有效，即将F2设置为“1”；最后，可以通过重启所述多模IoT设备的方式运行所述OTA分区中下载的更新的固件代码，以使所述多模IoT设备工作于与更新的固件代码对应的Zigbee通信模式。
根据本公开的又一个实施方式，其中，在使多模IoT设备工作于与第 二分区对应的通信模式后，所述方法还包括：将第二分区中的通信模式启动代码复制到与第二分区对应的通信模式所对应的第一分区中，并将第二分区的分区启动标志位设置为无效，将与第二分区对应的通信模式所对应的第一分区中的分区启动标志位设置为有效。这样，当多模IoT设备重启后，会从存储有更新的通信模式启动代码的低压分区中启动，以更新的通信模式启动代码来运行该通信模式。
图6示出了本发明实施例多模IoT设备的存储空间布局变化图。
在一示例中，如图6所示，假设多模IoT设备运行在Zigbee通信模式(即当前通信模式)，其对应的#1分区(即第一分区)的分区启动标志位为有效，即F1设置为“1”，而目前正需要针对与BLE通信模式对应的#0分区(即第一分区)的当前固件代码进行升级。首先，多模IoT设备与升级设备进行无线通信，以使IoT设备下载该新的固件代码至空中下载OTA分区(即第二分区)，其中，当所述多模IoT设备在下载了完整的新的固件代码后，首先对其进行完整性检查和认证，之后才存储该新的固件代码至空中下载OTA分区；再次，多模IoT设备将正在运行的#1分区的分区启动标志位设置为无效，即将F1设置为“0”，并将所述空中下载OTA分区的分区启动标志位设置为有效，即将F2记为“1”；接着，可以通过等待特定时长后或者立即重启多模IoT设备，触发多模IoT设备运行OTA分区中已下载的新的固件代码，以使多模IoT设备工作于与所述新的固件代码对应的BLE通信模式；最后，多模IoT设备从空中下载OTA分区拷贝所述新的固件代码至BLE通信模式对应的分区，即#0分区，同时多模IoT设备将空中下载OTA分区的分区启动标志位设置为无效，即将F2设置为“0”，并将所述已完成代码更新的#0的分区启动标志位设置为有效，即将F0设置为“1”，因此在多模IoT设备重启时就能够从#0分区启动更新后的BLE通信模式启动代码。
在以上示例的一种变型中，假设多模IoT设备运行在Zigbee通信模式(即当前通信模式)，其对应的#1分区(即第一分区)的分区启动标志位为有效，即F1设置为“1”，而目前正需要针对与Zigbee通信模式对应的#1分区(即第一分区)的当前固件代码进行升级。首先，多模IoT设备与升级设备进行无线通信，以使多模IoT设备下载该新的固件代码至控制下 载OTA分区(即第二分区)，其中，当多模IoT设备在下载了完整的新的固件代码后，首先对其进行完整性检查和认证，之后才存储该新的固件代码至空中下载OTA分区；再次，多模IoT设备将正在运行的#1分区的分区启动标志位设置为无效，即将F1设置为“0”，并将所述空中下载OTA分区的分区启动标志位设置为有效，即将F2设置为“1”；接着，可通过等待特定时长后后者立即重启多模IoT设备，触发多模IoT设备运行OTA分区中已下载的新的固件代码，以使多模IoT设备工作于与所述新的固件代码对应的Zigbee通信模式；最后，多模IoT设备从空中下载OTA分区拷贝所述新的固件代码至Zigbee通信模式对应的分区，即#1分区，同时多模IoT设备将空中下载OTA分区的分区启动标志位设置为无效，即将F2设置为“0”，并将所述已完成代码更新的#1的分区启动标志位设置为有效，即将F1设置为“1”，因此在多模IoT设备重启时就能够从#1分区启动更新后的Zigbee通信模式启动代码。
如此，本发明实施例能够基于特定的存储区域划分而有效实现多模IoT设备在启动时运行期望存储区域中的特定通信模式的启动代码，在运行多模IoT设备支持多种IoT通信模式的同时，提高IoT设备所支持的每种通信模式对IoT设备硬件资源的利用率，有效降低因IoT设备硬件资源限制而引起的网络时延，进而提升IoT设备的用户体验。另外，本发明实施例还能够借用共同的控制下载OTA分区实现通信模式启动代码的更新升级，且实现第一分区在通信模式启动代码更新升级前不会替换该分区中存储的通信模式启动代码，实现更加安全可靠的更新升级过程。
图7示出了本发明实施例多模IoT设备的组成结构示意图。
如图7所示，本发明实施例提供一种多模IoT设备，该设备70包括：控制单元701；存储器702，所述存储器702包括多个第一分区，所述多个第一分区分别存储有一种通信模式启动代码并且包含分区启动标志位，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区；射频收发单元703，支持多种通信模式；其中，所述控制单元701响应于对所述多模IoT设备的启动操作而检测所述存储器702中的分区启动标志位，当检测到有效的分区启动标志位时，运行与所述有效的分区启动标志 位对应的第一分区中的通信模式启动代码，以使所述射频收发单元703工作于与所对应的第一分区对应的通信模式。
其中，所述通信模式包括蓝牙低功耗或蓝牙低功耗Mesh，Zigbee，Thread，HomeKit，ANT，以及私有通信协议。
根据本公开的一个实施方式，其中，所述存储器702还包括第二分区，所述第二分区用于通信模式启动代码的更新并且包括分区启动标志位；所述控制单元701还用于：检测所述第二分区的分区启动标志位；如果检测到所述第二分区的分区启动标志位为有效，则运行所述第二分区中的通信模式启动代码，以使所述射频收发单元703工作于与所述第二分区对应的通信模式。
根据本公开的一个实施方式，其中，所述控制单元701还用于：在所述第二分区中下载与所述射频收发单元703的当前通信模式对应的更新代码；将所述第二分区的分区启动标志位设置为有效，并将当前通信模式对应的第一分区的分区启动标志位设置为无效。
根据本公开的一个实施方式，其中，在使所述射频收发单元703工作于与所述第二分区对应的通信模式后，所述控制单元701还用于：将所述第二分区中的通信模式启动代码复制到与所述第二分区对应的通信模式所对应的第一分区中，并将所述第二分区的分区启动标志位设置为无效，将与所述第二分区对应的通信模式所对应的第一分区中的分区启动标志位设置为有效。
这里需要指出的是：以上设备实施例中的描述，与上述方法描述是类似的，能获得与方法相同的有益效果，对其不作赘述。对于本发明设备实施例中未披露的技术细节，请参照本发明方法实施例的描述。
示例性设备
在介绍了本发明示例性实施方式的方法和设备之后，接下来，介绍根据本发明的另一示例性实施方式的多模IoT设备。
所属技术领域的技术人员能够理解，本发明的各个方面可以实现为系统、方法或程序产品。因此，本发明的各个方面可以具体实现为以下形式，即：完全的硬件实施方式、完全的软件实施方式(包括固件、微代码等)，或硬件和软件方面结合的实施方式，这里可以统称为“电路”、“模块”或“系 统”。
在一些可能的实施方式中，本发明的多模IoT设备可以至少包括一个或多个处理器、以及至少一个存储器。其中，存储器存储有计算机程序，当计算机程序被处理器执行时，使得处理器执行本说明书中描述的用于多模IoT设备的启动方法的各个步骤，例如，处理器可以执行如图1中所示的操作101，接收针对多模IoT设备的启动操作；操作102，响应于所述启动操作，对存储器中的分区启动标志位进行检测，其中所述存储器包括多个第一分区，所述多个第一分区分别存储有一种通信模式启动代码并且包含分区启动标志位，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区；操作103，当检测到有效的分区启动标志位时，运行与所述有效的分区启动标志位对应的第一分区中的通信模式启动代码，以使所述多模IoT设备工作在与所对应的第一分区对应的通信模式。
图8示出了根据本发明实施方式的多模IoT设备的实现示意图。
下面参照图8来描述根据本发明的这种实施方式的多模IoT设备800。图8显示的多模IoT设备800仅仅是一个示例，不应对本发明实施例的功能和使用范围带来任何限制。
如图8所示，设备800以通用计算设备的形式示出，包括但不限于：上述至少一个处理器810、上述至少一个存储器820、连接不同系统组件(包括存储器820和处理器810)的总线860。
总线860包括地址总线，控制总线和数据总线。
存储器820可以包括易失性存储器，例如随机存取存储器(RAM)821和/或高速缓存存储器822，还可以进一步包括只读存储器(ROM)823。
存储器820还可以包括一组(至少一个)程序模块824，这样的程序模块824包括但不限于：操作系统、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络环境的实现。
多模IoT设备800还可以与一个或多个外部设备80(例如键盘、指向设备、蓝牙设备等)通信。这种通信可以通过输入/输出(I/O)接口840进行，并在显示单元830上进行显示。并且，多模IoT设备800还可以通 过网络适配器850与一个或者多个网络(例如局域网(LAN)，广域网(WAN)和/或公共网络，例如因特网)通信。如图所示，网络适配器850通过总线860与多模IoT设备800中的其它模块通信。应当明白，尽管图中未示出，但可以结合多模IoT设备800使用其它硬件和/或软件模块，包括但不限于：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID系统、磁带驱动器以及数据备份存储系统等。
示例性计算机程序产品
在一些可能的实施方式中，本发明的各个方面还可以实现为一种计算机程序产品的形式，其包括程序代码，当所述程序代码在被处理器执行时，所述程序代码用于使所述处理器执行上面描述的方法的各个步骤，例如，处理器可以执行如图1中所示的操作101，接收针对多模IoT设备的启动操作；操作102，响应于所述启动操作，对存储器中的分区启动标志位进行检测，其中所述存储器包括多个第一分区，所述多个第一分区分别存储有一种通信模式启动代码并且包含分区启动标志位，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区；操作103，当检测到有效的分区启动标志位时，运行与所述有效的分区启动标志位对应的第一分区中的通信模式启动代码，以使所述多模IoT设备工作在与所对应的第一分区对应的通信模式。
所述计算机程序产品可以采用一个或多个可读介质的任意组合。可读介质可以是可读信号介质或者可读存储介质。可读存储介质例如可以是——但不限于——电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。可读存储介质的更具体的例子(非穷举的列表)包括：具有一个或多个导线的电连接、便携式盘、硬盘、随机存取存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。
图9示出了存储有实现根据本发明实施方式的用于多模IoT设备的启动方法的计算机程序的计算机可读存储介质的示意图。
如图9所示，描述了根据本发明的实施方式的程序产品900，其可以采用便携式紧凑盘只读存储器(CD-ROM)并包括程序代码，并可以在终 端或服务器上运行。然而，本发明的程序产品不限于此，在本文件中，可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
可以以一种或多种程序设计语言的任意组合来编写用于执行本发明操作的程序代码，所述程序设计语言包括面向对象的程序设计语言—诸如Java、C++等，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算设备上执行、部分地在用户设备上执行、部分在用户计算设备上执行、或者完全在远程计算设备或服务器上执行。在涉及远程计算设备的情形中，远程计算设备可以通过任意种类的网络——包括局域网(LAN)或广域网(WAN)—连接到用户计算设备，或者，可以连接到外部计算设备(例如利用因特网服务提供商来通过因特网连接)。
此外，尽管在附图中以特定顺序描述了本发明方法的操作，但是，这并非要求或者暗示必须按照该特定顺序来执行这些操作，或是必须执行全部所示的操作才能实现期望的结果。附加地或备选地，可以省略某些步骤，将多个步骤合并为一个步骤执行，和/或将一个步骤分解为多个步骤执行。
应当注意，尽管在上文详细描述中提及了用于软件测试的若干装置及子装置，但是这种划分并非强制性的。实际上，根据本发明的实施方式，上文描述的两个或更多装置的特征和功能可以在一个装置中具体化。反之，上文描述的一个装置的特征和功能可以进一步划分为由多个装置来具体化。
虽然已经参考若干具体实施方式描述了本发明的精神和原理，但是应该理解，本发明并不限于所公开的具体实施方式，对各方面的划分也不意味着这些方面中的特征不能组合以进行受益，这种划分仅是为了表述的方便。本发明旨在涵盖所附权利要求的精神和范围内所包括的各种修改和等同布置。

Claims (12)

  1. 一种用于多模IoT设备的启动方法，该方法包括：
    接收针对多模IoT设备的启动操作；
    响应于所述启动操作，对存储器中的分区启动标志位进行检测，其中所述存储器包括多个第一分区，所述多个第一分区分别存储有一种通信模式启动代码并且包含分区启动标志位，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区；
    当检测到有效的分区启动标志位时，运行与所述有效的分区启动标志位对应的第一分区中的通信模式启动代码，以使所述多模IoT设备工作于与所对应的第一分区对应的通信模式。
  2. 根据权利要求1所述的方法，其中，所述存储器还包括第二分区，所述第二分区用于通信模式启动代码的更新并且包括分区启动标志位，该方法进一步包括：
    检测所述第二分区的分区启动标志位；
    如果检测到所述第二分区的分区启动标志位为有效，则运行所述第二分区中的通信模式启动代码，以使所述多模IoT设备工作于与所述第二分区对应的通信模式。
  3. 根据权利要求2所述的方法，其中，所述方法还包括：
    在所述第二分区中下载与所述多模IoT设备的当前通信模式对应的更新代码；
    将所述第二分区的分区启动标志位设置为有效，并将当前通信模式对应的第一分区的分区启动标志位设置为无效。
  4. 根据权利要求2所述的方法，其中，在使所述多模IoT设备工作于与所述第二分区对应的通信模式后，所述方法还包括：
    将所述第二分区中的通信模式启动代码复制到与所述第二分区对应的通信模式所对应的第一分区中，并将所述第二分区的分区启动标志位设置为无效，将与所述第二分区对应的通信模式所对应的第一分区中的分区启动标志位设置为有效。
  5. 根据权利要求1至4中任一项所述的方法，其中，所述通信模式包括以下中的至少两者：蓝牙低功耗或蓝牙低功耗Mesh，Zigbee，Thread，HomeKit，ANT，以及私有通信协议。
  6. 一种多模IoT设备，该设备包括：
    控制单元；
    存储器，所述存储器包括多个第一分区，所述多个第一分区分别存储有一种通信模式启动代码并且包含分区启动标志位，所述分区启动标志位设置为有效时用以指示对应分区为可启动的分区，而所述分区启动标志位设置为无效时用以指示对应分区为不可启动的分区；
    射频收发单元，支持多种通信模式；
    其特征在于，所述控制单元响应于对所述多模IoT设备的启动操作而检测所述存储器中的分区启动标志位，当检测到有效的分区启动标志位时，运行与所述有效的分区启动标志位对应的第一分区中的通信模式启动代码，以使所述射频收发单元工作于与所对应的第一分区对应的通信模式。
  7. 根据权利要求6所述的多模IoT设备，其中，
    所述存储器还包括第二分区，所述第二分区用于通信模式启动代码的更新并且包括分区启动标志位；
    所述控制单元还用于：
    检测所述第二分区的分区启动标志位；
    如果检测到所述第二分区的分区启动标志位为有效，则运行所述第二分区中的通信模式启动代码，以使所述射频收发单元工作于与所述第二分区对应的通信模式。
  8. 根据权利要求7所述的多模IoT设备，其中，
    所述控制单元还用于：
    在所述第二分区中下载与所述射频收发单元的当前通信模式对应的更新代码；
    将所述第二分区的分区启动标志位设置为有效，并将当前通信模式对应的第一分区的分区启动标志位设置为无效。
  9. 根据权利要求7所述的多模IoT设备，其中，在使所述射频收发 单元工作于与所述第二分区对应的通信模式后，所述控制单元还用于：
    将所述第二分区中的通信模式启动代码复制到与所述第二分区对应的通信模式所对应的第一分区中，并将所述第二分区的分区启动标志位设置为无效，将与所述第二分区对应的通信模式所对应的第一分区中的分区启动标志位设置为有效。
  10. 根据权利要求6至9中任一项所述的多模IoT设备，其中，所述通信模式包括蓝牙低功耗或蓝牙低功耗Mesh，zigbee，Thread，HomeKit，ANT，以及私有通信协议。
  11. 一种多模IoT设备，包括：
    一个或者多个处理器；
    存储器；
    存储在所述存储器中的计算机程序，所述计算机程序在被所述一个或者多个处理器执行时使所述处理器执行如权利要求1-5中任一项所述的方法。
  12. 一种计算机可读存储介质，所述计算机可读存储介质存储有计算机程序，所述计算机程序在被处理器执行时使得处理器执行如权利要求1-5中任一项所述的方法。
PCT/CN2018/091935 2017-11-27 2018-06-20 用于多模IoT设备的启动方法、多模IoT设备及存储介质 WO2019100704A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US16/763,980 US11422823B2 (en) 2017-11-27 2018-06-20 Starting method for multi-mode IoT device, multi-mode IoT device, and storage medium
EP18880374.6A EP3719634A4 (en) 2017-11-27 2018-06-20 START-UP PROCEDURE FOR MULTI-MODE IOT DEVICE, MULTI-MODE IOT DEVICE AND MEMORY HOLDER

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201711207438.7A CN107911816B (zh) 2017-11-27 2017-11-27 用于多模IoT设备的启动方法、多模IoT设备及存储介质
CN201711207438.7 2017-11-27

Publications (1)

Publication Number Publication Date
WO2019100704A1 true WO2019100704A1 (zh) 2019-05-31

Family

ID=61847975

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/091935 WO2019100704A1 (zh) 2017-11-27 2018-06-20 用于多模IoT设备的启动方法、多模IoT设备及存储介质

Country Status (4)

Country Link
US (1) US11422823B2 (zh)
EP (1) EP3719634A4 (zh)
CN (1) CN107911816B (zh)
WO (1) WO2019100704A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4144184A4 (en) * 2020-04-28 2024-04-03 Hubbell Incorporated BATTERY POWERED WIRELESS SWITCH

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107911816B (zh) 2017-11-27 2020-03-27 泰凌微电子（上海）有限公司 用于多模IoT设备的启动方法、多模IoT设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103902322A (zh) * 2012-12-28 2014-07-02 联想(北京)有限公司 系统切换方法和电子设备
CN106255955A (zh) * 2014-03-19 2016-12-21 英特尔公司 多操作系统装置的访问隔离
US20170339640A1 (en) * 2016-05-18 2017-11-23 Qualcomm Incorporated Deep sleep mode abort mechanism for machine-type communication devices
CN107911816A (zh) * 2017-11-27 2018-04-13 泰凌微电子（上海）有限公司 用于多模IoT设备的启动方法、多模IoT设备及存储介质

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100464298C (zh) * 2005-08-11 2009-02-25 技嘉科技股份有限公司 一种通讯装置及其启动方法
CN100517246C (zh) * 2006-03-14 2009-07-22 联想(北京)有限公司 一种计算机远程控制方法及系统
CN202615384U (zh) * 2012-05-25 2012-12-19 惠州Tcl移动通信有限公司 一种具有安全防护功能的移动终端
TWI525542B (zh) 2013-09-09 2016-03-11 Insyde Software Corp Ｕｅｆｉ ｂｉｏｓ開機及更新之系統及方法、記錄媒體及電腦程式產品
US20170147021A1 (en) * 2015-11-19 2017-05-25 Top Victory Investments Ltd. Internet-of-things System Having Single-mode or Multi-mode Energy Harvesting Function
US20200073452A1 (en) * 2017-04-05 2020-03-05 Sony Corporation Wireless reset mechanism for machine-to-machine device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103902322A (zh) * 2012-12-28 2014-07-02 联想(北京)有限公司 系统切换方法和电子设备
CN106255955A (zh) * 2014-03-19 2016-12-21 英特尔公司 多操作系统装置的访问隔离
US20170339640A1 (en) * 2016-05-18 2017-11-23 Qualcomm Incorporated Deep sleep mode abort mechanism for machine-type communication devices
CN107911816A (zh) * 2017-11-27 2018-04-13 泰凌微电子（上海）有限公司 用于多模IoT设备的启动方法、多模IoT设备及存储介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ANONYMOUS: "Smallest LTE Cat M1/NB1 Multimode Module for IoT and M2M Applications", SCI GAZETTE, 10 July 2017 (2017-07-10), pages 1 - 2, XP009520105, Retrieved from the Internet <URL:https://scigazette.com/2017/07/smallest-lte-cat-m1nb1-multimode-module-iot-m2m-applications> *
See also references of EP3719634A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4144184A4 (en) * 2020-04-28 2024-04-03 Hubbell Incorporated BATTERY POWERED WIRELESS SWITCH
US12009173B2 (en) 2020-04-28 2024-06-11 Hubbell Incorporated Wireless battery-powered switch

Also Published As

Publication number Publication date
US11422823B2 (en) 2022-08-23
EP3719634A4 (en) 2021-01-20
CN107911816B (zh) 2020-03-27
EP3719634A1 (en) 2020-10-07
CN107911816A (zh) 2018-04-13
US20200278871A1 (en) 2020-09-03

Similar Documents

Publication Publication Date Title
US11847470B2 (en) Request processing method, system on chip, and public cloud management component
US9301164B2 (en) Method, system, and terminal for performing system update between mobile communication terminals
JP5307706B2 (ja) オペレーティングシステムの段階的ブート処理
US9507604B2 (en) Boot method and boot system
US10853087B2 (en) UEFI boot mode OS provisioning system
US9965292B2 (en) Method of bluetooth pairing with UEFI firmware and computer system thereof
US11671379B1 (en) System and method for subscription management using dynamically composed management entities
US8495349B2 (en) Generating a primary BIOS code memory address and a recovery BIOS code memory address, where the recovery BIOS service code is loaded when the primary BIOS code fails to execute
US10430181B1 (en) Retrieving updated firmware code
WO2018210063A1 (zh) 一种终端系统启动方法及终端
WO2019100704A1 (zh) 用于多模IoT设备的启动方法、多模IoT设备及存储介质
CN111338699A (zh) 电脑主板初始化方法、装置、计算机设备及存储介质
WO2022036670A1 (en) Methods and apparatus to perform an enhanced s3 protocol to update firmware with a boot script update
TWI601072B (zh) A New Way to Create Unified Extensible Firmware Interfaces
WO2024007800A1 (zh) 云终端系统升级方法、装置、云终端和存储介质
WO2023093633A1 (zh) 终端固件的启动方法、装置、电子设备及存储介质
WO2023060893A1 (zh) 存储空间管理方法、装置、设备及存储介质
JP5619999B2 (ja) ユーティリティプログラムを実行する方法、コンピュータシステム及びコンピュータプログラムプロダクト
US11068276B2 (en) Controlled customization of silicon initialization
CN113646745A (zh) 禁用软件持久性
US9928090B2 (en) Method for processing dynamic language and electronic device using the same
TWI733284B (zh) 硬體設定裝置及其硬體設定方法
US12019489B1 (en) System and method for provisioning free standing modules
CN110928582B (zh) 信息处理设备和配置信息处理设备的目标装置的方法
WO2023087696A1 (zh) 通信模组及其外部接口配置方法、配置装置和存储介质

Legal Events

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

Ref document number: 18880374

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2018880374

Country of ref document: EP

Effective date: 20200629