US20160270029A1 - Signage acknowledgement tied to personal computer device - Google Patents
Signage acknowledgement tied to personal computer device Download PDFInfo
- Publication number
- US20160270029A1 US20160270029A1 US14/657,318 US201514657318A US2016270029A1 US 20160270029 A1 US20160270029 A1 US 20160270029A1 US 201514657318 A US201514657318 A US 201514657318A US 2016270029 A1 US2016270029 A1 US 2016270029A1
- Authority
- US
- United States
- Prior art keywords
- mobile device
- circuitry
- notification
- electronic source
- user
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 230000004044 response Effects 0.000 claims abstract description 35
- 238000000034 method Methods 0.000 claims description 26
- 238000004891 communication Methods 0.000 claims description 6
- 230000006399 behavior Effects 0.000 claims description 3
- 238000004590 computer program Methods 0.000 claims description 3
- 230000000007 visual effect Effects 0.000 claims description 3
- 238000001514 detection method Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 5
- 230000003287 optical effect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000001413 cellular effect Effects 0.000 description 2
- 238000010276 construction Methods 0.000 description 2
- 230000011664 signaling Effects 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 208000027418 Wounds and injury Diseases 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000006378 damage Effects 0.000 description 1
- 230000001771 impaired effect Effects 0.000 description 1
- 208000014674 injury Diseases 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000009711 regulatory function Effects 0.000 description 1
- 230000035945 sensitivity Effects 0.000 description 1
- 238000005406 washing Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W68/00—User notification, e.g. alerting and paging, for incoming communication, change of service or the like
- H04W68/04—User notification, e.g. alerting and paging, for incoming communication, change of service or the like multi-step notification using statistical or historical mobility data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72403—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
- H04M1/72409—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
- H04M1/72412—User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/02—Services making use of location information
- H04W4/021—Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M1/00—Substation equipment, e.g. for use by subscribers
- H04M1/72—Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
- H04M1/724—User interfaces specially adapted for cordless or mobile telephones
- H04M1/72448—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
- H04M1/72463—User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions to restrict the functionality of the device
Definitions
- the present disclosure generally relates to electronic acknowledgment of information encountered in a user's environment, and more particularly to methods for tracking whether a user acknowledges the content of a posted sign.
- signs such as these play a significant role in informing and protecting the public
- many signs consist of nothing more than a written warning, perhaps accompanied with some colored and/or flashing lights to get a passerby's attention.
- Getting people to notice these signs, read them, understand them, and comply with them can be a significant problem, particularly when such signs are used to warn the public of potentially life-threatening hazards nearby (e.g., high-voltage wires, minefields, heavy machinery, quarantine areas).
- FIG. 1 is a logical block diagram that illustrates a system for acknowledging a posted sign, according to embodiments of the present disclosure.
- FIG. 2 illustrates a mobile device receiving a signal from an electronic source associated with a posted sign, according to embodiments of the present disclosure.
- FIG. 3 is a signal diagram that illustrates signaling between an electronic source, mobile device, and remote server, according to embodiments of the present disclosure.
- FIG. 4 illustrates a method for acknowledging a posted sign, according to embodiments of the present disclosure.
- FIG. 5 illustrates a more detailed method for acknowledging a posted sign, according to embodiments of the present disclosure.
- FIG. 6 is a logical block diagram that illustrates the physical circuitry of a mobile device configured according to embodiments of the present disclosure.
- FIG. 7 is a logical block diagram that illustrates physical units within the processing circuitry of a mobile device that are configured according to embodiments of the present disclosure.
- FIG. 8 is a logical block diagram that illustrates a memory containing software modules configured according to embodiments of the present disclosure.
- FIG. 1 illustrates an example system 100 for acknowledging signs using a mobile device 110 , such as a cellular phone, tablet, laptop computer, personal data assistant, or personal music player.
- the system includes the mobile device 110 , an electronic source 105 , a network 115 , and a remote server 120 .
- the mobile device 110 is able to detect the electronic source 105 once the electronic source is within a signal detection range 125 .
- the electronic source 105 may be, for example, an RFID tag, Wi-Fi access point, near field communications (NFC) terminal, active radio beacon, or a BLUETOOTH transmitter.
- the signal detection range 125 is a physical distance within which circuitry within the mobile device 110 is able to detect signals originating from the electronic source 105 .
- the outer limits of signal detection range 125 may depend on a number of factors, including the sensitivity of radio circuitry within the mobile device 110 , the strength of the signal emanating from electrical source 105 , and interference that may be present in the environment, among other factors. In order for the mobile device 110 to detect the electronic source 105 when the signal detection range 125 is small, the mobile device 110 and electronic source 105 will generally need to be physically closer together than when the signal detection range 125 is large. Thus, the signal detection range 125 may be used to control a relevant physical boundary around which embodiments of the present disclosure are practiced, at least to some degree.
- the mobile device 110 is also able to communicate with a network 115 , such as the Internet, a cellular network, or Local Area Network (LAN), over a wireless connection.
- the network 115 may be used to exchange messages with the remote server 120 .
- the network server 120 may be used, for example, to receive registration messages from the mobile device 110 in order to track when the user encounters the electronic source 105 , send content associated with the electronic source 105 to the mobile device 110 , and receive and store acknowledgement messages, relating to that content, from the mobile device 110 .
- the electronic source 105 may be positioned on or near a sign 205 , as depicted in FIG. 2 .
- the electronic source radiates a radio signal 220 that can be detected by the mobile device 110 .
- the signal 220 comprises an identifier 230 that identifies the electronic source 105 (e.g., a serial number, a Universally Unique Identifier (UUID)), and an address 225 of the remote server 120 (e.g., an Internet Protocol (IP) address).
- IP Internet Protocol
- the identifier 230 and the address 225 may be the same (e.g., a Media Access Control (MAC) address, a Uniform Resource Identifier (URI)).
- MAC Media Access Control
- URI Uniform Resource Identifier
- the mobile device 110 uses the signal 220 to display an appropriate notification 210 that corresponds to the sign 205 using content obtained from the remote server 120 (not shown in FIG. 2 ).
- the mobile device 110 also presents a prompt 215 to the user that can be used to acknowledge the notification 210 .
- the prompt 215 may be, for example, a graphical button that the user can tap or click on to indicate their acknowledgement.
- the prompt 215 can also be a more complex user interface element that requires the user's input, such as a text input field that requires the user to type certain words (e.g., “I agree,” “I accept,” “I acknowledge”).
- the sign 205 depicted in FIG. 2 is a reminder for employees to wash their hands before returning to work. Such a sign 205 may commonly be found fastened to the wall of a restaurant bathroom in a highly visible location.
- the electronic source 105 When the electronic source 105 is associated with such a sign 205 , it may be appropriate for the mobile device 110 to display a notification 210 asking the user whether they did, in fact, wash their hands.
- sign 205 and electronic source 105 are depicted as stationary, according to embodiments, the sign 205 and/or electronic source 105 may be movable, or even portable.
- sign 205 may be a warning printed on a portable power tool indicating that safety goggles are required to use the tool.
- the electronic source 105 may be affixed to the power tool itself, or may be installed within a toolbox or workbench where the power tool is stored, for example.
- the notification 210 displayed by the mobile device 110 may ask the user to certify that they are, in fact, wearing their safety googles, and/or may ask the user to accept the risk of physical injury that comes with using the power tool.
- various embodiments of system 100 may be useful to obtain acknowledgements from users in a wide variety of scenarios.
- FIG. 3 illustrates an example of the signaling exchanged between the electronic source 105 , mobile device 110 , and remote server 120 , according to embodiments of the present disclosure.
- the signal 220 is transmitted by the electronic source 105 in response to an earlier signal sent by the mobile device 110 (not shown in FIG. 3 ).
- a passive RFID tag for example, lacks its own power source.
- the passive RFID tag may use energy radiated from the mobile device 110 to induce a current within the passive RFID tag's antenna to transmit the signal 220 .
- the electronic source 105 has a source of power (e.g., a battery, a wall outlet) and sends the signal 220 periodically, at fixed or at varying intervals.
- a source of power e.g., a battery, a wall outlet
- the mobile device 110 having detected the signal 220 , sends a registration 260 to the remote server 120 .
- This registration 260 may include, for example, the identifier 230 of the electronic source 105 (as obtained from the signal 220 ) and an identifier 240 of the mobile device 110 (e.g., a phone number, an email address).
- Such registration 260 may, for example, serve to notify the remote server 120 that a particular user of the mobile device 110 is in proximity to the sign 205 associated with the electronic source 105 .
- mobile device 110 may have a registration policy 235 that governs whether or not the mobile device 110 registers when signal 220 is detected.
- sending the registration 260 may be based, according to embodiments, on a comparison 255 between information in the signal 220 and the registration policy 235 .
- the registration policy may indicate that the mobile device 110 is to send the registration 260 for signals 220 comprising a particular identifier 230 , or for signals 220 comprising an address 225 of a particular remote server 120 .
- the registration policy 235 may also indicate that the mobile device 110 is to send the registration 260 only during certain times, or when the mobile device 110 is in a certain state.
- the registration policy 235 may be used to include or exclude certain electronic sources 105 or mobile devices 110 from participating in the system 100 at given times or under certain conditions.
- sign 205 reminds restaurant employees that they must wash their hands before returning to work.
- This sign 205 is directed only at employees, and not, for example, customers.
- Such a sign 205 may be present in both the men's and women's bathroom of the restaurant, and each may have a respective electronic source 105 , each of which transmits a respective signal 220 that comprises a respective identifier 230 of the corresponding electronic source 105 .
- Employees of the restaurant may have a registration policy 235 on their respective mobile devices 110 indicating that the mobile devices 110 are to send the registration 260 when a signal 220 comprising the identifier 230 of the electronic source 105 in either bathroom is detected.
- Each signal may also, or instead, comprise an address 225 to the same remote server 120 , which may be at a known IP address 225 on a local network 115 .
- the registration policy 235 may indicate that the mobile devices 110 are to send the registration 260 when a signal 220 comprising the known IP address 225 of the network server 120 is detected. Accordingly, non-employees may refrain from sending the registration 260 , as they would typically lack a registration policy 235 configured as described above. More generally, the registration policy 235 may be present on the mobile devices 110 of users over whom an administrator of the electronic source 105 has some measure of control. For example, a business owner may use the system 100 to track employees, parents may use the system 100 to track children, teachers may use the system 100 to track students, and doctors may use the system 100 to track nurses and/or patients.
- the mobile device 110 receives content 265 associated with the electronic source 105 in response.
- the mobile device 110 displays 275 a notification 210 comprising this content 265 and a prompt 215 through which the user may provide input 295 to acknowledge the notification 210 .
- the content 265 may be a question asking the user of mobile device 110 to certify that they have, in fact, washed their hands.
- the content 265 may be a reminder that failure to comply with jobsite safety requirements is punishable by immediate termination.
- the content may be an animated gif or video illustrating the path from the room to the nearest exit.
- the content 265 may be configured by an administrator of the system 100 , and may vary widely depending on the particular use case to which the system 100 is applied.
- the mobile device 110 may send an acknowledgement message 300 to the remote server 120 .
- the remote server 120 may not only track which users have come in contact with the sign 205 , but also track which users have actually read, understood, indicated their compliance with, or otherwise acknowledged content provided by the remote server 120 concerning the sign 205 .
- the mobile device 110 may also receive a notification policy 270 from the remote server 120 .
- the notification policy 270 may define at least one behavior for the mobile device 110 when displaying 275 the notification 210 .
- the notification policy 270 may require the content 265 to be displayed 275 in the notification 210 for at least a minimum duration before the user may use the prompt 215 to acknowledge the notification 210 .
- the notification policy 270 may require that the user acknowledge the notification 210 within a maximum duration, at a particular location, and/or may dictate that the phone vibrate when the notification 210 is displayed, according to embodiments.
- this notification policy 270 is not received from the remote server 120 , at least in part, but is instead preconfigured, at least partly, at the mobile device 110 .
- a user's acknowledgement that they understand a particular sign 205 may be at least slightly more reliable if the user is required to stand in close proximity to the sign 205 in order for the system 100 to accept the acknowledgment.
- requiring that the user be physically close to the electronic source 105 in order to successfully acknowledge the notification may help to prevent users from merely “clicking through” the notification 210 (i.e., acknowledging the notification 210 without actually reading or understanding it).
- the mobile device 110 may disable 280 sending the acknowledgement message 300 to the network server 120 in response to failing to detect that the electronic source 105 is in the signal detection range 125 (e.g., by deactivating or removing the prompt 215 ). Similarly, the mobile device may enable 290 sending the acknowledgement message 300 in response to detecting that the electronic source 105 is in the signal detection range 125 .
- FIG. 3 depicts an electronic source 105 that sends the signal 220 periodically.
- mobile device 110 After receiving the first signal 220 , mobile device 110 fails to receive the next four transmissions of the signal 220 (e.g., the mobile device moves such that the electronic source 105 is no longer in signal detection range 125 ).
- the mobile device 110 having sent the registration 260 , received content 265 from the remote server 120 in response, and having failed to detect the electronic source 105 for some duration, disables 280 sending the acknowledgement message 300 .
- the user input 285 does not result in any acknowledgement message 300 to be sent to the remote server 120 (i.e., the user input 285 is received while sending the acknowledgement 300 is disabled 280 ).
- the mobile device 110 It is not until after the mobile device 110 receives the sixth signal 220 transmission from the electronic source 105 that the mobile device 110 enables 290 sending the acknowledgement message 300 (e.g., the mobile device 110 may return to, or near to, where the first signal 220 was received, such that the electronic source 105 is once again in signal detection range 125 ).
- User input 295 being received after sending the acknowledgement 300 has been enabled 290 , results in the mobile device 110 sending the acknowledgement message 300 to the remote server 120 . In this way, the user may be required to return to physical proximity with the electronic source 105 in order for the mobile device 110 to send the acknowledgement message 300 .
- the mobile device 110 receives a reward notice 305 in response to sending the acknowledgement message 300 .
- the user may be enticed to acknowledge the notification 210 , even if doing so would involve the inconvenience of returning to a location where the signal 220 can be detected.
- One example of enticing the user to acknowledge the notification 210 may involve an electronics store that has a sign 205 in the window advertising a special price on laptop computers for customers who have an electronic coupon.
- their mobile device 110 may detect a signal 220 sent by an electronic source 105 on or near the sign 205 .
- the mobile device 110 may then send a registration 260 to the remote server 120 at the address 225 indicated in the signal 220 and receive content 265 in response that asks the user if they would like to receive the electronic coupon.
- the mobile device 110 displays 275 this content 265 to the user, and the user may then provide input 295 acknowledging that they would like to receive the coupon.
- the mobile device 110 sends an acknowledgement message 300 to the remote server 120 , and the remote server 120 responds with the reward notice 305 , which comprises the electronic coupon for the laptop.
- FIG. 4 illustrates a method 400 , implemented in a mobile device 110 , according to embodiments of the present disclosure.
- the method 400 comprises receiving, via a radio interface of the mobile device 110 , a signal 220 from an electronic source 105 within range 125 of the radio interface, the signal 220 originating from the electronic source 105 and comprising an address 225 of a remote server 120 that is distinct from the electronic source 105 , and an identifier 230 of the electronic source 105 (block 405 ).
- the method further comprises sending a registration 260 to the remote server 120 at the address 225 , the registration 260 comprising an identifier 240 of the mobile device 110 and the identifier 230 of the electronic source 105 (block 410 ).
- the method further comprises receiving content 265 associated with the electronic source 105 from the remote server 120 in response to the registration 260 (block 415 ), and displaying 275 , on a display of the mobile device 110 , a notification 210 comprising the content 265 and a prompt 215 for the user to acknowledge the notification 210 (block 420 ).
- the method further comprises receiving input 295 from the user acknowledging the notification 210 (block 425 ) and sending an acknowledgement message 300 to the remote server 120 in response to receiving the input 295 (block 430 ).
- a more detailed method 500 is illustrated in FIG. 5 .
- the mobile device 110 receives the signal 220 from the electronic source 105 as previously described (step 502 ).
- the mobile device 110 decides whether or not to register with the remote server 120 (e.g., based on a registration policy 235 as previously described) (step 504 ). If the mobile device 110 decides not to register, the method 500 ends (step 530 ). If the mobile device 110 decides to register, the mobile device 110 sends the registration 260 (step 506 ).
- the mobile device receives content 265 associated with the electronic source 105 and a notification policy 270 (step 508 ).
- the mobile device 110 displays a notification comprising the content 265 and a prompt 215 through which the user may acknowledge the notification 210 in accordance with the notification policy 270 (step 510 ).
- the notification policy 270 indicates that the usability of the mobile device 110 is to be impaired until input 295 from the user acknowledging the notification 210 is received. Accordingly, the mobile device 110 impairs the usability of the mobile device 110 according to the notification policy 270 (step 512 ).
- the mobile device 110 may prevent the user from launching particular software, may prevent communication with certain other devices on the network 115 , may partially or fully obscure visual elements in the mobile device's 110 display, may vibrate continuously or periodically, and/or may be block the output of audio, until the user successfully acknowledges the notification 210 .
- the notification policy 270 also indicates that the user be alerted until the input 295 from the user acknowledging the notification 210 is received. Further, the notification policy 270 indicates that the user is to be alerted if the mobile device 110 fails to detect that the electronic source 105 is in range 125 . Accordingly, the mobile device 110 alerts the user according to the notification policy 270 (step 514 ). According to embodiments, such alerting may include outputting audio (e.g., alarms, audible messages, ringtones) and vibrating the mobile device 110 .
- audio e.g., alarms, audible messages, ringtones
- alerting may be, according to embodiments, periodic, continuous, or in response detecting certain events (e.g., failing to detect the signal 220 within a particular duration, failing to acknowledge the notification within a particular duration, detecting that the user is attempting to circumvent the notification 210 ).
- the mobile device 110 attempts to detect the signal 220 from the electronic source 105 (step 516 ). If the mobile device 110 fails to detect the signal 220 , the mobile device 110 disables 280 sending the acknowledgement 300 (step 518 ) and alert the user again (step 514 ). Thus, the user is not able to provide input 295 to acknowledge the notification 210 so long as the signal 220 is not detected, according to the method 500 . However, if the mobile device 110 detects the signal 220 , the mobile device 110 enables 290 sending the acknowledgement 300 (step 520 ) and check whether user input 295 acknowledging the notification 210 has been received (step 522 ).
- the mobile device 110 alerts the user again (step 514 ). However, if the mobile device 110 receives user input 295 acknowledging the notification 210 while sending the acknowledgment message 300 is enabled, the mobile device sends the acknowledgement 300 (step 526 ) and receives a reward notice 305 from the remote server 120 in response (step 528 ). The method 500 then ends (step 530 ).
- FIG. 6 illustrates exemplary hardware of the mobile device 110 according to embodiments.
- the mobile device 110 comprises processing circuitry 510 that is communicatively coupled to radio circuitry 505 , a memory 515 , display circuitry 525 , input circuitry 530 , and optionally alerting circuitry 535 , via one or more buses.
- the processing circuitry 510 may comprise any sequential state machine capable of executing machine instructions stored as a machine-readable computer program 520 in the memory 515 , such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored-program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above.
- the processing circuitry 510 is communicatively coupled to memory 515 via one or more buses.
- the memory 515 of the various embodiments may comprise any non-transitory machine-readable media known in the art or that may be developed, including but not limited to magnetic media (e.g., floppy disc, hard disc drive, etc.), optical media (e.g., CD-ROM, DVD-ROM, etc.), solid state media (e.g., SRAM, DRAM, DDRAM, ROM, PROM, EPROM, Flash memory, solid state disc, etc.), or the like.
- magnetic media e.g., floppy disc, hard disc drive, etc.
- optical media e.g., CD-ROM, DVD-ROM, etc.
- solid state media e.g., SRAM, DRAM, DDRAM, ROM, PROM, EPROM, Flash memory, solid state disc, etc.
- the radio circuitry 505 is configured to receive a radio signal from an electronic source 105 (e.g., via NFC, BLUETOOTH, RFID) and exchange data with a remote server 120 that is distinct from the electronic source 105 via a communications network 115 (e.g., via Wi-Fi, Long-Term Evolution (LTE)).
- the radio circuitry 505 may comprise analog and/or digital transceiving circuitry capable of communicating with each other, or with other devices, according to one or more communication protocols known in the art or that may be developed, such as HTTP, RTP, RTCP, HTTPs, Ethernet, TCP/IP, ATM, or the like.
- the radio circuitry 505 implements receiver and transmitter functionality appropriate to the communication network 115 to which it is attached (e.g., Wi-Fi, LTE) and appropriate for receiving a signal from the electronic source 105 (e.g., NFC, BLUETOOTH, RFID).
- the transmitter and receiver functionality may share circuit components and/or software, or alternatively may be implemented separately within the radio interface circuitry.
- the input circuitry 530 is configured to accept input signals from a user of the mobile device 110 .
- the input circuitry 530 may be comprised within one or more of a pointing device (such as a mouse, stylus, touchpad, trackball, pointing stick, joystick), a touchscreen, an accelerometer, a microphone for speech input, an optical sensor for optical recognition of gestures, and a keypad or keyboard.
- the radio circuitry 505 may also serve as the input circuitry 530 , according to embodiments, for accepting input signals from a remote user or other entity within the network 115 .
- the display circuitry 525 is configured to present visual information to a user of the mobile device 110 .
- the display circuitry 525 may be comprised within one or more of a graphics adapter, a graphical processing unit, a display port, a Liquid Crystal display, and a Light Emitting Diode display.
- the alerting circuitry 535 comprises one or more of audio circuitry 540 configured to output audio and vibration circuitry 545 configured to vibrate the device, according to embodiments.
- the processing circuitry 510 is configured to receive the signal 220 from the electronic source 105 within range 125 of, and via, the radio circuitry 505 , the signal 220 originating from the electronic source 105 and comprising an address 225 of the remote server 120 and an identifier 230 of the electronic source 105 .
- the processing circuitry 510 is further configured to send a registration 260 to the remote server 120 at the address 225 via the radio circuitry 505 , the registration 260 comprising an identifier 240 of the mobile device 110 and the identifier 230 of the electronic source 105 .
- the processing circuitry 510 is further configured to receive content 265 associated with the electronic source 105 from the remote server 120 in response to the registration 260 via the radio circuitry 505 , and display 275 , via the display circuitry 525 , a notification 210 comprising the content 265 and a prompt 215 for the user to acknowledge the notification 210 via the input circuitry 530 .
- the processing circuitry 510 is further configured to receive input 295 , via the input circuitry 530 , from the user acknowledging the notification 210 and send an acknowledgement message 300 to the remote server 120 , via the radio circuitry 505 , in response to receiving the input 295 via the input circuitry 530 .
- FIG. 7 illustrates an embodiment of the processing circuitry 510 comprising physical hardware units.
- the processing circuitry 510 comprises a signal receiving unit 705 , a registration sending unit 710 , a content receiving unit 715 , a displaying unit 720 , an input receiving unit 725 , and an acknowledgement receiving unit 730 .
- the signal receiving unit 705 is configured to receive, via a radio interface of the mobile device 110 , a signal 220 from an electronic source 105 within range 125 of the radio interface, the signal 220 originating from the electronic source 105 and comprising an address 225 of a remote server 120 that is distinct from the electronic source 105 , and an identifier 230 of the electronic source 105 .
- the registration sending unit 710 is configured to send a registration 260 to the remote server 120 at the address 225 , the registration 260 comprising an identifier 240 of the mobile device 110 and the identifier 230 of the electronic source 105 .
- the content receiving unit 715 is configured to receive content 265 associated with the electronic source 105 from the remote server 120 in response to the registration 260 .
- the displaying unit 720 is configured to display 275 , on a display of the mobile device 110 , a notification 210 comprising the content 265 and a prompt 215 for the user to acknowledge the notification 210 .
- the input receiving unit 725 is configured to receive input 295 from the user acknowledging the notification 210 .
- the acknowledgment sending unit 730 is configured to send an acknowledgement message 300 to the remote server 120 in response to receiving the input 295 .
- FIG. 8 illustrates memory 510 comprising software modules for performing embodiments as discussed above.
- the memory 510 comprises a signal receiving module 805 , a registration sending module 810 , a content receiving module 815 , a displaying module 820 , an input receiving module 825 , and an acknowledgement receiving module 830 .
- the signal receiving module 805 is configured to receive, via a radio interface of the mobile device 110 , a signal 220 from an electronic source 105 within range 125 of the radio interface, the signal 220 originating from the electronic source 105 and comprising an address 225 of a remote server 120 that is distinct from the electronic source 105 , and an identifier 230 of the electronic source 105 .
- the registration sending module 810 is configured to send a registration 260 to the remote server 120 at the address 225 , the registration 260 comprising an identifier 240 of the mobile device 110 and the identifier 230 of the electronic source 105 .
- the content receiving module 815 is configured to receive content 265 associated with the electronic source 105 from the remote server 120 in response to the registration 260 .
- the displaying module 820 is configured to display 275 , on a display of the mobile device 110 , a notification 210 comprising the content 265 and a prompt 215 for the user to acknowledge the notification 210 .
- the input receiving module 825 is configured to receive input 295 from the user acknowledging the notification 210 .
- the acknowledgment sending module 830 is configured to send an acknowledgement message 300 to the remote server 120 in response to receiving the input 295 .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- Probability & Statistics with Applications (AREA)
- Human Computer Interaction (AREA)
- Telephone Function (AREA)
Abstract
Description
- The present disclosure generally relates to electronic acknowledgment of information encountered in a user's environment, and more particularly to methods for tracking whether a user acknowledges the content of a posted sign.
- Signs posted within an environment play an important role in notifying onlookers of important information. Many signs merely serve to enhance the convenience of the public. For example, street signs are often used to inform pedestrians of their current location. However, other signs serve important public safety or regulatory functions. For example, some signs inform drivers of when it is legal to park their vehicle in a particular place. Other signs remind employees that they must wash their hands before returning to work after using the bathroom. Yet other signs warn people that wearing a hard hat is required to enter a construction site.
- Although signs such as these play a significant role in informing and protecting the public, many signs consist of nothing more than a written warning, perhaps accompanied with some colored and/or flashing lights to get a passerby's attention. Getting people to notice these signs, read them, understand them, and comply with them can be a significant problem, particularly when such signs are used to warn the public of potentially life-threatening hazards nearby (e.g., high-voltage wires, minefields, heavy machinery, quarantine areas).
-
FIG. 1 is a logical block diagram that illustrates a system for acknowledging a posted sign, according to embodiments of the present disclosure. -
FIG. 2 illustrates a mobile device receiving a signal from an electronic source associated with a posted sign, according to embodiments of the present disclosure. -
FIG. 3 is a signal diagram that illustrates signaling between an electronic source, mobile device, and remote server, according to embodiments of the present disclosure. -
FIG. 4 illustrates a method for acknowledging a posted sign, according to embodiments of the present disclosure. -
FIG. 5 illustrates a more detailed method for acknowledging a posted sign, according to embodiments of the present disclosure. -
FIG. 6 is a logical block diagram that illustrates the physical circuitry of a mobile device configured according to embodiments of the present disclosure. -
FIG. 7 is a logical block diagram that illustrates physical units within the processing circuitry of a mobile device that are configured according to embodiments of the present disclosure. -
FIG. 8 is a logical block diagram that illustrates a memory containing software modules configured according to embodiments of the present disclosure. -
FIG. 1 illustrates anexample system 100 for acknowledging signs using amobile device 110, such as a cellular phone, tablet, laptop computer, personal data assistant, or personal music player. The system includes themobile device 110, anelectronic source 105, anetwork 115, and aremote server 120. Themobile device 110 is able to detect theelectronic source 105 once the electronic source is within asignal detection range 125. According to embodiments, theelectronic source 105 may be, for example, an RFID tag, Wi-Fi access point, near field communications (NFC) terminal, active radio beacon, or a BLUETOOTH transmitter. Thesignal detection range 125 is a physical distance within which circuitry within themobile device 110 is able to detect signals originating from theelectronic source 105. The outer limits ofsignal detection range 125 may depend on a number of factors, including the sensitivity of radio circuitry within themobile device 110, the strength of the signal emanating fromelectrical source 105, and interference that may be present in the environment, among other factors. In order for themobile device 110 to detect theelectronic source 105 when thesignal detection range 125 is small, themobile device 110 andelectronic source 105 will generally need to be physically closer together than when thesignal detection range 125 is large. Thus, thesignal detection range 125 may be used to control a relevant physical boundary around which embodiments of the present disclosure are practiced, at least to some degree. - The
mobile device 110 is also able to communicate with anetwork 115, such as the Internet, a cellular network, or Local Area Network (LAN), over a wireless connection. Thenetwork 115 may be used to exchange messages with theremote server 120. Accordingly, thenetwork server 120 may be used, for example, to receive registration messages from themobile device 110 in order to track when the user encounters theelectronic source 105, send content associated with theelectronic source 105 to themobile device 110, and receive and store acknowledgement messages, relating to that content, from themobile device 110. - The
electronic source 105 may be positioned on or near asign 205, as depicted inFIG. 2 . The electronic source radiates aradio signal 220 that can be detected by themobile device 110. Thesignal 220 comprises anidentifier 230 that identifies the electronic source 105 (e.g., a serial number, a Universally Unique Identifier (UUID)), and anaddress 225 of the remote server 120 (e.g., an Internet Protocol (IP) address). According to embodiments, theidentifier 230 and theaddress 225 may be the same (e.g., a Media Access Control (MAC) address, a Uniform Resource Identifier (URI)). Themobile device 110 uses thesignal 220 to display anappropriate notification 210 that corresponds to thesign 205 using content obtained from the remote server 120 (not shown inFIG. 2 ). Themobile device 110 also presents aprompt 215 to the user that can be used to acknowledge thenotification 210. Theprompt 215 may be, for example, a graphical button that the user can tap or click on to indicate their acknowledgement. Theprompt 215 can also be a more complex user interface element that requires the user's input, such as a text input field that requires the user to type certain words (e.g., “I agree,” “I accept,” “I acknowledge”). - The
sign 205 depicted inFIG. 2 is a reminder for employees to wash their hands before returning to work. Such asign 205 may commonly be found fastened to the wall of a restaurant bathroom in a highly visible location. When theelectronic source 105 is associated with such asign 205, it may be appropriate for themobile device 110 to display anotification 210 asking the user whether they did, in fact, wash their hands. Althoughsign 205 andelectronic source 105 are depicted as stationary, according to embodiments, thesign 205 and/orelectronic source 105 may be movable, or even portable. For example,sign 205 may be a warning printed on a portable power tool indicating that safety goggles are required to use the tool. In such case, theelectronic source 105 may be affixed to the power tool itself, or may be installed within a toolbox or workbench where the power tool is stored, for example. In addition, thenotification 210 displayed by themobile device 110 may ask the user to certify that they are, in fact, wearing their safety googles, and/or may ask the user to accept the risk of physical injury that comes with using the power tool. Thus, various embodiments ofsystem 100 may be useful to obtain acknowledgements from users in a wide variety of scenarios. -
FIG. 3 illustrates an example of the signaling exchanged between theelectronic source 105,mobile device 110, andremote server 120, according to embodiments of the present disclosure. According to embodiments, thesignal 220 is transmitted by theelectronic source 105 in response to an earlier signal sent by the mobile device 110 (not shown inFIG. 3 ). A passive RFID tag, for example, lacks its own power source. Thus, when used to implementelectronic source 105, the passive RFID tag may use energy radiated from themobile device 110 to induce a current within the passive RFID tag's antenna to transmit thesignal 220. According to other embodiments, theelectronic source 105 has a source of power (e.g., a battery, a wall outlet) and sends thesignal 220 periodically, at fixed or at varying intervals. - The
mobile device 110, having detected thesignal 220, sends aregistration 260 to theremote server 120. Thisregistration 260 may include, for example, theidentifier 230 of the electronic source 105 (as obtained from the signal 220) and anidentifier 240 of the mobile device 110 (e.g., a phone number, an email address).Such registration 260 may, for example, serve to notify theremote server 120 that a particular user of themobile device 110 is in proximity to thesign 205 associated with theelectronic source 105. According to embodiments,mobile device 110 may have aregistration policy 235 that governs whether or not themobile device 110 registers whensignal 220 is detected. Thus, sending theregistration 260 may be based, according to embodiments, on acomparison 255 between information in thesignal 220 and theregistration policy 235. For example, the registration policy may indicate that themobile device 110 is to send theregistration 260 forsignals 220 comprising aparticular identifier 230, or forsignals 220 comprising anaddress 225 of a particularremote server 120. Theregistration policy 235 may also indicate that themobile device 110 is to send theregistration 260 only during certain times, or when themobile device 110 is in a certain state. Thus, theregistration policy 235 may be used to include or exclude certainelectronic sources 105 ormobile devices 110 from participating in thesystem 100 at given times or under certain conditions. - For example,
sign 205, as illustrated inFIG. 2 , reminds restaurant employees that they must wash their hands before returning to work. Thissign 205 is directed only at employees, and not, for example, customers. Such asign 205 may be present in both the men's and women's bathroom of the restaurant, and each may have a respectiveelectronic source 105, each of which transmits arespective signal 220 that comprises arespective identifier 230 of the correspondingelectronic source 105. Employees of the restaurant may have aregistration policy 235 on their respectivemobile devices 110 indicating that themobile devices 110 are to send theregistration 260 when asignal 220 comprising theidentifier 230 of theelectronic source 105 in either bathroom is detected. Each signal may also, or instead, comprise anaddress 225 to the sameremote server 120, which may be at a knownIP address 225 on alocal network 115. In such case, theregistration policy 235 may indicate that themobile devices 110 are to send theregistration 260 when asignal 220 comprising the knownIP address 225 of thenetwork server 120 is detected. Accordingly, non-employees may refrain from sending theregistration 260, as they would typically lack aregistration policy 235 configured as described above. More generally, theregistration policy 235 may be present on themobile devices 110 of users over whom an administrator of theelectronic source 105 has some measure of control. For example, a business owner may use thesystem 100 to track employees, parents may use thesystem 100 to track children, teachers may use thesystem 100 to track students, and doctors may use thesystem 100 to track nurses and/or patients. - Returning to
FIG. 3 , after themobile device 110 sends theregistration 260 to theremote server 120, themobile device 110 receivescontent 265 associated with theelectronic source 105 in response. Themobile device 110 displays 275 anotification 210 comprising thiscontent 265 and a prompt 215 through which the user may provide input 295 to acknowledge thenotification 210. For example, when theelectronic source 105 is associated with the hand-washing sign 205 ofFIG. 2 , thecontent 265 may be a question asking the user ofmobile device 110 to certify that they have, in fact, washed their hands. When theelectronic source 105 is associated with awarning sign 205 indicating that hard hats are required in a particular construction zone, thecontent 265 may be a reminder that failure to comply with jobsite safety requirements is punishable by immediate termination. When theelectronic source 105 is associated with a fire evacuation map in a hotel room, the content may be an animated gif or video illustrating the path from the room to the nearest exit. Thecontent 265 may be configured by an administrator of thesystem 100, and may vary widely depending on the particular use case to which thesystem 100 is applied. After the user provides input 295 to acknowledge thenotification 210, themobile device 110 may send anacknowledgement message 300 to theremote server 120. In this way, theremote server 120 may not only track which users have come in contact with thesign 205, but also track which users have actually read, understood, indicated their compliance with, or otherwise acknowledged content provided by theremote server 120 concerning thesign 205. - According to embodiments, the
mobile device 110 may also receive anotification policy 270 from theremote server 120. Thenotification policy 270 may define at least one behavior for themobile device 110 when displaying 275 thenotification 210. For example, thenotification policy 270 may require thecontent 265 to be displayed 275 in thenotification 210 for at least a minimum duration before the user may use the prompt 215 to acknowledge thenotification 210. Alternatively or additionally, thenotification policy 270 may require that the user acknowledge thenotification 210 within a maximum duration, at a particular location, and/or may dictate that the phone vibrate when thenotification 210 is displayed, according to embodiments. Thus, receiving thenotification policy 270 from theremote server 120 enables themobile device 110 to display 275 thenotification 210 in accordance with thatnotification policy 270. According to other embodiments, thisnotification policy 270 is not received from theremote server 120, at least in part, but is instead preconfigured, at least partly, at themobile device 110. - There are a variety of scenarios in which it is important that the user acknowledge the
notification 210 while they are still physically close to theelectronic source 105. For example, a user's acknowledgement that they understand aparticular sign 205 may be at least slightly more reliable if the user is required to stand in close proximity to thesign 205 in order for thesystem 100 to accept the acknowledgment. Thus, requiring that the user be physically close to theelectronic source 105 in order to successfully acknowledge the notification may help to prevent users from merely “clicking through” the notification 210 (i.e., acknowledging thenotification 210 without actually reading or understanding it). Thus, according to embodiments, themobile device 110 may disable 280 sending theacknowledgement message 300 to thenetwork server 120 in response to failing to detect that theelectronic source 105 is in the signal detection range 125 (e.g., by deactivating or removing the prompt 215). Similarly, the mobile device may enable 290 sending theacknowledgement message 300 in response to detecting that theelectronic source 105 is in thesignal detection range 125. - For example,
FIG. 3 depicts anelectronic source 105 that sends thesignal 220 periodically. After receiving thefirst signal 220,mobile device 110 fails to receive the next four transmissions of the signal 220 (e.g., the mobile device moves such that theelectronic source 105 is no longer in signal detection range 125). Themobile device 110, having sent theregistration 260, receivedcontent 265 from theremote server 120 in response, and having failed to detect theelectronic source 105 for some duration, disables 280 sending theacknowledgement message 300. Thus, the user input 285 does not result in anyacknowledgement message 300 to be sent to the remote server 120 (i.e., the user input 285 is received while sending theacknowledgement 300 is disabled 280). It is not until after themobile device 110 receives thesixth signal 220 transmission from theelectronic source 105 that themobile device 110 enables 290 sending the acknowledgement message 300 (e.g., themobile device 110 may return to, or near to, where thefirst signal 220 was received, such that theelectronic source 105 is once again in signal detection range 125). User input 295, being received after sending theacknowledgement 300 has been enabled 290, results in themobile device 110 sending theacknowledgement message 300 to theremote server 120. In this way, the user may be required to return to physical proximity with theelectronic source 105 in order for themobile device 110 to send theacknowledgement message 300. - According to embodiments, the
mobile device 110 receives areward notice 305 in response to sending theacknowledgement message 300. Thus, the user may be enticed to acknowledge thenotification 210, even if doing so would involve the inconvenience of returning to a location where thesignal 220 can be detected. One example of enticing the user to acknowledge thenotification 210 may involve an electronics store that has asign 205 in the window advertising a special price on laptop computers for customers who have an electronic coupon. When the user approaches thesign 205, theirmobile device 110 may detect asignal 220 sent by anelectronic source 105 on or near thesign 205. Themobile device 110 may then send aregistration 260 to theremote server 120 at theaddress 225 indicated in thesignal 220 and receivecontent 265 in response that asks the user if they would like to receive the electronic coupon. Themobile device 110displays 275 thiscontent 265 to the user, and the user may then provide input 295 acknowledging that they would like to receive the coupon. Themobile device 110 sends anacknowledgement message 300 to theremote server 120, and theremote server 120 responds with thereward notice 305, which comprises the electronic coupon for the laptop. -
FIG. 4 illustrates amethod 400, implemented in amobile device 110, according to embodiments of the present disclosure. Themethod 400 comprises receiving, via a radio interface of themobile device 110, asignal 220 from anelectronic source 105 withinrange 125 of the radio interface, thesignal 220 originating from theelectronic source 105 and comprising anaddress 225 of aremote server 120 that is distinct from theelectronic source 105, and anidentifier 230 of the electronic source 105 (block 405). The method further comprises sending aregistration 260 to theremote server 120 at theaddress 225, theregistration 260 comprising anidentifier 240 of themobile device 110 and theidentifier 230 of the electronic source 105 (block 410). The method further comprises receivingcontent 265 associated with theelectronic source 105 from theremote server 120 in response to the registration 260 (block 415), and displaying 275, on a display of themobile device 110, anotification 210 comprising thecontent 265 and a prompt 215 for the user to acknowledge the notification 210 (block 420). The method further comprises receiving input 295 from the user acknowledging the notification 210 (block 425) and sending anacknowledgement message 300 to theremote server 120 in response to receiving the input 295 (block 430). - A more
detailed method 500 is illustrated inFIG. 5 . According to themethod 500, themobile device 110 receives thesignal 220 from theelectronic source 105 as previously described (step 502). Themobile device 110 then decides whether or not to register with the remote server 120 (e.g., based on aregistration policy 235 as previously described) (step 504). If themobile device 110 decides not to register, themethod 500 ends (step 530). If themobile device 110 decides to register, themobile device 110 sends the registration 260 (step 506). In response to theregistration 260, the mobile device receivescontent 265 associated with theelectronic source 105 and a notification policy 270 (step 508). Themobile device 110 displays a notification comprising thecontent 265 and a prompt 215 through which the user may acknowledge thenotification 210 in accordance with the notification policy 270 (step 510). - According to the
method 500, thenotification policy 270 indicates that the usability of themobile device 110 is to be impaired until input 295 from the user acknowledging thenotification 210 is received. Accordingly, themobile device 110 impairs the usability of themobile device 110 according to the notification policy 270 (step 512). For example, themobile device 110 may prevent the user from launching particular software, may prevent communication with certain other devices on thenetwork 115, may partially or fully obscure visual elements in the mobile device's 110 display, may vibrate continuously or periodically, and/or may be block the output of audio, until the user successfully acknowledges thenotification 210. - According to the
method 500, thenotification policy 270 also indicates that the user be alerted until the input 295 from the user acknowledging thenotification 210 is received. Further, thenotification policy 270 indicates that the user is to be alerted if themobile device 110 fails to detect that theelectronic source 105 is inrange 125. Accordingly, themobile device 110 alerts the user according to the notification policy 270 (step 514). According to embodiments, such alerting may include outputting audio (e.g., alarms, audible messages, ringtones) and vibrating themobile device 110. Further, such alerting may be, according to embodiments, periodic, continuous, or in response detecting certain events (e.g., failing to detect thesignal 220 within a particular duration, failing to acknowledge the notification within a particular duration, detecting that the user is attempting to circumvent the notification 210). - The
mobile device 110 then attempts to detect thesignal 220 from the electronic source 105 (step 516). If themobile device 110 fails to detect thesignal 220, themobile device 110 disables 280 sending the acknowledgement 300 (step 518) and alert the user again (step 514). Thus, the user is not able to provide input 295 to acknowledge thenotification 210 so long as thesignal 220 is not detected, according to themethod 500. However, if themobile device 110 detects thesignal 220, themobile device 110 enables 290 sending the acknowledgement 300 (step 520) and check whether user input 295 acknowledging thenotification 210 has been received (step 522). If user input 295 acknowledging thenotification 210 is not received while sending theacknowledgment message 300 is enabled and after some duration, themobile device 110 alerts the user again (step 514). However, if themobile device 110 receives user input 295 acknowledging thenotification 210 while sending theacknowledgment message 300 is enabled, the mobile device sends the acknowledgement 300 (step 526) and receives areward notice 305 from theremote server 120 in response (step 528). Themethod 500 then ends (step 530). -
FIG. 6 illustrates exemplary hardware of themobile device 110 according to embodiments. Themobile device 110 comprisesprocessing circuitry 510 that is communicatively coupled toradio circuitry 505, amemory 515,display circuitry 525,input circuitry 530, and optionally alertingcircuitry 535, via one or more buses. Theprocessing circuitry 510 may comprise any sequential state machine capable of executing machine instructions stored as a machine-readable computer program 520 in thememory 515, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored-program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. According to embodiments, theprocessing circuitry 510 is communicatively coupled tomemory 515 via one or more buses. Thememory 515 of the various embodiments may comprise any non-transitory machine-readable media known in the art or that may be developed, including but not limited to magnetic media (e.g., floppy disc, hard disc drive, etc.), optical media (e.g., CD-ROM, DVD-ROM, etc.), solid state media (e.g., SRAM, DRAM, DDRAM, ROM, PROM, EPROM, Flash memory, solid state disc, etc.), or the like. - The
radio circuitry 505 is configured to receive a radio signal from an electronic source 105 (e.g., via NFC, BLUETOOTH, RFID) and exchange data with aremote server 120 that is distinct from theelectronic source 105 via a communications network 115 (e.g., via Wi-Fi, Long-Term Evolution (LTE)). According to various embodiments, theradio circuitry 505 may comprise analog and/or digital transceiving circuitry capable of communicating with each other, or with other devices, according to one or more communication protocols known in the art or that may be developed, such as HTTP, RTP, RTCP, HTTPs, Ethernet, TCP/IP, ATM, or the like. Theradio circuitry 505 implements receiver and transmitter functionality appropriate to thecommunication network 115 to which it is attached (e.g., Wi-Fi, LTE) and appropriate for receiving a signal from the electronic source 105 (e.g., NFC, BLUETOOTH, RFID). The transmitter and receiver functionality may share circuit components and/or software, or alternatively may be implemented separately within the radio interface circuitry. - The
input circuitry 530 is configured to accept input signals from a user of themobile device 110. For example, theinput circuitry 530 may be comprised within one or more of a pointing device (such as a mouse, stylus, touchpad, trackball, pointing stick, joystick), a touchscreen, an accelerometer, a microphone for speech input, an optical sensor for optical recognition of gestures, and a keypad or keyboard. Theradio circuitry 505 may also serve as theinput circuitry 530, according to embodiments, for accepting input signals from a remote user or other entity within thenetwork 115. - The
display circuitry 525 is configured to present visual information to a user of themobile device 110. For example, thedisplay circuitry 525 may be comprised within one or more of a graphics adapter, a graphical processing unit, a display port, a Liquid Crystal display, and a Light Emitting Diode display. - The alerting
circuitry 535 comprises one or more ofaudio circuitry 540 configured to output audio andvibration circuitry 545 configured to vibrate the device, according to embodiments. - The
processing circuitry 510 is configured to receive thesignal 220 from theelectronic source 105 withinrange 125 of, and via, theradio circuitry 505, thesignal 220 originating from theelectronic source 105 and comprising anaddress 225 of theremote server 120 and anidentifier 230 of theelectronic source 105. Theprocessing circuitry 510 is further configured to send aregistration 260 to theremote server 120 at theaddress 225 via theradio circuitry 505, theregistration 260 comprising anidentifier 240 of themobile device 110 and theidentifier 230 of theelectronic source 105. Theprocessing circuitry 510 is further configured to receivecontent 265 associated with theelectronic source 105 from theremote server 120 in response to theregistration 260 via theradio circuitry 505, anddisplay 275, via thedisplay circuitry 525, anotification 210 comprising thecontent 265 and a prompt 215 for the user to acknowledge thenotification 210 via theinput circuitry 530. Theprocessing circuitry 510 is further configured to receive input 295, via theinput circuitry 530, from the user acknowledging thenotification 210 and send anacknowledgement message 300 to theremote server 120, via theradio circuitry 505, in response to receiving the input 295 via theinput circuitry 530. -
FIG. 7 illustrates an embodiment of theprocessing circuitry 510 comprising physical hardware units. Theprocessing circuitry 510 comprises asignal receiving unit 705, aregistration sending unit 710, acontent receiving unit 715, a displayingunit 720, aninput receiving unit 725, and anacknowledgement receiving unit 730. - The
signal receiving unit 705 is configured to receive, via a radio interface of themobile device 110, asignal 220 from anelectronic source 105 withinrange 125 of the radio interface, thesignal 220 originating from theelectronic source 105 and comprising anaddress 225 of aremote server 120 that is distinct from theelectronic source 105, and anidentifier 230 of theelectronic source 105. Theregistration sending unit 710 is configured to send aregistration 260 to theremote server 120 at theaddress 225, theregistration 260 comprising anidentifier 240 of themobile device 110 and theidentifier 230 of theelectronic source 105. Thecontent receiving unit 715 is configured to receivecontent 265 associated with theelectronic source 105 from theremote server 120 in response to theregistration 260. The displayingunit 720 is configured to display 275, on a display of themobile device 110, anotification 210 comprising thecontent 265 and a prompt 215 for the user to acknowledge thenotification 210. Theinput receiving unit 725 is configured to receive input 295 from the user acknowledging thenotification 210. Theacknowledgment sending unit 730 is configured to send anacknowledgement message 300 to theremote server 120 in response to receiving the input 295. -
FIG. 8 illustratesmemory 510 comprising software modules for performing embodiments as discussed above. Thememory 510 comprises asignal receiving module 805, aregistration sending module 810, acontent receiving module 815, a displayingmodule 820, aninput receiving module 825, and anacknowledgement receiving module 830. - The
signal receiving module 805 is configured to receive, via a radio interface of themobile device 110, asignal 220 from anelectronic source 105 withinrange 125 of the radio interface, thesignal 220 originating from theelectronic source 105 and comprising anaddress 225 of aremote server 120 that is distinct from theelectronic source 105, and anidentifier 230 of theelectronic source 105. Theregistration sending module 810 is configured to send aregistration 260 to theremote server 120 at theaddress 225, theregistration 260 comprising anidentifier 240 of themobile device 110 and theidentifier 230 of theelectronic source 105. Thecontent receiving module 815 is configured to receivecontent 265 associated with theelectronic source 105 from theremote server 120 in response to theregistration 260. The displayingmodule 820 is configured to display 275, on a display of themobile device 110, anotification 210 comprising thecontent 265 and a prompt 215 for the user to acknowledge thenotification 210. Theinput receiving module 825 is configured to receive input 295 from the user acknowledging thenotification 210. Theacknowledgment sending module 830 is configured to send anacknowledgement message 300 to theremote server 120 in response to receiving the input 295. - Those skilled in the art will appreciate that the various methods and processes described herein may be implemented using various hardware configurations that generally, but not necessarily, include the use of one or more microprocessors, microcontrollers, digital signal processors, or the like, coupled to, or comprising, memory storing software instructions or data for carrying out the techniques described herein.
- The present invention may be carried out in other ways than those specifically set forth herein without departing from the essential characteristics of the invention. The present embodiments are to be considered in all respects as illustrative and not restrictive, and all changes coming within the meaning and equivalency range of the appended claims are intended to be embraced therein.
Claims (17)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/657,318 US9445396B1 (en) | 2015-03-13 | 2015-03-13 | Signage acknowledgement tied to personal computer device |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/657,318 US9445396B1 (en) | 2015-03-13 | 2015-03-13 | Signage acknowledgement tied to personal computer device |
Publications (2)
Publication Number | Publication Date |
---|---|
US9445396B1 US9445396B1 (en) | 2016-09-13 |
US20160270029A1 true US20160270029A1 (en) | 2016-09-15 |
Family
ID=56881492
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US14/657,318 Active US9445396B1 (en) | 2015-03-13 | 2015-03-13 | Signage acknowledgement tied to personal computer device |
Country Status (1)
Country | Link |
---|---|
US (1) | US9445396B1 (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20170351815A1 (en) * | 2016-06-03 | 2017-12-07 | Kathleen Schmelka | Patient management system for interphysician communications |
US20180018689A1 (en) * | 2015-02-25 | 2018-01-18 | Kimberly-Clark Worldwide, Inc. | Method and System for Consumer Award Program for Washroom Usage |
US10719790B2 (en) | 2015-03-30 | 2020-07-21 | Kimberly-Clark Worldwide, Inc. | System and method for instructing personnel on washroom maintenance requirements |
US11156554B2 (en) * | 2017-10-09 | 2021-10-26 | Pathspot Technologies, Inc. | Systems and methods for detection of contaminants on surfaces |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE102015226194A1 (en) * | 2015-12-21 | 2017-06-22 | Robert Bosch Gmbh | Mobile functional device |
US20230298070A1 (en) * | 2018-03-09 | 2023-09-21 | Charles Isgar | Route advertisement and entertainment system |
US10581972B1 (en) | 2019-02-19 | 2020-03-03 | Cisco Technology, Inc. | Internet of things (IoT) gateway-based carrier-operator signage monitoring |
Family Cites Families (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2004240761A (en) * | 2003-02-06 | 2004-08-26 | Fujitsu Ltd | Messaging system |
JP4345368B2 (en) * | 2003-06-17 | 2009-10-14 | 株式会社日立製作所 | Presence management device and information distribution system |
US20040266460A1 (en) | 2003-06-25 | 2004-12-30 | Nokia Corporation | System and method for interacting with a shared electronic display |
DE602004004233T2 (en) | 2003-11-24 | 2007-10-25 | Black & Decker Inc., Newark | Wireless surveillance and security system for goods |
EP1571590A1 (en) * | 2004-03-03 | 2005-09-07 | Swisscom Mobile AG | Order method for mobile telephone users |
US20070203796A1 (en) | 2006-02-28 | 2007-08-30 | Riggs George Iii | RFID Advertisement and Purchase Information Dispersion Method |
US20070252891A1 (en) | 2006-04-27 | 2007-11-01 | Symon Communications, Inc. | System and Method for Interacting Wirelessly with Digital Signage |
EP2134307B1 (en) | 2007-03-30 | 2017-01-25 | University Health Network | Hand hygiene compliance system |
GB0724078D0 (en) | 2007-12-10 | 2008-01-23 | Carr Andrew | System for maintaining and displaying information |
US20100223114A1 (en) | 2009-03-02 | 2010-09-02 | Cisco Technology | Digital signage proof of play |
US8593255B2 (en) | 2009-04-24 | 2013-11-26 | Nokia Corporation | Method and apparatus for providing user interaction via transponders |
CA2668078A1 (en) | 2009-06-05 | 2010-12-05 | Georges Raymond Brow | Automated hand washing reminder system for an entranceway |
US8544033B1 (en) | 2009-12-19 | 2013-09-24 | Cisco Technology, Inc. | System and method for evaluating content in a digital signage environment |
US8917176B2 (en) | 2010-01-14 | 2014-12-23 | Thinxtream Technologies Pte. Ltd. | Apparatus and methods for distributing and displaying emergency communications |
SG177089A1 (en) | 2010-06-30 | 2012-01-30 | Drishya Pte Ltd | Mobile phone empowered wireless digital signage system |
EP2595364A1 (en) * | 2010-07-12 | 2013-05-22 | Panasonic Corporation | Communication device and communication method |
FR2977358B1 (en) | 2011-06-29 | 2013-08-09 | Gilles Vaquin | WARNING SYSTEM OF HAZARDOUS SITUATIONS IN AGGRESSIVE ENVIRONMENT |
CN104115197A (en) | 2011-12-05 | 2014-10-22 | 布莱特瓦维森有限公司 | Smart traffic sign system and method |
US20130191149A1 (en) | 2012-01-24 | 2013-07-25 | Michael Kolberg | Latex detection and warning system and method |
AU2013222215B2 (en) | 2012-02-22 | 2017-12-21 | Master Lock Company Llc | Safety lockout systems and methods |
-
2015
- 2015-03-13 US US14/657,318 patent/US9445396B1/en active Active
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20180018689A1 (en) * | 2015-02-25 | 2018-01-18 | Kimberly-Clark Worldwide, Inc. | Method and System for Consumer Award Program for Washroom Usage |
US10395267B2 (en) * | 2015-02-25 | 2019-08-27 | Kimberly-Clark Worldwide, Inc | Method and system for consumer award program for washroom usage |
US10679236B2 (en) * | 2015-02-25 | 2020-06-09 | Kimberly-Clark Worldwide, Inc. | Method and system for consumer award program for washroom usage |
US10719790B2 (en) | 2015-03-30 | 2020-07-21 | Kimberly-Clark Worldwide, Inc. | System and method for instructing personnel on washroom maintenance requirements |
US11030553B2 (en) | 2015-03-30 | 2021-06-08 | Kimberly-Clark Worldwide, Inc. | System and method for instructing personnel on washroom maintenance requirements |
US11531937B2 (en) | 2015-03-30 | 2022-12-20 | Kimberly-Clark Worldwide, Inc. | System and method for instructing personnel on washroom maintenance requirements |
US20170351815A1 (en) * | 2016-06-03 | 2017-12-07 | Kathleen Schmelka | Patient management system for interphysician communications |
US11156554B2 (en) * | 2017-10-09 | 2021-10-26 | Pathspot Technologies, Inc. | Systems and methods for detection of contaminants on surfaces |
Also Published As
Publication number | Publication date |
---|---|
US9445396B1 (en) | 2016-09-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9445396B1 (en) | Signage acknowledgement tied to personal computer device | |
US9824571B2 (en) | Alerting on proximity of items | |
JP2015022751A (en) | Target search system and search method for the same | |
US20160189522A1 (en) | Status notification method and device | |
Sykes et al. | Context-aware mobile apps using iBeacons: towards smarter interactions | |
WO2011119273A2 (en) | System and apparatus for locating and surveillance of persons and/or surroundings | |
CN105336091A (en) | Method of carrying out alarm aiming at portable positioning equipment, apparatus and system | |
JP6660207B2 (en) | Information display program, information distribution method, and information distribution system | |
US10540868B2 (en) | Streetlight control for emergency response | |
US10643459B2 (en) | Alerthub system | |
US9600996B2 (en) | Devices and methods for providing mobile cellular beacons | |
JP6043631B2 (en) | Push type information distribution system, information receiving terminal and computer program | |
JP2017229054A (en) | Communication terminal, program, notification method, and positioning system | |
TW201820914A (en) | User location notification system and method thereof | |
JP2007336130A (en) | Electronic guide system | |
KR101066561B1 (en) | System for tracking location and the method for the same | |
EP3445268A1 (en) | Methods and systems for tracking an asset in a medical environment and determining its status | |
JPWO2019187628A1 (en) | Reporting device, reporting method, reporting system, and program | |
Almalki et al. | Crowd safety sensing (cross) for the post pandemic era | |
KR20200017940A (en) | Deep running based silver bell service system and Method thereof | |
WO2019010794A1 (en) | Internet of things based monitoring method and internet of things server | |
TW202032156A (en) | Trace positioning device and trace positioning method | |
JP6286027B2 (en) | POSITION INFORMATION TRANSMISSION DEVICE, POSITION INFORMATION TRANSMISSION SYSTEM, POSITION INFORMATION TRANSMISSION METHOD, AND PROGRAM | |
US20230252879A1 (en) | An apparatus and related method for proximity awareness | |
JP2014010689A (en) | Terminal device, terminal device system, monitoring method of terminal device system, and monitoring program of terminal device system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TOSHIBA GLOBAL COMMERCE SOLUTIONS HOLDINGS CORPORA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HERRING, DEAN FREDERICK;JOHNSON, BRAD M.;SMITH, JEFFREY;AND OTHERS;SIGNING DATES FROM 20150212 TO 20150220;REEL/FRAME:035236/0569 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |