Facilitation of container management for internet of things devices for 5g or other next generation network

Abstract

A lightweight machine-to-machine (LWM2M) protocol can be utilized as a management layer for other applications pertaining to communication and retrieval of information from hardware peripherals. The applications can be managed via a client and the applications can communicate to the client via a standard proxy or message broker. Consequently, sensor codes can be decoupled from the client codes, thus allowing them to both be independent interchangeable components of a specific device's architecture. Therefore, sensors can be added, removed, and/or manipulated without modifying the underlying management layer.

What is claimed is: 
     
         1 . A method, comprising:
 determining, by network equipment comprising a processor, that an object installed at the network equipment is being deleted; and   in response to determining that the object being deleted is associated with a driver installed at an Internet-of-things device, preventing, by the network equipment, the driver installed at the Internet-of-things device from controlling a hardware pin of the Internet-of-things device, wherein the hardware pin is associated with a sensor interface of the Internet-of-things device.   
     
     
         2 . The method of  claim 1 , wherein the object is a first object and the driver is a first driver, and further comprising:
 in response to determining that a second object is installed at the network equipment and the second object is associated with a second driver installed at the Internet-of-things device, enabling, by the network equipment, the second driver to control the hardware pin of the Internet-of-things device.   
     
     
         3 . The method of  claim 2 , wherein the first driver is associated with a first sensor that interfaces with the sensor interface of the Internet-of-things device, and the second driver is associated with a second sensor that interfaces with the sensor interface of the Internet-of-things device. 
     
     
         4 . The method of  claim 3 , wherein the first sensor is a different sensor type from the second sensor. 
     
     
         5 . The method of  claim 2 , wherein the first driver employs the hardware pin as an input pin, and the second driver employs the hardware pin as an output pin. 
     
     
         6 . The method of  claim 2 , wherein the first driver employs the hardware pin as an output pin, and the second driver employs the hardware pin as an input pin. 
     
     
         7 . The method of  claim 1 , further comprising, in response to determining that the object being deleted is associated with the driver installed at the Internet-of-things device, instructing, by the network equipment, the Internet-of-things device to delete the driver from the Internet-of-things device. 
     
     
         8 . Network equipment, comprising:
 a processor; and   a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising:
 determining that an object previously installed at the network equipment has been deleted; and 
 in response to determining that the object that has been deleted is associated with a driver installed at an Internet-of-things device, preventing the driver installed at the Internet-of-things device from control of a hardware pin of the Internet-of-things device, wherein the hardware pin is associated with a peripheral interface of the Internet-of-things device. 
   
     
     
         9 . The network equipment of  claim 8 , wherein the object is a first object and the driver is a first driver, and wherein the operations further comprise, in response to determining that a second object is installed at the network equipment and the second object is associated with a second driver installed at the Internet-of-things device, configuring the second driver to control the hardware pin of the Internet-of-things device. 
     
     
         10 . The network equipment of  claim 9 , wherein the first driver is associated with a first peripheral that interfaces with the peripheral interface of the Internet-of-things device, and the second driver is associated with a second peripheral that interfaces with the peripheral interface of the Internet-of-things device. 
     
     
         11 . The network equipment of  claim 10 , wherein the first peripheral is a different peripheral type from the second peripheral. 
     
     
         12 . The network equipment of  claim 9 , wherein the first driver employs the hardware pin as an input pin, and the second driver employs the hardware pin as an output pin. 
     
     
         13 . The network equipment of  claim 9 , wherein the first driver employs the hardware pin as an output pin, and the second driver employs the hardware pin as an input pin. 
     
     
         14 . The network equipment of  claim 8 , wherein the operations further comprises, in response to determining that the object being deleted is associated with the driver installed at the Internet-of-things device, instructing the Internet-of-things device to uninstall the driver from the Internet-of-things device. 
     
     
         15 . A non-transitory machine-readable medium, comprising executable instructions that, when executed by a processor of network equipment, facilitate performance of operations, comprising:
 determining that an object installed at the network equipment has been deleted; and   in response to determining that the object that has been deleted is associated with a driver installed at an Internet-of-things device, preventing the driver installed at the Internet-of-things device from controlling of a group of hardware pins of the Internet-of-things device, wherein the group of hardware pins are associated with a hardware interface of the Internet-of-things device.   
     
     
         16 . The non-transitory machine-readable medium of  claim 15 , wherein the object is a first object and the driver is a first driver, and wherein the operations further comprise, in response to determining that a second object is installed at the network equipment and the second object is associated with a second driver installed at the Internet-of-things device, configuring the second driver to control the group of hardware pins of the Internet-of-things device. 
     
     
         17 . The non-transitory machine-readable medium of  claim 16 , wherein the first driver is associated with a first hardware device that interfaces with the hardware interface of the Internet-of-things device, and the second driver is associated with a second hardware device that interfaces with the hardware interface of the Internet-of-things device. 
     
     
         18 . The non-transitory machine-readable medium of  claim 17 , wherein the first hardware device is a different hardware device type from the second hardware device. 
     
     
         19 . The non-transitory machine-readable medium of  claim 16 , wherein the configuring the second driver to control the group of hardware pins comprises are least one of:
 configuring a first input hardware pin of the group of hardware pins into a first output hardware pin, or   configuring a second output hardware pin of the group of hardware pins into a second input hardware pin.   
     
     
         20 . The network equipment of  claim 15 , wherein the operations further comprises, in response to determining that the object being deleted is associated with the driver installed at the Internet-of-things device, instructing the Internet-of-things device to uninstall the driver from the Internet-of-things device.