CN115114082A

CN115114082A - Method, apparatus and program product for backing up data in the internet of things

Info

Publication number: CN115114082A
Application number: CN202110309476.3A
Authority: CN
Inventors: 刘杰; 刘沁
Original assignee: EMC IP Holding Co LLC
Current assignee: EMC Corp
Priority date: 2021-03-23
Filing date: 2021-03-23
Publication date: 2022-09-27
Also published as: US11762739B2; US20220308964A1

Abstract

The present disclosure relates to methods, devices and program products for backing up data in the internet of things. The Internet of things system comprises an Internet of things manager and a plurality of Internet of things devices. In one method, a signed public key is received from an internet of things device in response to receiving a registration request to register the internet of things device of a plurality of internet of things devices with an internet of things manager. Atomic data associated with the internet of things device is received, the atomic data including a signature generated with a private signature key corresponding to the public signature key. The signature is verified based on the public signature key. In response to the signature being verified, a backup data package for backup is generated based on the atomic data. Corresponding apparatus and computer program products are provided. By using the exemplary implementation mode of the present disclosure, data can be backed up in the internet of things with higher performance, and thus, the safety and reliability of the whole internet of things are improved.

Description

Method, apparatus and program product for backing up data in the internet of things

Technical Field

Implementations of the present disclosure relate to the Internet of Things (IoT), and more particularly, to methods, apparatuses, and computer program products for backing up data in the Internet of Things.

Background

With the development of computer technology, internet of things systems have been related to more and more fields. For example, in an internet of things system, such as a plant monitoring system, internet of things devices may be deployed at various locations in a production line of a plant in order to acquire various device parameters and/or image data, and the like. For another example, in an internet of things system such as a traffic management system, internet of things devices may be deployed at various locations in a road environment in order to collect traffic status data for the various locations. With the operation of the internet of things system, more and more data can be collected. At this time, how to back up data in the internet of things with higher performance so as to improve the safety and reliability of the whole internet of things becomes a technical problem.

Disclosure of Invention

It is therefore desirable to develop and implement a solution for backing up data in the internet of things in a more efficient manner. The technical scheme is expected to be capable of backing up various data in the Internet of things in a more convenient and effective mode.

According to a first aspect of the present disclosure, a method for backing up data in the internet of things is provided. In the method, a signature public key is received from an internet of things device in response to receiving a registration request to register the internet of things device of the plurality of internet of things devices with an internet of things manager. Atomic data associated with the internet of things device is received, the atomic data including a signature generated using a signature private key corresponding to the signature public key. The signature is verified based on the public signature key. In response to the signature being verified, a backup data package for backup is generated based on the atomic data.

According to a second aspect of the present disclosure, there is provided an electronic device comprising: at least one processor; a volatile memory; and a memory coupled with the at least one processor, the memory having instructions stored therein that, when executed by the at least one processor, cause the apparatus to perform a method according to the first aspect of the disclosure.

According to a third aspect of the present disclosure, there is provided a computer program product tangibly stored on a non-transitory computer-readable medium and comprising machine executable instructions for performing a method according to the first aspect of the present disclosure.

Drawings

The features, advantages and other aspects of various implementations of the present disclosure will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings, which illustrate, by way of example and not by way of limitation, several implementations of the present disclosure. In the drawings:

fig. 1 schematically illustrates a block diagram of an internet of things environment in which an example implementation according to the present disclosure may be implemented;

fig. 2 schematically shows a block diagram of a process for backing up data in the internet of things according to an exemplary implementation of the present disclosure;

fig. 3 schematically illustrates a flow chart of a method for backing up data in the internet of things according to an exemplary implementation of the present disclosure;

fig. 4 schematically shows a block diagram of a process for registering an internet of things device with an internet of things device manager according to an example implementation of the present disclosure;

fig. 5 schematically illustrates a block diagram of a data structure of internet of things atomic data for backup according to an exemplary implementation of the present disclosure;

FIG. 6 schematically shows a block diagram of a process for transmitting IoT atomic data, according to an exemplary implementation of the present disclosure;

FIG. 7 schematically illustrates a block diagram of a data structure of a backup data package, according to an exemplary implementation of the present disclosure;

fig. 8 schematically illustrates a block diagram of a process for uploading data from an internet of things device to an internet of things device manager, according to an example implementation of the present disclosure;

fig. 9 schematically illustrates a block diagram of a process for downloading data from an internet of things device manager to an internet of things device, according to an exemplary implementation of the present disclosure; and

fig. 10 schematically illustrates a block diagram of an apparatus for backing up data in the internet of things according to an exemplary implementation of the present disclosure.

Detailed Description

Preferred implementations of the present disclosure will be described in more detail below with reference to the accompanying drawings. While a preferred implementation of the present disclosure is shown in the drawings, it should be understood that the present disclosure may be implemented in various forms and should not be limited by the implementations set forth herein. Rather, these implementations are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

The term "include" and variations thereof as used herein is meant to be inclusive in an open-ended manner, i.e., "including but not limited to". Unless specifically stated otherwise, the term "or" means "and/or". The term "based on" means "based at least in part on". The terms "one example implementation" and "one implementation" mean "at least one example implementation". The term "another implementation" means "at least one additional implementation". The terms "first," "second," and the like may refer to different or the same objects. Other explicit and implicit definitions are also possible below.

Referring initially to fig. 1, describing an example of an internet of things environment, fig. 1 schematically illustrates a block diagram 100 of an internet of things environment in which an example implementation according to the present disclosure may be implemented. As shown in fig. 1, the internet of things may include a plurality of internet of things devices, and the plurality of internet of things devices may be connected to different internet of things device managers. For example, the internet of

things devices

122, 124, 126, …, and 128 may be connected to the internet of things device manager 120, the internet of things devices 132, …, and 134 may be connected to the internet of things device manager 130, and the internet of things devices 142, …, and 144 may be connected to the internet of things device manager 140.

In different internet of things environments, internet of things devices may be of different types and used to collect different types of data. For example, in a plant monitoring system, an image capture device, a video capture device, a temperature capture device, a humidity capture device, and the like may be respectively disposed at various locations of a production line. In a traffic management system, image capture devices, speed capture devices, and the like may be deployed along a roadway. Internet of things devices typically have only small memory and processing power and need to constantly transmit collected devices to a data center of the internet of things (e.g., located in the internet of things or located in the internet 110). Each internet of things device can transmit the collected data to the connected internet of things device manager. For example, the internet of things devices 132, …, and 134 may transmit the collected data to the internet of things device manager 130.

In order to ensure that data from each internet of things device can be completely recorded, backup can be performed on the acquired original data. Alternatively and/or additionally, configuration information or other information of the internet of things devices may be backed up periodically. Backup solutions based on a client-server architecture have been provided. However, the number of internet of things devices in the internet of things is huge and the processing capacity is limited, and it is difficult to deploy a backup client at each internet of things device. In addition, the data of the internet of things generally relates to private information, has high acquisition frequency, relates to a complex working environment, has wide data diversity and supports various data transmission protocols. Therefore, it is difficult to migrate the existing data backup technical scheme to the environment of the internet of things.

In order to solve the above drawbacks, implementations of the present disclosure provide a technical solution for backing up data in the internet of things. In particular, a registration mechanism is provided that can register one or more internet of things devices with an internet of things device manager to manage backup of data from the one or more internet of things devices that have been registered by the internet of things device manager. Further, it is proposed to base the backup data package as a basic unit of data backup. Here, the backup data package is generated based on data to be backed up from one or more internet of things devices.

By using the exemplary implementation manner of the present disclosure, data collected by a large number of internet of things devices in the internet of things system can be packaged into the backup data packet. In this way, a large number of internet of things devices can be managed in a more centralized manner without having to perform a backup operation for each internet of things device one by one. By using the technical scheme of the exemplary implementation mode, the complexity of the backup operation can be reduced, and the backup efficiency is further improved.

Hereinafter, a procedure according to one exemplary implementation of the present disclosure is generally described with reference to fig. 2. Fig. 2 schematically shows a block diagram 200 of a process for backing up data in the internet of things according to an exemplary implementation of the present disclosure. A plurality of internet of things devices in the internet of things system can be registered with the internet of things device manager. As shown in fig. 2, the internet of

things devices

122, 124, 126, …, and 128 in the internet of things system may be registered with the internet of things device manager 120. Similarly, other multiple internet of things devices may be registered with other internet of

things device managers

130 and 140, respectively. At this time, each internet of things device manager may manage data from the already registered internet of things devices in a centralized manner and generate a backup data packet based on the received data.

In the following, more details will be described with reference to fig. 3. Fig. 3 schematically illustrates a flow chart of a method 300 for backing up data in the internet of things according to an exemplary implementation of the present disclosure. According to an example implementation of the present disclosure, method 300 may be performed by an internet of things device manager in an internet of things system. In this way, the internet of things device manager can manage data to be backed up from a large number of internet of things devices in a more centralized manner.

At block 310 of fig. 3, a public signature key is received from an internet of things device 122 in response to receiving a registration request to register the internet of things device 122 of the plurality of internet of things devices with an internet of things manager. According to one exemplary implementation of the present disclosure, which internet of things device manager to register an internet of things device to may be specified by an administrator of the internet of things system. For example, the registration relationship may be set according to the network topology of each device in the internet of things system.

According to one example implementation of the present disclosure, each internet of things device may generate its own signature key pair (e.g., a public signature key and a private signature key). Here, the private signature key can be used by the internet of things device itself, and can be used for signing data from the internet of things device itself so as to prove the legality of the data source. The internet-of-things device 122 may send the public signature key to the corresponding internet-of-things device manager 120 so that the internet-of-things device manager 120 verifies whether the received data to be backed up is from the desired internet-of-things device.

In the following, further details regarding registration will be described with reference to fig. 4. Fig. 4 schematically shows a block diagram of a process 400 for registering an internet of things device 122 with an internet of things device manager 120 according to an example implementation of the present disclosure. As shown in fig. 4, the internet of things device manager 120 may receive 410 a registration request. According to an example implementation of the present disclosure, the source of the registration request is not limited, but the registration request may come from an administrator of the internet of things system, a backup server of the internet of things system, or from another device. Upon receiving the registration request, the internet of things device manager 120 may generate 412 an encryption key pair. The internet of things device manager 120 may then locally retain 414 the encrypted private key and send 416 the encrypted public key to the internet of things device 122.

After receiving 418 the cryptographic public key, the internet of things device 122 may generate 420 a signature key pair (e.g., a public signature key and a private signature key). The internet of things device 122 may locally retain 422 the private signature key and send 424 the public signature key to the internet of things device manager 120. The internet of things device manager 120 may receive 426 the signed public key and the registration process is completed 428. It will be appreciated that the registration of the internet of things device 122 to the internet of things device manager 120 is described above with reference only to fig. 4. When the internet of things system includes a plurality of internet of things device managers and a plurality of internet of things devices, a registration relationship between the internet of things device manager and the internet of things devices may be determined based on a network topology of the internet of things. Each internet of things device may then register with a respective internet of things device manager in a similar manner.

In the following, further details regarding receiving data to be backed up from an internet of things device are described returning to fig. 3. At block 320 of fig. 3, atomic data associated with the internet of things device 122 is received, the atomic data including a signature generated with a private signature key corresponding to the public signature key. Hereinafter, the data structure of the atomic data will be described with reference to fig. 5. Fig. 5 schematically illustrates a block diagram 500 of a data structure of internet of things atomic data for backup according to an exemplary implementation of the present disclosure. Atomic data 510, as shown in FIG. 5, can include one or more of the following fields: device ID 512, timestamp 514, encrypted data 516, and signature 518.

Here, the device ID 512 represents an identifier of the internet of things device as a data source. The timestamp 514 indicates the relevant time information for collecting the raw data. It will be understood that the raw data herein may include data (e.g., images, etc.) collected by the internet of things device 122, or may include configuration information of the internet of things device 122 itself. The encrypted data 516 represents data obtained by encrypting the acquired original data. Signature 518 represents a signature for the device ID, timestamp 514, and encrypted data 516. The signature 518 can be generated by the internet of things device 122 using a private signature key, and the signature 518 can be used to verify whether the atomic data 510 is actually from the internet of things device 122.

According to one example implementation of the present disclosure, the cryptographic public key and the cryptographic private key may be generated by the internet of things device manager 120. Here, the internet of things device manager 120 may send the encrypted public key to an internet of things device (e.g., the internet of things device 122) registered to the internet of things device manager 120. After receiving the encrypted public key, the internet of things device 122 may encrypt the collected raw data using the encrypted public key to generate encrypted data 516.

According to one exemplary implementation manner of the disclosure, a different encryption key pair can be generated for each internet of things device so as to ensure the security of data transmission. According to one exemplary implementation of the present disclosure, encrypted data 516 in atomic data 510 is decryptable only to devices with associated keys, in such a way that data security during transmission and storage of atomic data 510 can be ensured.

According to an exemplary implementation manner of the present disclosure, each internet of things device in the internet of things system may generate corresponding atomic data for each collected raw data according to a format as shown in fig. 5. Then, the internet of things device may send the atomic data to the internet of things device manager 120 at a predetermined frequency. In the context of the present disclosure, the internet of things device manager 120 may simultaneously manage a large number of internet of things devices registered thereto. At this point, the internet of things device manager 120 may receive a large amount of atomic data from a large amount of internet of things devices. In this way, the internet of things device manager 120 can manage a large amount of atomic data in a centralized manner without the need to deploy a backup client at each internet of things device for performing backups.

According to an example implementation of the present disclosure, atomic data 510 can be received based on a variety of ways. More details regarding receiving atomic data 510 will be described below with reference to FIG. 6. Fig. 6 schematically shows a block diagram of a process 600 for transmitting internet of things atomic data, according to an exemplary implementation of the present disclosure. As shown in fig. 6, the internet of things device manager 120 and the internet of things device 122 are coupled to each other via a connection (e.g., a WAN connection, LAN connection, or other connection). If the connection 610 is operating properly, the internet of things device manager 120 and the internet of things device 122 may communicate with each other. At this point, the internet of things device manager 120 may receive the atomic data 510 directly from the internet of things device 122.

According to an example implementation of the present disclosure, between multiple internet of things devices registered to the same internet of things device manager 120, an internal connection may be provided to forward data via other internet of things devices when a certain internet of things device cannot be connected to the internet of things device manager 120. If the working state of the connection 610 is abnormal, the internet of things device manager 120 and the internet of things device 122 cannot communicate. At this point, the internet of things device manager 120 may receive the atomic data 510 via other internet of things devices (e.g., the internet of things device 124). As shown in fig. 6, the internet of things device 122 is coupled to the internet of things device 124 via a connection 620. At this point, the atomic data 510 may be forwarded from the internet of things device 122 to the internet of things device manager 120 via connections 620 and 630 using the internet of things device 124. In the context of the present disclosure, the connection 620 may be of different types, and based on the settings of the system of the internet of things, the connection 620 may be based on any of: bluetooth technology, short-range communication technology, and Zigbee technology, among others.

Hereinafter, the process will be described with respect to verifying the source of the atom data 510, returning to FIG. 3. At block 330 of fig. 3, the signature is verified based on the public signature key. Here, the internet of things device manager 120 may verify whether the signature 518 in the received atomic data 510 is legitimate using the public signature key from the internet of things device 122. If the internet-of-things device manager 120 determines that the signature 518 does not match the public signature key, the received atomic data 510 is deemed not to be from the expected internet-of-things device 122. At the moment, the Internet of things system can be considered to be possibly attacked, and then an alarm can be given to prompt an administrator of the Internet of things system to take safety measures in time. If the internet of things device manager 120 determines that the signature 518 matches the signature public key, the received atomic data 510 is considered to be data that is truly from the internet of things device 122. Then, a backup operation can be performed based on the received atomic data 510.

With continued reference to FIG. 3, at block 340, in response to the signature 518 being verified, a backup data package for backup is generated based on the atomic data 510. In the following, further details regarding the backup data package are described with reference to fig. 7. Fig. 7 schematically illustrates a block diagram of a data structure 700 of a backup data package according to an exemplary implementation of the present disclosure. As the internet of things system operates, the internet of things device manager 120 may receive a large amount of atomic data from the same or different internet of things devices at different points in time. The backup data package may be generated based on predetermined rules, for example, the number of atomic data in the backup data package may be defined.

Specifically, the internet of things device manager 120 can receive

atomic data

712, 714, …, and 716. The received atomic data may be first stored in a cache at the internet of things device manager 120, and when the atomic data in the cache reaches a predetermined amount, a backup data package 710 may be generated based on the

atomic data

712, 714, …, and 716. The internet of things device manager 120 can continually receive atomic data, for example, another backup data package 720 can be generated based on the received

atomic data

722, 724, …, and 726.

According to an example implementation of the present disclosure, backup data packages may be generated based on other rules. For example, backup data packets may be generated at predetermined time intervals (e.g., hourly, daily, etc.), may be generated based on a generation request, and so forth. According to one exemplary implementation of the present disclosure, a backup condition may be specified, and the generated backup data package is stored to the backup device when the backup condition is satisfied. For example, the backup condition may specify that the generated backup data package is stored to the backup device each time the backup data package is generated. For another example, the backup condition may specify that the generated backup data package is stored to the backup device when the generated data package reaches a predetermined number (e.g., 5 or other number). As another example, the backup condition may specify that the generated backup data package is stored to the backup device in response to a backup request, and so on.

With the exemplary implementation of the present disclosure, the backup data packet is the smallest data unit of the backup operation. In this way, mass data from a large number of internet of things devices do not need to be backed up one by one, but data to be backed up can be packaged into a backup data packet and unified backup operation is performed.

More details regarding the backup operation will be described below with reference to fig. 8. Fig. 8 schematically shows a block diagram of a process 800 for uploading data from an internet of things device 122 to an internet of things device manager 120 according to an example implementation of the present disclosure. As shown in fig. 8, the internet of things device 122 may constantly collect 812 raw data. The internet of things device 122 may then perform encryption and signature operations on the collected raw data in the format shown in fig. 5 to generate atomic data 510. The internet of things device 122 may send 816 atomic data to the internet of things device manager 120. Specifically, the internet of things device 122 may send directly, or may forward as a proxy via other internet of things devices.

The internet of things device manager 120 can verify 818 the received atomic data 510. If the atomic data 510 is validated, the internet of things device manager 120 can store 820 the atomic data 510 in a local cache to generate a backup data package. If predetermined backup conditions are met 822, the backup data package may be stored 824 to the backup device. In this way, the internet of things device manager 120 may backup data from a large number of internet of things devices in a simpler and efficient manner.

According to one exemplary implementation of the present disclosure, backed-up data may be retrieved from a backup server. More details regarding retrieving backup data are described below with reference to FIG. 9. Fig. 9 schematically shows a block diagram of a process 900 for downloading data from the internet of things device manager 120 to the internet of things device 122 according to an example implementation of the present disclosure. As shown in fig. 9, the internet of things device 122 may send 910 a retrieval request to the internet of things device manager 120.

According to one exemplary implementation of the present disclosure, the retrieval request may be sent based on a variety of ways. For example, if the internet of things device manager 120 is connected with the internet of things device 122, the internet of things device 122 may directly send a retrieval request to the internet of things device manager 120 (at this time, the internet of things device manager 120 directly receives the retrieval request from the internet of things device 122). For another example, if the internet of things device manager 120 is not connected to the internet of things device 122, the internet of things device 122 may forward the retrieval request to the internet of things device manager 120 via the other internet of things device (at this time, the internet of things device manager 120 receives the retrieval request from the other internet of things device).

Here, the retrieval request may include a device ID and a timestamp associated with the data to be retrieved. The internet of things device manager 120 may receive 912 the retrieval request. If the IOT device manager 120 receives a request for retrieval, backup data associated with the retrieval request may be retrieved 914 from the backup device. For example, corresponding backup data (i.e., atomic data) may be looked up in each atomic data in a plurality of backup data packages in the backup device based on the device ID and the timestamp in the retrieval request. The found atomic data may then be decrypted 916 based on the encryption private key to generate decrypted data. Further, the internet of things device manager 120 may send 918 the decrypted data to the internet of things device 122. It will be appreciated that the data to be transmitted here is already decrypted data, which needs to be transmitted directly to the internet of things device 122 in order to avoid data leakage.

According to an example implementation of the present disclosure, the internet of things device 122 may restore previously backed-up configuration information from the backup device. At this point, the internet of things device 122 may receive the configuration information with the specified timestamp for use in restoring 920 the internet of things device 122 to the desired configuration version. With the exemplary implementation of the present disclosure, the desired backup data can be quickly found from the backup device, and the internet of things device 122 can be restored to the desired configuration.

Examples of the method according to the present disclosure have been described in detail above with reference to fig. 2 to 9, in the following the implementation of the respective apparatus will be described. According to an example implementation of the present disclosure, an apparatus for backing up data in an internet of things system is provided. The internet of things system comprises an internet of things manager and a plurality of internet of things devices, and the device comprises: a signature public key receiving module configured to receive a signature public key from an internet of things device in response to receiving a registration request to register the internet of things device of the plurality of internet of things devices with the internet of things manager; the atomic data receiving module is configured to receive atomic data associated with the Internet of things equipment, and the atomic data comprise a signature generated by using a signature private key corresponding to the signature public key; a verification module configured to verify the signature based on the public signature key; and a generation module configured to generate a backup data package for backup based on the atomic data in response to the signature being verified. According to an exemplary implementation of the present disclosure, the apparatus further includes means for performing the other steps of the method 300 described above.

According to an exemplary implementation of the present disclosure, there is provided an electronic device including: at least one processor; a volatile memory; and a memory coupled with the at least one processor, the memory having instructions stored therein that, when executed by the at least one processor, cause the apparatus to perform a method for backing up data in an internet of things system. The Internet of things system comprises an Internet of things manager and a plurality of Internet of things devices, and the method comprises the following steps: receiving a signature public key from an internet of things device in response to receiving a registration request to register the internet of things device of the plurality of internet of things devices with an internet of things manager; receiving atomic data associated with the Internet of things device, the atomic data comprising a signature generated using a signature private key corresponding to the signature public key; verifying the signature based on the signature public key; and generating a backup package for backup based on the atomic data in response to the signature being verified.

According to an exemplary implementation of the present disclosure, the method further comprises: generating an encrypted public key and an encrypted private key; and sending the encrypted public key to the Internet of things equipment.

According to an exemplary implementation manner of the disclosure, the atomic data further comprises encrypted data, and the encrypted data is obtained by encrypting the original data from the internet-of-things device by using the encryption public key.

According to an example implementation of the present disclosure, the encrypted data is generated by the internet of things device, and the atomic data further includes an identifier of the internet of things device and a timestamp corresponding to the original data.

According to an exemplary implementation of the present disclosure, receiving atomic data includes at least any one of: receiving atomic data from the internet of things device in response to determining that the internet of things device manager is connected with the internet of things device; and in response to determining that the internet of things device manager is not connected with the internet of things device, receiving atomic data via another internet of things device connected with the internet of things device.

According to an exemplary implementation of the present disclosure, the method further comprises: in response to determining that the predetermined backup condition is satisfied, storing the backup data package to a backup device associated with the internet of things system.

According to an exemplary implementation of the present disclosure, the method further comprises: in response to receiving a retrieval request to retrieve data associated with an internet of things device, retrieving backup data associated with the retrieval request from a backup device; decrypting the backup data based on the encryption private key to generate decrypted data; and sending the decrypted data to the Internet of things equipment, wherein the decrypted data is used for recovering the configuration information of the Internet of things equipment.

According to an example implementation of the present disclosure, receiving the retrieval request includes at least any one of: in response to determining that the internet of things device manager is connected with the internet of things device, receiving a retrieval request from the internet of things device; and in response to determining that the internet of things device manager is not connected with the internet of things device, receiving a retrieval request via another internet of things device connected with the internet of things device.

According to an exemplary implementation of the present disclosure, the method further comprises: and providing an alarm that the IOT system is intruded in response to the atomic data not being verified.

According to one example implementation of the present disclosure, the device is deployed at an internet of things device manager.

Fig. 10 schematically illustrates a block diagram of an apparatus 1000 for backing up data in the internet of things according to an exemplary implementation of the present disclosure. As shown, device 1000 includes a Central Processing Unit (CPU)1001 that can perform various appropriate actions and processes according to computer program instructions stored in a Read Only Memory (ROM)1002 or computer program instructions loaded from a storage unit 1008 into a Random Access Memory (RAM) 1003. In the RAM1003, various programs and data necessary for the operation of the device 1000 can also be stored. The CPU 1001, ROM 1002, and RAM1003 are connected to each other via a bus 1004. An input/output (I/O) interface 1005 is also connected to bus 1004.

A number of components in device 1000 are connected to I/O interface 1005, including: an input unit 1006 such as a keyboard, a mouse, and the like; an output unit 1007 such as various types of displays, speakers, and the like; a storage unit 1008 such as a magnetic disk, optical disk, or the like; and a communication unit 1009 such as a network card, a modem, a wireless communication transceiver, or the like. The communication unit 1009 allows the device 1000 to exchange information/data with other devices through a computer network such as the internet and/or various telecommunication networks.

Various processes and processes described above, such as method 300, may be performed by processing unit 1001. For example, in some implementations, the method 300 may be implemented as a computer software program tangibly embodied in a machine-readable medium, such as the storage unit 1008. In some implementations, part or all of the computer program can be loaded and/or installed onto device 1000 via ROM 1002 and/or communications unit 1009. When the computer program is loaded into RAM1003 and executed by CPU 1001, one or more steps of method 300 described above may be performed. Alternatively, in other implementations, the CPU 1001 may also be configured in any other suitable manner to implement the processes/methods described above.

According to an exemplary implementation of the present disclosure, there is provided a computer program product, tangibly stored on a non-transitory computer-readable medium and comprising machine executable instructions for performing a method according to the present disclosure.

According to an exemplary implementation of the present disclosure, a computer-readable medium is provided. The computer-readable medium has stored thereon machine-executable instructions that, when executed by at least one processor, cause the at least one processor to implement a method according to the present disclosure.

The present disclosure may be methods, apparatus, systems, and/or computer program products. The computer program product may include a computer-readable storage medium having computer-readable program instructions embodied thereon for carrying out various aspects of the present disclosure.

The computer readable storage medium may be a tangible device that can hold and store the instructions for use by the instruction execution device. The computer readable storage medium may be, for example, but not limited to, an electronic memory device, a magnetic memory device, an optical memory device, an electromagnetic memory device, a semiconductor memory device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a Static Random Access Memory (SRAM), a portable compact disc read-only memory (CD-ROM), a Digital Versatile Disc (DVD), a memory stick, a floppy disk, a mechanical coding device, such as punch cards or in-groove projection structures having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media as used herein is not to be interpreted as a transitory signal per se, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (e.g., optical pulses through a fiber optic cable), or an electrical signal transmitted through an electrical wire.

The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing/processing device, or to an external computer or external storage device over a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. The network adapter card or network interface in each computing/processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium in the respective computing/processing device.

The computer program instructions for carrying out operations of the present disclosure may be assembler instructions, Instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider). In some implementations, aspects of the present disclosure are implemented by personalizing an electronic circuit, such as a programmable logic circuit, a Field Programmable Gate Array (FPGA), or a Programmable Logic Array (PLA), with state information of computer-readable program instructions, which can execute the computer-readable program instructions.

Various aspects of the present disclosure are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products implemented in accordance with the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.

These computer-readable program instructions may be provided to a processing unit of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processing unit of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable medium storing the instructions comprises an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various implementations of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

The foregoing has described implementations of the present disclosure, and the above description is illustrative, not exhaustive, and not limited to the implementations disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The terminology used herein was chosen in order to best explain the principles of implementations, the practical application, or improvements to the technology in the marketplace, or to enable others of ordinary skill in the art to understand the implementations disclosed herein.

Claims

1. A method for backing up data in an internet of things system, the internet of things system including an internet of things manager and a plurality of internet of things devices, the method comprising:

receiving a signature public key from the IOT device in response to receiving a registration request to register the IOT device of the plurality of IOT devices with the IOT manager;

receiving atomic data associated with the Internet of things device, the atomic data comprising a signature generated using a signature private key corresponding to the signature public key;

verifying the signature based on the signature public key; and

in response to the signature being verified, generating a backup data package for backup based on the atomic data.

2. The method of claim 1, wherein the method further comprises:

generating an encrypted public key and an encrypted private key; and

and sending the encrypted public key to the Internet of things equipment.

3. The method of claim 2, wherein the atomic data further comprises encrypted data obtained by encrypting raw data from the internet of things device with the encrypted public key.

4. The method of claim 3, wherein the encrypted data is generated by the Internet of things device, and the atomic data further comprises an identifier of the Internet of things device and a timestamp corresponding to the original data.

5. The method of claim 1, wherein receiving the atomic data comprises at least any one of:

receiving the atomic data from the Internet of things device in response to determining that the Internet of things device manager is connected with the Internet of things device; and

in response to determining that the Internet of things device manager is disconnected from the Internet of things device, receiving the atomic data via another Internet of things device connected with the Internet of things device.

6. The method of claim 2, further comprising: in response to determining that a predetermined backup condition is satisfied, storing the backup data package to a backup device associated with the internet of things system.

7. The method of claim 6, further comprising: in response to receiving a retrieval request to retrieve data associated with the internet of things device,

retrieving backup data associated with the retrieval request from the backup device;

decrypting the backup data based on the encryption private key to generate decrypted data; and

and sending the decryption data to the Internet of things equipment, wherein the decryption data is used for recovering the configuration information of the Internet of things equipment.

8. The method of claim 7, wherein receiving the retrieval request comprises at least any one of:

receiving the retrieval request from the Internet of things device in response to determining that the Internet of things device manager is connected with the Internet of things device; and

in response to determining that the internet of things device manager is not connected with the internet of things device, receiving the retrieval request via another internet of things device connected with the internet of things device.

9. The method of claim 1, further comprising: providing an alert that the system of things is being intruded in response to the atomic data not being verified.

10. The method of claim 1, wherein the method is performed at the internet of things device manager.

11. An electronic device, comprising:

at least one processor;

a volatile memory; and

a memory coupled with the at least one processor, the memory having instructions stored therein that when executed by the at least one processor cause the device to perform a method for backing up data in an internet of things system, the internet of things system including an internet of things manager and a plurality of internet of things devices, the method comprising:

verifying the signature based on the signature public key; and

12. The apparatus of claim 11, wherein the method further comprises:

generating an encrypted public key and an encrypted private key; and

and sending the encrypted public key to the Internet of things equipment.

13. The device of claim 12, wherein the atomic data further comprises encrypted data obtained by encrypting raw data from the internet of things device with the encrypted public key.

14. The device of claim 13, wherein the encrypted data is generated by the internet of things device, and the atomic data further comprises an identifier of the internet of things device and a timestamp corresponding to the original data.

15. The apparatus of claim 11, wherein receiving the atomic data comprises at least any one of:

in response to determining that the Internet of things device manager is not connected with the Internet of things device, receiving the atomic data via another Internet of things device connected with the Internet of things device.

16. The apparatus of claim 12, wherein the method further comprises: in response to determining that a predetermined backup condition is satisfied, storing the backup data package to a backup device associated with the internet of things system.

17. The apparatus of claim 16, wherein the method further comprises: in response to receiving a retrieval request to retrieve data associated with the internet of things device,

18. The apparatus of claim 17, wherein receiving the retrieval request comprises at least any one of:

19. The apparatus of claim 11, wherein the method further comprises: providing an alert that the Internet of things system is compromised in response to the atomic data not being verified, and wherein the device is deployed at the Internet of things device manager.

20. A computer program product tangibly stored on a non-transitory computer-readable medium and comprising machine executable instructions for performing the method of any one of claims 1 to 10.