An Internet of Things device identity information generation method, device, and electronic device

Abstract

The embodiments of this specification disclose a method, apparatus, and electronic device for generating identity information of Internet of Things devices. In this method, the location information of the Internet of Things terminal is obtained, and the initial device identity information of the Internet of Things terminal is determined based on the obtained location information of the Internet of Things terminal. Then, the terminal hardware identification information and the initial device identity information of the Internet of Things terminal are sent to the Internet of Things server, so that the Internet of Things server determines whether there is device identity information identical to the initial device identity information in the pre-stored device identity information set. After that, a feedback message about the identical device identity information is received from the Internet of Things server, and when the feedback message includes a discrimination code for distinguishing different terminal hardware identification information corresponding to the identical device identity information, the device identity information of the Internet of Things terminal is determined based on the discrimination code and the initial device identity information, and a device ID irrelevant to the service can be generated without production line programming.

Description

Technical Field

[0001] The embodiments of this specification relate to the field of computer technologies, and in particular, to a method, an apparatus, and an electronic device for generating identity information of Internet of Things (IoT) devices. Background Art

[0002] In recent years, with the rapid development of the Internet of Things (IoT) technology, the types of objects in the IoT have become increasingly rich, and the number of application systems or platforms of the IoT has also been growing rapidly.

[0003] IoT devices (or IoT terminals) are all configured with corresponding device IDs (Identities). This unique identification ID can be used to identify this device. Currently, IoT device IDs are generally pre-programmed by allocating or planning SNs by the IoT service platform, and IoT device IDs are often related to the services or platforms of IoT devices and cannot be used interchangeably in different services or platforms. Summary of the Invention

[0004] In view of this, the embodiments of this specification provide a method, an apparatus, and an electronic device for generating identity information of IoT devices, which are used to at least solve the problems in the related art that the IoT device ID is assigned by the platform and programmed into the device, resulting in the complication of the production line, and the IoT device ID is closely related to the platform and cannot be used interchangeably in different platforms.

[0005] The embodiments of this specification adopt the following technical solutions:

[0006] The embodiments of this specification provide a method for generating identity information of IoT devices, which is executed by an IoT terminal. The method includes: obtaining the location information of the IoT terminal; determining the initial device identity information of the IoT terminal based on the obtained location information of the IoT terminal; sending the terminal hardware identification information and the initial device identity information of the IoT terminal to an IoT server, so that the IoT server determines whether there is device identity information identical to the initial device identity information in a pre-stored set of device identity information, where the set of device identity information includes multiple terminal hardware identification information and corresponding device identity information; receiving a feedback message about the identical device identity information from the IoT server; when the feedback message includes a discrimination code for distinguishing different terminal hardware identification information corresponding to the identical device identity information, determining the device identity information of the IoT terminal based on the discrimination code and the initial device identity information.

[0007] An embodiment of this specification further provides a method for generating identity information of an Internet of Things device, which is executed by an Internet of Things server. The method includes: receiving and storing terminal hardware identification information and initial device identity information from an Internet of Things terminal, where the initial device identity information is determined by the Internet of Things terminal according to location information; determining whether there is device identity information identical to the initial device identity information in a pre-stored device identity information set, where the device identity information set includes multiple terminal hardware identification information and corresponding device identity information; when there is device identity information identical to the initial device identity information in the device identity information set, respectively configuring corresponding discrimination codes for each terminal hardware identification information corresponding to the identical device identity information and the initial device identity information, so as to determine the device identity information of the Internet of Things terminal according to the initial device identity information and the discrimination code; generating a feedback message according to the discrimination code, and sending the feedback message to the Internet of Things terminal.

[0008] An embodiment of this specification provides a device for generating identity information of an Internet of Things device, including: a location information acquisition unit, which acquires the location information of the Internet of Things terminal; an initial device identity determination unit, which determines the initial device identity information of the Internet of Things terminal based on the acquired location information of the Internet of Things terminal; an initial device identity sending unit, which sends the terminal hardware identification information and the initial device identity information of the Internet of Things terminal to an Internet of Things server, so that the Internet of Things server determines whether there is device identity information identical to the initial device identity information in a pre-stored device identity information set, where the device identity information set includes multiple terminal hardware identification information and corresponding device identity information; a feedback message receiving unit, which receives a feedback message about the identical device identity information from the Internet of Things server; a first device identity determination unit, which determines the device identity information of the Internet of Things terminal based on the discrimination code and the initial device identity information when the feedback message includes discrimination codes for distinguishing different terminal hardware identification information corresponding to the identical device identity information.

[0009] An embodiment of this specification also provides an Internet of Things device identity information generation device, including: an initial device identity receiving unit that receives and stores terminal hardware identification information and initial device identity information from an Internet of Things terminal, where the initial device identity information is determined by the Internet of Things terminal according to location information; a same device identity determination unit that determines whether there is device identity information identical to the initial device identity information in a pre-stored device identity information set, where the device identity information set includes multiple terminal hardware identification information and corresponding device identity information; a first device identity determination unit that, when there is device identity information identical to the initial device identity information in the device identity information set, configures corresponding differentiation codes for each terminal hardware identification information corresponding to the identical device identity information and the initial device identity information, so as to determine the device identity information of the Internet of Things terminal according to the initial device identity information and the differentiation codes; a first feedback message generation unit that generates a feedback message according to the differentiation codes; and a feedback message sending unit that sends the feedback message to the Internet of Things terminal.

[0010] The above at least one technical solution adopted in the embodiment of this specification can achieve the following beneficial effects:

[0011] The Internet of Things terminal determines the initial device identity information according to its own location information, and obtains a feedback message about the same device identity information through interaction with the Internet of Things server, and then determines the device identity information of the Internet of Things terminal. Thus, it is not necessary to burn the device ID for the Internet of Things terminal during the production stage, which can relieve the pressure on the production line and greatly reduce the management cost and the production and maintenance cost of customers. In addition, the device identity determined based on the location information is not easily repeated, and is confirmed through the feedback message of the server. When there is identical device identity information, it is distinguished by the differentiation code, which can ensure the uniqueness of the device ID of the determined Internet of Things server. In addition, the device identity information is mainly determined by the terminal rather than the platform, so that the device identity information is independent of the service or platform, and can be used commonly on multiple Internet of Things service platforms. Description of the Drawings

[0012] The drawings described herein are used to provide a further understanding of the embodiments of this specification, and constitute a part of this specification. The illustrative embodiments and descriptions of this specification are used to explain this specification, and do not constitute an improper limitation of this specification. In the drawings:

[0013] Figure 1 Shows a flowchart of an example of an Internet of Things device identity information generation method executed by an Internet of Things terminal according to an embodiment of this specification;

[0014] Figure 2The flowchart showing an example of determining the device identity information of an IoT terminal executed by the IoT terminal according to an embodiment of this specification;

[0015] Figure 3 The flowchart showing an example of the IoT device identity information generation method executed by the IoT terminal according to an embodiment of this specification;

[0016] Figure 4 The flowchart showing an example of the operation of updating the device ID executed by the IoT terminal according to an embodiment of this specification;

[0017] Figure 5 The flowchart showing an example of the IoT device identity information generation method executed by the IoT server according to an embodiment of this specification;

[0018] Figure 6 The flowchart showing an example of determining the device identity information of an IoT terminal executed by the IoT server according to an embodiment of this specification;

[0019] Figure 7 The signal interaction diagram showing an example of the IoT device identity information generation method according to an embodiment of this specification;

[0020] Figure 8 The structural block diagram showing an example of the IoT device identity information generation device according to an embodiment of this specification; and

[0021] Figure 9 The structural block diagram showing an example of the IoT device identity information generation device according to an embodiment of this specification. Detailed implementation manners

[0022] Currently, the device identity information (or device ID) of an IoT terminal can be uniformly generated and distributed by a network platform, which needs to be uniformly generated and distributed on the network platform side and burned into the corresponding hardware during production line operations. However, when the hardware is applied in different terminals (such as smart speakers, dragonfly face recognition devices, etc.), it may not meet the customer requirements and may affect or adjust the production line production. In addition, some IoT business platforms collect the hardware information of IoT terminals and generate device IDs accordingly. However, this will cause the device ID to be closely related to the platform business and cannot be pre-bound to the service before initialization; moreover, the communication times during the initialization process are relatively many and it takes a long time; in addition, the device ID is related to the hardware information, so that the dependence of the service ID will also change after some hardware information is changed.

[0023] Therefore, in the process of researching and developing an Internet of Things (IoT) system, device IDs are generally generated by collecting device information and project attributes. To meet the requirements of unified format and uniqueness, the generation points and distribution points of these methods rely on the network platform, which has certain requirements for the network platform. At the same time, a management system is required for identity distribution, and a burning operation is also required during the production process, resulting in defects such as non-universal business, high production and maintenance costs, etc.

[0024] To make the objectives, technical solutions, and advantages of this specification clearer, the technical solutions of this specification will be clearly and completely described below in conjunction with specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, rather than all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of implementation of this specification.

[0025] As used herein, the term "including" and its variants represent open terms, meaning "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" and "an embodiment" mean "at least one embodiment". The term "another embodiment" means "at least one other embodiment". The terms "first", "second", etc. may refer to different or the same objects. Other definitions may be included below, whether explicit or implicit. Unless clearly specified in the context, the definition of a term is consistent throughout the specification.

[0026] Figure 1 A flowchart showing an example of an IoT device identity information generation method executed by an IoT terminal according to an embodiment of this specification is shown.

[0027] As Figure 1 shown, in step 110, the location information of the IoT terminal is obtained. Here, the IoT terminal can use various positioning methods to obtain its own location information. Exemplarily, the location information (or raw information) can be obtained by collecting positioning methods such as satellite positioning systems (Beidou, GPS, GLONASS, and GALILEO, etc.), operator base station systems, WIFI environment information, Bluetooth environment information, other wireless communication location information, and IP information.

[0028] In step 120, based on the obtained location information of the IoT terminal, the initial device identity information of the IoT terminal is determined. Here, the initial device identity information can be determined according to the conversion rules preset at the terminal regarding the location information and the initial device identity information.

[0029] In step 130, the terminal hardware identification information and the initial device identity information of the Internet of Things terminal are sent to the Internet of Things server. Here, the Internet of Things server can determine whether there is device identity information identical to the initial device identity information in the pre-stored device identity information set, and the device identity information set includes multiple terminal hardware identification information and corresponding device identity information. It should be noted that the terminal hardware identification information can be the hardware component information of the terminal, or other serial numbers or IDs that can identify the terminal hardware and are burned into the hardware during the production process, such as IMEI, SN, BT MAC address, WIFI MAC address, etc.

[0030] In some examples of the embodiments of this specification, the Internet of Things server may need to collect the device identity information corresponding to each Internet of Things terminal (for example, one or more hardware information of the acquisition terminal) to create a device identity information set, and then provide corresponding services for each Internet of Things terminal. In some low-probability events, multiple (for example, two or more) device identity information determined based on location information may be repeated, such as multiple Internet of Things terminals with the same location information, and do not meet the standards or requirements for generating device IDs. Through step 130, the Internet of Things terminal can interact and confirm with the Internet of Things server, and can avoid the situation of duplicate device IDs.

[0031] In step 140, a feedback message regarding the same device identity information is received from the Internet of Things server, and the device identity information of the Internet of Things terminal is determined based on the feedback message and the initial device identity information.

[0032] In an example of the embodiments of this specification, when the feedback message includes denial information for the same device identity information, the initial device identity information can be determined as the device identity information of the Internet of Things terminal based on the denial information. In addition, when the feedback message includes confirmation information for the same device identity information, generating device identity information for the terminal can be rejected or the device ID generation method for the terminal can be adjusted, and more details will be elaborated below.

[0033] In the embodiments of this specification, the device ID is mainly generated by the Internet of Things terminal itself, and it is not necessary to completely hand over the generation work of the device ID to the service platform, which can achieve the universality of the device ID among multiple service platforms and has higher freedom. In addition, it is not necessary to burn the device ID for the device through the production line, which can reduce the production and maintenance costs of the device ID. Moreover, the generation of geographical location information has natural exclusivity, and the device identity determined based on location information is not easy to be repeated. And through the interaction process of the feedback message with the server, the uniqueness of the generated device ID can be effectively guaranteed, which can meet the generation standards and requirements of the device ID.

[0034] Regarding some embodiments of the above step 120, the Internet of Things (IoT) terminal may calculate the location information according to a preset algorithm (e.g., a hashing algorithm) to determine the initial device identity information. Further, in order to ensure that the determined initial device identity information has a high recognition degree and uniqueness, more factors may also be considered during the calculation and conversion process between the location and the initial device ID. In some examples of the embodiments of this specification, the signal strength corresponding to the location information may also be determined, and the location information and the signal strength may be calculated according to a set algorithm to determine the initial device identity information. In this way, even for devices at adjacent locations, the collected geographical information, signal strength, etc. are also different, and differences can be achieved for different IoT terminals in terms of the initial device identity information.

[0035] In some examples of the embodiments of this specification, the IoT terminal can be universal among multiple different platforms. Specifically, there may be a service configuration in the IoT terminal, and the service configuration includes the IoT servers of multiple IoT service platforms associated with the IoT terminal, e.g., the IoT servers of multiple IoT service platforms that can provide services for the IoT terminal. Furthermore, the IoT terminal can send the initial device identity information to the associated multiple IoT servers according to the preset service configuration. Thus, through the pre-configured services for the terminal, the device ID can be made universal among multiple IoT service platforms.

[0036] It should be understood that the services provided by the IoT server should be adapted to the capabilities of the IoT terminal device itself. For example, if the IoT terminal device itself does not have video capabilities, there is no IoT server corresponding to the video service in the corresponding service configuration. In addition, the initial device identity information can also be sent to the associated multiple IoT servers according to the capabilities of the device itself.

[0037] Figure 2 The figure shows a flowchart of an example of determining the device identity information of an IoT terminal executed by the IoT terminal according to the embodiments of this specification.

[0038] As Figure 2 shown, in step 210, it is parsed whether the feedback message includes denial information or a discrimination code.

[0039] If the feedback message includes denial information for the same device identity information, it jumps to step 221. If the feedback message includes a discrimination code for distinguishing different terminal hardware identification information corresponding to the same device identity information, it jumps to step 223.

[0040] It should be noted that the discrimination code can be information used to distinguish the terminal hardware identification information of the same device identity information, and it can have various forms. For example, numbers can be used to distinguish different terminal hardware identification information.

[0041] In step 221, based on the denial information, the initial device identity information is determined as the device identity information of the IoT terminal.

[0042] In step 223, based on the discrimination code and the initial device identity information, the device identity information of the IoT terminal is determined. Exemplarily, the discrimination code and the initial device identity information can be used together as the device identity information of the IoT terminal. Correspondingly, the server can also use the discrimination code and the initial device identity information together as the device identity information of the IoT terminal. Alternatively, the IoT terminal and the server can also calculate or convert the discrimination code and the initial device identity information based on a predefined rule to obtain the device identity information of the IoT terminal.

[0043] In the embodiments of this specification, by using the discrimination code configured by the server to distinguish IoT terminals with the same device identity information (or, initial device identity information), the uniqueness of the generated IoT terminal identifier can be guaranteed.

[0044] Figure 3 The flowchart shows an example of the IoT device identity information generation method executed by the IoT terminal according to the embodiments of this specification.

[0045] In step 310, the location information of the IoT terminal is obtained.

[0046] In step 320, based on the obtained location information of the IoT terminal, the initial device identity information of the IoT terminal is determined.

[0047] In step 330, the terminal hardware identification information and the initial device identity information of the IoT terminal are sent to the IoT server.

[0048] In step 340, a feedback message regarding the same device identity information is received from the IoT server, and the device identity information of the IoT terminal is determined based on the feedback message and the initial device identity information.

[0049] Regarding the operations in steps 310 to 340 above, reference can be made to the descriptions of steps 110 to 140 in Figure 1 above.

[0050] In step 350, it is detected whether the working mode of the IoT terminal is in the test mode or the stealth usage mode. Here, the IoT terminal can have multiple working modes (for example, test mode, stealth usage mode, and normal operation mode, etc.).

[0051] If the detection result in step 350 indicates that the working mode is in the test mode or the traceless usage mode, jump to step 361. If the detection result in step 350 indicates that the working mode is not in the test mode or the traceless usage mode, jump to step 363.

[0052] In step 361, clear the device identity information of the determined Internet of Things (IoT) terminal. Here, it is allowed to detect the reliability of the device ID generation function of the IoT terminal in the test mode without affecting the normal device ID generation operation of the IoT terminal in the later stage. In addition, in the traceless usage mode, the IoT terminal can achieve a difficult-to-trace and high-security terminal usage process by changing the device ID.

[0053] Correspondingly, the device ID of the IoT terminal in the IoT server also needs to be modified. In an example of the embodiment of the present specification, the IoT terminal can send a clear notification to the IoT server so that the IoT server clears the terminal device identification information and the device ID corresponding to the terminal. In another example of the embodiment of the present specification, the IoT server does not need to receive the clear notification, and when receiving a new device ID for the terminal device identification information subsequently, it can perform an update operation using the new device ID.

[0054] In step 363, end the operation of generating the IoT device identity information.

[0055] In some application scenarios, the IoT terminal may change its location during use. In an example of the embodiment of the present specification for this situation, it can be that the device ID process for the IoT terminal is completed during the first configuration process when the IoT terminal is normally started, and when the location changes subsequently, the device ID is not changed.

[0056] Figure 4 Shows a flowchart of an example for an IoT terminal to determine the initial device identity information according to an embodiment of the present specification.

[0057] In step 410, detect whether there is device identity information in the IoT terminal.

[0058] If the detection result in step 410 indicates that there is no device identity information, jump to step 421. If the detection result in step 410 indicates that there is device identity information, jump to step 423.

[0059] In step 421, trigger the determination of the initial device identity information of the IoT terminal based on the obtained location information of the IoT terminal.

[0060] In step 423, end the operation.

[0061] In the embodiments of this specification, the IoT terminal can independently detect the existence of device identity information and trigger the generation of a device ID only when the identity information does not exist. For example, the device ID is generated only during the first configuration process when the IoT terminal is normally started, and will not be updated as the position of the IoT terminal changes subsequently.

[0062] In another example of the embodiments of this specification, when the IoT terminal changes its position, the device ID of the IoT terminal will also change accordingly.

[0063] Specifically, the position information of the IoT terminal is re-obtained. Here, the operation of re-obtaining the position information can be triggered by the power-on operation or manual control operation of the IoT terminal. Additionally, the position information of the IoT terminal can also be obtained periodically.

[0064] Next, when it is found that the position information has changed, the device identity information of the IoT terminal is updated based on the re-obtained position information. Specifically, the device identity information can be generated based on the re-obtained position information, and then the original device identity information of the IoT terminal is updated. Correspondingly, the device identity information of the IoT terminal in the IoT server can also be updated accordingly.

[0065] Furthermore, the IoT terminal may be served by multiple IoT servers simultaneously. To ensure the continuity of services after the device ID changes, when the device ID is generated, the IoT terminal receives authorization tokens assigned by each IoT server respectively, and the continuity of services is ensured through these authorization tokens.

[0066] In the embodiments of this specification, when the position of the IoT terminal changes, the IoT terminal can update the device identity information of the IoT terminal based on the re-obtained position information, and the device ID is not bound to the device hardware and has strong flexibility.

[0067] Figure 5 Shows a flowchart of an example of a method for generating IoT device identity information executed by an IoT server according to the embodiments of this specification.

[0068] In step 510, the terminal hardware identification information and the initial device identity information are received from the IoT terminal and stored. Here, the initial device identity information is determined by the IoT terminal according to the position information. For more details, reference can be made to the details described in other relevant parts above, and will not be elaborated here.

[0069] In step 520, it is determined whether there is device identity information identical to the initial device identity information in the pre-stored device identity information set. Here, the device identity information set includes multiple terminal hardware identification information and corresponding device identity information.

[0070] In step 530, a feedback message is generated according to the judgment result and sent to the IoT terminal.

[0071] In step 540, the device identity information of the IoT terminal is determined based on the feedback message and the initial device identity information.

[0072] In the embodiments of this specification, determining the initial device ID based on the IoT terminal and verifying whether there is duplicate device identity information by the server based on the device identity information set can ensure the uniqueness of the device IDs of each IoT terminal.

[0073] Figure 6 The flowchart shows an example of determining the device identity information of an IoT terminal executed by an IoT server according to the embodiments of this specification.

[0074] As Figure 6 shown, in step 610, it is determined whether there is device identity information identical to the initial device identity information in the device identity information set.

[0075] If the judgment result in step 610 indicates that there is no device identity information identical to the initial device identity information in the device identity information set, then jump to step 621. If the judgment result in step 610 indicates that there is device identity information identical to the initial device identity information in the device identity information set, then jump to step 623.

[0076] In step 621, a feedback message is generated according to the denial information for the same device identity information.

[0077] Then, in step 631, the feedback message is sent to the IoT terminal.

[0078] Then, in step 641, the initial device identity information is determined as the device identity information of the IoT terminal based on the denial information.

[0079] In addition, in step 623, corresponding discrimination codes are respectively configured for each terminal hardware identification information corresponding to the same device identity information and the initial device identity information.

[0080] Then, in step 633, a feedback message is generated according to the discrimination code.

[0081] Then, in step 643, the feedback message is sent to the IoT terminal.

[0082] Next, in step 650, the device identity information of the IoT terminal is determined according to the initial device identity information and the discrimination code.

[0083] In the embodiments of the present specification, when the same device identity information is caused by factors such as overlapping location information, the final device identity information can be generated through the discrimination code used to distinguish different IoT terminals, ensuring the uniqueness of the device ID.

[0084] It should be noted that in some examples of the embodiments of the present specification, the IoT terminal can be common among multiple different platforms, or the IoT terminal can be served by multiple IoT servers. In this case, the same device identity information problem may also be caused by factors such as overlapping location information. In some examples of the embodiments of the present specification, each IoT server can respectively configure different discrimination codes for the IoT terminal based on its own discrimination code generation mechanism, so that the IoT terminal can use the corresponding discrimination code to communicate with the corresponding IoT server.

[0085] In some application scenarios, the device ID of the IoT terminal will be updated as the location changes. To ensure the continuity of the service, when the IoT server generates the device ID, an authorization token can be sent to the corresponding IoT terminal. In this way, even if the device ID of the IoT terminal changes, the continuity of the service can be ensured based on the authorization token.

[0086] Figure 7 Fig. shows a signal interaction diagram of an example of the method for generating IoT device identity information according to the embodiments of the present specification.

[0087] As Figure 7 shown, in step 701, the IoT terminal 710 obtains location information.

[0088] In step 703, the IoT terminal 710 determines the initial device identity information of the IoT terminal based on the obtained location information of the IoT terminal. Here, the location information is used as the input to generate the device ID, and the algorithm setting is relatively flexible and can be unrestricted. However, to avoid duplication, it is recommended to perform a hashing operation on the location information.

[0089] In some embodiments, the IoT terminal 710 can also detect whether there is already a device ID locally, and only trigger the subsequent device ID generation operation when there is no device ID locally at the terminal.

[0090] In step 705, the IoT terminal 710 sends the terminal hardware identification information and the initial device original information to the IoT server 720.

[0091] In step 707, the IoT server 720 determines whether there is device identity information identical to the initial device identity information in the pre-stored device identity information set. Exemplarily, if the server discovers, based on records, that there are terminal devices with the same device ID but different hardware information, corresponding discrimination codes (or, duplicate numbers) can be given for each piece of hardware information, and thus the duplicate numbers are fed back according to the hardware information.

[0092] In step 709, the IoT server 720 generates a feedback message according to the judged result. In some examples, the feedback message may include the result of the terminal's registration on the platform and the corresponding discrimination code.

[0093] In step 711, the IoT server 720 sends the feedback message to the IoT terminal 710.

[0094] In step 715, the IoT terminal 710 determines the device ID according to the feedback message and the initial device identity information. And

[0095] In step 717, the IoT server 720 determines the device ID according to the feedback message and the initial device identity information.

[0096] In some examples of the embodiments of this specification, the initial device identity information and the discrimination code can be used together as the device ID.

[0097] In step 719, the IoT terminal 710 detects whether the working mode is in the test mode or the stealth usage mode. Here, when it is detected that the working mode is in the test mode or the stealth usage mode, it jumps to step 721.

[0098] In step 721, the IoT terminal 710 clears the device identity information of the determined IoT terminal.

[0099] In step 723, the IoT terminal 710 sends a device ID clearing notification to the IoT server 720.

[0100] In step 725, the IoT server 720 clears the terminal hardware identification information and the corresponding device ID corresponding to the IoT terminal 710. Thus, the IoT terminal supports the test behavior in the test mode, so that the test mode does not affect the subsequent normal device ID generation.

[0101] In the embodiments of this specification, the device ID is mainly determined based on the Internet of Things (IoT) terminal. Compared with the generation scheme on the pure server side, there is no need to burn special information, and there is no need to change the production line process. Moreover, the device ID itself has nothing to do with the service attributes. In addition, the local generation algorithm of the device ID can, with a very high probability, avoid duplication. Therefore, very little or even no information about the hardware needs to be collected. At the same time, since the device ID has nothing to do with the service, the device ID can be registered without the need for the platform to associate with the service. In addition, since the data communication process between the terminal and the server is simple (for example, only one data upload and download is required), the registration process is simple and fast.

[0102] It should be understood that in the embodiments of this specification, the process of removing duplicates for the hardware information is only used with a relatively low probability. Therefore, the situation caused by the change of the hardware while the position of the terminal device remains unchanged can be ignored.

[0103] Figure 8 Fig. shows a structural block diagram of an example of an IoT device identity information generation device according to an embodiment of this specification.

[0104] As Figure 8 shown, the IoT device identity information generation device 800 includes a location information acquisition unit 810, an initial device identity determination unit 820, an initial device identity sending unit 830, a feedback message receiving unit 840, a first device identity determination unit 850, a second device identity determination unit 860, a signal strength determination unit 870, a mode detection unit 880, a device identity clearing unit 890, and a device identity detection unit 8100.

[0105] The location information acquisition unit 810 is configured to acquire the location information of the IoT terminal. For more details about the location information acquisition unit 810, reference can be made to the operations described in reference step 110 above. Figure 1 in.

[0106] The initial device identity determination unit 820 is configured to determine the initial device identity information of the IoT terminal based on the acquired location information of the IoT terminal. For more details about the initial device identity determination unit 820, reference can be made to the operations described in reference step 120 above. Figure 1 in.

[0107] The initial device identity sending unit 830 is configured to send the terminal hardware identification information and the initial device identity information of the IoT terminal to the IoT server, so that the IoT server determines whether there is device identity information identical to the initial device identity information in the pre-stored device identity information set, and the device identity information set includes multiple terminal hardware identification information and corresponding device identity information. For more details about the initial device identity sending unit 830, reference can be made to the operations described in reference above. Figure 1Refer to the operation described in step 130 in the reference above.

[0108] In an example of an embodiment of this specification, the initial device identity sending unit 830 sends the initial device identity information to the IoT service ends of multiple associated IoT service platforms according to a preset service configuration, where the service configuration includes the IoT service ends of multiple IoT service platforms associated with the IoT terminal.

[0109] The feedback message receiving unit 840 is configured to receive a feedback message about the same device identity information from the IoT service end. For more details about the feedback message receiving unit 840, refer to the operation described in step 140 in the reference above. Figure 1 Refer to the operation described in step 140 in the reference above.

[0110] The first device identity determining unit 850 is configured to, when the feedback message includes a discrimination code for differentiating different terminal hardware identification information corresponding to the same device identity information, determine the device identity information of the IoT terminal based on the discrimination code and the initial device identity information. For more details about the device identity determining unit 850, refer to the operation described in step 223 in the reference above. Figure 2 Refer to the operation described in step 223 in the reference above.

[0111] The second device identity determining unit 860 is configured to, when the feedback message includes a denial message for the same device identity information, determine the initial device identity information as the device identity information of the IoT terminal based on the denial message. For more details about the second device identity determining unit 860, refer to the operation described in step 221 in the reference above. Figure 2 Refer to the operation described in step 221 in the reference above.

[0112] In some embodiments, the initial device identity determining unit 830 includes: an algorithm module (not shown), configured to calculate the position information according to a preset algorithm to determine the initial device identity information.

[0113] The signal strength determining unit 870 is configured to determine the signal strength corresponding to the position information. Accordingly, the algorithm module is further configured to calculate the position information and the signal strength according to a set algorithm to determine the initial device identity information.

[0114] The mode detecting unit 880 is configured to detect whether the working mode of the IoT terminal is in a test mode or a stealth usage mode. For more details about the mode detecting unit 880, refer to the operation described in step 350 in the reference above. Figure 3 Refer to the operation described in step 350 in the reference above.

[0115] The device identity clearing unit 890 is configured to clear the determined device identity information of the Internet of Things terminal when it is detected that the Internet of Things terminal is in the test mode or the trace-free usage mode. For more details about the device identity clearing unit 890, reference can be made to the operation described in reference step 361 above Figure 3 as described in the reference step 361 above.

[0116] The device identity detection unit 8100 is configured to detect whether there is device identity information in the Internet of Things terminal. Accordingly, the initial device identity determination unit 820 is configured to trigger the determination of the initial device identity information of the Internet of Things terminal based on the acquired location information of the Internet of Things terminal when the detection result indicates that there is no such device identity information in the Internet of Things terminal. For more details about the device identity detection unit 8100, reference can be made to the operation described in reference step 410 above Figure 4 as described in the reference step 410 above.

[0117] It should be noted that some units in the device 800 described above are non-essential or optional in some application scenarios. For example, the signal strength determination unit 870, the mode detection unit 880, the device identity clearing unit 890, and the device identity detection unit 8100 may not be retained in some examples.

[0118] Figure 9 Fig. shows a structural block diagram of an example of an Internet of Things device identity information generation device according to an embodiment of the present specification.

[0119] As Figure 9 shown, the Internet of Things device identity information generation device 900 includes an initial device identity receiving unit 910, an identical device identity judging unit 920, a first feedback message generating unit 930, a second feedback message generating unit 940, a feedback message sending unit 950, a first device identity determination unit 960, and a second device identity determination unit 970.

[0120] The initial device identity receiving unit 910 is configured to receive and store the terminal hardware identification information and the initial device identity information from the Internet of Things terminal, and the initial device identity information is determined by the Internet of Things terminal according to the location information. For more details about the initial device identity receiving unit 910, reference can be made to the operation described in reference step 510 above Figure 5 as described in the reference step 510 above.

[0121] The identical device identity judging unit 920 is configured to judge whether there is device identity information identical to the initial device identity information in the pre-stored device identity information set, and the device identity information set includes a plurality of terminal hardware identification information and corresponding device identity information. For more details about the identical device identity judging unit 920, reference can be made to the operation described in reference step 510 above Figure 5Refer to the operation described in step 520 in the above.

[0122] The first device identity determination unit 930 is configured to, when there is device identity information identical to the initial device identity information in the device identity information set, respectively configure corresponding discrimination codes for each terminal hardware identification information corresponding to the identical device identity information and the initial device identity information, so as to determine the device identity information of the Internet of Things terminal according to the initial device identity information and the discrimination codes. For more details about the first device identity determination unit 930, reference can be made to the above Figure 6 Refer to the operation described in step 650 in the above.

[0123] The first feedback message generation unit 940 is configured to generate a feedback message according to the discrimination code. For more details about the first feedback message generation unit 940, reference can be made to the above Figure 6 Refer to the operations described in steps 623 and 633 in the above.

[0124] The feedback message sending unit 950 is configured to send the feedback message to the Internet of Things terminal. For more details about the feedback message sending unit 950, reference can be made to the above Figure 6 Refer to the operations described in steps 623 and 633 in the above. For more details about the feedback message sending unit 950, reference can be made to the above Figure 6 Refer to the operations described in step 631 and step 643 in the above.

[0125] The second device identity determination unit 960 is configured to, when there is no device identity information identical to the initial device identity information in the device identity information set, based on the denial information for the identical device identity information, determine the initial device identity information as the device identity information of the Internet of Things terminal. For more details about the second device identity determination unit 960, reference can be made to the above Figure 6 Refer to the operation described in step 641 in the above.

[0126] The second feedback message generation unit 970 is configured to generate the feedback message according to the denial information. For more details about the second feedback message generation unit 970, reference can be made to the above Figure 6 Refer to the operation described in step 621 in the above.

[0127] As referred to above Figures 1 to 9 The embodiments of the method and apparatus for generating Internet of Things device identity information according to the embodiments of the present specification have been described. The details mentioned in the above description of the method embodiments also apply to the embodiments of the apparatus in the present specification. The above Internet of Things device identity information generation apparatus can be implemented by hardware, or can be implemented by software or a combination of hardware and software.

[0128] In the 1990s, it was quite obvious to distinguish whether an improvement to a technology was an improvement in hardware (e.g., improvement to circuit structures such as diodes, transistors, switches, etc.) or an improvement in software (improvement to method flows). However, with the development of technology, many improvements to method flows today can be regarded as direct improvements to hardware circuit structures. Almost all designers obtain the corresponding hardware circuit structures by programming the improved method flows into the hardware circuits. Therefore, it cannot be said that an improvement to a method flow cannot be implemented with a hardware entity module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. The designer can program by himself to "integrate" a digital system on a PLD without having to ask a chip manufacturer to design and fabricate a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing. The original code before compilation also has to be written in a specific programming language, which is called a Hardware Description Language (HDL). There is not only one type of HDL, but many types, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones currently are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also be aware that as long as the method flow is slightly logically programmed with the above-mentioned several hardware description languages and programmed into the integrated circuit, it is easy to obtain the hardware circuit that implements the logical method flow.

[0129] The controller can be implemented in any suitable manner. For example, the controller can take the form of, for example, a microprocessor or a processor and a computer-readable medium storing computer-readable program code (such as software or firmware) executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller. Examples of the controller include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320. The memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that in addition to implementing the controller in the form of pure computer-readable program code, it is entirely possible to implement the same function by logically programming the method steps so that the controller takes the form of logic gates, switches, application specific integrated circuits, programmable logic controllers, embedded microcontrollers, etc. Therefore, such a controller can be considered a hardware component, and the devices included therein for implementing various functions can also be regarded as the structures within the hardware component. Or even, the devices for implementing various functions can be regarded as either software modules for implementing the method or structures within the hardware component.

[0130] The systems, devices, modules, or units illustrated in the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0131] For the convenience of description, when describing the above devices, they are described separately as various units according to their functions. Of course, when implementing this specification, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0132] Those skilled in the art should understand that the embodiments of this specification can be provided as a method, a system, or a computer program product. Therefore, this specification can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the embodiments of this specification can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk memory, CD-ROM, optical memory, etc.) containing computer-usable program code.

[0133] This specification is described with reference to the flowcharts and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the specification. It should be understood that each flow and / or block in the flowchart and / or block diagram, and combinations of flows and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to the processors of general purpose computers, special purpose computers, embedded processors, or other programmable data processing devices to produce a machine, such that the instructions executed by the processors of the computer or other programmable data processing devices generate means for implementing the functions specified in the flow Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in a block or multiple blocks.

[0134] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, such that the instructions stored in the computer-readable memory produce a manufacture including instruction means that implement the functions specified in the flow Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in a block or multiple blocks.

[0135] These computer program instructions can also be loaded onto a computer or other programmable data processing device, such that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in the flow Figure 1 one or more flows and / or blocks Figure 1 or means for implementing the functions specified in a block or multiple blocks.

[0136] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and memory.

[0137] The memory may include non-permanent memory in the form of computer-readable media, random access memory (RAM), and / or non-volatile memory such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of computer-readable media.

[0138] A computer-readable medium includes both permanent and non-permanent, removable and non-removable media and can implement information storage by any method or technology. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to store information accessible by a computing device. As defined herein, a computer-readable medium does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0139] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising a..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises the element.

[0140] Embodiments of this specification can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types. This specification can also be practiced in a distributed computing environment where tasks are performed by remote processing devices connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media including storage devices.

[0141] Each embodiment in this specification is described in a progressive manner. For the same or similar parts among the embodiments, reference can be made to each other. Each embodiment focuses on the differences from other embodiments. In particular, for system embodiments, since they are basically similar to method embodiments, the description is relatively simple, and reference can be made to the relevant parts of the method embodiments for the related content.

[0142] The above are only embodiments of this specification and are not intended to limit this specification. For those skilled in the art, various modifications and changes can be made to this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this application shall be included within the scope of the claims of this application.

Claims

1. A method for generating identity information of an Internet of Things device, which is executed by an Internet of Things terminal. The method includes: Determining initial device identity information of the Internet of Things terminal based on the location information of the Internet of Things terminal; Sending the terminal hardware identification information and the initial device identity information of the Internet of Things terminal to an Internet of Things server, so that the Internet of Things server feeds back a feedback message indicating whether there is device identity information identical to the initial device identity information to the Internet of Things terminal; If the feedback message indicates that there is device identity information identical to the initial device identity information, generating the device identity information of the Internet of Things terminal based on a discrimination code and the initial device identity information; wherein, the discrimination code is used to distinguish different terminal hardware identification information corresponding to the identical device identity information.

2. The method for generating identity information of an Internet of Things device according to claim 1, wherein if the feedback message indicates that there is device identity information identical to the initial device identity information, determining the device identity information of the Internet of Things terminal based on a discrimination code and the initial device identity information specifically includes: Determining the device identity information of the Internet of Things terminal based on the discrimination code and the initial device identity information included in the feedback message.

3. The method for generating identity information of an Internet of Things device according to claim 1, if the feedback message indicates that there is no device identity information identical to the initial device identity information, determining the initial device identity information as the device identity information of the Internet of Things terminal.

4. The method for generating identity information of an Internet of Things device according to claim 3, wherein if the feedback message indicates that there is no device identity information identical to the initial device identity information, determining the initial device identity information as the device identity information of the Internet of Things terminal specifically includes: When the feedback message includes denial information for the identical device identity information, Based on the denial information, determining the initial device identity information as the device identity information of the Internet of Things terminal.

5. The method for generating identity information of an Internet of Things device according to claim 1, wherein: Determining initial device identity information of the Internet of Things terminal based on the location information of the Internet of Things terminal specifically includes: Calculating the location information according to a preset algorithm to determine the initial device identity information.

6. The method for generating identity information of an Internet of Things device according to claim 5 further includes: Determining the signal strength corresponding to the location information; Wherein, calculating the location information according to a set algorithm to determine the initial device identity information specifically includes: Calculating the location information and the signal strength according to a set algorithm to determine the initial device identity information.

7. The method for generating identity information of an Internet of Things device according to claim 1 further includes: Detecting whether the working mode of the Internet of Things terminal is in a test mode or a stealth usage mode; When it is detected that the Internet of Things terminal is in a test mode or a stealth usage mode, clearing the determined device identity information of the Internet of Things terminal.

8. The method for generating identity information of an Internet of Things device according to claim 1 further includes: Detecting whether device identity information exists in the IoT terminal; The step of determining the initial device identity information of the IoT terminal based on the location information of the IoT terminal specifically includes: When the detection result indicates that the device identity information does not exist in the Internet of Things terminal, it is triggered to determine the initial device identity information of the Internet of Things terminal based on the acquired location information of the Internet of Things terminal.

9. The method for generating the identity information of the Internet of Things device according to any one of claims 1-8, wherein, Sending the initial device identity information to the IoT server includes: According to a preset business configuration, the initial device identity information is sent to the Internet of Things service ends of multiple associated Internet of Things business platforms, and the business configuration includes the Internet of Things service ends of multiple Internet of Things business platforms associated with the Internet of Things terminal.

10. A method for generating identity information of an IoT device, executed by an IoT server, the method comprising: Acquire terminal hardware identification information of an Internet of Things terminal and initial device identity information of the Internet of Things terminal; wherein the initial device identity information is determined by the Internet of Things terminal based on location information; Determine whether there is device identity information that is the same as the initial device identity information, and obtain a determination result; When the judgment result indicates that there is device identity information that is identical to the initial device identity information, corresponding distinction codes are configured for each terminal hardware identification information corresponding to the identical device identity information and the initial device identity information, and the judgment result and the distinction code are sent to the Internet of Things terminal, so that the Internet of Things terminal can determine the device identity information of the Internet of Things terminal based on the initial device identity information and the distinction code.

11. The method for generating IoT device identity information according to claim 10, wherein the determining whether there is device identity information identical to the initial device identity information specifically comprises: It is determined whether there is device identity information identical to the initial device identity information in a pre-stored device identity information set, wherein the device identity information set includes a plurality of terminal hardware identification information and corresponding device identity information.

12. The method for generating the identity information of the Internet of Things device according to claim 11, wherein, When the device identity information set does not contain device identity information identical to the initial device identity information, the method further includes: Based on the denial information for the identical device identity information, determining the initial device identity information as the device identity information of the Internet of Things terminal; A feedback message is generated based on the denial information.

13. An IoT device identity information generation device, comprising: An initial device identity information determining unit, configured to determine the initial device identity information of the Internet of Things terminal based on the location information of the Internet of Things terminal; an initial device identity information sending unit, configured to send the terminal hardware identification information of the IoT terminal and the initial device identity information to the IoT server, so that the IoT server feeds back a feedback message to the IoT terminal indicating whether there is device identity information identical to the initial device identity information; The first device identity information determination unit is configured to, if the feedback message indicates that there is device identity information identical to the initial device identity information, determine the device identity information of the Internet of Things terminal based on the discrimination code and the initial device identity information; wherein, the discrimination code is used to distinguish different terminal hardware identification information corresponding to the same device identity information.

14. An Internet of Things device identity information generation apparatus, comprising: An initial device identity information acquisition unit, configured to acquire the terminal hardware identification information of the Internet of Things terminal and the initial device identity information of the Internet of Things terminal; wherein, the initial device identity information is determined by the Internet of Things terminal according to location information; A same device identity information judgment unit, configured to judge whether there is device identity information identical to the initial device identity information, and obtain a judgment result; A judgment result sending unit, configured to, when the judgment result indicates that there is device identity information identical to the initial device identity information, respectively configure corresponding discrimination codes for each piece of terminal hardware identification information corresponding to the same device identity information and the initial device identity information, and send the judgment result and the discrimination code to the Internet of Things terminal, so that the Internet of Things terminal determines the device identity information of the Internet of Things terminal according to the initial device identity information and the discrimination code.

15. An electronic device, comprising: At least one processor; And A memory, the memory stores instructions, when the instructions are executed by the at least one processor, enabling the at least one processor to execute the method according to any one of claims 1 to 12.

Images