The IoT Toothbrush is a device used to monitor a user's vital signs through its interaction the user's finger touch with the toothbrush's sensor. The IoT Toothbrush is connected through a Wi-Fi protocol via its associated base, the Toothbrush-Hub in order to send personal identification and vital signs to the individual's personal mobile device. Monitoring the user's vital signs can be tracked via the Client Application downloaded through the user's personal mobile device.
The present disclosure relates generally to IoT communications networking to facilitate the process of monitoring human health.
When the human fingers touch the sensor on the IoT Toothbrush, personal identification and human vital signs are collected and transferred to a simple Bluetooth-Wi-Fi interface device, called the Toothbrush-Hub. This device in turn transfers the collected data to the Server Software through the Wi-Fi interface. The Server Software listens to the Toothbrush-Hub to accept data from this device. The software will save data from each person based on personal identification of the individual user. Overtime, the software will analyze the collected data and archive such historic data. It will alert the individual if their data triggers any health-related risk factors set pursuant to certain pre-defined thresholds (i.e. chronic dehydration from elevated heart rate). Furthermore, abrupt changes in vital signs will also alert the user and any other persons they wish to share such information with (i.e. significant decrease in oxygen saturation in an elderly person.
For a more complete understanding of the present disclosure and its features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawing, in which:
According to the embodiment, information about a user's vital signs may be collected, analyzed, and disseminated in a comprehensible manner to the user in a simple routine activity that most individuals perform daily. Daily tooth brushing could trigger a complete sequence of events to achieve this task.
Certain embodiments of the disclosure may provide one or more technical advantages. A technical advantage of one embodiment may include the alarm message that is sent to a user periodically until they acknowledge it. Another includes the disclosure of data collected from the IoT Toothbrush to another trusted individual (i.e. monitoring the health of a loved one). Certain embodiments of the disclosure may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art from the figures, descriptions, and claims included herein.
Each toothbrush has its associated base station—the Toothbrush-Hub—which in
The Toothbrush-Hub may maintain a permanent connection with the Server Software using a Wi-Fi protocol. The connection is implementation choice, either a simple User Datagram Protocol/Transmission Control Protocol (“UDP/TCP”) socket or Secure Shell (“SSH”) connection. When the Toothbrush-Hub receives data from the IoT Toothbrush, it packs and sends the packet data into a message that the Server Software can interpret and understand. The Server Software is a software that runs as a server, and its clients are the Toothbrush-Hub and personal mobile devices. The Toothbrush-Hubs, H1 and H2, are registered as source clients. The source clients supply raw data collected from the IoT Toothbrush when the sensor is touched by a human person. The personal mobile devices, P1 and P2, are registered as destination clients. The destination clients receive notifications after raw data gets analyzed. H1, H2, P1, and P2 can use the Dynamic Host Configuration Protocol (“DHCP”) to register with the Server Software. Users will need to install a simple Client Application on their mobile devices to register the service with the Server Software. The Client Application has two phases of registration. The first phase uses the DHCP to establish a connection with the Server Software. The second phase of registration occurs when the user touches the IoT Toothbrush sensor. The Client Application receives personal identification from the Server Software and prompts for confirmation from the individual who touches the sensor. If the person confirms the query upon reviewing its Terms and Conditions and Privacy Policy, the Client Application sends confirmation back to the Server Software. This completes the registration.
To correlate the personal mobile device and IoT Toothbrush personal identification, two phases of registration are needed. The Client Application uses the DHCP protocol to register the personal mobile device's IP address with the Server Software. A person may need to touch the IoT Toothbrush sensor during the second phase destination of client registration. When personal identification is sent to the Server Software, it broadcasts to all registered mobile devices the personal identification. The Server Software then waits for confirmation from the Client Application for confirmation to the Server Software registers the personal identification with the personal mobile device.
At any given time, when the person uses the toothbrush, raw data collected from the sensor is sent to the Server Software via the Toothbrush-Hub. The Server Software analyzes the raw data for any abnormal behavior, which will prompt the Server Software to send notifications to the mobile device, alarming the person to take appropriate action.