A user is enabled to use a mobile device to electronically acknowledge information relating to a sign encountered by the user within the user's environment. The mobile device detects a signal transmitted by an electronic source placed on or near the sign and register with a remote server. The registration may include an identifier of the electronic source and an identifier of the mobile device. In response to the registration, the mobile device receives content associated with the electronic source, and displays that content in a notification on a display of the mobile device. The user may then acknowledge the notification via a prompt on the display. The mobile device receives input from the user acknowledging the notification, and sends an acknowledgement message to the remote server.
|
1. A method, implemented by a mobile device, the method comprising:
receiving, via a radio interface of the mobile device, a signal from an electronic source within range of the radio interface, the signal originating from the electronic source and comprising:
an address of a remote server that is distinct from the electronic source;
an identifier of the electronic source;
sending a registration to the remote server at the address, the registration comprising an identifier of the mobile device and the identifier of the electronic source;
receiving content associated with the electronic source from the remote server in response to the registration;
displaying, on a display of the mobile device, a notification comprising the content and a prompt for the user to acknowledge the notification;
receiving input from the user acknowledging the notification;
sending an acknowledgement message to the remote server in response to receiving the input.
17. A computer program product stored in a non-transitory computer readable medium for controlling a programmable mobile device, the computer program product comprising software instructions that, when run on the programmable mobile device, cause the programmable mobile device to:
receive, via a radio interface of the programmable mobile device, a signal from an electronic source within range of the radio interface, the signal originating from the electronic source and comprising:
an address of a remote server that is distinct from the electronic source;
an identifier of the electronic source;
send a registration to the remote server at the address, the registration comprising an identifier of the programmable mobile device and the identifier of the electronic source;
receive content associated with the electronic source from the remote server in response to the registration;
display, on a display of the programmable mobile device, a notification comprising the content and a prompt for the user to acknowledge the notification;
receive input from the user acknowledging the notification;
send an acknowledgement message to the remote server in response to receiving the input.
9. A mobile device comprising:
display circuitry configured to present visual information to a user;
input circuitry configured accept input signals from a user;
radio circuitry configured to:
receive a radio signal from an electronic source;
exchange data with a remote server that is distinct from the electronic source via a communications network;
processing circuitry communicatively coupled to the display circuitry, input circuitry, and radio circuitry, and configured to:
receive the signal from the electronic source within range of, and via, the radio circuitry, the signal originating from the electronic source and comprising:
an address of the remote server;
an identifier of the electronic source;
send a registration to the remote server at the address via the radio circuitry, the registration comprising an identifier of the mobile device and the identifier of the electronic source;
receive content associated with the electronic source from the remote server in response to the registration via the radio circuitry;
display, via the display circuitry, a notification comprising the content and a prompt for the user to acknowledge the notification via the input circuitry;
receive input, via the input circuitry, from the user acknowledging the notification;
send an acknowledgement message to the remote server, via the radio circuitry, in response to receiving the input via the input circuitry.
2. The method of
3. The method of
receiving a notification policy from the remote server in response to the registration, the notification policy defining at least one behavior for the mobile device when displaying the notification;
wherein displaying the notification on the display of the mobile device comprises displaying the notification according to the notification policy.
4. The method of
5. The method of
6. The method of
7. The method of
disabling the sending of the acknowledgement message in response to failing to detect that the electronic source is in range of the radio interface;
enabling the sending of the acknowledgement message in response to detecting that the electronic source is in range of the radio interface.
8. The method of
10. The mobile device of
11. The mobile device of
wherein the processing circuitry is further configured to receive a notification policy from the remote server via the radio circuitry in response to the registration, the notification policy defining at least one behavior for the mobile device when displaying the notification;
wherein to display the notification via the display circuitry, the processing circuitry is configured to display the notification according to the notification policy.
12. The mobile device of
13. The mobile device of
further comprising alerting circuitry communicatively coupled to the processing circuitry, the alerting circuitry comprising one or more of:
audio circuitry configured to output audio;
vibration circuitry configured to vibrate the device;
wherein the processing circuitry is further configured to periodically alert the user via the alerting circuitry until the input from the user acknowledging the notification is received.
14. The mobile device of
further comprising alerting circuitry communicatively coupled to the processing circuitry, the alerting circuitry comprising one or more of:
audio circuitry configured to output audio;
vibration circuitry configured to vibrate the device;
wherein the processing circuitry is further configured to alert the user via the alerting circuitry before sending the acknowledgement message in response to the processing circuitry failing to detect that the electronic source is in range via the radio circuitry.
15. The mobile device of
disable the sending of the acknowledgement message in response to failing to detect that the electronic source is in range via the radio circuitry;
enable the sending of the acknowledgement message in response to detecting that the electronic source is in range via the radio circuitry.
16. The mobile device of
|
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).
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. Accordingly, 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
The sign 205 depicted in
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. According to embodiments, mobile device 110 may have a registration policy 235 that governs whether or not the mobile device 110 registers when signal 220 is detected. Thus, 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. For example, 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. Thus, 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.
For example, sign 205, as illustrated in
Returning to
According to embodiments, 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. For example, 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. Alternatively or additionally, 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. Thus, receiving the notification policy 270 from the remote server 120 enables the mobile device 110 to display 275 the notification 210 in accordance with that notification policy 270. According to other 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.
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 the electronic source 105. For example, 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. Thus, 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). Thus, according to embodiments, 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.
For example,
According to embodiments, the mobile device 110 receives a reward notice 305 in response to sending the acknowledgement message 300. Thus, 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. When the user approaches the sign 205, 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.
A more detailed method 500 is illustrated in
According to the method 500, 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). For example, 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.
According to the method 500, 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. Further, such 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 then 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). If user input 295 acknowledging the notification 210 is not received while sending the acknowledgment message 300 is enabled and after some duration, 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).
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)). According to various embodiments, 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. For example, 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. For example, 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.
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.
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.
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.
Smith, Jeffrey, Herring, Dean Frederick, Johnson, Brad M., Rodriguez, Adrian
Patent | Priority | Assignee | Title |
10581972, | Feb 19 2019 | Cisco Technology, Inc. | Internet of things (IoT) gateway-based carrier-operator signage monitoring |
9998893, | Dec 21 2015 | Robert Bosch GmbH | Mobile function device |
Patent | Priority | Assignee | Title |
7319395, | Nov 24 2003 | Black & Decker Inc | Wireless asset monitoring and security system using user identification tags |
7801514, | Mar 03 2004 | INTERDIGITAL CE PATENT HOLDINGS, SAS | Order method for mobile radio network users |
7898407, | Mar 30 2007 | University Health Network | Hand hygiene compliance system |
8400310, | Jun 05 2009 | Automated hand cleaning reminder system for an entranceway | |
8544033, | Dec 19 2009 | Cisco Technology, Inc. | System and method for evaluating content in a digital signage environment |
8593255, | Apr 24 2009 | Nokia Technologies Oy | Method and apparatus for providing user interaction via transponders |
20040156487, | |||
20040266460, | |||
20050021773, | |||
20070203796, | |||
20070252891, | |||
20100223114, | |||
20110169634, | |||
20120171952, | |||
20130191149, | |||
20130214903, | |||
20140139356, | |||
WO2009074791, | |||
WO2012001704, | |||
WO2013084225, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Feb 12 2015 | HERRING, DEAN FREDERICK | Toshiba Global Commerce Solutions Holdings Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035236 | /0569 | |
Feb 12 2015 | JOHNSON, BRAD M | Toshiba Global Commerce Solutions Holdings Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035236 | /0569 | |
Feb 12 2015 | RODRIGUEZ, ADRIAN | Toshiba Global Commerce Solutions Holdings Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035236 | /0569 | |
Feb 20 2015 | SMITH, JEFFREY | Toshiba Global Commerce Solutions Holdings Corporation | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 035236 | /0569 | |
Mar 13 2015 | Toshiba Global Commerce Solutions Holdings Corporation | (assignment on the face of the patent) | / |
Date | Maintenance Fee Events |
Feb 27 2020 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Feb 28 2024 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Date | Maintenance Schedule |
Sep 13 2019 | 4 years fee payment window open |
Mar 13 2020 | 6 months grace period start (w surcharge) |
Sep 13 2020 | patent expiry (for year 4) |
Sep 13 2022 | 2 years to revive unintentionally abandoned end. (for year 4) |
Sep 13 2023 | 8 years fee payment window open |
Mar 13 2024 | 6 months grace period start (w surcharge) |
Sep 13 2024 | patent expiry (for year 8) |
Sep 13 2026 | 2 years to revive unintentionally abandoned end. (for year 8) |
Sep 13 2027 | 12 years fee payment window open |
Mar 13 2028 | 6 months grace period start (w surcharge) |
Sep 13 2028 | patent expiry (for year 12) |
Sep 13 2030 | 2 years to revive unintentionally abandoned end. (for year 12) |