Facilitation of identification of internet-of-things host devices

Abstract

A more efficient internet-of-things (IoT) manufacturing process can be achieved using hash functions to authenticate and identify IoT devices. Device data comprising manufacturer name data, device name data, software version data, and/or hardware version data can be feed through a hash function to generate hashed data. Additionally, same and/or similar data can be hashed via a manufacturing process. The two outputs from both sets of data can then be matched to determine the authentication of a device. Based on the authenticity of the device being verified, the IoT device can undergo a certification process as a part of the manufacturing process. This manufacturing process comprising hashed data can eliminate current manufacturing processes and allow for a unique identifier to be associated with the IoT device.

What is claimed is: 
     
         1 . A method, comprising:
 in response to receiving internet-of-things development data representative of development data to be used to manufacture an internet-of-things device, applying, by network equipment comprising a processor, a first hash function to the internet-of-things development data to encrypt the internet-of-things development data, resulting in encrypted data, wherein the first hash function is associated with a manufacturer identity;   in response to applying the first hash function, applying, by the network equipment, a second hash function to the encrypted data to decrypt the encrypted data, resulting in decrypted data, wherein the second hash function is associated with a carrier identity;   in response to applying the second hash function, matching, by the network equipment, the first hash function to the second hash function, resulting in hash function match data representative of a hash function match; and   based on the hash function match data, receiving, by the network equipment, carrier certification data representative of a carrier certification, from the carrier identity, associated with the internet-of-things device.   
     
     
         2 . The method of  claim 1 , wherein the internet-of-things development data comprises company name data representative of a company that comprises a capability to manufacturing the internet-of-things device. 
     
     
         3 . The method of  claim 1 , wherein the internet-of-things development data comprises device name data representative of an identification of the internet-of-things device. 
     
     
         4 . The method of  claim 1 , wherein the internet-of-things development data comprises software data representative of a software version to be utilized by the internet-of-things device. 
     
     
         5 . The method of  claim 1 , wherein the internet-of-things development data comprises hardware data representative of a hardware version to be utilized by the internet-of-things device. 
     
     
         6 . The method of  claim 1 , wherein the first hash function is a secure hash function. 
     
     
         7 . The method of  claim 1 , further comprising:
 increasing, by the network equipment, a length associated with the first hash function to increase a security feature of the first hash function.   
     
     
         8 . A system, comprising:
 a processor; and   a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising:
 in response to receiving development data representative of a criterion to be used to manufacture an internet-of-things device, employing a first hash function with respect to the development data to encrypt the development data, resulting in encrypted development data, wherein the first hash function is associated with a manufacturer entity; 
 in response to the employing of the first hash function, matching the first hash function to a second hash function to decrypt the encrypted development data, resulting in decrypted data, wherein the second hash function is associated with a carrier entity; and 
 based on the decrypted data, receiving carrier certification data representative of a carrier certification, from the carrier entity, for the internet-of-things device to utilize. 
   
     
     
         9 . The system of  claim 8 , wherein the operations further comprise:
 receiving, from the internet-of-things device, hash data associated with the first hash function.   
     
     
         10 . The system of  claim 8 , wherein the internet-of-things device is a first internet-of-things device, and wherein the operations further comprise:
 in response to receiving the hash data, determining that a second internet-of-things device is a same type of internet-of-things device as the first internet-of-things device.   
     
     
         11 . The system of  claim 8 , wherein the operations further comprise:
 determining a number of internet-of-things devices that are a same type of internet-of-things device as the internet-of-things device.   
     
     
         12 . The system of  claim 8 , wherein the development data comprises manufacturer name data representative of a manufacturer of the internet-of-things device, software data representative of software to be employed by the internet-of-things device, hardware data representative of hardware to be employed by the internet-of-things device, and name data representative of a identification of the internet-of-things device. 
     
     
         13 . The system of  claim 8 , wherein the operations further comprise:
 utilizing a public key to facilitate an encryption of the development data, resulting in the encrypted development data.   
     
     
         14 . The system of  claim 8 , wherein the operations further comprise:
 decrypting the encrypted development data to facilitate a manufacturing process based on the development data.   
     
     
         15 . A non-transitory machine-readable medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising:
 based on development data representative of a criterion to be used to manufacture an internet-of-things device, encrypting the development data utilizing a first hash function associated with a manufacturing identity, resulting in encrypted development data;   in response to the encrypting of the development data, decrypting the encrypted development data, resulting in decrypted development data, wherein decrypting the development data utilizes a second hash function from a carrier identity;   determining that a first result of a first function of the first hash function is equal to a second result of a second function of the second hash function; and   based on the first result being determined to be equal to the second result, receiving carrier certification data representative of a carrier certification, from the carrier identity, for the internet-of-things device to access.   
     
     
         16 . The non-transitory machine-readable medium of  claim 15 , wherein the encrypting of the development data comprises utilizing asymmetric cryptography. 
     
     
         17 . The non-transitory machine-readable medium of  claim 15 , wherein the development data comprises manufacturer identification data representative of a manufacturer of the internet-of-things device. 
     
     
         18 . The non-transitory machine-readable medium of  claim 15 , wherein the development data comprises software data representative of software to be employed by the internet-of-things device. 
     
     
         19 . The non-transitory machine-readable medium of  claim 15 , wherein the development data comprises hardware data representative of hardware to be employed by the internet-of-things device. 
     
     
         20 . The non-transitory machine-readable medium of  claim 15 , wherein the development data comprises device name data representative of a name of the internet-of-things device.