# Patent

## Title
Touchless management system

## Abstract

A touchless management method and system can include: a server beacon, the server beacon including a gesture sensor, a motion sensor, a managed sensor, a server beacon mass storage, and a server beacon power transceiver; detecting gesture data from the gesture sensor; recording sensor data with the managed sensor; a power station including a power station power transceiver, a station control unit, upload coordinator, and a station storage unit; sending a packet from the server beacon to the power station; prioritizing the packet; uploading a message including the sensor data to the power station; and uploading the message to a database server.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
This is a Continuation of U.S. patent application Ser. No. 15/261,976 filed Sep. 11, 2016, which claims the benefit of priority to U.S. Provisional Patent Application No. 62/217,699 filed Sep. 11, 2015. U.S. patent application Ser. No. 15/261,976 is also a Continuation-in-Part of U.S. patent application Ser. No. 15/077,874 filed Mar. 22, 2016, now U.S. Pat. No. 9,516,662, which claims the benefit of priority to U.S. Provisional Patent Application No. 62/217,699 filed Sep. 11, 2015. The content of these applications is incorporated herein by reference in their entirety.


TECHNICAL FIELD
This disclosure relates to automated compliance systems, more particularly to touchless control of, and interface with, automated compliance systems.
BACKGROUND
With the advancement of mobile devices and machine automation, new ways of interfacing with technology are emerging. Users now have the ability to interact with automated systems in many environments.
One such interaction can take place in the field of automated compliance and monitoring systems, such as hand washing compliance systems in restaurants and hospitals. These automated systems can reduce many expenses including costs due to human error, employment costs, and costs of complexity arising from lack of standardization.
Automated systems of this kind are increasingly seen as invaluable in environments where compliance is crucial and alternatives are difficult and expensive to implement. Illustratively, it has been reported that more than 50% of all nosocomial infections can be directly related to the transmission of harmful bacteria by healthcare workers who have not properly washed their hands before and after each patient contact.
Thus, the best means to prevent transfer of these organisms from patient to patient and to reduce the emergence of resistant organisms is hand-washing with soap and water between patient contacts. The Centers for Disease Control and Prevention as well as other regulatory agencies recommend hand-washing before and after each patient encounter.
Automated compliance systems in a healthcare environment can increase compliance rates noticeably; however, the implementation of automated compliance systems is fraught with difficulties. Chief among these difficulties is preventing the spread and exposure to health care-associated infections during use and control of the compliance system in a streamlined and intuitive way that does not prohibitively increase the workload of the users, which can lead to an aversion to using the system.
The spread and exposure to health care-associated infections can arise when users are required to interface and control an automated compliance system by using direct physical contact. Many previous developments have been advanced to address this problem.
For example, some automated systems attempt to isolate the use of a compliance system and the control of the compliance system. This isolation method introduces the additional problems of higher workload and the additional responsibility to return to the compliance system at a later time.
Effective solutions have been long sought but prior developments have not taught or suggested any, and solutions to these problems have long eluded those skilled in the art. Thus, there remains a considerable need for devices and methods that can touchlessly control and interface with compliance systems.
SUMMARY
A touchless compliance system and methods, providing accurate, simple, and intuitive control and communication are disclosed. The touchless compliance system and methods can include: a server beacon, the server beacon including a gesture sensor, a motion sensor, a managed sensor, a server beacon mass storage, and a server beacon power transceiver; detecting gesture data from the gesture sensor; recording sensor data with the managed sensor; a power station including a power station power transceiver, a station control unit, upload coordinator, and a station storage unit; sending a packet from the server beacon to the power station; prioritizing the packet; uploading a message including the sensor data to the power station; and uploading the message to a database server.
Other contemplated embodiments can include objects, features, aspects, and advantages in addition to or in place of those mentioned above. These objects, features, aspects, and advantages of the embodiments will become more apparent from the following detailed description, along with the accompanying drawings.



BRIEF DESCRIPTION OF THE DRAWINGS
The compliance system is illustrated in the figures of the accompanying drawings which are meant to be exemplary and not limiting, in which like reference numerals are intended to refer to like components, and in which:
FIG. 1 is a block diagram of a beacon for use with the compliance system in a first embodiment.
FIG. 2 is a block diagram of a station for use with the compliance system in the first embodiment.
FIG. 3 is a block diagram of a compliance system in the first embodiment.
FIG. 4 is a graphical view of the beacon sensor data of FIG. 1.
FIG. 5 is a graphical view of the station sensor data of FIG. 2.
FIG. 6 is a graphical view of the station user interface of FIG. 2.
FIG. 7 is a user engagement control flow for the compliance system of FIG. 3.
FIG. 8 is a control flow of the detection step of FIG. 7.
FIG. 9 is a control flow of the process step of FIG. 7.
FIG. 10 is a communication control flow for the user identification step of FIG. 9.
FIG. 11 is a control flow of the sending step of FIG. 10.
FIG. 12 is a control flow of the receiving step of FIG. 10.
FIG. 13 is a control flow of the processing step of FIG. 12.
FIG. 14 is a control flow of the user identification step of FIG. 9.
FIG. 15 is a control flow of the filter candidates step of FIG. 14.
FIG. 16 is a control flow of the build Match_List step of FIG. 14.
FIG. 17 is a control flow of the disambiguation step of FIG. 14.
FIG. 18 is a control flow of the accelerometer disambiguation step of FIG. 17.
FIG. 19 is a control flow of the game disambiguation step of FIG. 17.
FIG. 20 is a control flow of the probability step of FIG. 17.
FIG. 21 is a block diagram of a compliance system in a second embodiment.
FIG. 22 is a block diagram for wear leveling the memory of the server beacon mass storage for the server beacon of FIG. 21.
FIG. 23 is a block diagram of an upload coordinator in the power station of FIG. 21.
FIG. 24 is a block diagram of the packet of FIG. 23.
FIG. 25 is a block diagram of manual transcription for the compliance system of FIG. 21.
FIG. 26 is a block diagram of automatic transcription for the compliance system of FIG. 21.
FIG. 27 is a block diagram of a training mode for the automatic transcription of FIG. 26.
FIG. 28 is a block diagram and graphical display of an audio record user interface for the external computer.
FIG. 29 is a block diagram and graphical display of a medical record transaction user interface for the external computer.
FIG. 30 is a graphical view of the gesture data for the gesture sensor of the server beacon of FIG. 21.
FIG. 31 is a first control flow for the gesture sensor of FIG. 21.
FIG. 32 is a second control flow for the gesture sensor continuing from the turn off motion sensor step of FIG. 31.
FIG. 33 is a first control flow for uploading the audio data of FIG. 21.
FIG. 34 is a second control flow for uploading the audio data of FIG. 21 and continuing from the log and reset step of FIG. 33.
FIG. 35 is a third control flow for uploading the audio data of FIG. 21 and continuing from the F_HIT threshold decision step of FIG. 34.
FIG. 36 is a control flow for providing the queue for the upload coordinator of FIG. 23.
FIG. 37 is a control flow for processing the packets of FIG. 23 from the queue of FIG. 36.



DETAILED DESCRIPTION
In the following description, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration, embodiments in which the compliance system may be practiced. It is to be understood that other embodiments may be utilized and structural changes may be made without departing from the scope of the compliance system.
When features, aspects, or embodiments of the compliance system are described in terms of steps of a process, an operation, a control flow, or a flow chart, it is to be understood that the steps can be combined, performed in a different order, deleted, or include additional steps without departing from the compliance system as described herein.
Further, when features, aspects, or embodiments of the compliance system are described in terms of steps of a process, an operation, a control flow, or a flow chart, it is to be understood, unless otherwise specifically described, that the steps can be executed by a processor and the results, thresholds, and variables from the steps can be stored in a non-transitory computer readable medium.
The compliance system is described in sufficient detail to enable those skilled in the art to make and use the compliance system and provide numerous specific details to give a thorough understanding of the compliance system; however, it will be apparent that the compliance system may be practiced without these specific details.
In order to avoid obscuring the compliance system, some well-known system configurations are not disclosed in detail. Likewise, the drawings showing embodiments of the system are semi-diagrammatic and not to scale and, particularly, some of the dimensions are for the clarity of presentation and are shown greatly exaggerated in the drawing FIGS. Generally, the compliance system can be operated in any orientation.
As used herein, the term system is defined as a device or method depending on the context in which it is used. For expository purposes, the term “horizontal” as used herein is defined as a plane parallel to the top plane or surface of the display, regardless of its orientation.
The term “vertical” refers to a direction perpendicular to the horizontal as just defined. Terms, such as “above”, “below”, “bottom”, “top”, “side”, “higher”, “lower”, “upper”, “over”, and “under”, are defined with respect to the horizontal plane. The term computer readable medium is defined as an article of manufacture.
Referring now to FIG. 1, therein is shown a block diagram of a beacon 100 for use with a compliance system in a first embodiment. The beacon 100 is depicted as including a beacon control unit 102, a beacon storage unit 104, a beacon communication unit 106, a beacon sensor unit 108, and a beacon user interface 110.
The beacon control unit 102 can be implemented in a number of different manners. For example, the control unit can be a processor, an embedded processor, a microprocessor, a hardware control logic, a hardware finite state machine, a digital signal processor, or a combination thereof.
The beacon control unit 102 is depicted including a beacon counter 112 and a beacon state 114. The beacon counter 112 can provide a countdown before engaging the beacon user interface 110 to provide an audio notification. It is further contemplated that the beacon counter 112 can provide a count to trigger the beacon communication unit 106 for transmitting or receiving with the station 200 of FIG. 2.
The beacon state 114 can be used to set the operational state of the beacon 100. Illustratively the operational state of the beacon 100 can include counting down with the beacon counter 112, transmitting or receiving with the beacon communication unit 106, waiting, signaling a user with the beacon user interface 110, and reading the beacon sensor unit 108.
The beacon storage unit 104 can be a volatile memory, a nonvolatile memory, an internal memory, an external memory, or a combination thereof. For example, the storage unit can be a nonvolatile storage such as random access memory, flash memory, disk storage, or a volatile storage such as static random access memory.
The beacon storage unit 104 can include a user ID 116. The user ID 116 can be a single unique identifier for each of the beacons 100 used with the compliance system.
The beacon communication unit 106 can be implemented with antennas, and transceivers. The beacon communication unit 106 can include beacon communication modes 118 and beacon parameters 120. The beacon communication modes 118 can include receive, transmit, and low power.
The beacon parameters 120 can be used to control various parameters of the beacon communication unit 106 such as signal strength during transmission, transmission signal frequency, wait times between transmissions, length of transmission times, transmission of beacon sensor data 122 collected by the beacon sensor unit 108, transmission of the user ID 116, wait times between receptions, and length of reception times. The beacon parameters 120 can be stored in the beacon storage unit 104.
The beacon sensor unit 108 can be various sensors such as a magnetometer, a gyroscope, an accelerometer, a thermopile, or a combination thereof. The beacon sensor unit 108 can produce the beacon sensor data 122.
For example, it is contemplated that when the beacon sensor unit 108 is implemented as a magnetometer, a gyroscope, and an accelerometer, the magnetometer and the gyroscope can be used to produce the beacon sensor data 122 indicating the direction the beacon 100 is pointing, while the accelerometer can produce the beacon sensor data 122 indicating an acceleration of the beacon 100.
The beacon sensor data 122 for the beacon sensor unit 108 can be combined in this example to indicate a direction of travel of the beacon 100 as well as distance and speed that the beacon 100 travels. It is contemplated that the beacon sensor unit 108 can implement an accelerometer to produce the beacon sensor data 122 indicating the acceleration, speed, and distance that the beacon 100 travels without indicating the direction.
It is further contemplated that the beacon sensor unit 108 can be implemented as a thermopile and can produce the beacon sensor data 122 that indicates a position or movement of a heat source relative to the beacon 100. For example, it is contemplated that the beacon sensor unit 108 can be a thermopile array sensor and that the beacon sensor data 122 produced can indicate positions and direction of movement, independent of ambient light conditions.
It is contemplated that the beacon 100 could transmit the beacon sensor data 122 as it is read or could store the beacon sensor data 122 in the beacon storage unit 104 for later transmission or processing by the beacon control unit 102. For instance, the beacon sensor data 122 indicating the acceleration of the beacon 100 can be integrated in the beacon control unit 102 to provide a velocity of the beacon 100 and could be further processed to provide a distance that the beacon 100 moved over a particular timeframe.
The beacon sensor data 122 processed by the beacon control unit 102 can further be stored in the beacon storage unit 104 and transmitted by the beacon communication unit 106. The beacon sensor data 122 can be transmitted based on and in accordance with the beacon state 114, the beacon communication modes 118, and the beacon parameters 120.
The beacon user interface 110 can provide a visual indicator, an audio indicator, and a haptic indicator. For example, the beacon user interface 110 can provide visual indicators when implemented as LED lights providing visual indications by blinking, color, and brightness. The visual indicator can further provide visual indicators when implemented as an LED or LCD display providing symbols or graphical indicators.
As a further example the beacon user interface 110 can provide audio indicators when implemented as a speaker providing audio indications by beeping, chiming, or speaking. As yet a further example the beacon user interface 110 can provide haptic indicators when implemented as a vibration motor providing haptic indications by vibrating and twitching.
It will be understood by those having ordinary skill in the art that when the beacon 100 is described to execute, run, calculate, or initiate, the beacon 100 can utilize the beacon control unit 102 to execute, run, calculate, or initiate. It will be further understood by those having ordinary skill in the art that when the beacon 100 is described to set, update, or save, the beacon 100 can utilize the beacon storage unit 104 to set, update, or save.
It will be further understood by those having ordinary skill in the art that when the beacon 100 is described to send, transmit, or receive, the beacon 100 can utilize the beacon communication unit 106 to send, transmit, or receive. It will be further understood by those having ordinary skill in the art that when the beacon 100 is described to count or countdown, the beacon 100 can utilize the beacon counter 112 to count or countdown.
Referring now to FIG. 2, therein is shown a block diagram of a station 200 for use with the compliance system in the first embodiment. The station 200 is depicted as including a station control unit 202, a station storage unit 204, a station communication unit 206, a station sensor unit 208, and a station user interface 210.
The station control unit 202 can be implemented in a number of different manners. For example, the control unit can be a processor, an embedded processor, a microprocessor, a hardware control logic, a hardware finite state machine, a digital signal processor, or a combination thereof.
The station control unit 202 is depicted including a station counter 212 and a station state 214. The station counter 212 can provide a countdown until the end of a hygiene session. The countdown provided by the station counter 212 can be displayed on the station user interface 210 along with triggering notifications of a completed hygiene session. It is further contemplated that the station counter 212 can provide a count to trigger the station communication unit 206 for transmitting or receiving with the beacon 100 of FIG. 1.
The station state 214 can be used to set the operational state of the station 200. Illustratively the operational state of the station 200 can include counting down with the station counter 212, transmitting or receiving with the station communication unit 206, waiting, signaling a user with the station user interface 210, and reading the station sensor unit 208.
The station storage unit 204 can be a volatile memory, a nonvolatile memory, an internal memory, an external memory, or a combination thereof. For example, the storage unit can be a nonvolatile storage such as random access memory, flash memory, disk storage, or a volatile storage such as static random access memory.
The station storage unit 204 can include a user ID table 216 and a Match_List 218. The user ID table 216 can include a list of user names 220 associated with the user IDs 116 of FIG. 1 for each of the beacons 100. It is further contemplated that the user ID table 216 can include only those user IDs 116 that are authorized or known to use the station 200.
The user ID table 216 can further include an approved category 221. The approved category 221 can be a class or group of the user IDs 116 that the station 200 can recognize as valid users without the actual user IDs 116 being contained within the user ID table 216. It is contemplated that the user IDs 116 can include information indicating whether the beacon 100 having the user IDs 116 belong to the approved category 221.
The Match_List 218 can include a list of the user IDs 116 associated with a received signal strength indicator (RSSI) 222. The station 200 can detect the user ID 116 and the RSSI 222 for each of the beacons 100 that are close to the station 200. It is contemplated that the station 200 can detect RSSI 222, which can be the highest RSSI for the beacon 100, an average RSSI for the beacon 100, or the lowest RSSI for the beacon 100, each measured over a window of time.
The station communication unit 206 can communicate with the beacon communication unit 106 of FIG. 1 of the beacon 100. The station communication unit 206 can enable two-way communication with the beacon 100 and can be implemented with antennas, and transceivers.
The station sensor unit 208 can be various sensors such as thermal sensors, digital video sensors, or motion sensors. The motion sensors are contemplated to be passive infrared motion sensors, microwave motion sensors, ultrasonic motion sensors, or tomographic motion sensors.
The station sensor unit 208 can produce the station sensor data 224. For example, it is contemplated that when the station sensor unit 208 is implemented as a thermal sensor, the station sensor unit 208 could produce the station sensor data 224 that indicates a position or movement of a heat source relative to the station 200.
It is contemplated that the station 200 could store the station sensor data 224 in the station storage unit 204. It is further contemplated that the station sensor data 224 could further be processed by the station control unit 202. The station sensor data 224 processed by the station control unit 202 can further be stored in the station storage unit 204.
The station user interface 210 can provide a visual indicator, and an audio indicator. The station user interface 210 can include a display, speakers, and can also include a keypad, a touchpad, soft-keys, a keyboard, and a microphone.
It will be understood by those having ordinary skill in the art that when the station 200 is described to execute, run, calculate, or initiate, the station 200 can utilize the station control unit 202 to execute, run, calculate, or initiate. It will be further understood by those having ordinary skill in the art that when the station 200 is described to set, update, save, or add and remove information, the station 200 can utilize the station storage unit 204 to set, update, save, or add and remove information.
It will be further understood by those having ordinary skill in the art that when the station 200 is described to send, transmit, or receive, the station 200 can utilize the station communication unit 206 to send, transmit, or receive. It will be further understood by those having ordinary skill in the art that when the station 200 is described to count or countdown, the station 200 can utilize the station counter 212 to count or countdown.
Referring now to FIG. 3, therein is shown a diagrammatic overview of the compliance system 300 in the first embodiment. The compliance system 300 is depicted having the beacons 100 physically attached to users 302 near the station 200. The users 302 can include inactive users 304 and an active user 306 that are proximal to the station 200.
The active user 306 is one of the users 302 that is currently interacting with the station 200 while the inactive users 304 are the users 302 that are near the station 200 but are not currently interacting with the station 200. The beacons 100 are shown transmitting a signal 308. The signal 308 can be transmitted from the beacon communication unit 106 of FIG. 1 to the station communication unit 206 of FIG. 2. The station communication unit 206 can detect the signal 308 from the beacons 100 when the station 200 scans for the signal 308.
The signal 308 can include the beacon sensor data 122 and the user ID 116. The signal 308 can also be used to determine the RSSI 222 of the beacon 100 transmitting the signal 308. The beacon sensor data 122 along with the RSSI 222 and the user ID 116 can be stored in the station storage unit 204 of FIG. 2.
The signal 308 is depicted as a one-way communication from the beacons 100 providing the beacon sensor data 122 and populating the Match_List 218; however, the station 200 is shown to also transmit the signal 308 to the beacons 100. For example, the station 200 will transmit the signal 308 to the beacons 100 when updating and changing the beacon communication modes 118 of FIG. 1, the beacon parameters 120 of FIG. 1, or the beacon state 114 of FIG. 1.
The signal 308 transmitted from the station 200 can further be used to signal the users 302 wearing the beacons 100. Illustratively, when the compliance system 300 is used for hand washing compliance, the station 200 can transmit the signal 308 to the beacons 100 to display instructions for a type of wash on the user interface 110 of FIG. 1; such as, displaying instructions to wash with soap and water instead of alcohol during a subsequent cleansing.
The station 200 can also transmit the signal 308 triggering the beacon user interface 110 to display the number of washes the users 302 have performed during a current day. It is contemplated that the signal 308 from the station 200 to the beacon 100 could further include an amount of time the beacon 100 should wait before the beacon user interface 110 sounds a tone indicating that an alcohol scrub which the users 302 are currently performing is complete.
In some contemplated embodiments, the signal 308 can be implemented as a Bluetooth or Wi-Fi signal 308. For descriptive clarity, the information within the station 200 is shown collected in busses, which are indicated with thicker line widths while the direction of information travel is depicted with directional arrows.
It is contemplated that the signal 308 transmitted from the beacons 100 can include a sub-field of information indicating whether the beacons 100 belong to the approved category 221. It is contemplated that the approved category 221 may be used to identify one of the users 302 that is authorized to use the station 200 but whose full individual user ID 116 is not previously stored on the station 200. It is contemplated that the sub-field of information can be contained in the user ID 116 or other portions of the signal 308 from the beacons 100.
Furthermore, the signal 308 from the beacons 100, including the user IDs 116, to the station 200 can include plain or encrypted user name 220 information, which could allow the station 200 to create a new entry on the Match_List 218 for the user 302. Adding one of the users 302 in this manner could require that the user ID 116 and the user name 220 information sent from the beacon 100 be signed by a trusted source.
The station 200 can further detect the station sensor data 224 by detecting the active user 306 with the station sensor unit 208 of FIG. 2. Illustratively, the station sensor data 224 could include position, movement, or a combination thereof for the active user 306 with respect to the station 200.
The beacon sensor data 122, the user ID 116, the RSSI 222, and the station sensor data 224 can be fed into a user disambiguation block 310. The user disambiguation block 310 can be process steps implemented within the station control unit 202 of FIG. 2 and having results stored in the station storage unit 204.
Specifically, the user disambiguation block 310 can provide probabilities 312. The probabilities 312 can be the probability 312 that the user disambiguation block 310 assigns to the inactive users 304 and the probability 312 the user disambiguation block 310 assigns to the active user 306.
The user disambiguation block 310 can further provide a current user 314. The current user 314 is one of the users 302 that the user disambiguation block 310 determines is the most likely candidate for the active user 306.
The Match_List 218 is depicted having two-way data flow with the user disambiguation block 310. It is contemplated that the user disambiguation block 310 can update the Match_List 218 with the users 302 that are the most relevant. The user disambiguation block 310 can delete the users 302 that are not known to be in the user ID table 216 or that have a low probability 312 of being the active user 306.
The user disambiguation block 310 can match the beacon sensor data 122 to the station sensor data 224. The comparison of the beacon sensor data 122 to the station sensor data 224 can result in scores 316.
The scores 316 can be used to determine the probability 312 that any one of the beacons 100 corresponds to the active user 306. The user disambiguation block 310 can further assess aspects of the signal 308 like the RSSI 222 to determine the probability 312 that the beacons 100 corresponds to the active user 306.
The user disambiguation block 310 can compare the scores 316 and the RSSI 222 to a history record 318 to provide the probabilities 312 of the users 302 and the current user 314. The history record 318 can be stored on the station storage unit 204 and can be updated by the user disambiguation block 310 with current scores 316 and RSSI 222 data.
Once the user disambiguation block 310 has determined the current user 314 having the probability 312 above a threshold, the user disambiguation block 310 can correlate the user ID 116 of the current user 314 to the user names 220 within the user ID table 216 and the disambiguation will stop. If the user disambiguation block 310 does not determine the current user 314 with the probability 312 above a threshold the disambiguation will continue.
The user disambiguation block 310 can provide the user name 220 of the current user 314 to the station user interface 210. The station user interface 210 can display the user name 220 of the current user 314 on the station user interface 210 to the active user 306.
The station user interface 210 can further display the probabilities 312 and other supporting results of the disambiguation process to the active user 306. It is contemplated that the active user 306 can verify whether the user disambiguation block 310 has indicated the correct current user 314. The input of the active user 306 can be stored in the history record 318 for calculating the probabilities 312 of the users 302 in the future.
The station user interface 210 can also provide an output to the active user 306 that can induce an expected movement from the active user 306. This movement by the active user 306 can be identified by the station sensor unit 208 as the station sensor data 224 as well as being identified by the beacon sensor unit 108 of FIG. 1 as the beacon sensor data 122.
Referring now to FIG. 4, therein is shown a graphical view of the beacon sensor data 122 of FIG. 1. The beacon sensor data 122 can be illustratively arranged having an accelerometer force 402 in standard deviations along a y-axis and time 404 along an x-axis.
The beacon sensor data 122 can be the force sensed by the beacon sensor unit 108 of FIG. 1. The beacon sensor data 122 can be graphed to have early readings of the beacon sensor data 122 on the left and readings of the beacon sensor data 122 later in time to the right. That is, the time 404 values of the x-axis move from earlier on the left to later on the right.
For ease of description the beacon sensor data 122 will be described of being comprised of accelerations from 406 to 426. The beacon sensor data 122 is depicted showing accelerations 406 and 408 in a negative direction, which is indicated by the accelerations 406 and 408 being below the average.
The accelerations 410, 412, and 414 are subsequently depicted in a positive direction, which is indicated by the accelerations 410, 412, and 414 being above the average. The accelerations 416 and 418 are subsequently depicted in a negative direction. Following the accelerations 416 and 418, the accelerations 420, 422, and 424 are depicted in a positive direction.
Lastly, acceleration 426 is depicted in a slightly negative direction. As can be appreciated, greater accelerations are depicted further away from the average while smaller accelerations are depicted closer to the average.
As is depicted the accelerations 406 to 426 are normalized by standard deviation, which allows the standard deviation to be a dimensionless measure of the accelerometer force 402. Further, the mean is depicted as subtracted from the standard deviations of the accelerations 406 to 426 allowing a depiction of negative values for the accelerometer force 402 when the accelerometer force 402 is either only positive or only negative.
It will be appreciated that normalizing the beacon sensor data 122 by standard deviation and subtracting the mean allows the beacon sensor data 122 detected as acceleration forces to be compared with the station sensor data 224 of FIG. 2 detected as motion. This will be evident from comparing the beacon sensor data 122 depicted in FIG. 4 with the station sensor data 224 depicted in FIG. 5.
That is, the beacon sensor data 122 detected as positive acceleration at the beacon sensor unit 108 can be normalized and shifted about the mean so that the accelerations can be viewed as positive and negative accelerations. The beacon sensor data 122 can be normalized and shifted in the beacon control unit 102 of FIG. 1 and stored in the beacon storage unit 104 of FIG. 1 before being transmitted to the station 200. Alternatively, the beacon sensor data 122 can be transmitted to the station 200 and can be normalized and shifted in the station control unit 202 of FIG. 2.
Referring now to FIG. 5, therein is shown a graphical view of the station sensor data 224 of FIG. 2. The station sensor data 224 can be illustratively arranged having a motion 502 in standard deviations along a y-axis and time 504 along an x-axis.
The station sensor data 224 can be the motion sensed by the station sensor unit 208 of FIG. 2. The station sensor data 224 could also be the rate-of-change of the motions sensed by the station sensor unit 208. When representing rate-of-change of motion, a still, slow, or fast motion maintained over a certain time will be seen as not changing or changing very little over that time, and a motion going from fast to slow or slow to fast, or changing directions, may be seen as a high motion rate-of-change.
Illustratively, the station sensor unit 208 could be a motion sensor like a thermopile. In this illustrative example, the station sensor unit 208 could detect an increase in heat in one sector of the station sensor unit 208 and a decrease in heat in a different sector of the station sensor unit 208.
Detecting an increase in heat or decrease in heat can be interrelated or independent. A change in the heat detected by the station sensor unit 208 could be correlated to movement of the active user 306 of FIG. 3. The increase in heat detected by the station sensor unit 208 can be viewed as positive motion where a decrease in heat can be viewed as negative motion.
The station sensor data 224 can be graphed to have early readings of the station sensor data 224 on the left and readings of the station sensor data 224 later in time to the right. That is, the time 504 values of the x-axis move from earlier on the left to later on the right.
For ease of description the station sensor data 224 will be described of being comprised of motions from 506 to 526. The station sensor data 224 is depicted showing motions 506 and 508 in a negative direction, which is indicated by the motions 506 and 508 being below the average.
The motions 510, 512, and 514 are subsequently depicted in a positive direction, which is indicated by the motions 510, 512, and 514 being above the average. The motions 516 and 518 are subsequently depicted in a negative direction. Following the motions 516 and 518, the motions 520 and 522 are depicted in a positive direction.
Lastly, motions 524 and 526 are depicted in a negative direction. As can be appreciated, larger motions are depicted further away from the average while smaller motions are depicted closer to the average.
As is depicted the motions 506 to 526 are normalized by standard deviation, which allows the standard deviation to be the dimensionless measure of the motion 502. Further, the mean is depicted as subtracted from the standard deviations of the motions 506 to 526 allowing a depiction of negative values for the motions 502 when the motion 502 is either only positive or only negative.
It will be appreciated that normalizing the station sensor data 224 by standard deviation and subtracting the mean allows the station sensor data 224 detected as motions to be compared with the beacon sensor data 122 of FIG. 1 detected as accelerations. This will be evident from comparing the station sensor data 224 depicted in FIG. 5 with the beacon sensor data 122 depicted in FIG. 4.
That is, the station sensor data 224 detected as positive motion at the station sensor unit 208 can be normalized and shifted about the mean so that the motions can be viewed as positive and negative motions. The station sensor data 224 can be normalized and shifted in the station control unit 202 of FIG. 2.
The station sensor data 224 can be compared with the beacon sensor data 122 to produce the scores 316 of FIG. 3. The scores 316 can be a measurement of how closely the station sensor data 224 matches or correlates to the beacon sensor data 122.
Multiple methods are contemplated for comparing the similarity of the beacon sensor data 122 to the station sensor data 224. One such method is the cross-correlation, which is commonly used for comparing one series of data collected over time to another such series. A higher correlation will produce a larger score 316 and indicate that the beacon 100 of FIG. 1 is more likely to be attached to the active user 306 that was performing the motions detected by the station sensor unit 208 of the station 200 of FIG. 2.
It is contemplated that when scores 316 are larger, the beacons 100 associated with the larger score 316 will be maintained as a candidate for the current user 314 of FIG. 3 on the Match_List 218 of FIG. 2. Conversely, when the scores 316 are lower, the beacons 100 associated with the lower score 316 might be removed as a candidate for the current user 314 on the Match_List 218.
It is contemplated that the beacon sensor data 122 for each of the beacons 100 can be compared to the station sensor data 224 to produce the scores 316 for each of the beacons 100. It is further contemplated that if only one of the beacons 100 is determined to have the score 316 indicating correlation between the beacon sensor data 122 and the station sensor data 224, then the user ID 116 of FIG. 1 of the correlating beacon 100 can be assigned or designated as the current user 314.
The history record 318 of FIG. 3 can then be updated with information about the current user 314. For example, when the compliance system 300 of FIG. 3 is implemented in a hand washing compliance system 300, the history record 318 could be updated to include not only information about the score 316 and probability 312 of FIG. 3 that the beacon 100 should be identified with the current user 314 but also information about the hand wash process itself, like how long the wash lasted, how many times the current user 314 washed during the day, and how many times the current user 314 used an alcohol scrub as an alternative to a soap and water wash. This information stored in the history record 318 can be used for later reporting and analysis.
Another contemplated method for comparing the beacon sensor data 122 with the station sensor data 224 are to compare Fourier transforms of the beacon sensor data 122 and the station sensor data 224. Yet another contemplated method for comparing the beacon sensor data 122 with the station sensor data 224 is to compare the spectrograms of the beacon sensor data 122 to the station sensor data 224.
In some contemplated embodiments, it would be helpful to de-noise the beacon sensor data 122 and the station sensor data 224. The beacon sensor data 122 and the station sensor data 224 can be de-noised for example, by subtracting out oscillations that are known to occur with motions other than the motions detectable by the station sensor unit 208.
Illustratively, when the compliance system 300 is used in a mobile platform where the users 302 of FIG. 3 are walking, the beacon sensor data 122 might capture the acceleration from the walking motion of the users 302. The beacon sensor data 122 oscillating at a frequency known to be generated by the users 302 walking could be filtered out, which could help to improve the accuracy of the score 316 and subsequently the probability 312 of correctly identifying the current user 314.
Other beacon sensor data 122 that can be filtered out can come from identifying or categorizing the beacon sensor data 122 as coming from other motions of the active user 306 such as a continued scrubbing motion. Although the beacon sensor data 122 indicating a scrubbing motion could be filtered out for purposes of correlating the beacon sensor data 122 to the station sensor data 224, the beacon sensor data 122 indicating a scrubbing motion could be used by the compliance system 300 to verify hand wash compliance.
In other contemplated embodiments, either the beacon sensor data 122 or the station sensor data 224 might repeat at double the frequency of the other. Means of comparing the beacon sensor data 122 with the station sensor data 224 in these situations is still possible. One such contemplated method for comparing the beacon sensor data 122 with the station sensor data 224 would be to determine the likelihood that the period of oscillation in one set of data is an integer multiple of the period of oscillation in the other set of data.
The correlation and de-noising can be performed on the station control unit 202 from raw data from the beacons 100. Alternatively, some or all of the correlations and de-noising could be performed on the beacon control unit 102 of FIG. 1 and transmitted to the station 200 along with the raw beacon sensor data 122.
Referring now to FIG. 6, therein is shown a graphical view of the station user interface 210 of FIG. 2. The station user interface 210 can be used to induce movement of the active user 306 of FIG. 3 to provide the beacon sensor data 122 of FIG. 1 and the station sensor data 224 of FIG. 2 to the user disambiguation block 310 of FIG. 3 for determining the current user 314 of FIG. 3.
The station user interface 210 is depicted as a screen including graphics. Illustratively, station user interface 210 can depict a game and provide instructions 602 to the active user 306 to control a space ship 604 with the motions of the active user 306 and to attempt to keep the space ship 604 from being hit by a comet 606.
The comet 606 is depicted hurdling toward the space ship 604. The instructions 602 can explain to the active user 306 that leaning to the left causes the space ship 604 to move to the left, whereas leaning to the right causes space ship 604 to move to the right.
It is contemplated that the station communication unit 206 of FIG. 2 can scan for the signals 308 of FIG. 3 transmitted by the beacons 100 of FIG. 1. The signals 308 from the beacons 100 can contain the beacon sensor data 122 of FIG. 1 including orientation and accelerometer forces.
Once the station 200 detects the beacon sensor data 122 that indicates one of the users 302 has moved in a way appropriate to avoid the comet, the station 200 will depict the space ship 604 as moving on the station user interface 210. Specifically, the beacon sensor data 122 indicating a change in the orientation of the beacon 100 with respect to gravity can be understood as a leaning motion.
The beacon sensor data 122 can convey to the station 200 a number of degrees that the orientation of the beacon 100 changed with respect to gravity. The station 200 can provide visual feedback to the active user 306 through the station user interface 210 by moving the space ship 604 more for a larger orientation change of the beacon 100 and less for a smaller orientation change of the beacon 100.
It is contemplated that the game displayed on the station user interface 210 can be designed to produce a specific movement. In the illustrative example of FIG. 6, the comet 606 hurdling toward the space ship 604 should elicit a left lean by the active user 306 because leaning right would move the space ship 604 closer to the path of the comet 606.
In this way, the user disambiguation block 310 of the station 200 can identify the active user 306 from the inactive users 304 of FIG. 3 because the inactive users 304 will not react to the station user interface 210 by leaning as the active user 306 is expected to.
It is contemplated that the station 200 can assign an initial motion of the active user 306 to be the specific motion elicited by the game. A motion by the active user 306 in the opposite direction will be assigned to a motion opposite the specific motion elicited by the game. In this way, the station 200 can recognize motions of the active user 306 and accurately control the space ship 604 even when the active user 306 is wearing the beacon 100 upside down or backwards.
It is contemplated that once the beacon 100 associated with the active user 306 is identified, the user ID 116 of FIG. 1 for the active user 306 can be correlated with the user name 220 of FIG. 2 and displayed to the active user 306 through the station user interface 210. Information specific to the active user 306 can also be provided to the active user 306 through the station user interface 210 such as displaying family photos, displaying messages that have arrived for the active user 306, or playing the active user's 306 favorite music. The active user 306 will also be identified as the current user 314 and information about the interaction of the current user 314 with the station 200 along with the beacon sensor data 122 for the current user 314 can be stored in the history record 318 of FIG. 3.
In the situation where none of the beacons 100 for the users 302 transmits the beacon sensor data 122 indicating a motion that would be expected by one of the users 302 actively engaging with the station user interface 210, the station 200 can assign the active user 306 an “Unknown ID”. This can be an indication that the active user 306 is not wearing the beacon 100 or that the beacon 100 may be non-functional.
If the active user 306 is assigned the Unknown ID, the station 200 can prompt the active user 306 to display a hand sign that the active user 306 can later display to their phone to claim credit for interacting with the station 200. When the active user 306 is verified the information for the interaction of the active user 306 with the station 200 can be stored in the history record 318 for the active user 306.
Further it is contemplated that when the user disambiguation block 310 initially identifies the user ID 116 of the active user 306 having a lower probability 312 of FIG. 3, and subsequently determines that the score 316 of FIG. 3 for the correlation between the beacon sensor data 122 and the station sensor data 224 is too low, the station 200 can change from displaying the user ID 116 to the Unknown ID.
Referring now to FIG. 7, therein is shown a user engagement control flow 700 for the compliance system 300 of FIG. 3. The engagement control flow 700 is contemplated to illustrate an embodiment of the compliance system 300 when implemented with a hand wash compliance system.
The engagement control flow 700 can illustrate how the active user 306 of FIG. 3 engages with the station 200 of FIG. 2. In an initialize step 702, the users 302 of FIG. 3 can attach the beacons 100 of FIG. 1 to their persons and power the beacons 100 on.
Further in the initialize step 702 it is contemplated that the active user 306 will approach the station 200. The inactive users 304 of FIG. 3 can also proceed near the station 200.
When the active user 306 approaches the station 200, the station 200 can proceed to a detection step 704. The detection step 704 can detect the beacon sensor data 122 of FIG. 1 transmitted by the signal 308 of FIG. 3 from the beacon communication unit 106 of FIG. 1.
The detection step 704 can also be implemented to detect the station sensor data 224 of FIG. 2 from the station sensor unit 208 of FIG. 2 indicating the motions of the active user 306.
The station 200 can then initiate a process step 706. The process step 706 can be used to process the beacon sensor data 122 and the station sensor data 224 in the user disambiguation block 310 of FIG. 3 to provide the user ID 116 of FIG. 1 and the user names 220 of FIG. 2. The process step 706 can further provide an analysis of the hand washing compliance of the active user 306 and display the analysis to the active user 306 with the station user interface 210 of FIG. 2.
In the situation where the station 200 is used by multiple users 302 one after another, the process step 706 can be completed by the station 200 for the active user 306 then the station 200 could initiate the detection step 704 again for subsequent users 302.
Referring now to FIG. 8, therein is shown a control flow of the detection step 704 of FIG. 7. The detection step 704 can be initiated by a begin wash step 802 once the active user 306 of FIG. 3 approaches the station 200 of FIG. 2 in the initialize step 702 of FIG. 7.
In the begin wash step 802, the active user 306 can use soap and water and wash in a sink. The begin wash step 802 can also display the instructions 602 of FIG. 6 on the station user interface 210 of FIG. 2 instructing the active user 306 to begin washing.
The begin wash step 802 can trigger the station 200 to initiate a scan step 804. The scan step 804 can utilize the station sensor unit 208 of FIG. 2 to scan for motions or presence of the active user 306.
The scan step 804 can produce the station sensor data 224 of FIG. 2, which can be analyzed to determine whether the active user 306 is performing a hand washing motion in a detection decision step 806. The scan step 804 can also utilize the station communication unit 206 of FIG. 2 to scan for the signals 308 of FIG. 3 transmitted by the beacons 100 of FIG. 1.
The scan step 804 can send the station sensor data 224 to the detection decision step 806 triggering the detection decision step 806. If the detection decision step 806 determines that the active user 306 is not performing a hand washing motion, then the scan step 804 will be triggered again and the station 200 will attempt to detect the station sensor data 224 that will indicate that the active user 306 is performing a hand washing motion. If the detection decision step 806 determines that the active user 306 is performing a hand washing motion, then the station 200 will initiate the process step 706 of FIG. 7.
Referring now to FIG. 9, therein is shown a control flow of the process step 706 of FIG. 7. The process step 706 can begin with a countdown step 902 which can begin once the process step 706 detects a hand washing motion of the active user 306 of FIG. 3.
The countdown step 902 can initialize the station counter 212 of FIG. 2 for the station 200 of FIG. 2. The countdown step 902 can set the station counter 212 to the minimum time required for a compliant hand wash. Illustratively, this could be 30 seconds.
The countdown step 902 will also begin the counting down using the station counter 212 and can display the remaining time on the station user interface 210 of FIG. 2 to the active user 306. The countdown step 902 can update the station user interface 210 with a current countdown from the station counter 212.
Along with displaying the remaining time on the station user interface 210, the station 200 can also display a score of hand wash compliance, a game, a progress bar, or a combination thereof. Once the countdown of the station counter 212 is begun in the countdown step 902, the station 200 can initiate a user identification step 904.
The user identification step 904 can implement the user disambiguation block 310 of FIG. 3 to determine the current user 314 and to correlate the current user 314 with the user ID 116 of FIG. 1 and the user names 220 of FIG. 2. During the user identification step 904, the station 200 can correlate the station sensor data 224 of FIG. 2 with the beacon sensor data 122 of FIG. 1, analyze the RSSI 222 of FIG. 2, and update the Match_List 218 of FIG. 2 to determine which of the users 302 is the most likely candidate for the current user 314.
The station 200 can initiate a countdown decision step 906. If the countdown decision step 906 determines that the countdown of the station counter 212 has completed, the station 200 can implement a display and process step 908.
The display and process step 908 can process the station sensor data 224 and isolate the motions of the active user 306 that result from hand washing motions. The display and process step 908 can process this station sensor data 224 and determine the level of hand washing compliance for the active user 306.
The display and process step 908 can update the station user interface 210 indicating to the active user 306 that the hand washing is complete. During the display and process step 908, the station user interface 210 can display a final score and the total number of scrubs along with a reward screen.
Once the display and process step 908 has processed the motions of the active user 306 for hand washing compliance, the station 200 can upload the results of the compliance to the history record 318 of FIG. 3. The station 200 can then proceed to the begin wash step 802 of FIG. 8 for detecting whether another one of the users 302 of FIG. 3 is beginning to engage with the station 200.
If the countdown decision step 906 determines that the countdown of the station counter 212 has not finished, the station 200 can initiate a scrubbing decision step 910. The scrubbing decision step 910 can determine whether the active user 306 is continuing to wash or whether the active user 306 has stopped washing. If the scrubbing decision step 910 determines that the active user 306 has stopped washing, a process step 912 can be initiated by the station 200 to analyze the station sensor data 224 for scrubbing motions.
The process step 912 can process the station sensor data 224 and isolate the motions of the active user 306 that result from hand washing motions. The process step 912 can process this station sensor data 224 and determine the level of hand washing compliance for the active user 306.
Once the process step 912 has processed the motions of the active user 306 for hand washing compliance, the station 200 can upload the results of the compliance to the history record 318. The station 200 can then proceed to the begin wash step 802 for detecting whether another one of the users 302 is beginning to engage with the station 200.
If the scrubbing decision step 910 determines that the active user 306 is continuing to wash, the station 200 can initiate an ID decision step 914. If the ID decision step 914 determines that the user disambiguation block 310 from the user identification step 904 has identified the user ID 116 of the active user 306 that is valid from the user ID table 216 of FIG. 2, the station 200 can initiate a display name step 916.
The display name step 916 can display the user name 220 of the active user 306 on the station user interface 210. Further, the display name step 916 can also display previous performance or hand washing compliance records for the active user 306.
Once the display name step 916 displays the information for the active user 306 on the station user interface 210, the station 200 can again trigger the countdown decision step 906. If the ID decision step 914 determines that the user disambiguation block 310 has not yet been able to identify the current user 314, then the station 200 will again initiate the user identification step 904.
Referring now to FIG. 10, therein is shown a communication control flow 1000 for the user identification step 904 of FIG. 9. The communication control flow 1000 can illustrate the process by which the station 200 of FIG. 2 and the beacons 100 of FIG. 1 communicate during the user identification step 904.
It is contemplated that the steps of the communication control flow 1000 can be executed by the beacon control unit 102 of FIG. 1 for each of the beacons 100 and that the beacons 100 can store and set values of the beacon parameters 120 in the beacon storage unit 104 of FIG. 1. It is contemplated that the station communication unit 206 of FIG. 2 can communicate with the beacons 100 and provide instructions for the beacons 100 that will be executed by the beacon control unit 102 of the beacons 100.
Additionally, it is contemplated that the beacons 100 could execute the communication control flow 1000 independently of communication from the station 200. The communication control flow 1000 can begin with a beacon initialization step 1002. The beacon initialization step 1002 can initialize the beacons 100 for the first time or when the beacons 100 are first powered on.
The beacon initialization step 1002 can set the beacon parameters 120. For example, the beacon initialization step 1002 can set the beacon parameter 120, CLK_PREV 1004, to the current time. The beacon initialization step 1002 can further set the beacon parameter 120, T_BEEP 1006, to a previous time, such as zero when using Coordinated Universal Time (UTC). It is contemplated that T_BEEP 1006 can be set to a time in the distant past.
The T_BEEP 1006 is the time at which the beacon user interface 110 of FIG. 1 will emit an audio or visual queue such as a beep. Setting the T_BEEP 1006 to a previous time ensures that the beacon 100 will not emit the audio or visual queue.
The communication control flow 1000 can proceed from the beacon initialization step 1002 to an array initialization step 1008. During the array initialization step 1008, the station 200 can instruct the beacons 100 to create a wait time interval array 1010 and set the beacon parameters 120 other than the CLK_PREV 1004 and the T_BEEP 1006.
The wait time interval array 1010 can include wait times 1012. The wait time interval array 1010 is depicted having wait times 1012 one through eight. The wait times 1012 can be an amount of time that the beacon 100 waits before various procedures.
The wait times 1012 can be stored in the beacon storage unit 104 and measured using the beacon counter 112 of FIG. 1 in the beacon control unit 102. The wait times 1012 can be generated in compliance with beacon parameters 120 set prior to the creation of the wait time interval array 1010.
It is contemplated that the beacon parameter 120, NT 1014, can be set within the beacon 100 and can specify the total number of the wait times 1012 within the wait time interval array 1010. Further beacon parameters 120, WR_MIN 1016 and WR_MAX 1018, can be set within the beacon 100 and provide upper and lower bounds for the first wait time 1012 depicted as WT_0 in the wait time interval array 1010 and the last wait time 1012 depicted as WT_7 in the wait time interval array 1010.
The first and the last wait times 1012 within the wait time interval array 1010 can be the length of time that the beacon 100 waits after transmitting the signal 308 of FIG. 3 before initiating a receive window during which time the beacon communication unit 106 of FIG. 1 can receive the signal 308 from the station 200.
It is contemplated that the first and last wait times 1012 can be randomly generated by the beacon control unit 102 and stored within the beacon storage unit 104. The first and last wait times 1012 can be randomly generated to provide a length of time between the WR_MIN 1016 and WR_MAX 1018.
Illustratively, if WR_MIN 1016 is set to one second and WR_MAX 1018 is set to two seconds, then the beacon control unit 102 might generate the first and last wait times 1012 of 1.4 seconds and 1.2 seconds. Further beacon parameters 120, WT_MIN 1020 and WT_MAX 1022, can be set within the beacon 100 and provide upper and lower bounds for the middle wait times 1012 between the first and last wait times 1012.
The middle wait times 1012 are depicted as WT_1, WT_2, WT_3, WT_4, WT_5, and WT_6 in the wait time interval array 1010. The middle wait times 1012 within the wait time interval array 1010 can be the length of time the beacon 100 waits between the transmissions of the signal 308 from the beacon communication unit 106 to the station 200.
It is contemplated that the middle wait times 1012 can be randomly generated by the beacon control unit 102 and stored within the beacon storage unit 104. The middle wait times 1012 can be randomly generated to provide a length of time between the WT_MIN 1020 and WT_MAX 1022.
Illustratively, if WT_MIN 1020 is set to one second and WT_MAX 1022 is set to two seconds, then the beacon control unit 102 might generate the middle wait times 1012 of 1.3 seconds, 1.9 seconds, etc.
During the array initialization step 1008, the beacon 100 can also set the beacon parameter 120 CLK_WSTART 1024 to the current time. The CLK_WSTART 1024 can be the time at which the beacon 100 started processing a newly generated wait time interval array 1010 of wait times 1012.
During the array initialization step 1008, the beacon 100 can also set the beacon parameter 120 CLK_WPREV 1026 to the CLK_WSTART 1024. The CLK_WPREV 1026 can be the time that the beacon 100 started the current wait.
During the array initialization step 1008, the beacon 100 can also set the beacon parameter 120 W_REM 1028 to the sum of all the wait times 1012. During the array initialization step 1008 the beacon 100 can also set the beacon parameter 120 C_ACC 1030 to zero.
The C_ACC 1030 can be the total time that has elapsed since the beacon 100 started processing the current wait time interval array 1010 of wait times 1012. During the array initialization step 1008, the beacon 100 can also set the beacon parameter 120 CWI 1032 to zero.
The CWI 1032 can point to one of the wait times 1012 in the wait time interval array 1010 that the beacon 100 is currently processing and waiting for. The CWI 1032 can be incremented to index through the wait times 1012.
For example, when the CWI 1032 is set to zero in the array initialization step 1008, the beacon 100 will be indexed to process and wait according to WT_0. As the CWI 1032 is incremented, the beacon 100 will index to a different wait time 1012. For example, when the CWI 1032 is incremented to one, the beacon 100 will index to WT_1, when the CWI 1032 is incremented to two the beacon 100 will index to WT_2, and when the CWI 1032 is incremented to NT 1014, the beacon 100 will index to WT_NT, which is illustratively depicted as WT_7.
The communication control flow 1000 can proceed from the array initialization step 1008 to a sending step 1034. During the sending step 1034, the beacons 100 can activate and prepare messages that can be broadcast in the signal 308 with the beacon communication unit 106 to the station 200.
The communication control flow 1000 can proceed from the sending step 1034 to a receiving step 1036. During the receiving step 1036, the beacons 100 can receive and process messages broadcast in the signal 308 from the station 200. Once the receiving step 1036 is complete, the beacon 100 can proceed back to the array initialization step 1008.
Referring now to FIG. 11, therein is shown a control flow of the sending step 1034 of FIG. 10. The sending step 1034 can begin with an elapsed time decision step 1102. The elapsed time decision step 1102 can follow the array initialization step 1008 of FIG. 10.
The elapsed time decision step 1102 can compare the beacon parameters 120: CLK_PREV 1004 of FIG. 10, CLK_WSTART 1024 of FIG. 10, and C_ACC 1030 of FIG. 10 to T_BEEP 1006 of FIG. 10. Specifically, the elapsed time decision step 1102 checks to determine whether CLK_PREV 1004 is less or equal to T_BEEP 1006.
If CLK_PREV 1004 is greater than T_BEEP 1006, this indicates that the previous time the beacon 100 of FIG. 1 executed elapsed time decision step 1102 was after T_BEEP 1006 was set to go off. If CLK_PREV 1004 is less than or equal to T_BEEP 1006, this indicates that the previous time the beacon 100 executed the elapsed time decision step 1102 was before T_BEEP 1006 is set to go off.
If CLK_WSTART 1024+C_ACC 1030 is greater than T_BEEP 1006, this indicates that the current time the beacon 100 is executing the elapsed time decision step 1102 is after the T_BEEP 1006 was set to go off. If CLK_WSTART 1024+C_ACC 1030 is less than or equal to T_BEEP 1006, this indicates that the current time the beacon 100 is executing the elapsed time decision step 1102 is before the T_BEEP 1006 is set to go off.
The result of the elapsed time decision step 1102 will be to determine whether the previous execution was before or at the same time as T_BEEP 1006 and the current execution is after T_BEEP 1006. When this is the case the beacon 100 will execute a beep step 1104. The beep step 1104 can trigger the beacon user interface 110 of FIG. 1 to provide an audio or visual indicator to the user 302 of FIG. 3.
The beep step 1104 can also set CLK_PREV 1004 to CLK_WSTART 1024+C_ACC 1030. Setting CLK_PREV 1004 to CLK_WSTART 1024+C_ACC 1030 updates CLK_PREV 1004 to the time the beep step 1104 is executed providing the elapsed time decision step 1102 an updated CLK_PREV 1004 for comparison in a subsequent execution of the elapsed time decision step 1102.
When the elapsed time decision step 1102 determines that the previous execution of the elapsed time decision step 1102 was not before or at the same time as T_BEEP 1006 or the current execution is not after T_BEEP 1006, the beacon 100 will execute a timer set step 1106 and will not execute beep step 1104.
It will be appreciated that when T_BEEP 1006 is set to a past time in the beacon initialization step 1002 of FIG. 10, the elapsed time decision step 1102 will determine that the previous execution of the elapsed time decision step 1102 was not before or was not at the same time as T_BEEP 1006, which can prevent the beacon 100 from executing the beep step 1104.
The beacon 100 can proceed from the elapsed time decision step 1102 to the timer set step 1106 when the result of elapsed time decision step 1102 is negative, and the beacon 100 can proceed from executing the beep step 1104 to executing the timer set step 1106. The timer set step 1106 can set the C_ACC 1030 to C_ACC 1030+WT_[CWI]. That is, C_ACC 1030 is set to C_ACC 1030 plus the currently indexed wait time 1012 of FIG. 10.
The timer set step 1106 can subsequently set the beacon counter 112 of FIG. 1 to wake the beacon 100 at a wake time CLK_WSTART 1024+C_ACC 1030. The beacon 100 can proceed from the timer set step 1106 to an index step 1108.
The index step 1108 can set the beacon parameter 120, W_REM 1028 of FIG. 10, to W_REM 1028−WT_[CWI]. That is, W_REM 1028 minus the currently indexed wait time 1012, which can be used as an indication of how long until the beacon communication unit 106 of FIG. 1 of the beacon 100 will be ready to receive the signal 308 of FIG. 3 from the station 200 of FIG. 2. The index step 1108 can also increment CWI 1032 for indexing to the next wait time 1012. That is, CWI 1032=CWI 1032+1.
Once the beacon 100 executes the index step 1108, the beacon 100 can proceed to enter a low power state in a very-low-power step 1112. The beacon 100 can remain in the low power state until the beacon counter 112 completes the time set in the timer set step 1106.
Once the beacon counter 112 finishes the count set in the timer set step 1106, the beacon 100 can execute a wake step 1114. The wake step 1114 can bring the beacon 100 out of the low power state initiated in the very-low-power step 1112.
After the beacon 100 wakes in the wake step 1114, the beacon 100 can execute an indexing decision step 1116. The indexing decision step 1116 can determine whether CWI 1032=NT 1014 of FIG. 10. That is, whether the current indexed wait time 1012 is the last wait time 1012 of the wait time interval array 1010 of FIG. 10.
When the indexing decision step 1116 determines that CWI 1032 does not equal NT 1014, the last wait time 1012 of the wait time interval array 1010 has not been reached and the beacon 100 can proceed to execute a message preparation step 1118.
During the message preparation step 1118, the beacon 100 can create a message 1120 that can be stored in the beacon storage unit 104 of FIG. 1 for later transmission to the station 200. The message 1120 can include the user ID 116 of FIG. 1 along with the W_REM 1028 set in index step 1108.
Providing the W_REM 1028 in the message 1120 indicates to the station 200 when the beacon 100 will execute the receiving step 1036 of FIG. 10 and thereby be in a listening state ready to receive the signal 308 from the station 200. It is further contemplated that the beacon 100 can insert the beacon sensor data 122 of FIG. 1, such as acceleration forces into the message 1120 if the beacon 100 is currently parametrized to do so.
The beacon 100 can include the beacon parameter 120 W_P 1122. The W_P 1122 can be the power at which the message 1120 is transmitted at.
Once the beacon 100 executes the message preparation step 1118, the beacon 100 can proceed to execute a broadcast step 1124. The broadcast step 1124 can power up the beacon communication unit 106 and broadcast the signal 308 containing the message 1120 at the specified power W_P 1122.
The beacon 100 will proceed from the broadcast step 1124 back to the elapsed time decision step 1102. The beacon 100 will continue to cycle through the sending step 1034 until the indexing decision step 1116 determines that CWI 1032=NT 1014.
That is, until the current indexed wait time 1012 is the last wait time 1012 of the wait time interval array 1010. When the current indexed wait time 1012 is the last wait time 1012 of the wait time interval array 1010, the beacon 100 will proceed to the receiving step 1036.
Referring now to FIG. 12, therein is shown a control flow of the receiving step 1036 of FIG. 10. During the receiving step 1036, the beacon 100 of FIG. 1 can wake or activate the beacon communication unit 106 of FIG. 1 to operate in a receive mode in a wake step 1202.
Further, during the wake step 1202, the beacon 100 can set the beacon parameter 120 of FIG. 1, CLK_RSTART 1204, to the current time. The CLK_RSTART 1204 can indicate the time that the beacon communication unit 106 started operating in a receive mode.
Yet further, during the wake step 1202, the beacon 100 can set the beacon parameter 120, W_R 1206. The W_R 1206 can be a short time window, but a time window that is long enough to receive the shortest message 1120 of FIG. 11 being repeated out of phase by the station 200 of FIG. 2.
The beacon counter 112 of FIG. 1 can countdown the W_R 1206 length of time and then proceed to execute a wait step 1208. During the wait step 1208, the beacon 100 can wait for the message 1120 to be received from the station 200.
The wait step 1208 can wait for a length of time R_PIECE 1210. The R_PIECE 1210 can be one of the beacon parameters 120 representing the interval between repetitions of the receiving step 1036. The beacon counter 112 can countdown through the R_PIECE 1210 time length.
Once the beacon 100 completes the R_PIECE 1210 wait time, the beacon 100 can proceed to a message received decision step 1212. The message received decision step 1212 can determine whether the beacon 100 has received the message 1120 from the station 200 during the wait step 1208.
If the message received decision step 1212 determines that the message 1120 has not been received by the beacon 100 during the wait step 1208, the beacon 100 will execute a receive window decision step 1214. The receive window decision step 1214 can determine whether the current time is greater than CLK_RSTART 1204+WR 1216.
The beacon parameter 120, WR 1216, can be a length of time of a listening window for the beacon 100. That is, WR 1216 can be how long the beacon communication unit 106 should operate in the receive mode.
The CLK_RSTART 1204 plus the WR 1216 can be a time that the beacon 100 should be done operating in a receive mode. If the current time is greater than the CLK_RSTART 1204+the WR 1216, the beacon 100 will initiate the array initialization step 1008 of FIG. 10. If the current time is less than or equal to the CLK_RSTART 1204+the WR 1216, the beacon 100 will again execute the wait step 1208.
If the message 1120 is being received by the beacon 100 at the moment the current time reaches CLK_RSTART 1204+the WR 1216 then the beacon 100 may include the function of waiting for the current message 1120 from the station 200 to finish being received before deactivating the receiver in the beacon communication unit 106 of FIG. 1 and checking to see if the beacon parameters 120 should be modified based on the message 1120. If the message received decision step 1212 determines that the message 1120 has been received by the beacon 100 during the wait step 1208, the beacon 100 will execute a current beacon decision step 1218.
During the current beacon decision step 1218 the beacon 100 can check the message 1120 to determine whether the station 200 has designated the beacon 100 by including the user ID 116 of FIG. 1 of the beacon 100 in the message 1120.
If the message 1120 from the station 200 does not include the user ID 116 designating the beacon 100, the beacon 100 will again execute the receive window decision step 1214. If the message 1120 from the station 200 does include the user ID 116 designating the beacon 100, the beacon 100 will execute a processing step 1220.
During the processing step 1220, the beacon 100 will process the message 1120 from the station 200 received during the wait step 1208. The message 1120 from the station 200 can update the beacon parameters 120.
For example, the message 1120 could require the beacon 100 to send specific beacon sensor data 122 of FIG. 1 such as acceleration forces detected by the beacon sensor unit 108 of FIG. 1. In such a case the beacon 100 could power up the beacon sensor unit 108 to detect acceleration forces to be transmitted to the station 200 during the sending step 1034 of FIG. 10.
During the processing step 1220, the station 200 can modify the beacon parameters 120 controlling the length of the beacon's 100 listening window, controlling how frequently and strongly the beacon 100 broadcasts the message 1120 to the station 200, and controlling how frequently the beacon 100 operates with the beacon communication unit 106 activates the listening window.
It is contemplated that the beacon 100 can have a parameter timeout 1222. When the parameter timeout 1222 is triggered the beacon 100 can switch back to previously saved beacon parameters 120.
It is contemplated that implementing the parameter timeout 1222 allows previously saved beacon parameters 120 to be reverted. The previously saved beacon parameters 120 can include the beacon parameters 120 controlling frequencies, wait times, transmission strengths, and which portions of the beacon 100 should be operated such as the beacon sensor unit 108, the beacon storage unit 104 of FIG. 1, or the beacon communication unit 106. Once the beacon 100 executes the processing step 1220, the beacon 100 can again execute the array initialization step 1008.
Referring now to FIG. 13, therein is shown a control flow of the processing step 1220 of FIG. 12. The processing step 1220 depicts the steps by which the beacon parameters 120 of FIG. 1 for the beacon 100 of FIG. 1 are updated.
The beacon parameters 120 may control the frequency with which the beacon 100 broadcasts. For example, the beacon 100 could transmit the signal 308 of FIG. 3 containing the message 1120 of FIG. 11 with the beacon communication unit 106 of FIG. 1 once per second, ten times per second, or once per minute.
The beacon parameters 120 may also control the power with which the beacon 100 broadcasts. For example, the beacon 100 could broadcast the signal 308 containing the message 1120 with the beacon communication unit 106 with a specific milliwatt in decibels.
The beacon parameters 120 may also control how frequently with which the beacon 100 provides the listening window of the wait step 1208 of FIG. 12. For example, the beacon 100 could execute a listening window by waiting for the R_PIECE 1210 of FIG. 12 in the wait step 1208 once for every ten times the beacon 100 broadcasts while executing the broadcast step 1124 of FIG. 11.
The beacon parameters 120 may also control the length of time with which the beacon 100 provides the listening window of the wait step 1208. For example, the beacon 100 could execute a listening window by waiting for the R_PIECE 1210 in the wait step 1208 for 1 millisecond, 100 microseconds, or 1 second.
It has been discovered that a random arrangement in time of broadcast and listening windows helps reduce the chances that multiple beacons 100 will repeatedly broadcast the signal 308 to the station 200 of FIG. 2 at the same time or will repeatedly listen for the signal 308 from the station 200 at the same time. It is contemplated that the beacon parameters 120 can include minimum and maximum lengths of time between broadcasts or listening windows and that the beacon 100 itself may assign an actual amount of time as a random number taken between these two limits.
Illustratively, as previously set forth, the station 200 can include the WT_MIN 1020 of FIG. 10 and the WT_MAX 1022 of FIG. 10 in the message 1120 sent to the beacons 100. The WT_MIN 1020 and the WT_MAX 1022 can be lower and upper bounds, respectively.
Further, the WT_MIN 1020 and the WT_MAX 1022 can be used by the beacon 100 to randomly set the wait times 1012 of FIG. 10 between the broadcasts in the broadcast step 1124. It is contemplated that the station 200 could further provide other minimum and maximum beacon parameters 120 that the beacons 100 could utilize to randomly generate a random arrangement in time of the broadcast and listening windows.
It is contemplated that the station 200 could send minimum and maximum beacon parameters 120 that the beacon 100 could use to randomly generate times between listening windows during the receiving step 1036 of FIG. 10. It is further contemplated that the station 200 could send minimum and maximum beacon parameters 120 that the beacon 100 could use to randomly generate the length of listening windows during the receiving step 1036.
These minimum and maximum beacon parameters 120 could be set to the same value, which would indicate a constant length for the listening window without randomness. It is contemplated that the minimum and maximum beacon parameters 120 of the message 1120 could be the same for some of the beacon parameters 120 as a default, in which case, two separate values for the beacon parameters 120 could indicate a special case when randomness is requested by the station 200. The default of identical lengths can decrease the typical size of the message 1120 that is communicated by the station 200 with the beacon parameters 120.
It is further contemplated that the station 200 could send minimum and maximum beacon parameters 120 that the beacon 100 could use to randomly generate the length of transmission windows during the broadcast step 1124. These minimum and maximum beacon parameters 120 could be set to the same value, which would indicate a constant length for the listening window without randomness.
It is contemplated that the minimum and maximum beacon parameters 120 of the message 1120 could be the same for some of the beacon parameters 120 as a default, in which case, two separate values for the beacon parameters 120 could indicate a special case when randomness is requested by the station 200. The default of identical lengths can decrease the typical size of the message 1120 that is communicated by the station 200 with the beacon parameters 120. It is contemplated that the station 200 could broadcast the message 1120 containing the beacon parameters 120 repeatedly.
It has been discovered that repeatedly transmitting the message 1120 in the signal 308 by the station 200 can ensure that the beacons 100 will be able to receive the message 1120 once the randomly generated listening window for the beacon 100 is activated during the wait step 1208. It has further been discovered that repeatedly transmitting the message 1120 in the signal 308 from the station 200 to the beacons 100 implementing randomized receive windows enables accurate communication between the station 200 and the beacons 100 even when communication latencies resulting with the station 200 not knowing the exact moment when the listening window for the beacon 100 begins, such as accuracy to the millisecond but not microsecond due to out-of-synch clocks between the beacon 100 and the station 200.
The processing step 1220 is depicted having a start processing step 1302. The start processing step 1302 can be initiated and executed by the beacon 100 after an affirmative result from the current beacon decision step 1218 of FIG. 12.
The start processing step 1302 can be executed during the beacon's 100 listening window during the receiving step 1036. During the start processing step 1302 the beacon 100 can store the message 1120 using the beacon storage unit 104 of FIG. 1, can decode the message 1120 from the signal 308 using the beacon control unit 102 of FIG. 1, or can isolate portions of the message 1120 and de-noise the message 1120 using the beacon control unit 102.
It is contemplated that the start processing step 1302 could include the current beacon decision step 1218. It is further contemplated that the current beacon decision step 1218 could be performed initially or in a different order. It is yet further contemplated it is contemplated that the station 200 could encrypt or digitally sign the message 1120 so that the station 200 can be identified by the beacon 100.
The beacon 100 could decrypt or verify the digital signature of the station 200 during the start processing step 1302. It is further contemplated that the station 200 could include a message ID 1304 within the message 1120 sent from the station 200 to the beacon 100.
It has been discovered that including the message ID 1304 in the message 1120 can allow the station 200 to repeatedly broadcast the similar messages 1120 with identical instructions for the beacon 100 to modify or not modify the beacon parameters 120 and can be used by the beacon 100 to prevent the beacon 100 from acting on the same message 1120 multiple times even when the same message 1120 is received by the beacon 100 multiple times. The beacon 100 can execute a modified parameters decision step 1306 once the start processing step 1302 is complete.
The modified parameters decision step 1306 can determine whether the message 1120 from the station 200 instructs the beacon 100 to modify the beacon parameters 120 with modified beacon parameters 1308. If the message 1120 from the station 200 indicates that the beacon 100 should use the modified beacon parameters 1308, then the beacon 100 executes a save modified parameter step 1310.
During the save modified parameter step 1310, the beacon 100 can save the modified beacon parameters 1308 contained in the message 1120 received by the beacon 100 from the station 200 during the receiving step 1036. The new beacon parameters 120 can be saved in the beacon storage unit 104 and utilized by the beacon 100.
It is contemplated that the message 1120 could additionally contain a data payload and the beacon state 114 of FIG. 1, which the can prompt the beacon control unit 102 to change the beacon state 114 of the beacon 100 in order to process the data payload. Prompting the beacon 100 to process the data payload can require the beacon 100 to process the data payload before initiating a modified restart step 1312.
Alternatively, after the modified beacon parameters 1308 are saved in the save modified parameter step 1310 the beacon 100 can execute the modified restart step 1312. The modified restart step 1312 can restart the beacon 100 with the modified beacon parameters 1308 and specifically the beacon 100 can proceed to execute the array initialization step 1008 of FIG. 10 utilizing the modified beacon parameters 1308.
If the message 1120 from the station 200 indicates that the beacon 100 should use old beacon parameters 1314, then the beacon 100 executes a cancel modified parameter step 1316. During the cancel modified parameter step 1316 the beacon 100 can cancel the use of the modified beacon parameters 1308.
The beacon 100 can proceed from the cancel modified parameter step 1316 to a set old parameters step 1318. The set old parameters step 1318 can set the beacon parameters 120 to the old beacon parameters 1314.
For example, the modified beacon parameters 1308 that the beacon 100 could have saved during a previous execution of the save modified parameter step 1310, can be replaced by the old beacon parameters 1314 so that the modified beacon parameters 1308 are no longer used by the beacon 100. It is contemplated that the station 200 could send the message 1120 indicating that the modified beacon parameters 1308 should no longer be used when the result of the user disambiguation block 310 of FIG. 3 indicates that the beacon 100 does not belong to the active user 306 of FIG. 3.
When the user disambiguation block 310 of the station 200 determines that any of the beacons 100 belong to the inactive users 304 of FIG. 3 rather than the active user 306, all of the beacons 100 belonging to the inactive users 304 can revert to the old beacon parameters 1314. It has been discovered that reverting to the old beacon parameters 1314 for the beacons 100 coupled to the inactive users 304 can significantly reduce the power consumed by the beacons 100.
It has been discovered that the modified beacon parameters 1308 can significantly aid in determining which of the beacons 100 belongs to the active user 306 but at the expense of using more power. For example, disambiguation accuracy improves and beacon power consumption increases if the modified beacon parameters 1308 are utilized to change the power at which the signal 308 is broadcast from the beacon 100 from −10 decibel-milliwatts (dBm) to 4 dBm, or if the modified beacon parameters 1308 are utilized to change the frequency at which the signal 308 is broadcast from the beacon 100 from 1 Hz to 10 Hz.
It has been discovered that by utilizing the old beacon parameters 1314, which reduce the power consumption of the beacon 100 when disambiguation is not needed, the power consumption cost of falsely identifying the beacons 100 as candidates for the current user 314 of FIG. 3 is minimized. Once the beacon 100 sets the old beacon parameters 1314 in the set old parameters step 1318 the beacon 100 can execute an old restart step 1320.
The old restart step 1320 can restart the beacon 100 with the old beacon parameters 1314 and proceed to the array initialization step 1008 utilizing the old beacon parameters 1314. The old beacon parameters 1314 can allow the beacon 100 to return to less frequent operation of the listening window, less frequent broadcast, and less powerful broadcast.
The old beacon parameters 1314 can also indicate that the beacon 100 should no longer activate the beacon sensor unit 108 of FIG. 1 to generate the beacon sensor data 122 of FIG. 1 or to include the beacon sensor data 122 in the message 1120 broadcast from the beacon 100. The old beacon parameters 1314 can place the beacon sensor unit 108 into a low power or inactive state.
Referring now to FIG. 14, therein is shown a control flow of the user identification step 904 of FIG. 9. The user identification step 904 can be an illustrative embodiment of how the station 200 of FIG. 2 identifies the current user 314 of FIG. 3 as the active user 306 of FIG. 3 and distinguishes the active user 306 from the inactive users 304 of FIG. 3. The user identification step 904 can implement the communication control flow 1000 of FIG. 10 to control and direct the communications between the station 200 and the beacons 100 of FIG. 1.
The user identification step 904 is depicted having a start identification step 1402. The start identification step 1402 sets station parameters 1404. The station parameters 1404 can be variables set by the station control unit 202 of FIG. 2 and stored in the station storage unit 204 of FIG. 2.
The start identification step 1402 sets one of the station parameters 1404, T_SC 1406, to zero. The T_SC 1406 can be the current amount of time that has elapsed since the active user 306 began interacting with the station 200 such as in the begin wash step 802 of FIG. 8. The start identification step 1402 can further set the station parameter 1404, B1_R 1408.
The B1_R 1408 can be the best RSSI 222 of FIG. 2 of the signals 308 of FIG. 3 sent from the beacons 100 that the station 200 has received so far during the active user's 306 interaction with the station 200. The B1_R 1408 can be set to a very low number.
It is contemplated that the B1_R 1408 should be set to a number that is lower than any expected RSSI 222 from a beacon 100 near the station 200. For example, the B1_R 1408 can be set to −300 dBm. This can ensure that any RSSI 222 received from the beacons 100 will be higher than B1_R 1408.
The start identification step 1402 can further set the Match_List 218 of FIG. 2 to empty. This can clear the Match_List 218 and enable a new Match_List 218 to be built from the users 302 of FIG. 3 near to the station 200.
It is contemplated that the start identification step 1402 can clear, set, or store other station parameters 1404 such as a T_SL 1410, a C_R 1412, a CRT 1414, a CB 1416 and a CB_ID 1418. Alternatively, it is contemplated that the station parameters 1404: T_SL 1410, C_R 1412, CRT 1414, CB 1416, and CB_ID 1418 can be set to previously used values and can be overwritten during different steps of the user identification step 904.
The T_SL 1410 can be the length of time that the station 200 waits after the initial value of the T_SC 1406 has been set in the start identification step 1402 before the station 200 implements the user disambiguation block 310 of FIG. 3. It is contemplated that the T_SL 1410 can be set during the start identification step 1402 or can be preset before the station 200 is utilized by the active user 306.
The T_SL 1410 can be set or changed according to the length of time the active user 306 is expected to interact with the station 200 and based on the expected accuracy of the station 200 in determining the current user 314. Illustratively, the T_SL 1410 can be set to the current time plus the preset value or can simply be a preset value.
The C_R 1412 can be the RSSI 222 of the current signal 308 being processed from the beacons 100. The C_R 1412 can be cleared in the start identification step 1402.
The CRT 1414 can be used to determine a signal strength limit in dBm. The CRT 1414 is contemplated to be a threshold relative to the B1_R 1408. The C_R 1412 must be within the CRT 1414 range of B1_R 1408 to avoid being filtered out. It is contemplated that, as B1_R 1408 changes, the threshold filtering out the C_R 1412 can change also.
The CB 1416 can be the current beacon 100 being considered by the user identification step 904. The CB 1416 can transmit the C_R 1412. The CB 1416 can have the user ID 116 of FIG. 1 assigned as the CB_ID 1418.
The start identification step 1402 can be initiated by the countdown step 902 of FIG. 9. The station 200 can proceed from the start identification step 1402 to a disambiguation time limit decision step 1420.
The disambiguation time limit decision step 1420 can compare the T_SC 1406 with the T_SL 1410. If the T_SC 1406 is after the T_SL 1410, the disambiguation time limit decision step 1420 can return an affirmative result and activate the user disambiguation block 310 in a disambiguation step 1422.
The disambiguation step 1422 can be executed by the station 200 to determine the current user 314, the probabilities 312 of FIG. 3, and the scores 316 of FIG. 3. If the disambiguation time limit decision step 1420 determines that the T_SC 1406 is not after the T_SL 1410, the disambiguation time limit decision step 1420 can return a negative result.
A negative result from the disambiguation time limit decision step 1420 can trigger the execution of a new message received decision step 1424. The new message received decision step 1424 can be executed by the station 200 to determine whether the station communication unit 206 has detected the transmission of a signal 308 from the beacons 100 containing a new one of the messages 1120 of FIG. 11.
If the new message received decision step 1424 determines that none of the messages 1120 have been newly received, the new message received decision step 1424 can provide a negative result. When the new message received decision step 1424 provides a negative result the station 200 again executes the disambiguation time limit decision step 1420.
If the new message received decision step 1424 indicates that one of the messages 1120 has been newly received in the signal 308 from one of the beacons 100, the new message received decision step 1424 can provide an affirmative result. When the new message received decision step 1424 provides an affirmative result the station 200 can set the CB_ID 1418 to the user ID 116 contained in the message 1120 from the beacon 100.
Further, when the new message received decision step 1424 returns an affirmative result, the C_R 1412 can be set to the RSSI 222 of the signal 308 containing the new message 1120. Once the CB_ID 1418 and the C_R 1412 are set in the new message received decision step 1424, the station 200 can proceed to a known user in table decision step 1426.
The known user in table decision step 1426 can verify that the CB_ID 1418 of the CB 1416 is in the user ID table 216 of FIG. 2. If the CB_ID 1418 of the CB 1416 is not in the user ID table 216, then the known user in table decision step 1426 will return a negative result and the station 200 will then proceed to again execute the disambiguation time limit decision step 1420.
Alternatively, it is contemplated that when the CB_ID 1418 is not found in the user ID table 216, the CB_ID 1418 may be further processed to extract a group ID or to determine whether the CB 1416 belongs to the approved category 221 of FIG. 2 that can be found in the user ID table 216. It is contemplated that the user ID table 216 may hold the approved category 221 as groups or categories of the users 302 that can be recognized as approved allowing the station 200 to proceed to a RSSI window decision step 1428 even when the CB_ID 1418 is not found in the user ID table 216.
When the CB_ID 1418 of the CB 1416 is confirmed to be within the user ID table 216, the known user in table decision step 1426 will return an affirmative result and the station 200 will proceed to execute an RSSI window decision step 1428. The RSSI window decision step 1428 can determine whether the C_R 1412 is greater than B1_R 1408 minus CRT 1414.
That is, the RSSI window decision step 1428 determines whether the C_R 1412 is above the threshold of the best RSSI 222 of the current scan by the station 200 minus the CRT 1414. When the RSSI window decision step 1428 determines that the C_R 1412 is not above the threshold B1_R 1408 minus CRT 1414 then the RSSI window decision step 1428 will return a negative result and the station 200 will again execute the disambiguation time limit decision step 1420.
When the RSSI window decision step 1428 determines that the C_R 1412 is above the threshold B1_R 1408 minus CRT 1414 then the RSSI window decision step 1428 will return a positive result and the station 200 will execute a filter candidates step 1430. The filter candidates step 1430 can be executed by the station 200 to determine whether the CB_ID 1418 should be added to the Match_List 218 and whether any of the user IDs 116 should be removed from the Match_List 218.
The station 200 can proceed from the filter candidates step 1430 to a build Match_List step 1432. During the build Match_List step 1432, the station 200 can add or remove the user IDs 116.
The station 200 can proceed from the build Match_List step 1432 to the disambiguation time limit decision step 1420. The disambiguation time limit decision step 1420 can also be executed by the station 200 as a result of a negative result from the ID decision step 914 of FIG. 9.
It is contemplated that the beacons 100 can transmit multiple signals 308 each having new messages 1120. It has been discovered that executing the user identification step 904 can help determine the user ID 116 of the current user 314 even when the signals 308 received by the station 200 from the beacon 100 of the active user 306 has multiple different RSSI 222 readings, including some of the signals 308 with a high RSSI 222 and other signals 308 with a low RSSI 222 reading for the same beacon 100.
Referring now to FIG. 15, therein is shown a control flow of the filter candidates step 1430 of FIG. 14. The filter candidates step 1430 can be executed by the station 200 of FIG. 2 when the RSSI window decision step 1428 of FIG. 14 determines that the C_R 1412 of FIG. 14 is above the threshold B1_R 1408 of FIG. 14 minus CRT 1414 of FIG. 14.
The filter candidates step 1430 can begin with an RSSI power decision step 1502. The RSSI power decision step 1502 can determine whether the C_R 1412 is greater than the B1_R 1408. That is, the RSSI power decision step 1502 determines whether the RSSI 222 of FIG. 2 for the signal 308 of FIG. 3 including the message 1120 of FIG. 11 currently being processed is higher than the highest RSSI 222 measured during the current scan by the station 200.
The station 200 can scan for the beacons 100 of FIG. 1 and can detect multiple beacons 100 during a single scan. The station 200 can then process each of the messages 1120 of each individual beacon 100 sequentially.
If the RSSI power decision step 1502 determines that the C_R 1412 of the current message 1120 is greater than the B1_R 1408, then the station 200 will proceed to execute a set B1_R step 1504. The set B1_R step 1504 can set B1_R 1408 to the C_R 1412.
Setting the B1_R 1408 to the C_R 1412 in the set B1_R step 1504 means that the RSSI 222 of the signal 308 having the current message 1120, is the highest RSSI 222 detected during the current scan for the messages 1120 processed up to this point.
If the RSSI power decision step 1502 determines that the C_R 1412 of the current message 1120 is not greater than the B1_R 1408, then the station 200 will proceed to execute an ID Match_List decision step 1506. The ID Match_List decision step 1506 can check and determine whether Match_List 218 of FIG. 2 contains an existing entry equal to the CB_ID 1418 of FIG. 14.
If the ID Match_List decision step 1506 determines that the CB_ID 1418 does not exist in the Match_List 218 then the ID Match_List decision step 1506 will return a negative result and the station 200 will proceed to execute a Make_Entry true step 1508. The Make_Entry true step 1508 can set one of the station parameters 1404 of FIG. 14.
The station parameter 1404 set by the Make_Entry true step 1508 is Make_Entry 1510. The Make_Entry 1510 can indicate whether a new entry should be made in the Match_List 218 for the CB 1416 of FIG. 14 later in the user identification step 904 of FIG. 9. The Make_Entry true step 1508 can set the Make_Entry 1510 to true.
If the ID Match_List decision step 1506 determines that the CB_ID 1418 does exist in the Match_List 218 then the ID Match_List decision step 1506 will return an affirmative result and the station 200 will proceed to execute a Make_Entry false step 1512. The Make_Entry false step 1512 can set the Make_Entry 1510 to false, which indicates that the station 200 should not create a new entry in the Match_List 218 for the CB 1416.
The Make_Entry false step 1512 can also set the RSSI 222 value that corresponds to the CB 1416 in the Match_List 218 to the C_R 1412 when the C_R 1412 is larger than the currently recorded RSSI 222 value in the Match_List 218. After the completion of the Make_Entry false step 1512 and the Make_Entry true step 1508, the station 200 can proceed to execute a more entry decision step 1514.
The more entry decision step 1514 can determine whether any more beacons 100 have the user IDs 116 of FIG. 1 in the Match_List 218. In addition, the more entry decision step 1514 can determine whether any more of the beacons 100 have the user IDs 116 that belong to a user category or user group contained in the Match_List 218. The more entry decision step 1514 can index sequentially through the Match_List 218.
If the more entry decision step 1514 determines that there are more entries in the Match_List 218 that have not been evaluated, the more entry decision step 1514 can return an affirmative result and the station 200 can execute a get next entry step 1516. The get next entry step 1516 can index to the next entry in the Match_List 218.
Once the get next entry step 1516 indexes to the next entry in the Match_List 218 the CB 1416, the CB_ID 1418, and the C_R 1412 can be updated to correspond to the entry in the Match_List 218 indexed by the get next entry step 1516. The station 200 can proceed to execute the RSSI window decision step 1428.
The RSSI window decision step 1428 can determine whether the C_R 1412 of the CB 1416 currently indexed by the get next entry step 1516 is greater than B1_R 1408 minus CRT 1414. When the RSSI window decision step 1428 determines that the C_R 1412 is not above the threshold B1_R 1408 minus CRT 1414 then the RSSI window decision step 1428 will return a negative result and the station 200 will execute a remove from list step 1518.
The remove from list step 1518 can remove the CB_ID 1418 and the C_R 1412 of the CB 1416 from the Match_List 218. Once the remove from list step 1518 is complete the more entry decision step 1514 can be again executed.
When the RSSI window decision step 1428 determines that the C_R 1412 is above the threshold B1_R 1408 minus CRT 1414 then the RSSI window decision step 1428 will return an affirmative result and the station 200 will again execute the more entry decision step 1514. If the more entry decision step 1514 determines that there are not any more entries in the Match_List 218 that should be evaluated, the more entry decision step 1514 can return a negative result and the station 200 can execute the build Match_List step 1432 of FIG. 14.
Referring now to FIG. 16, therein is shown a control flow of the build Match_List step 1432 of FIG. 14. The build Match_List step 1432 can begin with a Make_Entry decision step 1602. The Make_Entry decision step 1602 can be executed and initiated by a negative result from the more entry decision step 1514 of FIG. 15.
The Make_Entry decision step 1602 can determine whether the Make_Entry 1510 of FIG. 15 is set to true. When the Make_Entry decision step 1602 determines that the Make_Entry 1510 is set to false then the Make_Entry decision step 1602 can provide a negative result and the station 200 of FIG. 2 can again execute the disambiguation time limit decision step 1420 of FIG. 14.
When the Make_Entry decision step 1602 determines that the Make_Entry 1510 is set to true then the Make_Entry decision step 1602 can provide an affirmative result and the station 200 can execute a Match_List room decision step 1604. The Match_List room decision step 1604 can determine whether there is an available space in the Match_List 218 of FIG. 2.
When the Match_List room decision step 1604 determines that there is space in the Match_List 218, the Match_List room decision step 1604 will return an affirmative result and the station 200 will execute an add new entry step 1606. The add new entry step 1606 can enter the CB_ID 1418 of FIG. 14 and the C_R 1412 of FIG. 14 for the CB 1416 of FIG. 14 to the Match_List 218.
Once the add new entry step 1606 adds the CB 1416 to the Match_List 218, the station 200 can again execute the disambiguation time limit decision step 1420. When the Match_List room decision step 1604 determines that there is no space in the Match_List 218, the Match_List room decision step 1604 will return a negative result and the station 200 will execute a remove lowest RSSI step 1608.
The remove lowest RSSI step 1608 will determine which entry in the Match_List 218 has the lowest RSSI 222 of FIG. 2 value and will delete the user ID 116 of FIG. 1 corresponding to the lowest RSSI 222. Once the remove lowest RSSI step 1608 completes the removal of the entry from the Match_List 218, the station 200 will execute the add new entry step 1606.
Referring now to FIG. 17, therein is shown a control flow of the disambiguation step 1422 of FIG. 14. The disambiguation step 1422 can be executed by the station 200 of FIG. 2 once the disambiguation time limit decision step 1420 of FIG. 14 determines that the T_SC 1406 of FIG. 14 is after the T_SL 1410 of FIG. 14 and the disambiguation time limit decision step 1420 returns an affirmative result.
The disambiguation step 1422 can begin with a multiple user decision step 1702. The multiple user decision step 1702 can check the Match_List 218 of FIG. 2 and determine whether the Match_List 218 includes multiple user IDs 116 of FIG. 1 or whether the Match_List 218 includes only a single user ID 116.
If the multiple user decision step 1702 determines that the Match_List 218 includes only a single entry of the user ID 116 for a single user 302 of FIG. 3, then the multiple user decision step 1702 can return a negative result and the station 200 can then proceed to a record step 1704. The record step 1704 can record the user ID 116 in the Match_List 218 in the history record 318 of FIG. 3 and thereby assigning and recognizing the user ID 116, which is the CB_ID 1418 of FIG. 14, as the current user 314.
Once the CB_ID 1418 is recorded in the history record 318 as the current user 314, the station 200 can proceed to execute the countdown decision step 906 of FIG. 9. If the multiple user decision step 1702 determines that the Match_List 218 includes multiple entries of the user IDs 116 for multiple users 302, then the multiple user decision step 1702 can return an affirmative result and the station 200 can then proceed to a probability step 1706.
The probability step 1706 can utilize the scores 316 of FIG. 3 to calculate the probabilities 312 of FIG. 3 that the user IDs 116 in the Match_List 218 correspond to the active user 306 of FIG. 3. It is contemplated that when the station 200 executes the probability step 1706 for the first time during the user identification step 904, only the user IDs 116 broadcast by the beacons 100 and the RSSI 222 of FIG. 2 for the signal 308 of FIG. 3 broadcast by the beacons 100 will be available. When only the RSSI 222 is available, the probabilities 312 will depend primarily on the RSSI 222.
Illustratively, the beacons 100 with the strongest RSSI 222 could be calculated to have the highest probability of being coupled to the active user 306. It is further contemplated that the entries in the Match_List 218 could be filtered during the probability step 1706 by excluding any of the signals 308 coming from sources not found in the user ID table 216 of FIG. 2 either as an exact match or as a member of the approved category 221 of FIG. 2.
It has been discovered that filtering out the signals 308 that come from sources not in the user ID table 216 improves the user identification step 904 because only the RSSI 222 of beacons 100 that are in the user ID table 216 need to be obviously stronger than the other Match_List 218 entries. In this way, a signal 308 that is very strong near to the station 200 but is not transmitted from a beacon 100 in the user ID table 216 will not ruin the identification of the current user 314 or the calculation of the probabilities 312.
The station 200 can proceed from the probability step 1706 to a recognition threshold decision step 1708. The recognition threshold decision step 1708 can determine whether the probability 312 of the entries in the Match_List 218 is above a threshold, P_TP 1710. The P_TP 1710 can be a probability of 99.9% or an error rate of 1 in 1000.
If the recognition threshold decision step 1708 determines that one of the user IDs 116 has the probability 312 above the P_TP 1710, the recognition threshold decision step 1708 will return an affirmative result and the station 200 will proceed to execute the record step 1704. If the recognition threshold decision step 1708 determines that none of the user IDs 116 has the probability 312 above the P_TP 1710, the recognition threshold decision step 1708 will return a negative result and the station 200 will proceed with further disambiguation measures.
It is contemplated that the station 200 can implement multiple different types of disambiguation measures to determine the scores 316 for each user ID 116 in the Match_List 218 and determine which user ID 116 should be identified as the current user 314. Specifically, it is contemplated that a signal quality disambiguation step 1712, an accelerometer disambiguation step 1714, and a game disambiguation step 1716 can be executed by the station 200 to calculate the scores 316 used during the probability step 1706 to determine the probabilities 312.
It will be appreciated that the station 200 can implement different disambiguation measures based on how many times the recognition threshold decision step 1708 returns a negative result. Illustratively, the first time the recognition threshold decision step 1708 returns a negative result the station 200 can execute the signal quality disambiguation step 1712. The second time the recognition threshold decision step 1708 returns a negative result the station 200 can execute the accelerometer disambiguation step 1714.
The third time the recognition threshold decision step 1708 returns a negative result the station 200 can execute the game disambiguation step 1716. The fourth time the recognition threshold decision step 1708 returns a negative result the station 200 can execute an off line disambiguation step 1718.
It is contemplated that once the station 200 executes either the signal quality disambiguation step 1712, the accelerometer disambiguation step 1714, or the game disambiguation step 1716, the station 200 can again execute the multiple user decision step 1702. When the station 200 completes the off line disambiguation step 1718, the station 200 can proceed to execute the countdown decision step 906.
It is contemplated that the signal quality disambiguation step 1712, the accelerometer disambiguation step 1714, and the game disambiguation step 1716 can be arranged in a different order to be executed by the station 200. It is further contemplated that the signal quality disambiguation step 1712, the accelerometer disambiguation step 1714, and the game disambiguation step 1716 can be ordered to be executed by the station 200 in a way that provides the best balance between power consumption of the beacons 100 and ambiguity reduction. Ambiguity reduction means the probability 312 that one of the beacons 100 can be identified as the current user 314 increases while the probability 312 that other beacons 100 are not the current user 314 decreases.
For example, the signal quality disambiguation step 1712, the accelerometer disambiguation step 1714, or the game disambiguation step 1716 may require much more power on the part of the beacons 100 and cut ambiguity in half, which decreases the error rate of the disambiguation step 1422. Conversely, the signal quality disambiguation step 1712, the accelerometer disambiguation step 1714, or the game disambiguation step 1716 might require only slightly more power consumption on the part of the beacons 100 and cut ambiguity by only 25%.
It is contemplated that the signal quality disambiguation step 1712, the accelerometer disambiguation step 1714, or the game disambiguation step 1716 can be executed in a different order based on the battery life of each specific beacon 100. That is, if one of the beacons 100 has a low battery the station 200 might prioritize the execution of the disambiguation measures so the disambiguation measures with the lowest power requirements are executed first and the disambiguation measures with higher power requirements are executed later.
Alternatively, if one of the beacons 100 has a highly charged battery the station 200 might prioritize the execution of the disambiguation measures so the disambiguation measures that are the most effective at removing ambiguity are executed by the station 200 first while the disambiguation measures that are less effective are executed by the station 200 later. It is contemplated that a second factor in determining which order the signal quality disambiguation step 1712, the accelerometer disambiguation step 1714, or the game disambiguation step 1716 are executed can be the length of time that the disambiguation measure takes to complete.
For example, monitoring the beacon sensor data 122 of FIG. 1 from the beacon sensor unit 108 of FIG. 1 and correlating the beacon sensor data 122 with the station sensor data 224 of FIG. 2 as part of the execution of the accelerometer disambiguation step 1714 might be calculable quickly whereas providing the instructions 602 of FIG. 6 on the station user interface 210 of FIG. 2 as part of the execution of the game disambiguation step 1716 might take more time. In this situation, the accelerometer disambiguation step 1714 might be ordered before the game disambiguation step 1716.
It has been discovered that the longer time the station 200 takes to identify the current user 314, the longer the time required before the station 200 displays the user's name 220 of FIG. 2 on the station user interface 210. By displaying the user's name 220 sooner, rather than later, the active user 306 may be better encouraged to complete the hand washing exercise (since they will understand that a high level of accountability and transparency is being achieved during the wash).
As depicted, the signal quality disambiguation step 1712 can be executed first by the station 200. During the signal quality disambiguation step 1712, the station 200 can send instructions to the beacons 100 to modify the beacon parameters 120, for example when the beacons 100 execute the receiving step 1036 of FIG. 10.
The beacon parameters 120 can be modified during the signal quality disambiguation step 1712 to change the frequency of the signal 308 transmitted by the beacons 100, the duration with which the beacons 100 transmit the signal 308, or how frequently the beacons 100 transmit the signal 308. The beacon parameters 120 can further be modified in the signal quality disambiguation step 1712 to increase the power of the signal 308 transmitted by the beacons 100.
It has been discovered that modifying the power, frequency, duration of the signals 308 transmitted by the beacons 100 can help to distinguish the beacons 100 and reduce the ambiguity of which beacon 100 should be considered the current user 314. It has further been discovered that increasing how frequently the beacons 100 transmit the signal 308 can provide increased data points that can reduce the ambiguity of which beacon 100 should be considered the current user 314.
During the accelerometer disambiguation step 1714, the station 200 can modify the beacon parameters 120, when the beacons 100 execute the receiving step 1036, and can instruct the beacons 100 to power up the beacon sensor unit 108, monitor the beacon sensor unit 108, and transmit the beacon sensor data 122 in the message 1120 of FIG. 11 of the signal 308. The station 200 can then compare the beacon sensor data 122 with the station sensor data 224.
During the game disambiguation step 1716, the station 200 can modify the beacon parameters 120, when the beacons 100 execute the receiving step 1036, and can instruct the beacons 100 to power up the beacon sensor unit 108, monitor the beacon sensor unit 108, and transmit the beacon sensor data 122 in the message 1120 of FIG. 11 of the signal 308. The station 200 can also provide the instructions 602 to the active user 306 to induce a specific movement. The station 200 can then compare the beacon sensor data 122 with the station sensor data 224.
It has been discovered that any significant leaning-like motion observed by the beacon sensor unit 108 of the beacons 100 can reduce the ambiguity that the beacon 100 sensing the motion is coupled to the active user 306. It has further been discovered that the beacon sensor data 122 indicating a leaning motion by the user 302 can indicate the orientation of the of the beacon 100 relative to the user 302 it is coupled to and that the motions detected by the beacon sensor unit 108 can be translated into motions of the space ship 604 of FIG. 6.
It is contemplated that communication latency during the game disambiguation step 1716 can be avoided by automatically depicting the space ship 604 moving out of the way of the comet 606 of FIG. 6 in anticipation of and before the station 200 recognizes such a motion from the beacon sensor data 122. It is contemplated that when the signal quality disambiguation step 1712, the accelerometer disambiguation step 1714, and the game disambiguation step 1716 do not enable the probability step 1706 to calculate the probability 312 that any of the beacons 100 are the current user 314 to a level above P_TP 1710, the station 200 can execute the off line disambiguation step 1718.
During the off line disambiguation step 1718 the active user 306 can be assigned an “Unknown ID”. The interaction with the station 200, such as a hand washing compliance, can be credited to multiple users 302 or partial credit for the interaction with the station 200 might be given to multiple users 302.
It is contemplated that the off line disambiguation step 1718 could be completed at a later time and could analyze the history records 318 for the users 302 to resolve and identify the current user 314. It is further contemplated that the station 200 could display a code to the active user 306 or to request a signal from the active user 306 that can later be used to identify the current user 314 and assign credit for the interaction with the station 200 to the active user 306.
For example, the station 200 could prompt the active user 306 to show a hand sign of some kind to the station 200 that would be detected by the station sensor unit 208. Later, the active user 306 could log into an application on their phone, show the same hand sign, and be identified as the current user 314 during the interaction with the station 200.
Referring now to FIG. 18, therein is shown a control flow of the accelerometer disambiguation step 1714 of FIG. 17. The accelerometer disambiguation step 1714 can begin with a beacon notification step 1802.
The beacon notification step 1802 can transmit the message 1120 of FIG. 11 in the signal 308 of FIG. 3 to the beacons 100 of FIG. 1 that have the user IDs 116 of FIG. 1 remaining in the Match_List 218 of FIG. 2. The message 1120 from the station 200 of FIG. 2 can update the beacon parameters 120 of FIG. 1 for the beacons 100 and trigger the beacons 100 to power up the beacon sensor unit 108 of FIG. 1 and include the beacon sensor data 122 of FIG. 1 in the messages 1120 sent from the beacons 100 to the station 200.
The station 200 can further provide the beacon parameters 120 to broadcast the signal 308 more frequently. The beacon parameters 120 can be updated when the beacons 100 execute the receiving step 1036 of FIG. 10.
The station 200 can proceed from the beacon notification step 1802 to a retrieve sensor data step 1804. During the retrieve sensor data step 1804, the station 200 can detect the signal 308 from the beacons 100 using the station communication unit 206 of FIG. 2. The station 200 can isolate the beacon sensor data 122 from the message 1120 contained within the signal 308.
Further, during the retrieve sensor data step 1804, the station 200 can detect the station sensor data 224 of FIG. 2 from the station sensor unit 208 of FIG. 2. Once the station 200 has collected the beacon sensor data 122 and the station sensor data 224, the station 200 can proceed to execute a correlation decision step 1806.
During the correlation decision step 1806, the station 200 can determine whether sufficient correlation exists between the station sensor data 224 and the beacon sensor data 122. Multiple methods are contemplated for comparing the similarity of the beacon sensor data 122 to the station sensor data 224. One such method is the cross-correlation, which is commonly used for comparing one series of data collected over time to another such series. A higher correlation will produce a larger score 316 of FIG. 3 and indicate that the beacon 100 is more likely to be attached to the active user 306 of FIG. 3 that was performing the motions detected by the station sensor unit 208 of the station 200.
It is contemplated that when scores 316 are larger, the beacons 100 associated with the larger score 316 will be maintained as a candidate for the current user 314 of FIG. 3 on the Match_List 218. Conversely, when the scores 316 are lower, the correlation decision step 1806 can return a negative result and the station 200 can initiate a remove user step 1808.
During the remove user step 1808 the beacons 100 associated with the lower score 316 might be removed as a candidate for the current user 314 on the Match_List 218. Once the remove user step 1808 is complete or when the scores 316 are sufficiently high and the correlation decision step 1806 returns an affirmative result indicating that there is sufficient correlation, the station 200 can initiate an all candidates step 1810.
The all candidates step 1810 can determine whether each of the user IDs 116 of FIG. 1 in the Match_List 218 have been evaluated during the accelerometer disambiguation step 1714. If not all of the user IDs 116 have been evaluated, the all candidates step 1810 will return a negative result and the station 200 will index to the next user ID 116, and execute the retrieve sensor data step 1804. If all of the user IDs 116 have been evaluated, the all candidates step 1810 will return an affirmative result and the station 200 will execute the multiple user decision step 1702 of FIG. 17.
Referring now to FIG. 19, therein is shown a control flow of the game disambiguation step 1716 of FIG. 17. The game disambiguation step 1716 can begin with a beacon notification step 1902.
The beacon notification step 1902 can transmit the message 1120 of FIG. 11 in the signal 308 of FIG. 3 to the beacons 100 of FIG. 1 that have the user IDs 116 of FIG. 1 remaining in the Match_List 218 of FIG. 2. The message 1120 from the station 200 of FIG. 2 can update the beacon parameters 120 of FIG. 1 for the beacons 100 and trigger the beacons 100 to power up the beacon sensor unit 108 of FIG. 1 and include the beacon sensor data 122 of FIG. 1 in the messages 1120 sent from the beacons 100 to the station 200.
The station 200 can further provide the beacon parameters 120 to broadcast the signal 308 more frequently. The beacon parameters 120 can be updated when the beacons 100 execute the receiving step 1036 of FIG. 10.
The station 200 can proceed from the beacon notification step 1902 to a present game step 1904. During the present game step 1904 the station 200 can display instructions 602 of FIG. 6 and the game of FIG. 6 including the space ship 604 of FIG. 6 and the comet 606 of FIG. 6 on the station user interface 210 of FIG. 2.
The station 200 can proceed from the present game step 1904 to a retrieve sensor data step 1906. During the retrieve sensor data step 1906, the station 200 can detect the signal 308 from the beacons 100 using the station communication unit 206 of FIG. 2. The station 200 can isolate the beacon sensor data 122 from the message 1120 contained within the signal 308.
Further, during the retrieve sensor data step 1906, the station 200 can detect the station sensor data 224 of FIG. 2 from the station sensor unit 208 of FIG. 2. Once the station 200 has collected the beacon sensor data 122 and the station sensor data 224, the station 200 can proceed to execute a correlation decision step 1908.
During the correlation decision step 1908, the station 200 can determine whether sufficient correlation exists between the station sensor data 224 and the beacon sensor data 122. Multiple methods are contemplated for comparing the similarity of the beacon sensor data 122 to the station sensor data 224.
One such method is the cross-correlation, which is commonly used for comparing one series of data collected over time to another such series. A higher correlation will produce a larger score 316 of FIG. 3 and indicate that the beacon 100 is more likely to be attached to the active user 306 of FIG. 3 that was performing the motions detected by the station sensor unit 208 of the station 200.
It is contemplated that when scores 316 are larger, the beacons 100 associated with the larger score 316 will be maintained as a candidate for the current user 314 of FIG. 3 on the Match_List 218. Conversely, when the scores 316 are lower, the correlation decision step 1908 can return a negative result and the station 200 can initiate a remove user step 1910.
During the remove user step 1910 the beacons 100 associated with the lower score 316 might be removed as a candidate for the current user 314 on the Match_List 218. After the remove user step 1910 or when the scores 316 are sufficiently high that the correlation decision step 1908 returns an affirmative result indicating that there is sufficient correlation, the station 200 can initiate an all candidates step 1912.
The all candidates step 1912 can determine whether each of the user IDs 116 of FIG. 1 in the Match_List 218 have been evaluated during the game disambiguation step 1716. If not all of the user IDs 116 have been evaluated, the all candidates step 1912 will return a negative result and the station 200 will index to the next user ID 116, and execute the retrieve sensor data step 1906. If all of the user IDs 116 have been evaluated, the all candidates step 1912 will return an affirmative result and the station 200 will execute the multiple user decision step 1702 of FIG. 17.
Referring now to FIG. 20, therein is shown a control flow of the probability step 1706 of FIG. 17. The probability step 1706 can calculate the probabilities 312 of FIG. 3. The probabilities 312 can be the probability of correct identification of the active user 306 of FIG. 3 as the current user 314 of FIG. 3.
The probability step 1706 can begin with a top matches step 2002. The top matches step 2002 can set one of the station parameters 1404 of FIG. 14, N_T 2004.
The N_T 2004 can be set to the number of records from the history record 318 of FIG. 3 where the highest score 316 of FIG. 3 for the candidate beacon 100 for the current user 314, of a previous interaction with the station 200, was at least as high as the current highest score 316 for the beacons 100 on the Match_List 218 of FIG. 3 and the second highest score 316 for the candidate beacon 100 for the current user 314, of a previous interaction with the station 200, was at least as low as the current second highest score 316 for the beacons 100 on the Match_List 218. It is contemplated that the N_T 2004 can be set by comparing the scores 316 from previous interactions with the station 200 where the identification of the current user 314 is known to be correct, such as with supervised data.
It is contemplated that the second highest score 316 for the candidate beacon 100 for the current user 314, of a previous interaction with the station 200, could be empty. That is, it is contemplated that no beacon 100 would have a second highest score 316 from a previous interaction with the station 200 recorded in the history record 318.
The station 200 can proceed from top matches step 2002 to a top user check step 2006. The top user check step 2006 calculates the number of records from the N_T 2004 set in the top matches step 2002 that resulted in false-positive identifications of the current user 314 when using the current disambiguation measure. The number of false positives can be recorded in the station parameter 1404, N_FP 2008.
For example, it may be the case that 10 records exist where the best matching candidate had the score 316 equal or lower than the current best matching candidate beacon 100, and the second best matching candidate had the score 316 at least as high as the current second best matching candidate beacon 100.
In this case N_T 2004 would be 10. If the system displayed the best matching user name 220 of FIG. 2 to the active user 306 and was informed of an incorrect identification in one such instance, then N_FP 2008 would be 1. The station 200 can proceed from top user check step 2006 to a calculation step 2010.
During the calculation step 2010, the station 200 can calculate the probability 312 that the beacons 100 are coupled to the active user 306. The calculation step 2010 can identify the best matching beacon 100 from the Match_List 218.
The probabilities 312 for each of the beacons 100 on the Match_List 218 can be calculated by the formula 1−(N_FP/N_T). For example, if N_T 2004=10, and N_FP 2008=1, then the probability 312 of the best matching candidate beacon 100 being coupled to the active user 306 is 1−(1/10)=90%.
It is possible to get the user 302 of FIG. 3 to supervise the results of the user identification step 904 of FIG. 9 by prompting the active user 306 to confirm the user name 220 displayed on the station user interface 210 of FIG. 2 as a result of the user identification step 904 is correct. In this way, the users 302 can provide the supervising information required by the top matches step 2002 and the top user check step 2006.
In this way, it is possible for the active user 306 to provide supervising information even though the station 200 may not know with certainty what beacon 100 should be identified as the current user 314. It is contemplated that the users 302 can confirm the identification of user identification step 904 by showing a hand sign or motion to the station 200, which can be detected by the station sensor unit 208 of FIG. 2. In this way, it is possible for the accuracy of the compliance system to improve over time as the accuracy of the probabilities 312 derived from disambiguation measures improve.
Referring now to FIG. 21, therein is shown a block diagram of the compliance system 2100 in a second embodiment. For clarity and to reduce useless surplusage, the description of the station 200 of FIG. 2 and the beacon 100 as they apply to the second embodiment of the compliance system 2100 are defined herein as implemented with the same or equivalent functions, physical elements, hardware usage, control flows, and data requirements as they are described above with regard to the compliance system 300 of FIG. 3 in the first embodiment and the compliance system 2100 additionally includes the functions, physical elements, hardware usage, control flows, and data requirements described below.
Further, for ease of description the functions, physical elements, hardware usage, control flows, and data requirements of the compliance system 2100 will generally be described as implemented on additional hardware unique to the compliance system 2100; however, it will be appreciated by those of ordinary skill in the art that the physical elements of the compliance system 300 or the control flow steps of the compliance system 2100 could be incorporated into or combined with the physical elements, hardware usage, control flow steps, and data requirements of the compliance system 300.
The compliance system 2100 is shown to have a server beacon 2102 communicatively coupled to a power station 2104. The server beacon 2102 can include the beacon 100 as described in FIG. 1 and additionally include server beacon sensors 2106, server beacon mass storage 2108, and a server beacon power transceiver 2110.
The server beacon sensors 2106 can include a motion sensor 2112 such as an accelerometer, a gyroscope, or a magnetometer. The motion sensor 2112 can produce motion data 2114.
The motion data 2114 can be stored in physical memory on the server beacon 2102 such as in the beacon storage unit 104 of FIG. 1, on the server beacon mass storage 2108, or even on memory within a microprocessor like the beacon control unit 102 of FIG. 1. The motion data 2114 can be motion of the server beacon 2102 detected by the motion sensor 2112.
Illustratively, the motion sensor 2112 can detect physical movement or vibration of the server beacon 2102. The motion data 2114 generated by the motion sensor 2112 can be used to activate other server beacon sensors 2106 when they are in a low power state.
Further, a time threshold stored within the server beacon 2102 can be implemented to return server beacon sensors 2106, other than the motion sensor 2112, to a low power state if the motion sensor 2112 has not detected motion of the server beacon 2102 for a time longer than the time threshold.
The server beacon sensors 2106 can similarly include a sound sensor 2116. The sound sensor 2116 can be an ultra low power sound sensor or a piezoelectric sensor for detecting vibration. The sound sensor 2116 can produce sound data 2118.
The sound data 2118 can be stored in physical memory on the server beacon 2102 such as in the beacon storage unit 104, on the server beacon mass storage 2108, or even on memory within a microprocessor like the beacon control unit 102. The sound data 2118 can be an audio signal from near the server beacon 2102 detected by the sound sensor 2116.
The sound data 2118 generated by the sound sensor 2116 can be used to activate other server beacon sensors 2106 when they are in a low power state. Further, the time threshold stored within the server beacon 2102 can be implemented to return server beacon sensors 2106, other than the sound sensor 2116, to a low power state if the sound sensor 2116 has not detected motion of the server beacon 2102 for a time longer than the time threshold.
It is contemplated that the motion sensor 2112 and the sound sensor 2116 can be utilized together to filter out false positive indications of motion or sound, or can be used to increase the sensitivity of the server beacon 2102. The server beacon sensors 2106 can yet further include a microphone 2120.
It is contemplated that the microphone 2120 can be the sound sensor 2116 or can be an independent higher power audio sensor. The microphone 2120 can produce audio data 2122.
The audio data 2122 is contemplated to be a larger amount of data than the sound data 2118 and is therefore contemplated to be stored on the server beacon mass storage 2108. The microphone 2120 can further include a microphone mode 2124.
The microphone mode 2124 can indicate whether the microphone 2120 is turned on, turned off, or in a low power state. The server beacon sensors 2106 can still further include a gesture sensor 2126.
The gesture sensor 2126 can be a low power gesture sensor such as a proximity-based gesture sensor, an infrared gesture sensor, an optical gesture sensor, a distance sensor, or even a pressure sensor in a remote location and detached from the server beacon 2102. The gesture sensor 2126 can detect gestures or hand movements and produce gesture data 2128.
The gesture data 2128 can be stored on the server beacon mass storage 2108 or other memory locations within the server beacon 2102. The gesture data 2128 can be used to control portions of the compliance system 2100. Illustratively, the gesture sensor 2126 producing the gesture data 2128 can be used by the compliance system 2100 to turn on the microphone 2120 and record the audio data 2122 or to turn the microphone 2120 off and end the recording of the audio data 2122.
It has been discovered that when the gesture data 2128 from the gesture sensor 2126 is used to control aspects and functions of the compliance system 2100, the transmission of germs and pathogens can be greatly reduced. More particularly, health care-associated infections can be greatly reduced by controlling the compliance system 2100 in a touchless manner by implementing the gesture sensor 2126.
The gesture sensor 2126 can also include a gesture sensor mode 2130. The gesture sensor mode 2130 can indicate whether the gesture sensor 2126 is turned on or turned off.
It is contemplated that the server beacon 2102 can include the beacon control unit 102 implemented as a microprocessor with a limited amount of memory so the server beacon mass storage 2108 can function as an off chip storage unit for storing the audio data 2122 and the gesture data 2128. The server beacon mass storage 2108 can be non-transitory and implemented as low-power mass storage (LPMS), a volatile memory, a nonvolatile memory, an internal memory, an external memory, or a combination thereof. For example, the storage unit can be a nonvolatile storage such as random access memory, flash memory, disk storage, or a volatile storage such as static random access memory.
The server beacon mass storage 2108 can include a storage mode 2132, which can indicate whether the server beacon mass storage 2108 is turned on, turned off, and indicate the available storage within the server beacon mass storage 2108. The server beacon mass storage 2108 can include a mass storage queue 2134.
The mass storage queue 2134 can function as a pointer to indicate the beginning and end of messages 2135, including the audio data 2122 and the gesture data 2128, stored within memory 2136. The mass storage queue 2134 can further function as a pointer to indicate the beginning location for new messages 2135, including the audio data 2122 and the gesture data 2128, to be written to the memory 2136 within the server beacon mass storage 2108.
The messages 2135 are used herein to describe data including a single piece of the audio data 2122, such as one uninterrupted recording of the audio data 2122, and can include other data such as metadata as described below. The messages 2135 are further used herein to describe data including a single uninterrupted recording of the gesture data 2128, or a recording of the gesture data 2128 that is a single complete command for executing a function of the compliance system 2100.
As can be appreciated, the memory 2136 can include bit locations BIT (0) 2138, BIT (1) 2140, BIT (2) 2142, and BIT (N) 2144. The entire size of the memory 2136 can be the bits BIT (0) 2138 through BIT (N) 2144. The audio data 2122 and the gesture data 2128 can be stored within the memory 2136 using the bits BIT (0) 2138 through BIT (N) 2144.
The server beacon power transceiver 2110 can transmit the audio data 2122, the gesture data 2128, and other messages to the power station 2104. The server beacon power transceiver 2110 can also be used for wireless communication to other devices on a local network.
The server beacon power transceiver 2110 can include a receiver which can primarily function to receive acknowledgements from the power station 2104 that sent data was received so that reliable transmission may occur. The server beacon power transceiver 2110 includes a server beacon transceiver mode 2146.
The server beacon transceiver mode 2146 can indicate whether the server beacon power transceiver 2110 is turned on, turned off, transmitting, or receiving. The server beacon power transceiver 2110 of the server beacon 2102 can communicate the messages 2135 to a power station power transceiver 2148 of the power station 2104.
The power station 2104 is contemplated to be the station 200 that is plugged into a power receptacle allowing more power to be consumed while running the power station power transceiver 2148. Alternatively, the power station 2104 is contemplated to be a high power forwarder without requiring all the functionality of the station 200. The power station power transceiver 2148 of the power station 2104 can receive the messages 2135 from the server beacon power transceiver 2110 of the server beacon 2102 and transmit back acknowledgements that the messages 2135 were properly received or can transmit back indications that the messages 2135 were not properly received.
It is contemplated that the server beacon power transceiver 2110 and the power station power transceiver 2148 can be turned off or placed in a low power state most of the time. During the off state or low power state the server beacon power transceiver 2110 and the power station power transceiver 2148 will consume little to no power.
It is further contemplated that the beacon communication unit 106 of FIG. 1 residing within the server beacon 2102 and the station communication unit 206 of FIG. 2 residing within the power station 2104 can perform the communications as described above with regard to the compliance system 300 and the server beacon power transceiver 2110 and the power station power transceiver 2148 can be turned on to transfer the messages 2135 at high speed. Further, it is contemplated that the server beacon 2102 and the power station 2104 can coordinate the short high-speed and high-power of the server beacon power transceiver 2110 and the power station power transceiver 2148 by utilizing the lower power communications of the beacon communication unit 106 and the station communication unit 206.
It has been discovered that utilizing both the lower power communications of the beacon communication unit 106 and the station communication unit 206 together with and to synchronize the high power communications of the server beacon power transceiver 2110 and the power station power transceiver 2148 unexpectedly reduces the overall power consumed and overall transmission time relative to using only the lower power communications of the beacon communication unit 106 and the station communication unit 206 or the high power communications of the server beacon power transceiver 2110 and the power station power transceiver 2148. This unexpectedly results from the data transfer components of the compliance system 2100 being active for a shorter amount of time, thus consuming less power.
The messages 2135 can be transmitted from the power station 2104 through a local network 2150. From the local network 2150, the messages 2135 can be sent to a gateway 2152.
The gateway 2152 can be connected to the internet 2154. The gateway 2152 can forward the messages 2135 through the internet 2154 to a secure online server 2156, which can also be connected to the internet 2154.
The messages 2135 can be organized and stored within the online server 2156. When the messages 2135 include the audio data 2122, the messages 2135 can be organized and stored in an audio database server 2158.
The messages 2135 stored on the audio database server 2158 can include metadata for the specific audio data 2122 contained within the messages 2135 such as user info 2160, and an audio time stamp 2162. The user info 2160 can include a user name, user ID, and a location indicating the name of the facility where the user performs their job duties. The audio time stamp 2162 can indicate the time the audio data 2122 was recorded by the microphone 2120 or the time the audio data 2122 recording was initiated and ended.
It is contemplated that additional fields could be included in the message 2135 including a location of where the audio data 2122 was recorded, which could be based on the specific wireless transmitters that were nearby the server beacon 2102 at the time the audio data 2122 was recorded. Along with the user info 2160, the audio data 2122, and the audio time stamp 2162, the messages 2135 can further include a transcription 2164 of the audio data 2122 within the message 2135.
The transcription 2164 can be a text transcription of the audio data 2122 within the message 2135. It is contemplated that users can access the messages 2135 on the audio database server 2158 and can even manipulate portions of the message 2135 using an external computer 2166, such as a cellular phone, a tablet computer, or a laptop computer. It is contemplated that the external computer 2166 could be used to manipulate, adjust, or change portions of the message 2135 such as the transcription 2164 which would then be uploaded back onto the audio database server 2158.
Referring now to FIG. 22, therein is shown a block diagram for wear leveling the memory 2136 of the server beacon mass storage 2108 for the server beacon 2102 of FIG. 21. The server beacon 2102 is depicted having the server beacon mass storage 2108 with the mass storage queue 2134 and the memory 2136 included therein. For clarity the following wear leveling is described with regard to uploading the audio data 2122 of FIG. 21 to the memory 2136; however, it will be appreciated that the same technique is used on other data such as portions of the messages 2135 of FIG. 21 and the gesture data 2128 of FIG. 21.
It is contemplated that the audio data 2122 can be uploaded and stored within the memory 2136 before being uploaded to the audio database server 2158 of FIG. 21. In some configurations the memory 2136 can be implemented as flash memory, which has a limited number of reads and writes to each of the bits BIT (0) 2138 of FIG. 21 through BIT (N) 2144 of FIG. 21.
For example, if BIT (2) 2142 of FIG. 21 is constantly written to, then BIT (2) 2142 could fail after a certain number of writes. A bit failure could possibly render the server beacon 2102 useless or such that it propagates corrupt data that is noisy or impossible to interpret by downstream computer systems.
To prevent any single bit from being used more often than others, the server beacon 2102 can implement the mass storage queue 2134 which is contemplated to be a circular queue. That is, the mass storage queue 2134 will step sequentially through the bits BIT (0) 2138 through BIT (N) 2144 when recording the audio data 2122, once the last bit BIT (N) 2144 is reached, the mass storage queue 2134 will circle back to the first bit BIT (0) 2138.
To illustrate the function of the mass storage queue 2134, the memory 2136 is shown in three different states including a pre-upload memory 2202, a post-upload memory 2204, and a full memory 2206. The pre-upload memory 2202 depicts the memory 2136 in an initial state having existing audio data 2208 saved therein.
As can be seen, the existing audio data 2208 is saved to the pre-upload memory 2202 beginning at BIT (0) 2138. The existing audio data 2208 is further shown as recorded to the pre-upload memory 2202 sequentially. The memory 2136 is shown having free memory 2210 listed sequentially after the end of the existing audio data 2208 and extending sequentially from the existing audio data 2208 to the BIT (N) 2144.
The post-upload memory 2204 depicts the pre-upload memory 2202 after new audio data 2212 is uploaded and recorded to the memory 2136. The existing audio data 2208 retains its location relative to the bits within the memory 2136 while the mass storage queue 2134 points to the next bit after the existing audio data 2208 for recording the new audio data 2212.
The new audio data 2212 thus is recorded in the bits beginning immediately after the existing audio data 2208 sequentially down. The amount of the free memory 2210 is shown to be reduced by the amount of the new audio data 2212 and extends from just after the new audio data 2212 to the BIT (N) 2144.
It is contemplated that the mass storage queue 2134 will be incremented to the end of the new audio data 2212 only after a complete save. For example, if the upload of the new audio data 2212 to the memory 2136 is interrupted, the mass storage queue 2134 will remain as a pointer for the server beacon 2102 to upload subsequent data immediately after the existing audio data 2208.
The full memory 2206 depicts an alternate initial starting state from the pre-upload memory 2202. That is, the existing audio data 2208 is shown occupying bits in the middle of the memory 2136.
As will be appreciated, when the new audio data 2212 is uploaded and recorded to the memory 2136, the mass storage queue 2134 will point the server beacon 2102 to begin the upload of the new audio data 2212 to the bits immediately after the existing audio data 2208 and proceed to the end of the memory 2136, or BIT (N) 2144. Once the mass storage queue 2134 hits BIT (N) 2144, the mass storage queue 2134 will circle back to BIT (0) 2138 and the server beacon 2102 will continue recording the new audio data 2212 from BIT (0) 2138.
The remaining free memory 2210 is shown between the new audio data 2212, above, and the existing audio data 2208, below.
It is contemplated that after the audio data 2122 is uploaded from the memory 2136 to the power station 2104 of FIG. 21, the portion of the memory holding the audio data 2122 uploaded to the power station 2104 will be considered as the free memory 2210 and used to record subsequent data. However, it will be understood that the mass storage queue 2134 does not adjust based on the audio data 2122 being uploaded to the power station 2104 but remains pointed to the same bit within the memory 2136 for subsequent data uploads to the memory 2136.
It has been discovered that one important aspect of the mass storage queue 2134 is that it is a very simple data structure maintaining just a pointer to the start of the bit holding data, and a pointer to last bit holding data, which is well suited for implementation with microcontrollers that lack the resources of larger processors.
Referring now to FIG. 23, therein is shown a block diagram of an upload coordinator 2302 in the power station 2104 of FIG. 21. The upload coordinator 2302 will be described as a component within the power station 2104; however, it is alternatively contemplated that the upload coordinator 2302 can be located inside a standalone device in a form factor similar to a wall mounted AC-DC converter or included within a Wi-Fi router, which can provide power savings.
The upload coordinator 2302 is depicted having an upload coordinator queue 2303. The upload coordinator queue 2303 can contain data about priorities of the audio data 2122 of FIG. 21.
In order to illustrate the upload coordinator 2302, the upload coordinator 2302 is shown wirelessly connected to three server beacons 2102 of FIG. 21 each of the server beacon 2102 including the server beacon mass storage 2108. The server beacon mass storages 2108 of the three server beacon 2102 connected to the upload coordinator 2302 can be communicatively coupled through the server beacon power transceiver 2110 of FIG. 21 and the power station power transceiver 2148 of FIG. 21.
For example, the server beacon mass storage 2108 of the three server beacons 2102 can include a first mass storage 2304, a second mass storage 2306, and a third mass storage 2308. The first mass storage 2304, the second mass storage 2306, and the third mass storage 2308 are all shown having the memory 2136 each including a different ratio of the existing audio data 2208 and the free memory 2210.
For clarity the memory 2136 and the upload coordinator 2302 will be illustrated with regard to the audio data 2122; however, it will be appreciated that other data including the message 2135 of FIG. 21 and the gesture data 2128 of FIG. 21 could also be used with the compliance system 2100 of FIG. 21. The upload coordinator 2302 can be used to store packets 2310 from server beacon 2102.
The packets 2310 can be segments of data about the audio data 2122 or other data such as the gesture data 2128. As is shown, the first mass storage 2304 can include the existing audio data 2208 requiring much less space within the memory 2136 than the free memory 2210 still available, thus the first mass storage 2304 is depicted having a large amount of free memory 2210 available.
The second mass storage 2306 is depicted having the existing audio data 2208 occupying just over half of the memory 2136 available while the free memory 2210 of the second mass storage 2306 occupies slightly less than half of the total memory 2136. The third mass storage 2308 is depicted having the existing audio data 2208 occupying most of the memory 2136 space while the free memory 2210 is shown as relatively little of the total memory 2136 available.
The server beacon mass storages 2108 are also shown to include a storage threshold 2312. The storage thresholds 2312 of the server beacon mass storages 2108 can be unique for each of the server beacon sensors 2106 depending on the usage and memory requirements for each of the server beacon sensors 2106.
The storage thresholds 2312 can also be preset to a standard size or ratio of the memory 2136. For example, it is contemplated that the storage thresholds 2312 could be set to eighty percent usage. When the existing audio data 2208 is greater than eighty percent of the total memory 2136 available then the existing audio data 2208 would be above the storage threshold 2312.
Referring now to FIG. 24, therein is shown a block diagram of the packet 2310 of FIG. 23. The packet 2310 can be an exemplary packet from any one of the server beacon sensors 2106 of FIG. 21 as described with regard to FIG. 23. As will be appreciated, the packets 2310 can enable the upload coordinator 2302 of FIG. 23 to organize the upload coordinator queue 2303 for determining which of the audio data 2122 within the server beacon mass storages 2108 of FIG. 21 should be uploaded in which order.
The packet 2310 is depicted including fields such as a preamble 2402, an ID field 2404, a quantity field 2406, and a priority flag 2408. The preamble 2402 can be a header and contain data about the type of the packet 2310 being transmitted and other information allowing the power station 2104 of FIG. 21 to detect the beginning of the packet 2310 transmission.
The ID field 2404 can contain data indicating or identifying the specific server beacon 2102 transmitting the packet 2310. The ID field 2404 can enable the power station 2104 an acknowledgement or response to the specific server beacon 2102 transmitting the packet 2310.
The quantity field 2406 can contain data for the upload coordinator 2302 of FIG. 23 to determine how much the server beacon 2102 transmitting the packet 2310 is requesting to upload to the power station 2104. For example, the quantity field 2406 can indicate the size of the existing audio data 2208 of FIG. 23.
The priority flag 2408 is contemplated to include at least two priorities, such as a high priority and a low priority. Alternate implementations of the priority flag 2408 can include more priorities such as a low priority, a medium priority, and a high priority.
It is contemplated that the storage threshold 2312 of FIG. 23 can be used to set the priority flag 2408. For example, if the size of the existing audio data 2208 that the server beacon 2102 is requesting to upload to the power station 2104 is above the storage threshold 2312, the priority flag 2408 can be set to high priority. On the other hand, if the size of the existing audio data 2208 that the server beacon 2102 is requesting to upload to the power station 2104 is less than the storage threshold 2312, the priority flag 2408 can be set to low priority.
It is contemplated that when the priority flag 2408 includes multiple priorities, the storage threshold 2312 can include multiple thresholds. For example, the storage threshold 2312 could contain a medium level, like fifty percent, and could further contain a high level, like eighty percent.
Continuing with this example, the priority flag 2408 could be set to low priority based on the existing audio data 2208 that the server beacon 2102 is requesting to upload to the power station 2104 being below the medium level of the storage threshold 2312. The priority flag 2408 could be set to medium priority based on the existing audio data 2208 that the server beacon 2102 is requesting to upload to the power station 2104 being between the medium level and the high level of the storage threshold 2312. The priority flag 2408 could be set to high priority based on the existing audio data 2208 that the server beacon 2102 is requesting to upload to the power station 2104 being above the high level of the storage threshold 2312.
The priority flag 2408 can be used by the upload coordinator 2302 of the power station 2104 for many things. For example, the upload coordinator 2302 can request that the server beacon 2102 upload the packet 2310 using the high speed server beacon power transceiver 2110 rather than a lower power option such as the beacon communication unit 106 of FIG. 1.
Further, the priority flag 2408 can be used by the upload coordinator 2302 of the power station 2104 to determine which order the server beacons 2102 will upload the packets 2310 to the power station 2104. For example, the upload coordinator 2302 may select a server beacon 2102 having the packet 2310 with the priority flag 2408 set to high priority to upload the packet 2310 before selecting a server beacon 2102 having the packet 2310 with the priority flag 2408 set to low priority.
It is further contemplated that the priority flag 2408 can be set based on a user input such as a gesture detected by the gesture sensor 2126 of FIG. 21. For example, if the gesture sensor 2126 detects a gesture of a user indicating a request to immediately upload the audio data 2122 to the power station 2104, the priority flag 2408 can be set to high and prioritized above uploads from other server beacon sensors 2106 having packets 2310 with the priority flag 2408 set to lower priorities.
Referring now to FIG. 25, therein is shown a block diagram of manual transcription for the compliance system 2100 of FIG. 21. The manual transcription can generate the transcription 2164 from the audio data 2122.
As is shown, a user 2502 can provide the audio data 2122 by utilizing the microphone 2120 of FIG. 21 within the server beacon 2102 of FIG. 21. Once the audio data 2122 is generated, the audio data 2122 can be uploaded to the memory 2136 of FIG. 21 within the server beacon 2102, then eventually to the audio database server 2158 through the power station 2104 and other elements within the compliance system 2100 of FIG. 21.
The audio data 2122 can be pushed or pulled from the audio database server 2158 by a manual transcriber 2504. The manual transcriber 2504 is contemplated to be the user 2502 or a paid audio transcriber service provider.
Whether the manual transcriber 2504 is the user 2502 or the paid audio transcriber service provider it is contemplated that the audio data 2122 will be transcribed manually by a person. It is contemplated that the manual transcriber 2504 can request the audio data 2122 from the audio database server 2158, the audio database server 2158 can then provide the audio data 2122 to the manual transcriber 2504.
The manual transcriber 2504 can play the audio data 2122 as a recorded sound and produce the transcription 2164. The audio data 2122 can be played or provided through the external computer 2166 of FIG. 21 and the transcription 2164 can be entered and created with the same external computer 2166 or a different external computer 2166.
Once the transcription 2164 is created the transcription 2164 is uploaded to the audio database server 2158 and combined with the message 2135 of FIG. 21 as the transcription 2164 field of the message 2135. Upon request, the transcription 2164 and the audio data 2122 can be provided from the audio database server 2158 to the external computer 2166 of the user 2502.
Referring now to FIG. 26, therein is shown a block diagram of automatic transcription for the compliance system 2100 of FIG. 21. The automatic transcription can generate the transcription 2164 from the audio data 2122.
As is shown, the user 2502 can provide the audio data 2122 by utilizing the microphone 2120 of FIG. 21 within the server beacon 2102 of FIG. 21. Once the audio data 2122 is generated, the audio data 2122 can be uploaded to the memory 2136 of FIG. 21 within the server beacon 2102, then eventually to the audio database server 2158 through the power station 2104 and other elements within the compliance system 2100 of FIG. 21.
The audio data 2122 can be pushed or pulled from the audio database server 2158 by an automated transcriber 2604. The automated transcriber 2604 can receive the pushed audio data 2122 or pull the audio data 2122 from the audio database server 2158 using a processor and storing the audio data 2122 in non-transitory computer readable memory. The automated transcriber 2604 can be a standalone computer or part of a distributed system including the external computer 2166 of FIG. 21.
In one contemplated implementation, the automated transcriber 2604 can receive a signal from the audio database server 2158 indicating the audio data 2122 is available and needs to be transcribed. The automated transcriber 2604 can then pull the audio data 2122 from the audio database server 2158 to begin the transcription.
Once the transcription 2164 is created the transcription 2164 is uploaded to the audio database server 2158 and combined with the message 2135 of FIG. 21 as the transcription 2164 field of the message 2135. Upon request, the transcription 2164 and the audio data 2122 can be provided from the audio database server 2158 to the external computer 2166 of the user 2502.
It is contemplated that there may be a time delay for the user 2502 to receive the transcription 2164 if the audio data 2122 was uploaded with the priority flag 2408 of FIG. 24 was set to the low priority. It is contemplated that when the audio data 2122 was uploaded with the priority flag 2408 set to the high priority the automated transcriber 2604 can prioritize the transcription 2164 performing it before the transcription 2164 of audio data 2122 uploaded as low priority.
Further it is contemplated that the automated transcriber 2604 can prioritize the transcription 2164 of the audio data 2122, over audio data 2122 uploaded as low priority, based on the user 2502 opening an interface on the external computer 2166 for listening to the audio data 2122 or viewing the transcription 2164.
Referring now to FIG. 27, therein is shown a block diagram of a training mode for the automatic transcription of FIG. 26. The automated transcriber 2604 as depicted in FIG. 26, can be placed into a training mode to improve accuracy 2702 of the transcription 2164 by adapting to the particularities of each individual user's 2502 voice.
As is shown, the user 2502 can provide the audio data 2122 by utilizing the microphone 2120 of FIG. 21 within the server beacon 2102 of FIG. 21. Once the audio data 2122 is generated, the audio data 2122 can be uploaded to the memory 2136 of FIG. 21 within the server beacon 2102, then eventually to the audio database server 2158 through the power station 2104 and other elements within the compliance system 2100 of FIG. 21.
The audio data 2122 can be pushed or pulled from the audio database server 2158 by the manual transcriber 2504. The manual transcriber 2504 is contemplated to be the user 2502 or a paid audio transcriber service provider.
Whether the manual transcriber 2504 is the user 2502 or the paid audio transcriber service provider it is contemplated that the audio data 2122 will be transcribed manually by a person. It is contemplated that the manual transcriber 2504 can request the audio data 2122 from the audio database server 2158, the audio database server 2158 can then provide the audio data 2122 to the manual transcriber 2504.
The manual transcriber 2504 can play the audio data 2122 as a recorded sound and produce the transcription 2164. The audio data 2122 can be played or provided through the external computer 2166 of FIG. 21 and the transcription 2164 can be entered and created with the same external computer 2166 or a different external computer 2166.
Once the transcription 2164 is created the transcription 2164 is uploaded to the audio database server 2158 and combined with the message 2135 of FIG. 21 as the transcription 2164 field of the message 2135. Upon request, the transcription 2164 and the audio data 2122 can be provided from the audio database server 2158 to the external computer 2166 of the user 2502.
Further, the audio data 2122 can be pushed or pulled from the audio database server 2158 by the automated transcriber 2604. The automated transcriber 2604 can receive the pushed audio data 2122 or pull the audio data 2122 from the audio database server 2158 using a processor and storing the audio data 2122 in non-transitory computer readable memory. The automated transcriber 2604 can be a standalone computer or part of a distributed system including the external computer 2166.
In one contemplated implementation, the automated transcriber 2604 can receive a signal from the audio database server 2158 indicating the audio data 2122 is available and needs to be transcribed. The automated transcriber 2604 can then pull the audio data 2122 from the audio database server 2158 to begin the transcription and while in training mode, the automated transcriber 2604 will produce a training transcription 2702.
The training transcription 2702 can be an automated transcription of the audio data 2122 based on the current voice mapping of the user 2502 providing the audio data 2122. The automated transcriber 2604 can also pull the transcription 2164 from the audio database server 2158 produced by the manual transcriber 2504.
The training transcription 2702 can be compared with the transcription 2164 produced by the manual transcriber 2504 to determine an accuracy 2704. The accuracy 2702 can be a word for word comparison between the transcription 2164 and the training transcription 2702 and can be represented as a percentage. That is, the number of words in the training transcription 2702 that correctly correspond to the words of the transcription 2164 over the total number of words contained within transcription 2164.
The automated transcriber 2604 is further shown with an accuracy threshold 2706. The accuracy threshold 2706 can be the minimum accuracy 2702 needed before the automated transcriber 2604 will be placed in the standard automatic transcription mode described in FIG. 26.
The accuracy 2702 can be transmitted back to the audio database server 2158 where it can be associated with the audio data 2122. It is also contemplated that the training transcription 2702 can be transmitted back to the audio database server 2158 where it can be associated with the audio data 2122.
In other embodiments, the determination of the accuracy 2702 and comparison with the accuracy threshold 2706 can be done on other external processors, in which case the training transcription 2702 can be uploaded to the audio database server 2158 and then provided to the external processor for comparison to the transcription 2164 and for determining a current compliance with the accuracy threshold 2706.
The training transcription 2702, the audio data 2122 and the transcription 2164 can be pulled by the user 2502 from the audio database server 2158 and displayed on the external computer 2166. The user 2502 can provide a rating 2708 for the training transcription 2702.
The rating 2708 can be uploaded to the audio database server 2158 and associated with the audio data 2122, the training transcription 2702, and the transcription 2164 for determining whether the automated transcriber 2604 meets the accuracy threshold 2706 required to run in the standard mode described in FIG. 26. It is contemplated that the automated transcriber 2604 can be adapted to the particularities of each individual user's 2502 voice such as requiring the user 2502 to speak a list of words, which would then be recorded as the audio data 2122 and used to generate the training transcription 2702.
When the list of words is spoken by the user 2502; however, the manual transcriber 2504 is not required as the comparison for the accuracy 2702 can be accomplished by comparing the training transcription 2702 to a known transcription 2164 of the list of words. It is contemplated that requiring the user 2502 to speak the list of words can be required during an initial setup procedure or when it is determined that the training transcription 2702 is falling below a lower accuracy threshold.
Referring now to FIG. 28, therein is shown a block diagram and graphical display of an audio record user interface 2802 for the external computer 2166. The external computer 2166 can display the audio record user interface 2802. The external computer 2166 can include a cellular phone, a tablet computer, a laptop computer, or other standalone computing device.
The audio record user interface 2802 is shown to have rows and columns. The rows of the audio record user interface 2802 can correspond to each individual audio data 2122 recording while the columns of the audio record user interface 2802 can correspond to attributes of the audio data 2122 recordings.
The attributes of the audio data 2122 within the columns can include a count 2804, the audio time stamp 2162, a duration 2806, a location 2808, an audio control 2810, and a completion 2812. The count 2804 can be the sequential listing of each recording of the audio data 2122.
Illustratively, the count 2804 numbers the rows from one to three which indicates the consecutive relationship of the audio data 2122 recordings. The audio time stamp 2162 can be the time that the audio data 2122 was recorded. It is contemplated that when the audio data 2122 was recorded on a previous day the date would also be shown as part of the audio time stamp 2162.
The duration 2806 attribute indicates the length of the audio data 2122 in minutes and seconds. The location 2808 can indicate where the audio data 2122 was recorded.
It is to be understood that the audio record user interface 2802 can display visual depictions of a physical objects based on raw data collected from the server beacon 2102 of FIG. 21 at the time the audio data 2122 of FIG. 21 was recorded.
For example, when the server beacon 2102 records the audio data 2122, the server beacon 2102 can also detect the location that the audio data 2122 was recorded as described above with regard to the user info 2160 of FIG. 21 field within the message 2135 of FIG. 21. The location is herein understood as physical objects including rooms, hallways, and floor levels within buildings, which can be detected using proximity to various wireless devices. The proximity data is considered raw data which is then manipulated and displayed as a location 2808 on the audio record user interface 2802. For example, the location 2808 is depicted as “ROOM 22” or “SERG 2”, which identifies the location that the audio data 2122 was recorded.
The audio control 2810 can provide control for the play back of the audio data 2122. The audio control 2810 is depicted as a triangular play button. It is contemplated that when the audio data 2122 is playing the audio control 2810 can change into a pause button to allow the user 2502 of FIG. 25 to pause the playback of the audio data 2122.
The audio data 2122 can be played by a user over speakers on the external computer 2166 or, as is depicted by transmitting the audio data 2122 through an audio jack 2814 to be projected through headphones 2816. The completion 2812 attribute can be a check box that the user 2502 can check to indicate whether any further action is required.
In one contemplated embodiment, after the user 2502 checks the completion 2812 to indicate that no further action is required the audio data 2122 associated with the checked completion 2812 attribute will not be displayed once the audio record user interface 2802 is refreshed. The audio data 2122 associated with the completion 2812 that are not checked indicate that action may still be required and the audio data 2122 will continue to be displayed upon refreshing the audio record user interface 2802.
Referring now to FIG. 29, therein is shown a block diagram and graphical display of a medical record transaction user interface 2902 for the external computer 2166. The external computer 2166 can display the audio record user interface 2802 together with the medical record transaction user interface 2902 on a display 2904 of the external computer 2166. The external computer 2166 can be a cellular phone, a tablet computer, a laptop computer, or other standalone computing device.
The user 2502 is depicted interacting with the external computer 2166 through a peripheral 2906 such as a keyboard, touch pad, speech to text, touch screen, or on screen keyboard. The medical record transaction user interface 2902 can be used to create a transcription record 2908.
The transcription record 2908 can include a notes section 2910 including fields for patient's names 2912, transcription time stamps 2914, and the transcription 2164.
The patient's names 2912 can be a patient that the audio data 2122 of FIG. 21 is associated with. The transcription time stamps 2914 can indicate the time that the transcription 2164 was completed or can indicate the time that the transcription record 2908 was created.
The transcription record 2908 may be transmitted over the local network 2150, the internet 2154 of FIG. 21, or a combination there of as is described in FIG. 21. The transcription record 2908 can be uploaded and stored to the audio database server 2158.
The transcription 2164 can be associated with the audio data 2122 within the message 2135 of FIG. 21 within the audio database server 2158. The medical record transaction user interface 2902 can provide a separate dedicated user interface to enter information into a medical record that is run and operated completely independent from the process for recording the audio data 2122 and the process for producing the transcription 2164. Alternatively, an application may be constructed that integrates both.
It has been discovered that one benefit of keeping the interfaces separate is that regulations regarding medical records, which may be difficult or complicated to comply with, would not apply to the note-taking and transcribing system. In this way, the user 2502 may be able to use the note system in a more interactive way (such as an app on a phone) that would not be allowed were it subject to the Medical Record System regulations.
Referring now to FIG. 30, therein is shown a graphical view of the gesture data 2128 for the gesture sensor 2126 of the server beacon 2102 of FIG. 21. The gesture sensor 2126 is depicted having a sensory area 3002 where the gesture sensor 2126 can detect the gesture data 2128.
The sensory area 3002 is depicted sensing a hand 3004 of the user 2502 of FIG. 25. The gesture of the hand 3004 is shown to be the hand moving right with four fingers up.
The gesture sensor 2126 is shown to produce the gesture data 2128 when the hand 3004 gesture is made. Illustratively, gesture data 2128 created by the hand 3004 gesture with four fingers up moving to the right is depicted as gesture data having four pulses 3006.
The pulses 3006 can be the detection of each finger held apart from other fingers. The pulses can move with the movement of the hand 3004 across the sensory area 3002. Other gestures can include moving the hand 3004 with four fingers held up to the left.
Yet other gestures can include holding the hand 3004 up with only two fingers extended and moving to the left or the right. The gesture data 2128 detected when the hand 3004 holds only two fingers can be seen as the gesture data 2128 with only two pulses.
Yet other gestures can include holding the hand 3004 up with all fingers held tightly together without a space between the fingers, which produces the gesture data 2128 having only a single pulse. It is contemplated that other gestures can produce more varied gesture data 2128. For example, it is contemplated that the hand 3004 could be held and the fingers raised and lowered to produce the pulses 3006 that does not transition across the sensory area 3002 from the left or right but is stationary.
The server beacon 2102 can classify the gesture data 2128 detected by the gesture sensor 2126 and trigger other functions. For example, the microphone 2120 could be turned on when the user 2502 waives the hand 3004 holding up four fingers across the sensory area 3002 from left to right and turn off the microphone 2120 when the user 2502 waives the hand 3004 holding up four fingers across the sensory area 3002 from right to left.
Further, it is contemplated that the gesture data 2128 could be used to control the audio control 2810 of FIG. 28 for playing the audio data 2122, pausing the audio data 2122, or erasing the audio data 2122. It has been discovered that generating the gesture data 2128 by detecting the pulses 3006 for controlling the functions of the server beacon 2102 and other elements of the compliance system 2100 greatly reduces the amount of infections transmitted while using the compliance system 2100 while simultaneously providing accurate, simple, and intuitive control.
Referring now to FIG. 31, therein is shown a first control flow for the gesture sensor 2126 of FIG. 21. The server beacon 2102 of FIG. 21 can begin the control flow by executing an initialization step 2102.
During the initialization step 2102, the gesture sensor 2126 can be turned off and the motion sensor 2112 of FIG. 21 can be set to a low power monitoring mode. Further during the execution of the initialization step 2102 a variable R_S 3104 can be set to OFF.
The R_S 3104 can be a recording state of the microphone 2120 of FIG. 21. Once the initialization step 2102 is completed, the server beacon 2102 can execute a stillness decision step 3106.
The stillness decision step 3106 can determine whether the motion sensor 2112 of the server beacon 2102 detects any motion. For example, when the motion sensor 2112 is implemented as an accelerometer, the motion decision step 3106 can determine whether the server beacon 2102 is experiencing any acceleration.
If the server beacon 2102 is motionless or still, the stillness decision step 3106 can return an affirmative result and the server beacon 2102 can proceed to execute a stillness time decision step 3108. During the stillness time decision step 3108 the server beacon 2102 can compare the total time that the server beacon 2102 has been still against a stillness threshold 3110.
The stillness threshold 3110 can be a length of time and when the server beacon 2102 has been still for longer than the stillness threshold 3110, the stillness time decision step 3108 can return an affirmative result and the server beacon 2102 can again execute the initialization step 2102.
When the length of time that the server beacon 2102 has been still is less than the stillness threshold 3110, the stillness time decision step 3108 can return a negative result and the server beacon 2102 can again execute the stillness decision step 3106. Once the server beacon 2102 detects movement from the motion sensor 2112, the stillness decision step 3106 can return a negative result and the server beacon 2102 can proceed to execute a turn off motion sensor step 3112.
The turn off motion sensor step 3112 can turn off the motion sensor 2112 to save power when it is not needed. It is contemplated that the server beacon 2102 can reactivate the motion sensor 2112 if, for example, the server beacon 2102 is being used with a game on the power station 2104 similar to that described above with regard to the compliance system 300 of FIG. 3.
Referring now to FIG. 32, therein is shown a second control flow for the gesture sensor 2126 continuing from the turn off motion sensor step 3112 of FIG. 31. The server beacon 2102 can execute a set gesture sensor 3202.
While executing the set gesture sensor 3202, the server beacon 2102 can set a variable P_WAKE 3204 to a value indicating proximity to the server beacon 2102. For example, the P_WAKE 3204 could be set to 6-18 inches and when the gesture sensor 2126 detects an object within the P_WAKE 3204 the gesture sensor 2126 could operate in a high power mode allowing the gesture sensor 2126 to scan at a higher power, a higher frequency, or even use higher power sensors.
When the gesture sensor 2126 does not detect an object within the P_WAKE 3204, the gesture sensor 2126 can operate in a low power mode, for example scanning less frequently, with less power, or by using only low power sensors. It has been discovered that implementing the P_WAKE 3204 proximity threshold with the gesture sensor 2126 enables the gesture sensor 2126 to greatly reduce power consumption while enabling a higher degree of discernment in the detection and utilization of true gestures.
As will be appreciated, once the P_WAKE 3204 is set in the set gesture sensor 3202, the server beacon 2102 can execute a proximity decision step 3206. The proximity decision step 3206 can determine whether the server beacon 2102 is detecting an object or motion within the P_WAKE 3204.
If no motion or object is detected by the gesture sensor 2126 within the P_WAKE 3204, the proximity decision step 3206 can return a negative result and re-execute the proximity decision step 3206 until an object or motion is detected within the P_WAKE 3204.
Illustratively, when the server beacon 2102 is worn on the lapel of the user 2502 of FIG. 25, the value of the P_WAKE 3204 may be used to filter out motions and objects at an arm's length, for example when the user 2502 is speaking with a colleague; however, when the user 2502 begins to gesture with the hand 3004 of FIG. 30 within the P_WAKE 3204, the gesture sensor 2126 can recognize the motions of the user 2502 as potential gestures.
Once a motion or object is detected by the gesture sensor 2126 within the P_WAKE 3204, the proximity decision step 3206 can return an affirmative result and the server beacon 2102 can execute a gesture monitor step 3208. The gesture monitor step 3208 can wake a microprocessor on the server beacon 2102 to monitor and process the gesture data 2128 of FIG. 21 detected by the gesture sensor 2126.
Once the processor of the server beacon 2102 is activated, the server beacon 2102 can execute a gesture detected decision step 3210. During the execution of the gesture detected decision step 3210, the server beacon 2102 can determine whether the motion or object detected that is within or closer than the P_WAKE 3204 is a gesture, for example by correlating or resembling known gesture data 2128.
If the motion or object detected by the gesture sensor 2126 is not recognized as a known gesture the gesture detected decision step 3210 can return a negative result and the server beacon 2102 can again execute the set gesture sensor 3202. Alternatively, when the gesture data 2128 detected by the gesture sensor 2126 is similar, correlated, or resembling known gesture data 2128, the gesture detected decision step 3210 can return an affirmative result and the server beacon 2102 can execute an audio gesture decision step 3212.
The audio gesture decision step 3212 can determine whether the gesture data 2128 corresponds to an audio command such as waiving four raised spaced apart fingers to the right or left in front of the gesture sensor 2126 as is described with regard to FIG. 30. If the audio gesture decision step 3212 does not recognize the gesture data 2128 as an audio command, the gesture sensor 2126 can again execute the set gesture sensor 3202.
It is contemplated that the gesture sensor 2126 can execute many other specific types of gesture detection for commands other than audio. For example, if the audio gesture decision step 3212 returns a negative result the gesture sensor 2126 might, in other embodiments, execute a priority gesture such as determining whether the gesture of the user 2502 is recognized as a gesture that would instruct the gesture sensor 2126 to make the message 2135 of FIG. 21 high priority.
The audio commands are described here for ease of description only, and those having ordinary skill in the art would recognize that the gesture data 2128 could be determined by the gesture sensor 2126 to be many different and specific commands. Continuing with the audio example, if the audio gesture decision step 3212 recognizes the gesture data 2128 as corresponding, resembling, or being similar to an audio gesture, the audio gesture decision step 3212 can return an affirmative result and the server beacon 2102 can proceed to executing an R_S check decision step 3214.
The R_S check decision step 3214 can check and determine whether the variable R_S 3104 is set to on or off. For example, it is contemplated that the R_S 3104 could be a single flag set to a one or a zero, with one corresponding to the microphone 2120 of FIG. 21 set to on and zero corresponding to the microphone 2120 turned off.
If the gesture sensor 2126 executing the audio gesture decision step 3212 determines that the R_S 3104 is set to off, the gesture sensor 2126 can execute an activate microphone step 3218. The activate microphone step 3218 can set the R_S 3104 to on in order to activate the microphone 2120 on the server beacon 2102 and begin recording the audio data 2122 of FIG. 21.
If the R_S check decision step 3214 determines that the R_S 3104 is already set to on, the R_S check decision step 3214 can return an affirmative result and execute a stop recording step 3220. The stop recording step 3220 can set the R_S 3104 to off to turn the microphone 2120 off and stop the recording of the audio data 2122 by the server beacon 2102.
Further, during the stop recording step 3220, the server beacon 2102 can tag the audio data 2122 recorded by the microphone 2120 with the length of the recording as well as the user info 2160 of FIG. 21 and the audio time stamp 2162 of FIG. 21. Lastly, during the stop recording step 3220, the server beacon 2102 can copy the audio data 2122 to the server beacon mass storage 2108 of FIG. 21. Once the server beacon 2102 has executed either the activate microphone step 3218 or the stop recording step 3220, the server beacon 2102 can again execute the set gesture sensor 3202 and wait for a new gesture.
Gesture recognition steps such as audio gesture decision step 3212 can take into context the current state of the system, such as whether RS_ON is 0 or 1. By taking into account contextual information such as this it is possible for gesture recognition systems such as the audio gesture decision step 3212 to have improved accuracy since the set of gestures that are relevant in a given context may be reduced. It is contemplated that this reduction in the number of acceptable gestures for a given context significantly reduces the complexity of gesture recognition steps such that it can achieve higher accuracy from fewer sensor readings, thereby achieving lower power.
Referring now to FIG. 33, therein is shown a first control flow for uploading the audio data 2122 of FIG. 21. The control flow can begin with a data upload decision step 3302.
The data upload decision step 3302 can determine whether there is any of the audio data 2122 of FIG. 21 within the message 2135 of FIG. 21 stored in the server beacon mass storage 2108 of FIG. 21 that needs to be uploaded to the audio database server 2158 of FIG. 21 through the power station 2104 of FIG. 21. That is, the data upload decision step 3302 can check the server beacon mass storage 2108 and determine whether the server beacon mass storage 2108 includes any audio data 2122 that has not been uploaded to the audio database server 2158.
If there is no audio data 2122 that has not been uploaded to the audio database server 2158 or to the power station 2104, the data upload decision step 3302 can return a negative result and the server beacon 2102 of FIG. 21 will again execute the data upload decision step 3302 until the audio data 2122 is found that requires upload. It is contemplated that the server beacon power transceiver 2110 of FIG. 21 can be operated in a low power mode while the data upload decision step 3302 checks to determine whether any audio data 2122 needs to be uploaded.
If there is audio data 2122 on the server beacon mass storage 2108 that has not been uploaded to the power station 2104 or the audio database server 2158, the data upload decision step 3302 can return an affirmative result and an include request step 3304 can be executed by the server beacon 2102.
The include request step 3304 can include a fast request 3306 within the transmissions between the beacon communication unit 106 within the beacon 100 of FIG. 1 and the power station 2104. The fast request 3306 can be a low power communication signaling to the power station 2104 that a fast upload is requested. The fast request 3306 can be broadcast by the server beacon 2102 to the power station 2104 intermittently.
Simultaneously with the include request step 3304, or after the include request step 3304, the server beacon 2102 can execute a fast upload ready decision step 3308. The fast upload ready decision step 3308 can check to determine whether the server beacon 2102 received a fast ready 3310 signal from the power station 2104 indicating that the power station 2104 is ready to receive a fast upload from the server beacon power transceiver 2110 during the most recent listening window for the server beacon 2102.
It is contemplated that the fast upload ready decision step 3308 can be executed only once the server beacon 2102 receives a packet from the power station 2104 thus reducing the processing and power overhead required to perform the fast upload ready decision step 3308. If a packet has not been received by the server beacon 2102, then the server beacon 2102 can be operated in a low power state, for example, by placing electronic circuits in an off or non-switching state.
If the fast ready 3310 was not received by the server beacon 2102 during the most recent listening window the server beacon 2102 will continue to execute the fast upload ready decision step 3308 and can continue to execute the include request step 3304. If the fast ready 3310 was received by the server beacon 2102 during the most recent listening window, the server beacon 2102 can execute a log and reset step 3312.
During the log and reset step 3312 the server beacon 2102 can perform many actions such as logging a station ID 3314 of the power station 2104 that sent the fast ready 3310 to the server beacon 2102 and logging an RSSI 3316 of the power station 2104 that sent the fast ready 3310 to the server beacon 2102. Further, during the log and reset step 3312, the server beacon 2102 can set variables F_MISS 3318 and F_HIT 3320.
The F_MISS 3318 can be the total number of opportunities for a fast-ready-upload signal that were in fact not received by the server beacon 2102 during listening windows. During the log and reset step 3312 the F_MISS 3318 can be set to zero, thus resetting the F_MISS 3318, which can be used to monitor the availability for fast upload by the power station 2104.
The F_HIT 3320 can be a total number of packets received by the server beacon 2102 that lacked the fast ready 3310 signal from the power station 2104. During the log and reset step 3312, the server beacon 2102 can set F_HIT 3320 to zero.
Referring now to FIG. 34, therein is shown a second control flow for uploading the audio data 2122 of FIG. 21 and continuing from the log and reset step 3312 step of FIG. 33. The server beacon 2102 can execute a wait step 3402.
The 3402 can place the server beacon 2102 of FIG. 21 or the server beacon power transceiver 2110 of FIG. 21 in a low power state until the server beacon 2102 is again in a listening window. Once the next listening window is initiated by the server beacon 2102 or a period of time for the listening window to begin passes, the server beacon 2102 can wake the processor and initiate the fast upload ready decision step 3308.
The fast upload ready decision step 3308 can check to determine whether the server beacon 2102 received the fast ready 3310 signal from the power station 2104 indicating that the power station 2104 is ready to receive a fast upload from the server beacon power transceiver 2110 of FIG. 21 during the most recent listening window for the server beacon 2102.
It is contemplated that the fast upload ready decision step 3308 run after the wait step 3402 can be the same fast upload ready decision step 3308 as is described with regard to FIG. 33; however, the fast upload ready decision step 3308 performed after the wait step 3402 can be preceded and followed by different steps than those described above with regard to FIG. 33.
Illustratively, when the fast upload ready decision step 3308 of FIG. 34 determines that the fast ready 3310 was not received in the latest listening window of the server beacon 2102, the server beacon 2102 can execute an F_MISS increment step 3404. The F_MISS increment step 3404 can increment the value of the F_MISS 3318 variable by one or F_MISS+1.
After the F_MISS 3318 is incremented in the F_MISS increment step 3404, the server beacon 2102 can execute an F_MISS threshold decision step 3406. During the F_MISS threshold decision step 3406, the server beacon 2102 can compare the F_MISS 3318 to a threshold F_TMISS 3408. The F_TMISS 3408 can be a threshold for the F_MISS 3318.
If the F_MISS threshold decision step 3406 determines that the F_MISS 3318 does not exceed the F_TMISS 3408, the server beacon 2102 can again execute the wait step 3402. If the F_MISS threshold decision step 3406 determines that the F_MISS 3318 does exceed the F_TMISS 3408, the server beacon 2102 can execute a fast fail step 3410.
During the fast fail step 3410, the server beacon 2102 can include a signal indicating a failure to identify fast upload capability for an F_FAIL 3412 period of time. After the fast fail step 3410 is executed by the server beacon 2102, the server beacon 2102 can again execute the data upload decision step 3302 of FIG. 33.
Returning to the fast upload ready decision step 3308 of FIG. 34, when the fast upload ready decision step 3308 determines that the fast ready 3310 was received in the latest listening window of the server beacon 2102 the fast upload ready decision step 3308 can return an affirmative result and the server beacon 2102 can execute an RSSI threshold decision step 3414.
The RSSI threshold decision step 3414 can compare the RSSI 3316 of FIG. 33 for the power station 2104 to an RSSI threshold 3416. The RSSI threshold 3416 can be indicative of a minimum distance between the server beacon 2102 and the power station 2104 for the fast upload to be performed well.
It is contemplated that the RSSI threshold decision step 3414 can also determine whether the RSSI 3316 of the current transmission of the power station 2104 differs significantly from previous transmissions. If the RSSI 3316 does differ significantly the RSSI threshold decision step 3414 can return an affirmative result and the server beacon 2102 can execute further steps in a manner similar to when the RSSI threshold decision step 3414 returns an affirmative result if the RSSI 3316 is above the RSSI threshold 3416.
If the RSSI threshold decision step 3414 determines that the RSSI 3316 is not above the RSSI threshold 3416, the RSSI threshold decision step 3414 will return a negative result and the server beacon 2102 will again execute the F_MISS increment step 3404. If, however, the RSSI threshold decision step 3414 determines that the RSSI 3316 is above the RSSI threshold 3416, the RSSI threshold decision step 3414 will return an affirmative result and the server beacon 2102 can then execute an F_HIT increment step 3418.
During the F_HIT increment step 3418, the server beacon 2102 can increment the F_HIT 3320 of FIG. 33 by one, that is F_HIT 3320 will equal F_HIT 3320+1. Once the F_HIT increment step 3418 has been executed by the server beacon 2102, the server beacon 2102 can then execute an F_HIT threshold decision step 3420.
During the F_HIT threshold decision step 3420, the server beacon 2102 can compare the F_HIT 3320 to a threshold F_THIT 3422. The F_THIT 3422 can operate as an upper limit to the number of listening windows of the server beacon 2102 that lacked the fast ready 3310 signal during the current session with one of the power stations 2104 in the vicinity of the server beacon 2102.
If the F_HIT threshold decision step 3420 determines that the F_HIT 3320 is not above the F_THIT 3422, the F_HIT threshold decision step 3420 will return a negative result and the server beacon 2102 will again execute the wait step 3402. If the F_HIT threshold decision step 3420 determines that the F_HIT 3320 is above the F_THIT 3422, the F_HIT threshold decision step 3420 will return an affirmative result and the server beacon 2102 will execute the upload step 3502 of FIG. 35.
It is contemplated that the F_TMISS 3408 can operate as a threshold for F_MISS 3318 and for example, if F_MISS 3318 grows beyond F_TMISS 3408 before F_HIT 3320 grows beyond F_THIT 3422, it would result in a failed secession for detecting the fast-upload opportunity and the server beacon 2102 would restart the monitoring for the availability of the power station 2104 to perform the fast upload.
Referring now to FIG. 35, therein is shown a third control flow for uploading the audio data 2122 of FIG. 21 and continuing from the F_HIT threshold decision step 3420 of FIG. 34. The server beacon 2102 of FIG. 21 can begin by executing an upload step 3502.
During the upload step 3502, the server beacon 2102 can upload a portion of the audio data 2122 within the upload coordinator queue 2303 of FIG. 23. The server beacon 2102 can upload the portion of the audio data 2122 to the power station 2104 of FIG. 21.
Once the portion of the audio data 2122 is uploaded to the power station 2104, the portion of the audio data 2122 that is uploaded will be removed from the upload coordinator queue 2303. After the server beacon 2102 has executed the upload step 3502, the server beacon 2102 can proceed to execute a bandwidth check decision step 3504.
During the bandwidth check decision step 3504, the server beacon 2102 can check to determine whether the bandwidth between the server beacon 2102 and the power station 2104 is sufficiently high to maintain the upload power efficiently by, for example, comparing the detected bandwidth with a bandwidth threshold 3506. Low bandwidth results in a lower rate of transfer of data while consuming what is typically a similar amount of power to high speed transfers.
It is contemplated that the bandwidth check decision step 3504 can further check and determine whether any of the gesture data 2128 has been detected from the user 2502, for example indicating that the user 2502 wishes to pause the upload of the audio data 2122 to the power station 2104. If the bandwidth check decision step 3504 determines that the bandwidth detected by the server beacon 2102 is not greater than the bandwidth threshold 3506 or that the server beacon 2102 has detected the gesture data 2128 indicating that the user 2502 wishes to pause or stop the upload, the server beacon 2102 will again execute the fast upload ready decision step 3308 of FIG. 33.
On the other hand, if the bandwidth check decision step 3504 determines that the bandwidth detected by the server beacon 2102 is above the bandwidth threshold 3506 and that the user 2502 has not input any of the gesture data 2128 indicating that the user 2502 wishes to stop or pause the upload, the server beacon 2102 will proceed to execute a data for upload decision step 3508. The data for upload decision step 3508 can determine whether the server beacon mass storage 2108 of FIG. 21 includes any of the audio data 2122 that has not been uploaded to the power station 2104.
If the data for upload decision step 3508 determines that there is audio data 2122 within the server beacon mass storage 2108 of the server beacon 2102 that still needs to be uploaded to the power station 2104, the data for upload decision step 3508 will return an affirmative result and the server beacon 2102 will proceed to again execute the upload step 3502. If, on the other hand, the data for upload decision step 3508 determines that there is no further audio data 2122 within the server beacon mass storage 2108 that has not been uploaded to the power station 2104, the data for upload decision step 3508 will return a negative result and the server beacon 2102 will proceed to again execute the data upload decision step 3302.
Referring now to FIG. 36, therein is shown a control flow for providing the upload coordinator queue 2303 of FIG. 23 for the upload coordinator 2302 of FIG. 23. The control flow for providing the upload coordinator queue 2303 can begin with a receive transmission step 3602.
During the receive transmission step 3602, the power station 2104 can wait to receive a transmission of the packets 2310 of FIG. 23 from the server beacon 2102. Once one of the packets 2310 has been received by the power station 2104, the power station 2104 can proceed to execute a priority check decision step 3604 on each of the packets 2310.
It is contemplated that the server beacon 2102 will check each of the packets 2310 that is received with the priority check decision step 3604; however, for ease of description only a single packet will be described for the control flow for providing the upload coordinator queue 2303. The priority check decision step 3604 can check the priority flag 2408 of FIG. 24 for the packet 2310 from the server beacon 2102.
If the priority check decision step 3604 determines that the priority flag 2408 is a low priority, the priority check decision step 3604 will return a negative result and the power station 2104 will proceed to execute a load low priority step 3606. The load low priority step 3606 can load the packet 2310 having the low priority into a low priority queue 3608 within the upload coordinator queue 2303 of the power station 2104.
If the priority check decision step 3604 determines that the priority flag 2408 of the packet 2310 is not low priority, the priority check decision step 3604 will return an affirmative result and the power station 2104 will proceed to execute a load high priority step 3610. The load high priority step 3610 can load the packet 2310 having the high priority into a high priority queue 3612 within the upload coordinator queue 2303 of the power station 2104.
It is contemplated that the upload coordinator queue 2303 can include multiple queues other than the low priority queue 3608 and the high priority queue 3612. For example, when the priority flag 2408 includes multiple different priority states, like low, medium, and high, the upload coordinator queue 2303 can include a sub-queue for each of the priority states.
That is, when the priority flag 2408 can indicate low, medium, or high priorities, the upload coordinator queue 2303 can include the low priority queue 3608, the high priority queue 3612, and an additional medium priority queue. It is further contemplated that the packet 2310 could be classified within the upload coordinator queue 2303 in other ways such as based on a calculation from metadata within in the packet, or from cloud data identifying that the server beacon 2102 server beacon's 2102 ID within the user info 2160 of FIG. 21 as a high priority.
Referring now to FIG. 37, therein is shown a control flow for processing the packets 2310 of FIG. 23 from the upload coordinator queue 2303 of FIG. 36. The power station 2104 can begin by executing a packet in high priority queue decision step 3702.
If the packet in high priority queue decision step 3702 determines that there is one of the packets 2310 within the high priority queue 3612 of FIG. 36, the power station 2104 can proceed to execute a high priority request step 3704. During the high priority request step 3704 the power station 2104 can transmit a signal to the server beacon 2102 requesting that the server beacon 2102 send the audio data 2122 of FIG. 21.
After the transmission of the request by the power station 2104 during the high priority request step 3704, the power station 2104 can proceed to execute a high priority wait step 3706. During the high priority wait step 3706, the power station 2104 can wait for the server beacon 2102 to upload the message 2135 of FIG. 21 containing the audio data 2122 with the high priority request within the high priority queue 3612.
Once the upload of the message 2135 from the server beacon 2102 is complete the power station 2104 can proceed to execute a remove request step 3708. During the remove request step 3708, the power station 2104 can remove the upload request from the high priority queue 3612 for the message 2135 that was uploaded in the high priority wait step 3706.
Further, during the remove request step 3708, the power station 2104 can calculate the amount of the audio data 2122 that includes the priority flag 2408 of FIG. 24 within the high priority queue 3612 that has not been uploaded yet. It is contemplated that the power station 2104 can calculate the remaining amount of the audio data 2122 having the high priority flag 2408 by subtracting the amount of the audio data 2122 uploaded in the high priority wait step 3706 from the total amount of the audio data 2122 having the high priority priority flag 2408 within the high priority queue 3612 before the high priority wait step 3706 was initiated.
The power station 2104 can determine the amount of the data by adding the quantity field 2406 of FIG. 24 for all the packets 2310 within the high priority queue 3612 together before the high priority wait step 3706. The remaining amount of audio data 2122 calculated within the remove request step 3708 can alternatively be calculated by again adding all of the quantity field 2406 data for the packets 2310 within the high priority queue 3612 that have not yet corresponded to an upload of the audio data 2122.
Once the power station 2104 completes the remove request step 3708, the power station 2104 can proceed to executing the packet in high priority queue decision step 3702. The power station 2104 can execute the packet in high priority queue decision step 3702, the high priority request step 3704, the high priority wait step 3706, and the remove request step 3708 until the packet in high priority queue decision step 3702 no longer detects any high priority requests within the high priority queue 3612. Once the packet in high priority queue decision step 3702 no longer detects any high priority requests within the high priority queue 3612, the packet in high priority queue decision step 3702 will return a negative result and the power station 2104 will proceed to execute a packet in low priority queue decision step 3710.
The packet in low priority queue decision step 3710 will determine whether any of the packets 2310 are in the low priority queue 3608. That is, whether any of the packets 2310 having the priority flag 2408 indicating low priority have been allocated to the low priority queue 3608.
If the packet in low priority queue decision step 3710 determines that there are none of the packets 2310 within the low priority queue 3608, the packet in low priority queue decision step 3710 will return a negative result and the power station 2104 will proceed to execute the packet in high priority queue decision step 3702. Transitioning from packet in low priority queue decision step 3710 to packet in high priority queue decision step 3702 may include a temporary low-power mode period during which a certain amount of time, e.g. 100 milliseconds, the high priority queue 3612 is given a chance to fill.
On the other hand, if the packet in low priority queue decision step 3710 determines that there is at least one of the packets 2310 within the low priority queue 3608, the packet in low priority queue decision step 3710 will return an affirmative result and the power station 2104 will proceed to execute a low priority request step 3712. During the low priority request step 3712 the power station 2104 can transmit a signal to the server beacon 2102 requesting that the server beacon 2102 send the audio data 2122.
The power station 2104 can perform steps similar to the high priority wait step 3706 and the remove request step 3708 for the low priority queue 3608 and the low priority transmission of the audio data 2122 from the server beacon 2102. It is contemplated that the high priority wait step 3706 and the remove request step 3708 can be performed in a similar manner with the exception of performing a high priority request decision step 3714 during the time period that the server beacon 2102 is uploading the low priority audio data 2122.
The power station 2104 can execute the high priority request decision step 3714 during the upload from the server beacon 2102 of low priority audio data 2122. If the high priority request decision step 3714 determines that a packet 2310 is found within the high priority queue 3612, the high priority request decision step 3714 can return an affirmative result and the power station 2104 can proceed to execute a signal pause step 3716.
During the signal pause step 3716, the power station 2104 can transmit a signal requesting that the server beacon 2102 currently transmitting a low priority audio data 2122 pause the transmission. Once the signal pause step 3716 is initiated, the power station 2104 can proceed to again execute the high priority request step 3704 for the packet 2310 within the high priority queue 3612.
If the high priority request decision step 3714 determines that there are still no packets 2310 within the high priority queue 3612, the high priority request decision step 3714 can return a negative result and the power station 2104 can proceed to execute a low priority transmission complete decision step 3718. If the low priority transmission complete decision step 3718 determines that the low priority upload from the server beacon 2102 is not complete, the low priority transmission complete decision step 3718 will return a negative result and the power station 2104 can again execute the high priority request decision step 3714.
It is contemplated that the power station 2104 can further include a wait step to provide a time interval between a negative result by the low priority transmission complete decision step 3718 and the execution of the high priority request decision step 3714. Alternatively, it is contemplated that the power station 2104 can include a wait step before executing the low priority transmission complete decision step 3718 in order to provide a time interval between checks by the low priority transmission complete decision step 3718.
In this way, the low priority upload from the server beacon 2102 can be performed in a low priority manner and when a high priority upload is requested within the high priority queue 3612, the power station 2104 will pause the low priority upload and proceed with the high priority upload. If the low priority transmission complete decision step 3718 determines that the low priority upload is complete, the low priority transmission complete decision step 3718 will return an affirmative result and the power station 2104 can proceed to execute the packet in high priority queue decision step 3702.
It is contemplated that the power station 2104 can remove the packet requesting low priority from the low priority queue 3608 once the low priority upload is complete in a manner similar to the remove request step 3708. Further it is contemplated that the power station 2104 can update the amount of the audio data 2122 that is requesting low priority upload within the low priority queue 3608 in a manner similar to that described above for the remove request step 3708.
It is contemplated that the packet in high priority queue decision step 3702 and the low priority transmission complete decision step 3718 can be performed in a low priority manner by using wake signals whenever the upload coordinator queue 2303 is updated. The wake signals can wake electronic circuits or microcontrollers performing the steps of FIG. 37. Thus, the power station 2104 can operate in a low-power mode, rather than having circuits constantly checking the status of the upload coordinator queue 2303.
It has been discovered that the server beacon as described above with the server beacon sensors, the server beacon power transceiver, and the server beacon mass storage working as described with the power station, including the power station power transceiver, and further working as described with the audio database server unexpectedly improve the underlying technology of wireless transfer, hands free control, and secure storage by lowering memory requirements, lowering power requirements, lowering processing requirements, and lowering band width requirements while simultaneously increasing the speed at which the compliance system functions and allowing it to be seamlessly integrated into the health care industry solving real world problems.
Thus, it has been discovered that the compliance system furnishes important and heretofore unknown and unavailable solutions, capabilities, and functional aspects. The resulting configurations are straightforward, cost-effective, uncomplicated, highly versatile, accurate, sensitive, and effective, and can be implemented by adapting known components for ready, efficient, and economical manufacturing, application, and utilization.
While the compliance system has been described in conjunction with a specific best mode, it is to be understood that many alternatives, modifications, and variations will be apparent to those skilled in the art in light of the preceding description. Accordingly, it is intended to embrace all such alternatives, modifications, and variations, which fall within the scope of the included claims. All matters set forth herein or shown in the accompanying drawings are to be interpreted in an illustrative and non-limiting sense.

## Claims

1. A touchless management method comprising:
providing a server beacon, the server beacon including a gesture sensor, a motion sensor, a managed sensor, a server beacon mass storage, and a server beacon power transceiver;
detecting gesture data from the gesture sensor, the gesture data recognized by a processor in the server beacon as corresponding to a command for the managed sensor;
recording sensor data with the managed sensor based on the managed sensor being turned on in response to the gesture data;
uploading the sensor data to the server beacon mass storage;
providing a power station, the power station including a power station power transceiver, a station control unit, upload coordinator, and a station storage unit;
sending a packet from the server beacon to the power station;
prioritizing the packet within an upload coordinator queue of the upload coordinator;
uploading a message including the sensor data from the server beacon power transceiver within the server beacon to the power station through the power station power transceiver; and
uploading the message from the power station to a database server.

2. The method of claim 1 wherein detecting the gesture data includes:
detecting four pulses based on four spread apart fingers moving across a sensory area of the gesture sensor;
detecting two pulses based on two spread apart fingers moving across the sensory area of the gesture sensor; and
detecting one pulse based on four fingers, the four fingers in direct contact along a length of the four fingers, and the four fingers moving across the sensory area of the gesture sensor.

3. The method of claim 1 wherein:
prioritizing the packet within the upload coordinator queue includes prioritizing the packet into a low priority queue within the upload coordinator queue based on the packet having a priority flag indicating a low priority;
uploading the message with the sensor data includes uploading the sensor data corresponding to the packet based on the packet being classified into the low priority queue; and
further comprising pausing the upload of the message with the sensor data based on a new packet being classified within a high priority queue of the upload coordinator queue.

4. The method of claim 1 further comprising:
turning the gesture sensor and the managed sensor off based on the motion sensor detecting stillness for longer than a stillness threshold; and
turning the motion sensor off based on the motion sensor detecting motion of the server beacon.

5. The method of claim 1 wherein uploading the sensor data to the server beacon mass storage includes uploading the sensor data with a mass storage queue, the mass storage queue being a circular queue configured to increment sequentially through bits of the server beacon mass storage each time the server beacon mass storage uploads the sensor data, and the mass storage queue further configured to point to a first bit of the server beacon mass storage based on a last bit of the server beacon mass storage being previously written to.

6. The method of claim 1 further comprising changing an operation mode of the gesture sensor from a low power mode to a high power mode based on the gesture sensor detecting a motion or an object within a predetermined distance.

7. The method of claim 1 wherein prioritizing the packet within the upload coordinator queue includes prioritizing the packet based on the gesture data detected by the gesture sensor being recognized as corresponding to a priority.

8. A non-transitory computer readable medium, useful in association with a processor, including instructions configured to:
control a server beacon, the server beacon including a gesture sensor, a motion sensor, a managed sensor, a server beacon mass storage, and a server beacon power transceiver;
detect gesture data from the gesture sensor, the gesture data recognized by a processor in the server beacon as corresponding to a command for the managed sensor;
record sensor data with the managed sensor based on the managed sensor being turned on in response to the gesture data;
upload the sensor data to the server beacon mass storage;
control a power station, the power station including a power station power transceiver, a station control unit, upload coordinator, and a station storage unit;
send a packet from the server beacon to the power station;
prioritize the packet within an upload coordinator queue of the upload coordinator;
upload a message including the sensor data from the server beacon power transceiver within the server beacon to the power station through the power station power transceiver; and
upload the message from the power station to a database server.

9. The computer readable medium of claim 8 wherein the instructions configured to detect the gesture data includes instructions configured to:
detect four pulses based on four spread apart fingers moving across a sensory area of the gesture sensor;
detect two pulses based on two spread apart fingers moving across the sensory area of the gesture sensor; and
detect one pulse based on four fingers, the four fingers in direct contact along a length of the four fingers, and the four fingers moving across the sensory area of the gesture sensor.

10. The computer readable medium of claim 8 wherein:
the instructions configured to prioritize the packet within the upload coordinator queue includes instructions configured to prioritize the packet into a low priority queue within the upload coordinator queue based on the packet having a priority flag indicating a low priority;
the instructions configured to upload the message with the sensor data includes instructions configured to upload the sensor data corresponding to the packet based on the packet being classified into the low priority queue; and
further comprising instructions configured to pause the upload of the message with the sensor data based on a new packet being classified within a high priority queue of the upload coordinator queue.

11. The computer readable medium of claim 8 further comprising instructions configured to:
turn the gesture sensor and the managed sensor off based on the motion sensor detecting stillness for longer than a stillness threshold; and
turn the motion sensor off based on the motion sensor detecting motion of the server beacon.

12. The computer readable medium of claim 8 wherein the instructions configured to upload the sensor data to the server beacon mass storage includes instructions configured to upload the sensor data with a mass storage queue, the mass storage queue being a circular queue configured to increment sequentially through bits of the server beacon mass storage each time the server beacon mass storage uploads the sensor data, and the mass storage queue further configured to point to a first bit of the server beacon mass storage based on a last bit of the server beacon mass storage being previously written to.

13. The computer readable medium of claim 8 further comprising instructions configured to change an operation mode of the gesture sensor from a low power mode to a high power mode based on the gesture sensor detecting a motion or an object within a predetermined distance.

14. The computer readable medium of claim 8 wherein the instructions configured to prioritize the packet within the upload coordinator queue includes instructions configured to prioritize the packet based on the gesture data detected by the gesture sensor being recognized as corresponding to a priority.

15. A touchless management system comprising:
a server beacon, the server beacon including a gesture sensor, a motion sensor, a managed sensor, a server beacon mass storage, and a server beacon power transceiver, the gesture sensor configured to detect gesture data, the server beacon including a beacon processor configured to recognize the gesture data as corresponding to a command for the managed sensor, the managed sensor configured to record sensor data based on the managed sensor being turned on in response to the gesture data, the server beacon configured to upload the sensor data to the server beacon mass storage;
a power station, the power station including a power station power transceiver, a station control unit, upload coordinator, and a station storage unit, the power station configured to receive a packet from the server beacon power transceiver, the power station including a station processor configured to prioritize the packet within an upload coordinator queue of the upload coordinator, the power station power transceiver configured to receive a message including the sensor data from the server beacon power transceiver within the server beacon; and
a database server configured to receive the message from the power station.

16. The system of claim 15 wherein detecting the gesture sensor is configured to detect the gesture data including:
four pulses based on four spread apart fingers moving across a sensory area of the gesture sensor;
two pulses based on two spread apart fingers moving across the sensory area of the gesture sensor; and
one pulse based on four fingers, the four fingers in direct contact along a length of the four fingers, and the four fingers moving across the sensory area of the gesture sensor.

17. The system of claim 15 wherein:
the power station is configured to prioritize the packet within the upload coordinator queue into a low priority queue within the upload coordinator queue based on the packet having a priority flag indicating a low priority;
the power station power transceiver is configured to receive the message with the sensor data corresponding to the packet based on the packet being classified into the low priority queue; and
the server beacon configured to pause an upload of the message with the sensor data based on a new packet being classified within a high priority queue of the upload coordinator queue.

18. The system of claim 15 wherein:
the server beacon is configured to turn the gesture sensor and the managed sensor off based on the motion sensor detecting stillness for longer than a stillness threshold; and
the server beacon configured to turn the motion sensor off based on the motion sensor detecting motion of the server beacon.

19. The system of claim 15 wherein the server beacon includes a mass storage queue, the mass storage queue being a circular queue configured to increment sequentially through bits of the server beacon mass storage each time the server beacon mass storage uploads the sensor data, and the mass storage queue further configured to point to a first bit of the server beacon mass storage based on a last bit of the server beacon mass storage being previously written to.

20. The system of claim 15 wherein the power station including the station processor is configured to prioritize the packet based on the gesture data detected by the gesture sensor being recognized as corresponding to a priority.