Monitoring and controlling internet of things (IOT) devices

Abstract

This disclosure is related to methods and systems for the monitoring and control of Internet of Things (IoT) devices. Existing IoT device monitoring systems may require personnel to manually interact with the equipment to register the equipment with a server, and the registration process can oftentimes be faulty. Furthermore, most modern equipment monitoring systems are a patchwork of existing solutions that are not functional across a wide array of IoT device types, which can result in the need for registration of all IoT devices, as well as expensive platforms and edge devices to manage the IoT devices. Accordingly, there is a need for a more flexible, resilient, and easily-configurable IoT device monitoring system that address the shortcomings of existing solutions, e.g., by automatically detecting and connecting to IoT devices and obtaining appropriate data structures for such IoT devices, such that their data may be seamlessly managed by a cloud-based platform.

Description

Attorney Docket No: 2024P00264WO_stMONITORING AND CONTROLLING INTERNET OF THINGS (TOT) DEVICESTechnical Field

[0001] This disclosure is related generally to methods and systems for the monitoring and control of Internet of Things (loT) devices.Background

[0002] Real-time monitoring of equipment in industrial settings is crucial for ensuring that the equipment functions properly. Monitoring devices, including sensors connected to the equipment, provide real-time monitoring. The monitoring devices measure one or more parameters associated with the equipment and send data corresponding to the measured one or more parameters to user devices (e.g., a tablet or mobile phone) used by personnel who are responsible for the maintenance and uptime of the equipment. It is crucial that the equipment in industrial settings remain operational, because any downtime could affect the production of final goods generated by the equipment from the intermediate goods. Real-time monitoring provides the personnel responsible for said equipment with the ability to order and install worn or failing equipment parts long before they are due to be replaced according to routine maintenance schedules, thereby minimizing the likelihood of downtime of the equipment. However, there are no “one size fits all” solutions for monitoring equipment in industrial settings. In some settings, a first set of operational parameters might be collected from the equipment, whereas, in another setting, a second set of operational parameters might be collected from the equipment. Furthermore, certain operational parameters must be monitored more regularly than other operational parameters. This creates a need for a system providing the flexibility needed by personnel to curate equipment monitoring solutions that are tailormade for a given application.

[0003] Current solutions are inflexible and do not provide personnel with the ability to curate application-specific equipment monitoring systems that can be continuously updated, e.g., without the personnel having to be physically present in a facility housing the equipment. Most existing solutions require personnel to manually register new equipment that is brought online (i.e., added to the system) instead of being able to remotely register the equipment as it is being added to the system. Because existing equipment monitoring systems require personnel to manually interact with the equipment to register the equipment with a server, the registration process can oftentimes be faulty and / or plagued with errors — resulting in longerAttorney Docket No: 2024P00264WO_stwait times before the equipment monitoring systems bring new equipment online. Furthermore, most modern equipment monitoring systems are a patchwork of existing solutions that are not functional across a wide array of loT device types, which can result in troubleshooting errors when attempting to diagnose or troubleshoot problems with the equipment and / or monitoring systems. As a result, a considerable amount of time and money is often spent trying to create solutions to problems introduced by piecemeal equipment monitoring systems. Lastly, existing equipment monitoring systems require expensive loT equipment monitoring devices, also referred to as “edge devices,” that can further drive up costs associated with real-time equipment monitoring in industrial settings.

[0004] Accordingly, there is a need for a more flexible, resilient, easily-configurable, and malleable equipment monitoring system addressing the shortcomings of the existing equipment monitoring system solutions.Summary

[0005] According to some embodiments, a monitoring server for monitoring a status of at least one machine is disclosed, the monitoring server comprising: at least one memory storing computer executable instructions; at least one processor configured to execute the computer executable instructions thereby causing the processor to: send at least one operational status request signal to at least one Internet of Things (loT) device; detect at least one first operational status response signal received from the at least one loT device in response to the at least one operational status request signal; determine a device identifier associated with the at least one loT device in response to detecting the at least one first operational status response signal; determine that the at least one loT device is registered with a first server based, at least in part, on the machine identifier; receive at least one configuration response signal from the at least one loT device; determine configuration data associated with the at least one loT device based, at least in part, on the at least one configuration response signal; send at least one operational data request signal to the at least one loT device; and determine at least one operational parameter associated with the at least one loT device in response to detecting at least one operational data response signal from the at least one loT device, wherein the at least one operational parameter corresponds to one or more operational states that the machine has been in.

[0006] According to some such embodiments, the at least one processor is further configured to execute the computer executable instructions to cause the processor to: determine that theAttorney Docket No: 2024P00264WO_stat least one loT device is registered with the first server based, at least in part, on a type of the at least one loT device.

[0007] According to other such embodiments, the at least one processor is further configured to execute the computer executable instructions to cause the processor to: determine a first server identifier associated with the first server based, at least in part, on the device identifier. According to some such embodiments, the device identifier is tagged with the first server identifier.

[0008] According to other such embodiments, the at least one processor is further configured to execute the computer executable instructions to cause the processor to: determine a class that the at least one loT device, belongs to based, at least in part, on the first server identifier.

[0009] According to other such embodiments, the at least one processor is further configured to execute the computer executable instructions to cause the processor to: determine that at least a second loT device is registered with a second server based at least in part on a second type of the at least second loT device.

[0010] According to other such embodiments, the type of the at least one loT device is an automated adhesive dispenser, a syringe dispenser, a curing light emitting diode, testing equipment, a robot, or mixing equipment.

[0011] According to other such embodiments, the at least one processor is further configured to execute the computer executable instructions to cause the processor to: determine at least one maintenance schedule for the at least one loT device. According to some such embodiments, the at least one processor is further configured to execute the computer executable instructions to cause the processor to: send at least one maintenance message signal to at least one user device, the at least one maintenance message signal comprising the at least one maintenance schedule.

[0012] According to other embodiments, an Internet of Things (loT) device is disclosed, comprising: at least one sensor; at least one storage device; at least one memory storing computer executable instructions; at least one processor configured to execute the computer executable instructions thereby causing the processor to: receive at least one signal from a server comprising initialization data, wherein the initialization data comprises a request for an identifier associated with the loT device; store a server identifier associated with the server in the at least one storage device, wherein the server identifier is received in the initialization data; send at least one signal to the server comprising a request to register the identifierAttorney Docket No: 2024P00264WO_stassociated with the loT device with the server; receive a signal from the server confirming registration of the identifier associated with the loT device; send at least one sensor signal to at least one of the at least one sensors comprising instructions to detect at least one operational parameter corresponding to one or more operational states that the loT device has been in; and receive at least one sensor response signal from the at least one sensor comprising the at least one operational parameter corresponding to the one or more operational states that the loT device has been in.

[0013] According to some such embodiments, the at least one processor is further configured to execute the computer readable instructions to cause the at least one processor to: determine the server identifier based, at least in part, on the identifier associated with the loT device.

[0014] According to other such embodiments, the identifier associated with the loT device is tagged with the server identifier.

[0015] According to other such embodiments, the loT device belongs to a certain type based, at least in part, on the server identifier.

[0016] According to other such embodiments, the at least one processor is further configured to execute the computer readable instructions to cause the at least one processor to: detect at least one operational data request signal received from a monitoring server according to a first transmission protocol; and send at least one operational parameter associated with the loT device to the monitoring server in response to the detection of the at least one operational data request signal according to the first transmission protocol.

[0017] According to other such embodiments, the loT device comprises one of the following types of devices: an automated adhesive dispenser, a syringe dispenser, a curing light emitting diode, testing equipment, a robot, or mixing equipment.

[0018] According to other such embodiments, the at least one processor is further configured to execute the computer executable instructions to cause the processor to: determine how the loT device is being used based, at least in part, on at least one operational parameter associated with the loT device. According to some such embodiments, the at least one processor is further configured to execute the computer executable instructions to cause the processor to: receive at least one maintenance schedule for the loT device.

[0019] According to other embodiments, a method performed by an Internet of Things (loT) device is disclosed, the method comprising: receiving at least one signal from a server comprising initialization data, wherein the initialization data comprises a request for anAttorney Docket No: 2024P00264WO_stidentifier associated with the loT device; storing a server identifier associated with the server in at least one storage device of the loT device, wherein the server identifier is received in the initialization data; sending at least one signal to the server comprising a request to register the identifier associated with the loT device with the server; receiving a signal from the server confirming registration of the identifier associated with the loT device; sending at least one sensor signal to at least one sensor of the loT device comprising instructions to detect at least one operational parameter corresponding to one or more operational states that the loT device has been in; and receiving at least one sensor response signal from the at least one sensor of the loT device comprising the at least one operational parameter corresponding to the one or more operational states that the loT device has been in.

[0020] According to other such embodiments, the method further comprises determining the server identifier based, at least in part, on the identifier associated with the loT device.

[0021] According to still other such embodiments, the loT device is determined to belong to a certain type based, at least in part, on the server identifier.Brief Description of the Drawings

[0022] The present application is further understood when read in conjunction with the appended drawings. For the purpose of illustrating the subject matter, there are shown in the drawings exemplary embodiments of the subject matter; however, the presently disclosed subject matter is not limited to the specific methods, devices, and systems disclosed. In the drawings:

[0023] Fig. 1 illustrates an exemplary network for an Internet of Things (loT) equipment monitoring system, according to the present disclosure.

[0024] Fig. 2 illustrates an exemplary logical diagram illustrating functional relationships between different components of the loT equipment monitoring system of Fig. 1.

[0025] Fig. 3 illustrates an exemplary flow chart of a method of pinging loT devices for their operational parameters, according to the present disclosure.

[0026] Fig. 4 illustrates an exemplary flow chart of a method of generating operational parameters for loT devices, according to the present disclosure.

[0027] Fig. 5 illustrates, in block diagram form, an exemplary simplified multifunctional electronic device according to the present disclosure.Attorney Docket No: 2024P00264WO_st

[0028] Aspects of the disclosure will now be described in detail with reference to the drawings, wherein like reference numbers refer to like elements throughout, unless specified otherwise.Detailed Description of Illustrative Embodiments

[0029] The present disclosure is directed to methods and systems for monitoring Internet of Things (loT)-controlled equipment in an industrial, factory, or plant setting and providing operational instructions to loT-controlled devices, e.g., based on one or more operational parameters collected while the loT-controlled equipment is being monitored. For example, the techniques disclosed herein may be applied to loT devices for monitoring the automatic or semi-automatic precision dispensing of adhesives or other fluids.

[0030] Fig. 1 illustrates an exemplary system 100 of loT devices 131, 132, 133, and 134, servers 113, 123, 133, 143, 153, and 163 (e.g., edge servers) in an exemplary server rack 103, cloud monitoring / management servers 101, exemplary user devices 140, 141, and 142, and network 102 (which may represent a local network and / or a wider area network, such as the Internet). Each of the exemplary loT devices 131, 132, 133, or 134 could represent an automated dispenser for an adhesive, a syringe dispenser, a curing LED, testing equipment that determines or confirms the modulus of a mold, a robot, or mixing equipment that is used to mix one or more intermediate chemicals to generate a final chemical, or any other type of Internet-enabled device that can collect data using sensors and exchange information with other devices or systems. According to some embodiments, the loT devices can include one or more sensors that are equipped to: measure temperature or humidity parameters of certain components of devices or industrial infrastructure; measure parameters of components of devices or industrial infrastructure that pass fluids through valves; or measure parameters associated with the rotation of components in certain devices or industrial infrastructure. The loT devices can also include one or more processors, storage devices, and memory that communicatively coupled to the one or more sensors. The parameters measured by the one or more sensors can be written to storage and / or stored temporarily in memory, after which the one or more processors can send the measured parameters to a wireless radio processor for transmission to monitoring servers 101.

[0031] In addition to the parameters listed above, in some embodiments, the loT devices can record one or more other operational parameters associated with the measurements. For instance, the one or more loT device processors can record a timestamp when parameters areAttorney Docket No: 2024P00264WO_stmeasured. In some embodiments, the one or more loT device processors can record the amount of uptime that the device is operational. In other embodiments, the one or more loT device processors can measure the system pressure in different units.

[0032] As an example, loT devices 131 and 132 may comprise automated dispensers for adhesives (or may comprise other classes of automated or semi-automated devices) that include externally-connected wireless radio circuitry (e.g., 131a and 132a, respectively) for connecting loT devices 131 and 132 to the Internet or other wider area network. As another example, loT devices 133 and 134 may include integrated wireless radio circuitry for connecting loT devices 133 and 134 directly to the Internet or other wider area network. As discussed above, loT devicesl31, 132, 133 and 134 can measure and / or record various operational parameters associated with the respective loT devices’ functionality, e.g., the dispensing of a substance from the respective loT devices. The wireless radio circuitry integrated in or connected to the loT devices can transmit the measured operational parameters and / or device statuses via network 102 to cloud-based monitoring / management servers 101 for further processing and / or display to end users. In some embodiments, one or more processors in the monitoring / management servers 101 can process the operational parameters and can transmit one or more signals to the loT devices 131, 132, 133, and / or 134 including instructions to change one or more operational parameters, and / or keep certain operational parameters the same.

[0033] In the example provided above, assuming each of the loT devices 131, 132, 133, and 134 are automated dispensers, each of the loT devices 131, 132, 133, and 134 will send any measured operational parameters to an edge server in exemplary server rack 103 (e.g., an automated dispenser monitoring server that is configured to monitor the class of devices whose IDs indicate that they are automated dispensers), which information may then be passed on to the cloud monitoring / management servers 101, if so desired. The automated dispenser monitoring server can also send one or more signals to the loT devices 131, 132, 133, and 134 comprising instructions to make changes to the operational parameters of the respective devices. In return, the loT devices 131, 132, 133, and 134 can send updated measurements of the same operational parameters back to the automated monitoring server of server rack 103, which one or more processors in the automated dispenser monitoring server can use to determine whether the operating parameters are within a certain range of values.Attorney Docket No: 2024P00264WO_st

[0034] The loT devices may also be registered and / or initialized with a registration and / or initialization server in the server rack 103. For example, if loT device 131 is an automated dispenser, it may only connect to an initialization and registration server that exclusively registers and initializes automated dispensers. For instance, server 113 can be the initialization and registration server that registers and initializes each of the loT devices that are automated dispensers. In other embodiments, each of the loT devices can register with and be initialized by different servers in server rack 103 (e.g., servers 123, 133, 143, 153, and / or 163), e.g., based on their device type, or other criteria or parameters.

[0035] If, instead, e.g., in a different implementation, the loT devices 131, 132, 133, and 134 are each different types of devices (e.g., device 131 is mixing equipment, device 132 is an automated dispenser for adhesives, device 133 is a curing light emitting diode (LED), and device 134 is a syringe dispenser), the devices can be initialized and registered with different initialization and registration servers in server rack 103, based on their device type. For instance, servers 123, 133, 143, and 153 can be the registration and initialization servers that register and initialize the different types of loT devices 131, 132, 133, and 134, respectively.

[0036] One or more processors in the monitoring / management servers 101 can transmit one or more signals to the user devices 140, 41, and 142 wherein the one or more signals include the measured operational parameters of devices 131, 132, 133, and 134, and / or summarizations, visualizations, or analytics related thereto.

[0037] In some embodiments, the monitoring / management servers 101 can include one or more wireless radios that wirelessly transmit the operational parameters to the user devices 140, 141, and 142. Each of the user devices 140, 141, and 142 may also include wireless radios that are configured to receive the operational parameters (and / or other data related thereto) transmitted by the one or more processors in the monitoring / management servers 101. The one or more processors in the user devices 140, 141, and 142 may also be configured to send signals with instructions to change one or more operational parameters in loT devices 131, 132, 133, and / or 134, e.g., via the monitoring / management servers 101 and / or network 102. The wireless radios in the user devices, loT devices, and monitoring server(s) are capable of sending and receiving wireless signals in accordance with one or more of the following wireless protocols: IEEE 802.11, IEEE 802.16 (WiMAX), IEEE 802.15.4, any cellular standards including, but not limited to 6G, 5G, 4G, Long Term Evolution (LTE), Global Systems for Communication (GSM), Code Division MultipleAttorney Docket No: 2024P00264WO_stAccess (CDMA), Universal Mobile Telecommunications System (UMTS), or General Packet Radio Systems (GPRS). In other embodiments, the user devices 140, 141, and 142 may also transmit and / or receive operational parameters to loT devices via wired networks.

[0038] Fig. 2 illustrates an exemplary logical diagram 200 illustrating functional relationships between different components of the Internet of Things (loT) equipment monitoring system of Fig. 1. First, cloud management platform 202 (which may correspond to monitoring / management servers 101 of Fig. 1) may be configured to gather, store, and / or visualize data gathered from various loT devices 204. As illustrated by bi-directional communication arrow 203, cloud management platform 202 may listen to various information reported from loT devices 204, e.g., connections and disconnections of the various loT devices 204 over time and / or other status reports from loT device 204. In some embodiments, cloud management platform 202 may also be able to read or write device IDs or other information to loT devices 204.

[0039] According to some embodiments, each loT device 204, upon coming online, may connect to an appropriate server device 206. As illustrated by bi-directional communication arrow 205, each server device 206 may be capable of recognizing loT device types and device IDs, as well as obtaining appropriate configuration data for (if necessary) and gathering operational data from respective loT devices 204 during their operation. For example, according to some embodiments, when a particular loT device 204 connects to a server 206, the server 206 may check to see if the particular loT device 204 has already been registered with the loT equipment monitoring system. If the loT device 204 has already been registered, then the device type and its configuration data are known to the loT equipment monitoring system and server 206 may simply obtain the appropriate configuration data for the particular type loT device 204. If, instead, the particular loT device 204 is not recognized, the server 206 may create a virtual device (i.e., a “digital twin”) to represent the particular loT device 204, such that, the next time the particular loT device 204 connects to the server 206, the appropriate configuration data for the loT device 204 may be known and obtained, so that the loT device 204 is ready for operational use and management. According to some such embodiments, the data structures used for the configuration data may be shared across all loT devices of the same type.

[0040] As described above, servers 206 may comprise edge devices that are tasked with registering and initializing loT devices that are part of the loT equipment monitoring system.Attorney Docket No: 2024P00264WO_stAs illustrated by bi-directional communication arrow 207, servers 206 may be configured to read and write device IDs and other operational data to cloud management platform 202, such that the appropriate loT device-related data may be returned to and / or displayed at various user devices.

[0041] According to some embodiments, cloud management platform 202 may also be programmed with other smart functionality that provides novel benefits to users of the loT equipment management system. For example, cloud management platform 202 can analyze the operational data returned from the monitored loT devices 204 to determine use levels and / or recommend maintenance for individual loT devices 204 based on their estimated use levels. In some such embodiments, artificial intelligence (Al)-based data analysis techniques may be employed to intelligently predict (e.g., based on its usage and historical usage patterns of similar classes of loT devices) when a particular loT device is likely to fail or need to be serviced, refilled, etc. Doing so may allow cloud management platform 202 to send over the air (OTA) updates to particular loT devices, modify the operational parameters of loT devices to prolong their lifespans, or send alerts to customers regarding particular loT devices, etc. In still other embodiments, loT devices may comprise one or more cameras directed at the operational components of the loT devices, which may relay captured images back to cloud management platform 202 for further image analysis, e.g., to detect if an loT device (or a component thereof) is operating incorrectly, is out of alignment, or is facing some other condition causing the loT device to malfunction or function sub-optimally.

[0042] Fig. 3 illustrates an exemplary process 300 of pinging loT devices for operational parameters, according to the present disclosure. The process can begin at step 301, where a monitoring server (e.g., a monitoring server that is part of cloud monitoring / management servers 101) sends at least on operational status request signal to at least one loT device. For example, one or more processors in a monitoring server can send a signal via one or more wireless radios associated with the monitoring server to an loT device with instructions requesting an operational status of the loT device. For instance, a processor in the monitoring server can be configured to periodically send a signal to an loT device requesting the operational status of the loT device. The operational status can be an indication of whether (and / or to what degree) the device is operational.

[0043] Next, at step 303, one or more processors of the monitoring server can detect an operational status signal received from the at least one loT device. At Step 305, the one orAttorney Docket No: 2024P00264WO_stmore processors of the monitoring server can determine a device identifier associated with the loT device in response to detecting the operational status response signal. At step 307, the one or more processors of the monitoring server can determine whether the loT device is registered with a registration and initialization server based, at least in part, on the device identifier.

[0044] After determining that the loT device is registered, at step 309, the monitoring server can receive at least one configuration response signal from the loT device. In turn, at step 311, the one or more processors in the cloud-based monitoring sever can determine configuration data associated with the loT device based, at least in part, on configuration response signal. Next, at step 313, the one or more processors of the monitoring sever can send at least one operational data request signal to loT device. In response, at step 315, the one or more processor of the monitoring server can determine at least one operational parameter associated with the device in response to detecting at least one operational data response signal from the loT device. After step 315, process 300 can end.

[0045] Fig. 4 illustrates an exemplary process 400 of an loT device measuring one or more operational parameters of a device, according to the present disclosure. At step 401 of process 400, the loT device can receive at least one signal from a registration and initialization server (e.g., such as server rack 103 in Fig. 1) comprising initialization data. The initialization data can comprise a request for an identifier associated with the device. At step 403, the loT device can store an identifier associated with the registration and initialization server in the memory or storage in the loT device. At step 405, the loT device can send at least one signal to the registration and initialization server including a request to register the identifier of the loT device with the registration and initialization server. At step 407, the loT device can receive a signal from the registration and initialization server with a confirmation that the loT device’s identifier has been registered with the registration and initialization server. At step 409, one or more processors in the loT device can send a signal to one or more sensors in the loT device with instructions to detect at least one operational parameter corresponding to one or more operational states that the loT device was in or is currently in. Finally, at step 411, the one or more processors in the loT device can receive a response signal from the one or more sensors comprising the at least one operational parameter corresponding to the one or more operational states that the loT device was in or is currently in. After step 411, process 400 can end.Attorney Docket No: 2024P00264WO_st

[0046] Referring now to Fig. 5, a simplified functional block diagram of an illustrative multifunctional electronic device 500 for use in implementing an loT equipment and operational parameter monitoring system, according to various aspects of the disclosure, is shown. Multifunction electronic device 500 may include processor 510, memory 520, storage device 530, user interface 540, display 550, communications circuitry 560, and communications bus 570. Multifunction electronic device 500 may be, for example, a personal electronic device such as a personal digital assistant (PDA), mobile telephone, or a tablet computer.

[0047] Processor 510 may execute instructions necessary to carry out or control the operation of many functions performed by device 500. Processor 510 may, for instance, drive display 550 and receive user input from user interface 540. User interface 540 may allow a user to interact with device 500. For example, user interface 540 can take a variety of forms, such as a button, keypad, dial, a click wheel, keyboard, display screen and / or a touch screen. Processor 510 may also, for example, be a system-on-chip such as those found in mobile devices and include a dedicated graphics processing unit (GPU). Processor 510 may be based on reduced instruction-set computer (RISC) or complex instruction-set computer (CISC) architectures or any other suitable architecture and may include one or more processing cores.

[0048] Memory 520 may include one or more different types of media used by processor 510 to perform device functions. For example, memory 520 may include memory cache, readonly memory (ROM), and / or random access memory (RAM). Storage 530 may store media (e.g., audio, image and video files), computer program instructions or software, preference information, device profile information, and any other suitable data. Storage 530 may include one more non-transitory storage mediums including, for example, magnetic disks (fixed, floppy, and removable) and tape, optical media such as CD-ROMs and digital video disks (DVDs), and semiconductor memory devices such as Electrically Programmable Read-Only Memory (EPROM), and Electrically Erasable Programmable Read-Only Memory (EEPROM). Memory 520 and storage 530 may be used to tangibly retain computer program instructions or code organized into one or more modules and written in any desired computer programming language. When executed by, for example, processor 510 such computer program code may implement one or more of the methods described herein.

[0049] While systems and methods have been described in connection with the various embodiments of the various figures, it will be appreciated by those skilled in the art thatAttorney Docket No: 2024P00264WO_stchanges could be made to the embodiments without departing from the broad inventive concept thereof. It is understood, therefore, that this disclosure is not limited to the particular embodiments disclosed, and it is intended to cover modifications within the spirit and scope of the present disclosure as defined by the claims.

Claims

Attorney Docket No: 2024P00264WO_stWhat is claimed is:

1. A monitoring server for monitoring a status of at least one machine, the monitoring server comprising:at least one memory storing computer executable instructions;at least one processor configured to execute the computer executable instructions thereby causing the processor to:send at least one operational status request signal to at least one Internet of Things (loT) device;detect at least one first operational status response signal received from the at least one loT device in response to the at least one operational status request signal;determine a device identifier associated with the at least one loT device in response to detecting the at least one first operational status response signal;determine that the at least one loT device is registered with a first server based, at least in part, on the device identifier;receive at least one configuration response signal from the at least one loT device;determine configuration data associated with the at least one loT device based, at least in part, on the at least one configuration response signal;send at least one operational data request signal to the at least one loT device; anddetermine at least one operational parameter associated with the at least one loT device in response to detecting at least one operational data response signal from the at least one loT device, wherein the at least one operational parameter corresponds to one or more operational states that the machine has been in.

2. The monitoring server of claim 1, wherein the at least one processor is further configured to execute the computer executable instructions to cause the processor to:determine that the at least one loT device is registered with the first server based, at least in part, on a type of the at least one loT device.Attorney Docket No: 2024P00264WO_st3. The monitoring server of claim 1, wherein the at least one processor is further configured to execute the computer executable instructions to cause the processor to:determine a first server identifier associated with the first server based, at least in part, on the device identifier.

4. The monitoring server of claim 3, wherein the device identifier is tagged with the first server identifier.

5. The monitoring server of claim 2, wherein the at least one processor is further configured to execute the computer executable instructions to cause the processor to:determine a class that the at least one loT device, belongs to based, at least in part, on the first server identifier.

6. The monitoring server of claim 2, wherein the at least one processor is further configured to execute the computer executable instructions to cause the processor to:determine that at least a second loT device is registered with a second server based at least in part on a second type of the at least second loT device.

7. The monitoring server of claim 2, wherein the type of the at least one loT device is an automated adhesive dispenser, a syringe dispenser, a curing light emitting diode, testing equipment, a robot, or mixing equipment.

8. The monitoring server of claim 1, wherein the at least one processor is further configured to execute the computer executable instructions to cause the processor to:determine at least one maintenance schedule for the at least one loT device.

9. The monitoring server of claim 8, wherein the at least one processor is further configured to execute the computer executable instructions to cause the processor to:send at least one maintenance message signal to at least one user device, the at least one maintenance message signal comprising the at least one maintenance schedule.Attorney Docket No: 2024P00264WO_st10. An Internet of Things (loT) device, comprising:at least one sensor;at least one storage device;at least one memory storing computer executable instructions;at least one processor configured to execute the computer executable instructions thereby causing the processor to:receive at least one signal from a server comprising initialization data, wherein the initialization data comprises a request for an identifier associated with the loT device;store a server identifier associated with the server in the at least one storage device, wherein the server identifier is received in the initialization data;send at least one signal to the server comprising a request to register the identifier associated with the loT device with the server;receive a signal from the server confirming registration of the identifier associated with the loT device;send at least one sensor signal to at least one of the at least one sensors comprising instructions to detect at least one operational parameter corresponding to one or more operational states that the loT device has been in; andreceive at least one sensor response signal from the at least one sensor comprising the at least one operational parameter corresponding to the one or more operational states that the loT device has been in.

11. The loT device of claim 10, wherein the at least one processor is further configured to execute the computer executable instructions to cause the at least one processor to:determine the server identifier based, at least in part, on the identifier associated with the loT device.

12. The loT device of claim 11, wherein the identifier associated with the loT device is tagged with the server identifier.Attorney Docket No: 2024P00264WO_st13. The loT device of claim 10, wherein the loT device belongs to a certain type based, at least in part, on the server identifier.

14. The loT device of claim 10, wherein the at least one processor is further configured to execute the computer executable instructions to cause the at least one processor to:detect at least one operational data request signal received from a monitoring server according to a first transmission protocol; andsend at least one operational parameter associated with the loT device to the monitoring server in response to the detection of the at least one operational data request signal according to the first transmission protocol.

15. The loT device of claim 10, wherein the loT device comprises one of the following types of devices: an automated adhesive dispenser, a syringe dispenser, a curing light emitting diode, testing equipment, a robot, or mixing equipment.

16. The loT device of claim 10, wherein the at least one processor is further configured to execute the computer executable instructions to cause the processor to:determine how the loT device is being used based, at least in part, on at least one operational parameter associated with the loT device.

17. The loT device of claim 16, wherein the at least one processor is further configured to execute the computer executable instructions to cause the processor to:receive at least one maintenance schedule for the loT device.

18. A method performed by an Internet of Things (loT) device, the method comprising:receiving at least one signal from a server comprising initialization data, wherein the initialization data comprises a request for an identifier associated with the loT device;Attorney Docket No: 2024P00264WO_ststoring a server identifier associated with the server in at least one storage device of the loT device, wherein the server identifier is received in the initialization data;sending at least one signal to the server comprising a request to register the identifier associated with the loT device with the server;receiving a signal from the server confirming registration of the identifier associated with the loT device;sending at least one sensor signal to at least one sensor of the loT device comprising instructions to detect at least one operational parameter corresponding to one or more operational states that the loT device has been in; andreceiving at least one sensor response signal from the at least one sensor of the loT device comprising the at least one operational parameter corresponding to the one or more operational states that the loT device has been in.

19. The method of claim 18, further comprising:determining the server identifier based, at least in part, on the identifier associated with the loT device.

20. The method of claim 18, wherein the loT device is determined to belong to a certain type based, at least in part, on the server identifier.

Images