System and method for wearable smart device communications

Information

  • Patent Grant
  • 9958275
  • Patent Number
    9,958,275
  • Date Filed
    Tuesday, May 31, 2016
    8 years ago
  • Date Issued
    Tuesday, May 1, 2018
    6 years ago
Abstract
A wearable smart device includes an outer casing wearable by a user and defining at least one cavity and having a neck portion, a first end portion designed to rest on a first shoulder of the user, and a second end portion designed to rest on a second shoulder of the user. The wearable smart device also includes a wireless communication port at least partially positioned within the cavity and designed to communicate with a remote device. The wireless communication port includes a dedicated short range communication (DSRC) port, a near field communication (NFC) port, an infrared communication port and/or an ultrasound communication port. A processor is positioned within the cavity, coupled to the wireless communication port and designed to transmit one or more signals to the remote device and/or receive one or more signals from the remote device via the wireless communication port.
Description
BACKGROUND
1. Field

The present disclosure relates to systems and methods for providing communications between a wearable smart device and a remote device.


2. Description of the Related Art

As computing power becomes faster and electronic devices become smaller, technology is being implemented in increasingly smaller packages. Technology is now at a point in which advanced computing functions can be implemented in devices sufficiently small to be comfortably worn by users as accessories. Wearable computing devices provide the benefit of providing computing functions to a user without being concerned with the volume or the mass of the device while he or she is moving.


The reduction in size of computing equipment is also allowing for an ever-growing internet of things. More and more devices are beginning to include computing functions, and devices that already include some computing functions are being designed to include more and more functionality. For instance, vehicles are now being designed with the ability to drive themselves without human intervention. Vehicles are also being designed to include receivers and transmitters for vehicle-to-vehicle communications.


Thus, there is a need for systems and methods for providing connectivity between wearable smart devices and the internet of things.


SUMMARY

What is described is a wearable smart device for communicating with a remote device, such as a vehicle, a robot or another smart device. The wearable smart device includes an outer casing defining at least one cavity and having a neck portion designed to contact a neck of a user. The wearable smart device also includes a first end portion designed to rest on a first shoulder of the user and a second end portion designed to rest on a second shoulder of the user such that the wearable smart device may be worn by the user. The wearable smart device also includes a wireless communication port at least partially positioned within the at least one cavity and that is designed to communicate with the remote device. The wireless communication port includes at least one of a dedicated short range communication (DSRC) port, a near field communication (NFC) port, an infrared communication port or an ultrasound communication port. The wearable smart device also includes a processor positioned within the at least one cavity, coupled to the wireless communication port and designed to transmit one or more signals to the remote device and/or receive one or more signals from the remote device via the wireless communication port.


Also described is a wearable smart device for communicating with a remote device. The wearable smart device includes a first wireless communication port designed to receive a first signal from the remote device via a first communication protocol. The wearable smart device also includes a second wireless communication port designed to transmit a second signal to the remote device via a second communication protocol that is different than the first communication protocol. The wearable smart device also includes a processor coupled to the first wireless communication port and to the second wireless communication port. The processor is designed to receive the first signal via the first wireless communication port and to transmit the second signal via the second wireless communication port in response to receiving the first signal.


Also described is a wearable smart device for providing collision avoidance instructions to a user at least partially based on wireless communications. The wearable smart device includes a wireless communication port designed to receive a signal from a remote device. The wearable smart device also includes a processor coupled to the wireless communication port. The processor is designed to determine a location of the remote device relative to the wearable smart device based on the received signal and to determine navigation instructions to avoid a collision with the remote device based on the determined location of the remote device. The wearable smart device also includes an output device designed to output the navigation instructions.





BRIEF DESCRIPTION OF THE DRAWINGS

Other systems, methods, features, and advantages of the present invention will be or will become apparent to one of ordinary skill in the art upon examination of the following figures and detailed description. It is intended that all such additional systems, methods, features, and advantages be included within this description, be within the scope of the present invention, and be protected by the accompanying claims. Component parts shown in the drawings are not necessarily to scale, and may be exaggerated to better illustrate the important features of the present invention. In the drawings, like reference numerals designate like parts throughout the different views, wherein:



FIG. 1 is a block diagram illustrating features of a wearable smart device for communicating with one or more remote devices according to an embodiment of the present invention;



FIG. 2 is a drawing of a wearable smart device designed to be worn around a user's neck and having features for communicating with one or more remote devices according to an embodiment of the present invention;



FIG. 3 is a flowchart illustrating a method to be performed by a processor of a wearable smart device for optimizing bandwidth and battery power during communications with a remote device according to an embodiment of the present invention;



FIG. 4 is a drawing illustrating an exemplary use of the method of FIG. 3 by the wearable smart device of FIG. 2 according to an embodiment of the present invention;



FIG. 5 is a flowchart illustrating a method to be performed by a processor of a wearable smart device for determining and providing collision avoidance instructions based on data received via a wireless communication port of the wearable smart device according to an embodiment of the present invention; and



FIG. 6 is a drawing illustrating an exemplary use of the method of FIG. 5 by the wearable smart device of FIG. 2 according to an embodiment of the present invention.





DETAILED DESCRIPTION

Disclosed herein are systems and methods for providing communications between a wearable smart device and a remote device, such as a vehicle, a robot, another wearable smart device, a smartphone, or the like. The systems and methods provide several benefits and advantages such as allowing the wearable smart device to communicate with remote devices via one or more communication protocols. This provides benefits and advantages such as allowing the wearable smart device to communicate with remote devices having different communication capabilities, further providing the benefit and advantage of allowing the wearable smart device to interact with and/or control a variety of devices within a user's environment. For example, the wearable smart device can communicate with a vehicle to determine the location of the vehicle using one type of communication, may transmit and receive audio messages from another wearable smart device using another type of communication, and can determine a location of a storefront using yet another type of communication. The systems and methods provide additional benefits and advantages such as optimizing communications to preserve battery life and to provide relatively high bandwidth. The systems and methods provide additional benefits and advantages such as the ability to receive messages corresponding to a location, a heading, a velocity or an acceleration of a remote device and to provide instructions to a user for avoiding a potential collision with the remote device.


An exemplary system includes one or more wireless communication ports for communicating via one or more communication protocols. The protocols may include, for example, dedicated short-range communication (DSRC), Wi-Fi protocols, Bluetooth protocols, near field communications (NFC) protocols, infrared protocols and/or ultrasound protocols. The system may also include a processor. The processor may communicate with one or more remote devices via the one or more wireless communication ports. The processor may also manage communications over two or more wireless communication ports to optimize the bandwidth of the communications and to preserve the battery power of the wearable smart device. The processor may also determine a location, a heading, a velocity or an acceleration of a remote device based on data received from the remote device via the one or more wireless communication ports. Based on the location, heading, velocity and/or acceleration of the remote device, the processor may determine navigation instructions for avoiding a collision with the remote device. The system may also include an output device for outputting the navigation instructions to the user and/or to output communications received from the remote device.


Referring to FIG. 1, a wearable smart device 100 according to some embodiments may include a processor 102, a memory 104, an input device 106 and an output device 108. The wearable smart device 100 may also include a GPS sensor 110, an IMU 112, a camera 114, a first wireless communication port 116 and a second wireless communication port 118.


The processor 102 may be a computer processor such as an ARM processor, DSP processor, distributed processor or other form of processing. The processor 102 may be positioned on the wearable smart device 100, may be a remote processor or it may be a pairing of a local and a remote processor.


The memory 104 may be one or any combination of the following: a RAM or other volatile or nonvolatile memory, a non-transitory memory or a data storage device, such as a hard disk drive, a solid state disk drive, a hybrid disk drive or other appropriate data storage. The memory 104 may further store machine-readable instructions which may be loaded into the memory 104 and executed by the processor 102. As with the processor 102, the memory 104 may be positioned on the wearable smart device 100, may be remote from the wearable smart device 100 or may be a pairing of a local and a remote memory.


The input device 106 may include any input device such as a touch screen, a plurality of buttons, a microphone or the like. The input device 106 is designed to receive input from a user and/or from an environment of the user.


The output device 108 may include any output device such as a display, one or more speakers, one or more vibration units or the like. The output device 108 is designed to provide output to a user and/or an environment of the user.


The GPS sensor 110 may include one or more GPS receivers designed to detect location data. In that regard, the GPS sensor 110 may be coupled to the processor 102. The processor 102 may be capable of determining a location of the wearable smart device 100 based on the location data detected by the GPS sensor 110.


The IMU 112 may include one or more of an accelerometer, a gyroscope, a magnetometer or the like. The IMU 112 may detect inertial measurement data corresponding to movement of the wearable smart device 100. For example, the inertial measurement data may include an orientation of the wearable smart device 100, an acceleration of the wearable smart device 100, a velocity of the wearable smart device 100, or the like.


The camera 114 may include one or more cameras or other image sensors capable of detecting image data corresponding to an environment of the wearable smart device 100.


The first wireless communication port 116 and the second wireless communication port 118 may include any communication port capable of transmitting and/or receiving data from a remote device 120. A communication port can include at least one of a receiver, a transmitter or a combined receiver and transmitter for receiving and/or transmitting messages using a particular communication protocol. For example, at least one of the first wireless communication port 116 or the second wireless communication port 118 may be capable of transmitting and/or receiving data via a DSRC protocol, a Wi-Fi protocol, a Bluetooth protocol, a NFC protocol, an infrared light protocol or an ultrasound protocol.


DSRC technology may be used by the processor 102 to transmit location information corresponding to a location of the wearable smart device 100 to the remote device 120. DSRC technology may also be used by the processor 102 to receive location information corresponding to a location of the remote device 120. The location information may include a location within a predetermined area, a location relative to another device, an orientation, a velocity, a rate of acceleration or the like. As an example, the remote device 120 may include a transmitter at a storefront capable of transmitting DSRC information providing the name and location of the corresponding store. The user may wish to enter the store and may provide input to the wearable smart device 100 indicating so. The wearable smart device 100 may receive the DSRC signal from the remote device 120, may determine the location of the store relative to the wearable smart device, and may provide navigation instructions to the user directing the user to the storefront.


This function may be useful in situations in which multiple devices are located within a certain area, such as a factory. For example, a moving vehicle or robot may also include a DSRC port that is designed to receive and transmit location information. A vehicle may receive location information corresponding to the wearable smart device 100 and may initiate obstacle avoidance functions to avoid a collision with the user of the wearable smart device 100. Similarly, the wearable smart device 100 may receive location information corresponding to the remote device 120. If the user of the wearable smart device 100 is walking towards the location of the remote device 120, the wearable smart device 100 may provide collision avoidance instructions to the user for avoiding a collision with the remote device 120.


The DSRC communication port may be designed to transmit messages to and/or receive messages from all devices detectable by the wearable smart device 100. In some embodiments, the processor 102 may control the DSRC communication port to only communicate with devices within a predetermined area of the wearable smart device 100.


Wi-Fi technology may be used by the processor 102 for similar functions as DSRC technology. For example, the processor 102 may transmit and/or receive location information, orientation, velocity or the like via the first wireless communication port 116 and/or the second wireless communication port 118 using Wi-Fi protocols. Wi-Fi technology may also be used by the processor 102 for other navigation functions, for alerting other devices of the presence of the wearable smart device 100, for receiving alerts identifying the presence of other devices, or the like.


Wi-Fi technology may also be used for transmitting and/or receiving text, sound or images from nearby device or people and/or from other devices or people via the Internet. For example, the messages may be informational, such as informing the wearable smart device 100 of the identity of an oncoming bus (such as “bus 57 is approaching,” “there is a sale at the Gap,” “a customer has entered the shop,” “a warehouse shelf is empty,” “it's raining outside,” or the like. The messages may also be social in nature, such as uploading a photograph or audio to a website, transmitting a photograph or audio to a smart device of a friend or the like.


In some embodiments, the messages may include diagnostic or prognostic information regarding the device. For example, this information may include a battery health, an operating temperature, typical usage patterns, typical locations, or the like to nearby devices. The nearby device may alert the user or an administrator of the issue, may record the issue or may initiate a function to repair the issue.


In some embodiments, the messages may also or instead include data or routines for upgrading or enhancing the functionality of the processor 102. For example, the messages may include data for identification of new objects or logos, new apps, firmware upgrades or the like.


In some embodiments, the Wi-Fi communication port may communicate with all devices within a predetermined area of the wearable smart device 100. In some embodiments, the Wi-Fi communication port may only communicate with devices that the processor 102 has been previously paired with or programmed to communicate with. For example, a user of the wearable smart device 100 may indicate that a certain device belongs to a friend of the user. The wearable smart device 100 may then communicate with the friend's device.


Bluetooth technology may be used by the processor 102 for similar functions as Wi-Fi technology. For example, Bluetooth technology may be used to transmit and/or receive location information, orientation, velocity or the like. Bluetooth technology may also be used by the processor for transmitting or receiving data of others smart devices such as headphones, mobile phones, other wearable smart devices, activity trackers, heart rate monitors or the like.


For example, the processor 102 may be coupled to headphones via a Bluetooth port. The headphones may be worn by the user in which case the audio to be played by the headphones may be provided by the processor 102 via the Bluetooth port. In some embodiments, the headphones may be worn by another individual. In this case, the processor 102 may transmit an audio message to the other user's headphones via the Bluetooth port.


When the processor 102 is paired to another smart device via a Bluetooth port, the other smart device may function as another interface for the wearable smart device 100. Non-limiting examples of other smart devices include a smart watch, a smartphone, a tablet, a laptop computer, a personal computer, or the like. In that regard, a user may interact with the processor 102 via the other smart device. For example, the user may make a gesture detectable by the other smart device, push a button on the other smart device, touch a portion of a screen on the other smart device or the like to control functionality of the processor 102. In some embodiments, the other smart device may provide information to the processor 102 via the Bluetooth port. For example, appointment reminders, weather updates, bus schedules or the like may be provided to the processor 102 from the other smart devices via the Bluetooth port. The user may also exchange contact information with another individual via the Bluetooth port.


NFC technology may be used by the processor 102 to transmit and/or receive location information corresponding to the remote device 120. NFC technology may also be used by the processor 102 for controlling the remote device 120. For example, the processor 102 may control an NFC communication port to control a radio, a television, a robot, a lock on a door or the like. The processor 102 may also transmit and/or receive other messages from the remote device 120 via the NFC communication port.


Providing an NFC communication port on the wearable smart device 100 provides advantages. Currently, most NFC transmitters do not utilize battery power. Thus, these transmitters may be implemented in clothing, product packaging or the like. By allowing the wearable smart device 100 to receive NFC messages, the wearable smart device 100 may communicate with a multitude of devices that include a simple NFC transmitter.


Infrared technology may be used by the processor 102 to transmit and/or receive location information corresponding to the remote device 120. Infrared technology may also be used by the processor 102 for controlling the remote device 120 in a similar manner as NFC technology. The processor 102 may also transmit and/or receive other messages from the remote device 120 via the infrared communication port.


Ultrasound technology may be used by the processor 102 to transmit and/or receive location information corresponding to the remote device 120. Ultrasound technology may also be used by the processor 102 for transmitting an audio message to the remote device 120. For example, a user may provide speech input to the wearable smart device 100 via the input device 106. The processor 102 may convert the speech input to an ultrasound signal and transmit the ultrasound signal to the remote device 120 via an ultrasound communication port. The remote device 120 may receive the ultrasound signal and a processor of the remote device 120 may convert the ultrasound signal to an audible signal corresponding to the speech input. In this regard, only the remote device 120 will receive the speech input as opposed to a situation in which the speech input is output via speakers. In some embodiments, the processor 102 may also transmit and/or receive messages from the remote device 120 via the ultrasound port.


In some embodiments, either of the wireless communication ports 116, 118 may also include a display and/or speakers. The processor can relay information to a user or another device via the display and/or speakers. For example, the processor may provide data to a user via one or more lights such as by controlling the color of the light, the intensity of the light or the like. Similarly, the processor may control the light to flash to alert others that the user is distressed or is nearby. This may be particularly useful in low visibility conditions, such as in a fire. The processor may control the speakers to provide similar information. For example, the speakers may output a beeping sound to alert others that the user is distressed or nearby.


Turning now to FIG. 2, a wearable smart device 200 is shown. The wearable smart device 200 includes a processor 202 and a memory 204. The processor 202 and the memory 204 function in a similar manner as the processor 102 and the memory 104 of FIG. 1.


The wearable smart device 200 also includes buttons 206. The buttons 206 may be used by a user to control operation of the wearable smart device 200. In that regard, the buttons 206 correspond to an input device.


The wearable smart device 200 also includes a first output unit 208A and a second output unit 208B. Each of the output units 208A, 208B include a speaker and a vibration unit. In that regard, the wearable smart device 200 may provide stereo audio output and/or stereo haptic output via the output units 208A, 208B.


The wearable smart device 200 also includes a GPS sensor 210 and an IMU 212 that function in a similar manner as the GPS sensor 110 and IMU 112 of FIG. 1.


The wearable smart device 200 includes a stereo camera pair 214 including a first camera 214A and a second camera 214B. The stereo camera pair 214 may provide stereo image data to the processor 202. The processor 202 may determine distance information corresponding to objects in the environment of the wearable smart device 200 based on the stereo image data.


The wearable smart device 200 includes a first wireless communication port 216 and a second wireless communication port 218. The wireless communication ports 216, 218 function in a similar manner as the wireless communication ports 116, 118 of FIG. 1.


The wearable smart device 200 includes an outer casing 222 that resembles a necklace. The outer casing 222 includes a neck portion 224, a first end portion 226 and a second end portion 228. When worn, the neck portion 224 may rest against the back of the user's neck and/or shoulders. The first end portion 226 extends across one of the user's shoulders and may rest against the front of the user's shoulder and/or the user's chest. Similarly, the second end portion 228 extends across the user's other shoulder and may rest against the front of the user's other shoulder and/or the other side of the user's chest.


The outer casing 222 defines one or more cavities 230. One or more of the components of the wearable smart device 200 may be at least partially positioned within the one or more cavities 230. For example, a single cavity may be defined within the outer casing 222 such that each component is positioned within the same cavity. Alternatively, the outer casing 222 may define multiple cavities such that one or more components are positioned within each cavity.


Some components may only be partially positioned within a cavity. For example, the output units 208A, 208B may each have a portion that is positioned within the cavity and may also have a portion that is flush with or extends beyond the outer casing 222.


The wearable smart device 200 and/or the wearable smart device 100 of FIG. 1 may be designed to optimize communications by increasing battery life and communication bandwidth. For example, the first wireless communication port 216 may include an NFC communication port and the second wireless communication port 218 may include a Bluetooth port. The NFC communication port may utilize less battery power than the Bluetooth port and may provide a smaller bandwidth than the Bluetooth port.


Turning now to FIG. 3, a method 300 for optimizing communications by increasing battery power and bandwidth by a wearable smart device is shown. The method 300 may be performed by a processor of a wearable smart device, such as the processor 102 of FIG. 1. The wearable smart device may have two wireless communication ports. In some embodiments, the first wireless communication port may utilize less power to remain in an on state than the second wireless communication port, and in some embodiments, the second wireless communication port may provide for higher bandwidth communications than the first wireless communication port. In some embodiments, the first wireless communication port may include a DSRC port, a Wi-Fi port, a Bluetooth port, an NFC port, an infrared communication port or an ultrasound communication port. In some embodiments, the second wireless communication port may include a DSRC port, an infrared communication port, an ultrasound communication port, a Bluetooth port or a Wi-Fi port.


In some embodiments, the first wireless communication port may always remain in an on state when the wearable smart device is being worn by the user. The second wireless communication port may remain in an off state until instructed otherwise by the processor.


In block 302, the first wireless communication port may receive a signal from a remote device. The data contained in the signal may be received by the processor of the wearable smart device. For example, the remote device may transmit a signal using an NFC protocol indicating that the remote device wishes to establish communications with the wearable smart device. The signal transmitted by the remote device may also include a list of one or more protocols with which the remote device can communicate. The signal may also include an identifier usable by the wearable smart device to establish communications with the remote device via the one or more protocols. For example, the signal may indicate that the remote device can communicate via Wi-Fi and via Bluetooth. The signal may also include an identifier corresponding to the remote device's Wi-Fi port and another identifier corresponding to the remote device's Bluetooth port.


In response to receiving the signal requesting communications, the processor of the wearable smart device may determine if the wearable smart device is capable of communicating via one or more of the protocols provided by the remote device. If the wearable smart device is capable of communicating with the remote device via more than one of the protocols then the processor may determine the ideal protocol for communication.


The ideal protocol may be determined based on, for example, a remaining battery life of the wearable smart device, the power consumption required to communicate via the protocol, the bandwidth allowable by the protocol, a distance to the remote device, security risks associated with communicating via the protocols, the type of message to be communicated or the like.


For example, the remote device and the wearable smart device may each be capable of communicating via Wi-Fi and Bluetooth and the remote device may be at least 10 meters (32.1 feet) away from the wearable smart device. In this case, the processor may select to communicate with the remote device via Wi-Fi because the Bluetooth signal may become degraded over that distance. As another example, the remote device and the wearable smart device may each be capable of communicating via Wi-Fi and ultrasound and the message to be communicated may be an audio message. In this case, the processor may select to communicate with the remote device via ultrasound as the audio message may be transmitted clearly and the ultrasound communication port may require less power than the Wi-Fi port.


After the first signal requesting communications has been received by the wearable smart device in block 302, the processor of the wearable smart device may power on the second wireless communication port in block 304. Powering on the second wireless communication port may refer to switching the second wireless communication port to an on state such that data may be received and/or transmitted by the second wireless communication port.


After the second wireless communication port has been switched to the on state, the processor may transmit a signal to the remote device via the second wireless communication port in block 306. The signal transmitted from the wearable smart device via the second wireless communication port may be an initialization signal usable by the wearable smart device and/or the remote device to establish a communication channel between the wearable smart device and the remote device. In some embodiments, the signal transmitted from the wearable smart device via the second wireless communication port may include an identifier of the second wireless communication port such that the remote device can transmit messages to the wearable smart device via the second wireless communication port.


After the signal has been sent to the remote device, the processor of the wearable smart device or of the remote device may establish a communication channel between the wearable smart device and the remote device via the second wireless communication port in block 308. In some embodiments, a continuous communication channel is not established and the wearable smart device and the remote device may communicate via single messages or groups of messages without an established continuous communication channel. In that regard, the signal transmitted by the wearable smart device via the second wireless communication port may indicate to the remote device that the second wireless communication port is in an on state. In some embodiments, the second signal may be sent from the first wireless communication port and may include an identifier of the second wireless communication port and an indication that the wearable smart device can now receive messages via the second wireless communication port.


After communications have been established between the wearable smart device and the remote device (or the devices are aware that data may be transferred via the second wireless communication port), the processor of the wearable smart device may monitor the communications to determine when communications have stopped. For example, the remote device may have sent a signal requesting closure of the communication channel. As another example, the processor may be designed to close the communication channel when no messages have been transmitted or received by the second wireless communication port for a predetermined amount of time, such as 30 seconds, one minute, two minutes or the like.


As another example, the processor may determine to close the communication channel in response to a predetermined event such as an input from the user, transmission of all packets of a particular communication, receipt of all packets of a particular communication or the like. When communications have stopped or the processor determines that communications should stop, the processor may close the communication channel and power off the second wireless communication port in block 310.


Because the first wireless communication port has a smaller bandwidth than the second wireless communication port, the method 300 optimizes bandwidth by establishing communications via the second wireless communication port upon request from the remote device. The additional bandwidth provided by the second wireless communication port allows for faster communication between the wearable smart device and the remote device.


Because the second wireless communication port requires more power than the first wireless communication port, the method 300 optimizes power usage by powering off the second wireless communication port when communications with the remote device have ceased. Battery life is further optimized because the second wireless communication port remains in the off state until another communication request is received by the first wireless communication port. Thus, in this way, the processor optimizes bandwidth by providing for communications via the communication port having the higher bandwidth and optimizes power by causing the communication port that requires the most power to be in the off state when communications are not occurring.


A similar method to the method 300 may also be performed by a wearable smart device, such as the wearable smart device 100 of FIG. 1 or the wearable smart device 200 of FIG. 2, for establishing communications with the remote device. For example, instead of receiving a signal from the remote device in block 302, the wearable smart device may transmit a signal to the remote device via the first wireless communication port. The signal may include identification information usable by the remote device to establish communications with a second wireless communication port of the wearable smart device. The wearable smart device may then power on the second wireless communication port and, after a period of time, receive a message from the remote device via the second wireless communication port. A communication channel may then be established between the two devices via the second wireless communication port. When communications have ceased via the second communication port, the processor may power off the second communication port.


Referring now to FIGS. 2, 3 and 4, and exemplary use of the method 300 by the wearable smart device 200 is shown. A user 400 is wearing the wearable smart device 200. As the user 400 is walking down the street, another user 402 using another wearable smart device 404 may be walking towards the user 400. The other user 402 (or the other wearable smart device 404) may recognize the user 400 and wish to transfer information to the user 400 via the wearable smart devices 404 and 200. In that regard, the wearable smart device 404 may transmit a signal requesting that communications be established between it and the wearable smart device 200. The signal transmitted by the wearable smart device 404 may be transmitted via a first wireless communication port that has a lower bandwidth yet requires less power than a second wireless communication port.


The wearable smart device 200 may receive the signal via the first wireless communication port 216 that has a lower bandwidth and requires less power than the second wireless communication port 218. Upon receiving the signal, the wearable smart device 200 may power on the second wireless communication port 218 and may transmit a signal to the wearable smart device 404 via the second wireless communication port 218. The wearable smart device 200 may establish a communication channel and transmit and receive data via the second wireless communication port 218 that provides for higher bandwidth than the first wireless communication port 216. When communications have stopped, the wearable smart device 200 may power off the second wireless communication port 218 in order to preserve battery power.


Referring back now to FIG. 2, the wearable smart device 200 is also capable of providing navigation instructions to a user. Along with providing navigation instructions, the wearable smart device 200 may also provide collision avoidance instructions to the user to reduce the likelihood of collisions between the user and another device or object.


Turning to FIG. 5, a method 500 for providing navigation and/or collision avoidance instructions is shown. The method 500 may be performed by a processor of a wearable smart device such as the processor 102 of the wearable smart device 100 of FIG. 1 or the processor 202 of the wearable smart device 200 of FIG. 2. The method 500 may be used to provide navigation instructions and, in some embodiments, portions of the method 500 may be used to provide collision avoidance instructions.


In block 502, the processor may receive data corresponding to an environment of the wearable smart device, such as inertial measurement data from an IMU, location data from a GPS sensor, image data from a camera, or the like. For example, the processor may receive image data and one or more of inertial measurement data or location data. As another example, the processor may receive only one or more of inertial measurement data or location data. In some embodiments, the location data may be received from a device other than a GPS sensor, such as via Wi-Fi.


Based on the detected data and desired destination, the processor may determine navigation instructions from a current location of the wearable smart device to the desired destination. In some embodiments, the processor may begin providing navigation instructions via the output device. In some embodiments, the processor may not begin determining navigation instructions until the function of block 508 has been performed.


In block 506, the processor may receive a signal from a remote device. The signal may be received via a wireless communication port such as a DSRC port, a Wi-Fi port, a Bluetooth port, an NFC port, an infrared communications port or the like.


The processor may be capable of determining a location, heading and/or velocity of the remote device based on the received signal. In some embodiments, the signal transmitted by the remote device may provide location data corresponding to the location of the remote device. For example, the remote device may include a GPS sensor and the remote device may transmit the location data detected by the GPS sensor via its DSRC communication port.


In some embodiments, the signal may also or instead include inertial measurement data (such as orientation and movement data) that corresponds to orientation and movement of the remote device. For example, the remote device may include a GPS or IMU and the remote device may transmit the data detected by the GPS or the IMU. This data may be usable by the processor of the wearable smart device to determine an orientation and/or velocity of the remote device. For example, the processor may determine the location of the remote device relative to the wearable smart device via image data detected by the camera and may determine the heading, orientation, velocity and/or acceleration of the remote device based on the received orientation and movement data.


In some embodiments, the processor may be capable of determining the location of the remote device relative to the wearable smart device based on a signal intensity, a direction from which the signal was received or the like. For example, the remote device may transmit a signal using an NFC protocol. Based on the strength of the NFC signal and the direction from which the NFC signal was received, the processor may determine the location of the remote device relative to the wearable smart device. In some embodiments, the remote device may transmit multiple signals via the NFC protocol. The processor of the wearable smart device may determine two or more locations of the remote device based on the multiple signals. Based on an elapsed time between the signals and a change in distance between the two locations, the processor may be capable of determining the heading, velocity, acceleration or the like of the remote device.


After the location, heading and/or velocity of the remote device has been determined by the processor, the processor may adjust the navigation instructions to prevent a collision between the user and the remote device based on the determined location, heading and/or velocity of the remote device in block 510. For example, if the user is traveling in a direction towards a stationary remote device, the processor may adjust the navigation instructions to navigate the user around the remote device. As another example, if the user is stationary and the remote device is heading towards the location of the user, the processor may provide instructions to the user to move to a location away from the heading of the remote device. If the user and the remote device are both moving and the processor determines that a collision between the user and the remote device is likely based on the location, heading, velocity and/or acceleration of both, the processor may provide instructions to the user to change his heading, velocity or location to avoid the collision.


In some embodiments, the processor may begin providing navigation instructions after determining the location, heading and/or velocity of all remote devices within the detectable area of the wearable smart device. For example, upon receiving a desired destination, the processor may determine the location of all detectable remote devices and may plan the navigation instructions to avoid a collision with the detectable remote devices.


In some embodiments, the processor may provide the collision avoidance instructions without providing navigation instructions. In that regard, the wearable smart device may continuously receive signals from remote devices indicating their location, heading and velocity. The processor may continue to monitor locations, headings and velocities of the remote devices and may determine instructions to provide to the user for avoiding collisions whenever a collision appears likely.


In block 512, the processor may provide the adjusted navigation instructions, the collision avoidance instructions and/or the relative location of the remote device to the user. In some embodiments, the processor may cause this information to be output via one or more speakers of the wearable smart device. In some embodiments, the processor may provide the adjusted navigation instructions and/or collision avoidance instructions to the user via haptic feedback. For example, the processor may cause a left vibration unit to vibrate to instruct a user to turn to the left and may cause a right vibration unit to vibrate to instruct a user to turn to the right.


Referring to FIGS. 2, 5 and 6, an exemplary use of the method 500 by the wearable smart device 200 is shown. A user 600 is wearing the wearable smart device 200 and walking along a sidewalk 604. A vehicle 602 is traveling along a road 606 that intersects with the sidewalk 604. The vehicle 602 includes a DSRC port 608 that transmits information corresponding to a location of the vehicle 602.


When the wearable smart device 200 is sufficiently close to the vehicle 602 that the wearable smart device 200 can receive the signals from the DSRC port 608, the wearable smart device 200 may receive and analyze the signals. The processor 202 of the wearable smart device 200 may determine the location, heading and velocity of the vehicle 602 relative to the location of the user 600 based on the received signals.


Based on determined location, heading and velocity of the vehicle 602 as well as current location, heading and velocity of the user 600, the processor 202 may determine that a collision between the vehicle 602 and the user 600 is likely to occur. Based on this determination, the processor 202 may either adjust navigation instructions provided to the user or may provide collision avoidance instructions to the user via one or more of the output units 208A, 208B.


Upon receiving the adjusted navigation instructions or collision avoidance instructions, the user 600 may change his or her heading and/or velocity to avoid the collision. In this way, the data received by the wireless communication port of the wearable smart device 200 may be used to prevent collisions between a user and a remote device.


Exemplary embodiments of the methods/systems have been disclosed in an illustrative style. Accordingly, the terminology employed throughout should be read in a non-limiting manner. Although minor modifications to the teachings herein will occur to those well versed in the art, it shall be understood that what is intended to be circumscribed within the scope of the patent warranted hereon are all such embodiments that reasonably fall within the scope of the advancement to the art hereby contributed, and that that scope shall not be restricted, except in light of the appended claims and their equivalents.

Claims
  • 1. A wearable electronic device for communicating with a remote device, the wearable electronic device comprising: a first wireless communication port configured to receive a first signal from the remote device via a first communication protocol, wherein the first signal indicates a request by the remote device to communicate with the wearable electronic device;a second wireless communication port configured to transmit a second signal to the remote device via a second communication protocol that is different than the first communication protocol, wherein the second signal initializes communications with the remote device via the second wireless communication port; anda processor coupled to the first wireless communication port and to the second wireless communication port and configured to receive the first signal via the first wireless communication port and to transmit the second signal via the second wireless communication port in response to receiving the first signal.
  • 2. The wearable electronic device of claim 1 wherein the second wireless communication port provides for higher bandwidth communications between the wearable electronic device and the remote device than the first wireless communication port.
  • 3. The wearable electronic device of claim 1 wherein the second wireless communication port requires more power to be in an on state than the first wireless communication port.
  • 4. The wearable electronic device of claim 1 wherein the processor is further configured to switch the second wireless communication port to an on state in response to receiving the first signal.
  • 5. The wearable electronic device of claim 1 wherein the processor is further configured to determine when communications between the wearable electronic device and the remote device via the second wireless communication port have ended and to switch the second wireless communication port to an off state in response to determining that the communications have ended.
  • 6. The wearable electronic device of claim 1 wherein the first wireless communication port includes at least one of a dedicated short range communication (DSRC) port, a Bluetooth port, a near field communications (NFC) port, an infrared communication port or an ultrasound communication port and wherein the second wireless communication port includes at least one of a DSRC port, an infrared communication port, an ultrasound communication port, a Bluetooth port or a Wi-Fi port.
  • 7. The wearable electronic device of claim 1 further comprising an outer casing defining at least one cavity and wherein at least a portion of the first wireless communication port, at least a portion of the second wireless communication port, and the processor are positioned within the at least one cavity and wherein the outer casing has a neck portion configured to be positioned against a neck or back of a user and two end portions configured to extend across shoulders of the user.
  • 8. A wearable electronic device for communicating with a remote device, the wearable electronic device comprising: a first wireless communication port configured to receive a first signal from the remote device via a first communication protocol;a second wireless communication port configured to transmit a second signal to the remote device via a second communication protocol that is different than the first communication protocol, wherein the second wireless communication port provides for higher bandwidth communications between the wearable electronic device and the remote device than the first wireless communication port; anda processor coupled to the first wireless communication port and to the second wireless communication port and configured to receive the first signal via the first wireless communication port and to transmit the second signal via the second wireless communication port in response to receiving the first signal.
  • 9. The wearable electronic device of claim 8 wherein the second wireless communication port requires more power to be in an on state than the first wireless communication port.
  • 10. The wearable electronic device of claim 8 wherein the processor is further configured to switch the second wireless communication port to an on state in response to receiving the first signal.
  • 11. The wearable electronic device of claim 8 wherein the processor is further configured to determine when communications between the wearable electronic device and the remote device via the second wireless communication port have ended and to switch the second wireless communication port to an off state in response to determining that the communications have ended.
  • 12. The wearable electronic device of claim 8 wherein the first wireless communication port includes at least one of a dedicated short range communication (DSRC) port, a Bluetooth port, a near field communications (NFC) port, an infrared communication port or an ultrasound communication port and wherein the second wireless communication port includes at least one of a DSRC port, an infrared communication port, an ultrasound communication port, a Bluetooth port or a Wi-Fi port.
  • 13. The wearable electronic device of claim 8 further comprising an outer casing defining at least one cavity and wherein at least a portion of the first wireless communication port, at least a portion of the second wireless communication port, and the processor are positioned within the at least one cavity and wherein the outer casing has a neck portion configured to be positioned against a neck or back of a user and two end portions configured to extend across shoulders of the user.
  • 14. A wearable electronic device for communicating with a remote device, the wearable electronic device comprising: a first wireless communication port configured to receive a first signal from the remote device via a first communication protocol;a second wireless communication port configured to transmit a second signal to the remote device via a second communication protocol that is different than the first communication protocol, wherein the second wireless communication port requires more power to be in an on state than the first wireless communication port; anda processor coupled to the first wireless communication port and to the second wireless communication port and configured to receive the first signal via the first wireless communication port and to transmit the second signal via the second wireless communication port in response to receiving the first signal.
  • 15. The wearable electronic device of claim 14 wherein the processor is further configured to switch the second wireless communication port to an on state in response to receiving the first signal.
  • 16. The wearable electronic device of claim 14 wherein the processor is further configured to determine when communications between the wearable electronic device and the remote device via the second wireless communication port have ended and to switch the second wireless communication port to an off state in response to determining that the communications have ended.
  • 17. The wearable electronic device of claim 14 wherein the first wireless communication port includes at least one of a dedicated short range communication (DSRC) port, a Bluetooth port, a near field communications (NFC) port, an infrared communication port or an ultrasound communication port and wherein the second wireless communication port includes at least one of a DSRC port, an infrared communication port, an ultrasound communication port, a Bluetooth port or a Wi-Fi port.
  • 18. The wearable electronic device of claim 14 further comprising an outer casing defining at least one cavity and wherein at least a portion of the first wireless communication port, at least a portion of the second wireless communication port, and the processor are positioned within the at least one cavity and wherein the outer casing has a neck portion configured to be positioned against a neck or back of a user and two end portions configured to extend across shoulders of the user.
US Referenced Citations (412)
Number Name Date Kind
4520501 DuBrucq May 1985 A
4586827 Hirsch et al. May 1986 A
4786966 Hanson Nov 1988 A
5047952 Kramer Sep 1991 A
5097856 Chi-Sheng Mar 1992 A
5129716 Holakovszky et al. Jul 1992 A
5233520 Kretsch et al. Aug 1993 A
5265272 Kurcbart Nov 1993 A
5463428 Lipton et al. Oct 1995 A
5508699 Silverman Apr 1996 A
5539665 Lamming et al. Jul 1996 A
5543802 Villevielle et al. Aug 1996 A
5544050 Abe Aug 1996 A
5568127 Bang Oct 1996 A
5636038 Lynt Jun 1997 A
5659764 Sakiyama Aug 1997 A
5701356 Stanford et al. Dec 1997 A
5733127 Mecum Mar 1998 A
5807111 Schrader Sep 1998 A
5872744 Taylor Feb 1999 A
5884198 Kese Mar 1999 A
5953693 Sakiyama Sep 1999 A
5956630 Mackey Sep 1999 A
5982286 Vanmoor Nov 1999 A
6009577 Day Jan 2000 A
6055048 Langevin et al. Apr 2000 A
6067112 Wellner et al. May 2000 A
6199010 Richton Mar 2001 B1
6229901 Mickelson et al. May 2001 B1
6230135 Ramsay May 2001 B1
6230349 Silver et al. May 2001 B1
6285757 Carroll et al. Sep 2001 B1
6307526 Mann Oct 2001 B1
6323807 Golding et al. Nov 2001 B1
6349001 Spitzer Feb 2002 B1
6466232 Newell et al. Oct 2002 B1
6477239 Ohki Nov 2002 B1
6542623 Kahn Apr 2003 B1
6580999 Maruyama et al. Jun 2003 B2
6594370 Anderson Jul 2003 B1
6603863 Nagayoshi Aug 2003 B1
6619836 Silvant et al. Sep 2003 B1
6701296 Kramer Mar 2004 B1
6771224 Apostolos Aug 2004 B2
6774788 Balfe Aug 2004 B1
6825875 Strub et al. Nov 2004 B1
6826477 Ladetto et al. Nov 2004 B2
6834373 Dieberger Dec 2004 B2
6839667 Reich Jan 2005 B2
6857775 Wilson Feb 2005 B1
6920229 Boesen Jul 2005 B2
D513997 Wilson Jan 2006 S
6995723 Adams Feb 2006 B1
7027874 Sawan et al. Apr 2006 B1
D522300 Roberts Jun 2006 S
7069215 Bangalore Jun 2006 B1
7106220 Gourgey et al. Sep 2006 B2
7228275 Endo Jun 2007 B1
7299034 Kates Nov 2007 B2
7308314 Havey et al. Dec 2007 B2
7336226 Jung et al. Feb 2008 B2
7356473 Kates Apr 2008 B2
7413554 Kobayashi et al. Aug 2008 B2
7417592 Hsiao et al. Aug 2008 B1
7428429 Gantz et al. Sep 2008 B2
7463188 McBurney Dec 2008 B1
7496445 Mohsini et al. Feb 2009 B2
7501958 Saltzstein et al. Mar 2009 B2
7525568 Raghunath Apr 2009 B2
7564469 Cohen Jul 2009 B2
7565295 Hernandez-Rebollar Jul 2009 B1
7598976 Sofer et al. Oct 2009 B2
7618260 Daniel et al. Nov 2009 B2
D609818 Tsang et al. Feb 2010 S
7656290 Fein et al. Feb 2010 B2
7659915 Kurzweil et al. Feb 2010 B2
7715873 Biere May 2010 B1
7743996 Maciver Jun 2010 B2
7769412 Gailloux Aug 2010 B1
D625427 Lee Oct 2010 S
7843351 Bourne Nov 2010 B2
7843488 Stapleton Nov 2010 B2
7848512 Eldracher Dec 2010 B2
7864991 Espenlaub et al. Jan 2011 B2
7938756 Rodetsky et al. May 2011 B2
7991576 Roumeliotis Aug 2011 B2
8005263 Fujimura Aug 2011 B2
8035519 Davis Oct 2011 B2
D649655 Petersen Nov 2011 S
8123660 Kruse et al. Feb 2012 B2
D656480 McManigal et al. Mar 2012 S
8138907 Barbeau et al. Mar 2012 B2
8150107 Kurzweil et al. Apr 2012 B2
8177705 Abolfathi May 2012 B2
8239032 Dewhurst Aug 2012 B2
8253760 Sako et al. Aug 2012 B2
8300862 Newton et al. Oct 2012 B2
8325263 Kato et al. Dec 2012 B2
D674501 Petersen Jan 2013 S
8359122 Koselka et al. Jan 2013 B2
8391719 Alameh Mar 2013 B2
8395968 Vartanian et al. Mar 2013 B2
8401785 Cho et al. Mar 2013 B2
8414246 Tobey Apr 2013 B2
8418705 Ota et al. Apr 2013 B2
8428643 Lin Apr 2013 B2
8430310 Ho Apr 2013 B1
8483956 Zhang Jul 2013 B2
8494507 Tedesco et al. Jul 2013 B1
8494859 Said Jul 2013 B2
8538687 Plocher et al. Sep 2013 B2
8538688 Prehofer Sep 2013 B2
8571860 Strope Oct 2013 B2
8583282 Angle et al. Nov 2013 B2
8588464 Albertson et al. Nov 2013 B2
8588972 Fung Nov 2013 B2
8591412 Kovarik et al. Nov 2013 B2
8594935 Cioffi et al. Nov 2013 B2
8606316 Evanitsky Dec 2013 B2
8610879 Ben-Moshe et al. Dec 2013 B2
8630633 Tedesco et al. Jan 2014 B1
8676274 Li Mar 2014 B2
8676623 Gale et al. Mar 2014 B2
8694251 Janardhanan et al. Apr 2014 B2
8704902 Naick et al. Apr 2014 B2
8718672 Xie et al. May 2014 B2
8743145 Price Jun 2014 B1
8750898 Haney Jun 2014 B2
8768071 Tsuchinaga et al. Jul 2014 B2
8786680 Shiratori et al. Jul 2014 B2
8797141 Best et al. Aug 2014 B2
8797386 Chou et al. Aug 2014 B2
8803699 Foshee et al. Aug 2014 B2
8805929 Erol et al. Aug 2014 B2
8812244 Angelides Aug 2014 B2
8814019 Dyster et al. Aug 2014 B2
8825398 Alexandre et al. Sep 2014 B2
8836532 Fish, Jr. et al. Sep 2014 B2
8836580 Mendelson Sep 2014 B2
8836910 Cashin et al. Sep 2014 B2
8902303 Na'Aman et al. Dec 2014 B2
8909534 Heath Dec 2014 B1
D721673 Park et al. Jan 2015 S
8926330 Taghavi Jan 2015 B2
8930458 Lewis et al. Jan 2015 B2
8981682 Delson et al. Mar 2015 B2
8994498 Agrafioti Mar 2015 B2
D727194 Wilson Apr 2015 S
9004330 White Apr 2015 B2
9025016 Wexler et al. May 2015 B2
9042596 Connor May 2015 B2
9053094 Yassa Jun 2015 B2
9076450 Sadek Jul 2015 B1
9081079 Chao et al. Jul 2015 B2
9081385 Ferguson et al. Jul 2015 B1
D736741 Katz Aug 2015 S
9111545 Jadhav et al. Aug 2015 B2
D738238 Pede et al. Sep 2015 S
9137484 DiFrancesco et al. Sep 2015 B2
9137639 Garin et al. Sep 2015 B2
9140554 Jerauld Sep 2015 B2
9148191 Teng et al. Sep 2015 B2
9158378 Hirukawa Oct 2015 B2
D742535 Wu Nov 2015 S
D743933 Park et al. Nov 2015 S
9185489 Gerber et al. Nov 2015 B2
9190058 Klein Nov 2015 B2
9104806 Stivoric et al. Dec 2015 B2
9226097 Holman Dec 2015 B2
9230430 Civelli et al. Jan 2016 B2
9232366 Charlier Jan 2016 B1
9267801 Gupta et al. Feb 2016 B2
9269015 Boncyk et al. Feb 2016 B2
9275376 Barraclough et al. Mar 2016 B2
9304588 Aldossary Apr 2016 B2
D756958 Lee et al. May 2016 S
D756959 Lee et al. May 2016 S
9335175 Zhang et al. May 2016 B2
9341014 Oshima et al. May 2016 B2
9355547 Stevens et al. May 2016 B2
9820120 deCharms Nov 2017 B2
20010023387 Rollo Sep 2001 A1
20020067282 Moskowitz et al. Jun 2002 A1
20020071277 Starner et al. Jun 2002 A1
20020075323 O'Dell Jun 2002 A1
20020142734 Wickstead Oct 2002 A1
20020173346 Wang Nov 2002 A1
20020178344 Bourguet Nov 2002 A1
20030026461 Hunter Feb 2003 A1
20030133008 Stephenson Jul 2003 A1
20030133085 Tretiakoff Jul 2003 A1
20030179133 Pepin et al. Sep 2003 A1
20040056907 Sharma Mar 2004 A1
20040232179 Chauhan Nov 2004 A1
20040267442 Fehr et al. Dec 2004 A1
20050020845 Fink et al. Sep 2005 A1
20050221260 Kikuchi Oct 2005 A1
20050259035 Iwaki Nov 2005 A1
20050283752 Fruchter Dec 2005 A1
20060004512 Herbst et al. Jan 2006 A1
20060028550 Palmer, Jr. et al. Feb 2006 A1
20060029256 Miyoshi et al. Feb 2006 A1
20060129308 Kates Jun 2006 A1
20060171704 Bingle et al. Aug 2006 A1
20060177086 Rye Aug 2006 A1
20060184318 Yoshimine Aug 2006 A1
20060292533 Selod Dec 2006 A1
20070001904 Mendelson Jan 2007 A1
20070052672 Ritter et al. Mar 2007 A1
20070173688 Kim Jul 2007 A1
20070182812 Ritchey Aug 2007 A1
20070202865 Moride Aug 2007 A1
20070230786 Foss Oct 2007 A1
20070296572 Fein et al. Dec 2007 A1
20080024594 Ritchey Jan 2008 A1
20080068559 Howell et al. Mar 2008 A1
20080120029 Zelek et al. May 2008 A1
20080144854 Abreu Jun 2008 A1
20080145822 Bucchieri Jun 2008 A1
20080174676 Squilla et al. Jul 2008 A1
20080198222 Gowda Aug 2008 A1
20080198324 Fuziak Aug 2008 A1
20080208455 Hartman Aug 2008 A1
20080251110 Pede Oct 2008 A1
20080260210 Kobeli Oct 2008 A1
20090012788 Gilbert Jan 2009 A1
20090040215 Afzulpurkar Feb 2009 A1
20090058611 Kawamura Mar 2009 A1
20090069045 Cheng Mar 2009 A1
20090106016 Athsani Apr 2009 A1
20090118652 Carlucci May 2009 A1
20090122161 Bolkhovitinov May 2009 A1
20090122648 Mountain et al. May 2009 A1
20090157302 Tashev et al. Jun 2009 A1
20090177437 Roumeliotis Jul 2009 A1
20090189974 Deering Jul 2009 A1
20090210596 Furuya Aug 2009 A1
20100041378 Aceves et al. Feb 2010 A1
20100080418 Ito Apr 2010 A1
20100109918 Liebermann May 2010 A1
20100110368 Chaum May 2010 A1
20100179452 Srinivasan Jul 2010 A1
20100182242 Fields et al. Jul 2010 A1
20100182450 Kumar et al. Jul 2010 A1
20100198494 Chao et al. Aug 2010 A1
20100199232 Mistry et al. Aug 2010 A1
20100241350 Cioffi et al. Sep 2010 A1
20100245585 Fisher et al. Sep 2010 A1
20100267276 Wu et al. Oct 2010 A1
20100292917 Emam et al. Nov 2010 A1
20100298976 Sugihara et al. Nov 2010 A1
20100305845 Alexandre et al. Dec 2010 A1
20100308999 Chornenky Dec 2010 A1
20110066383 Jangle et al. Mar 2011 A1
20110071830 Kim Mar 2011 A1
20110092249 Evanitsky Apr 2011 A1
20110124383 Garra et al. May 2011 A1
20110125735 Petrou May 2011 A1
20110181422 Tran Jul 2011 A1
20110187640 Jacobsen et al. Aug 2011 A1
20110211760 Boncyk et al. Sep 2011 A1
20110216006 Litschel Sep 2011 A1
20110221670 King, III et al. Sep 2011 A1
20110234584 Endo Sep 2011 A1
20110246064 Nicholson Oct 2011 A1
20110260681 Guccione et al. Oct 2011 A1
20110307172 Jadhav et al. Dec 2011 A1
20120016578 Coppens Jan 2012 A1
20120053826 Slamka Mar 2012 A1
20120062357 Slamka Mar 2012 A1
20120069511 Azera Mar 2012 A1
20120075168 Osterhout et al. Mar 2012 A1
20120082962 Schmidt Apr 2012 A1
20120085377 Trout Apr 2012 A1
20120092161 West Apr 2012 A1
20120092460 Mahoney Apr 2012 A1
20120123784 Baker et al. May 2012 A1
20120136666 Corpier et al. May 2012 A1
20120143495 Dantu Jun 2012 A1
20120162423 Xiao et al. Jun 2012 A1
20120194552 Osterhout et al. Aug 2012 A1
20120206335 Osterhout et al. Aug 2012 A1
20120206607 Morioka Aug 2012 A1
20120207356 Murphy Aug 2012 A1
20120214418 Lee et al. Aug 2012 A1
20120220234 Abreu Aug 2012 A1
20120232430 Boissy et al. Sep 2012 A1
20120249797 Haddick et al. Oct 2012 A1
20120250615 Gupta Oct 2012 A1
20120252483 Farmer et al. Oct 2012 A1
20120316884 Rozaieski et al. Dec 2012 A1
20120323485 Mutoh Dec 2012 A1
20120327194 Shiratori Dec 2012 A1
20130002452 Lauren Jan 2013 A1
20130044005 Foshee et al. Feb 2013 A1
20130046541 Klein et al. Feb 2013 A1
20130066636 Singhal Mar 2013 A1
20130079061 Jadhav Mar 2013 A1
20130090133 D'Jesus Bencci Apr 2013 A1
20130115578 Shiina May 2013 A1
20130115579 Taghavi May 2013 A1
20130116559 Levin et al. May 2013 A1
20130127980 Haddick May 2013 A1
20130128051 Velipasalar et al. May 2013 A1
20130131985 Weiland et al. May 2013 A1
20130141576 Lord et al. Jun 2013 A1
20130144629 Johnston Jun 2013 A1
20130155474 Roach et al. Jun 2013 A1
20130157230 Morgan Jun 2013 A1
20130184982 DeLuca et al. Jul 2013 A1
20130201344 Sweet, III Aug 2013 A1
20130204605 Illgner-Fehns Aug 2013 A1
20130211718 Yoo et al. Aug 2013 A1
20130218456 Zelek et al. Aug 2013 A1
20130202274 Chan Sep 2013 A1
20130228615 Gates et al. Sep 2013 A1
20130229669 Smits Sep 2013 A1
20130243250 France Sep 2013 A1
20130245396 Berman et al. Sep 2013 A1
20130250078 Levy Sep 2013 A1
20130250233 Blum et al. Sep 2013 A1
20130253818 Sanders et al. Sep 2013 A1
20130265450 Barnes, Jr. Oct 2013 A1
20130271584 Wexler et al. Oct 2013 A1
20130290909 Gray Oct 2013 A1
20130307842 Grinberg et al. Nov 2013 A1
20130311179 Wagner Nov 2013 A1
20130328683 Sitbon et al. Dec 2013 A1
20130332452 Jarvis Dec 2013 A1
20140009561 Sutherland et al. Jan 2014 A1
20140031081 Vossoughi et al. Jan 2014 A1
20140031977 Goldenberg et al. Jan 2014 A1
20140032596 Fish et al. Jan 2014 A1
20140037149 Zetune Feb 2014 A1
20140055353 Takahama Feb 2014 A1
20140071234 Millett Mar 2014 A1
20140081631 Zhu Mar 2014 A1
20140085446 Hicks Mar 2014 A1
20140098018 Kim et al. Apr 2014 A1
20140100773 Cunningham et al. Apr 2014 A1
20140125700 Ramachandran et al. May 2014 A1
20140132388 Alalawi May 2014 A1
20140133290 Yokoo May 2014 A1
20140160250 Pomerantz Jun 2014 A1
20140184384 Zhu et al. Jul 2014 A1
20140184775 Drake Jul 2014 A1
20140204245 Wexler Jul 2014 A1
20140222023 Kim et al. Aug 2014 A1
20140233859 Cho Aug 2014 A1
20140236932 Ikonomov Aug 2014 A1
20140249847 Soon-Shiong Sep 2014 A1
20140251396 Subhashrao et al. Sep 2014 A1
20140253702 Wexler et al. Sep 2014 A1
20140278070 McGavran et al. Sep 2014 A1
20140281943 Prilepov Sep 2014 A1
20140287382 Villar Cloquell Sep 2014 A1
20140309806 Ricci Oct 2014 A1
20140313040 Wright, Sr. Oct 2014 A1
20140335893 Ronen Nov 2014 A1
20140343846 Goldman et al. Nov 2014 A1
20140345956 Kojina Nov 2014 A1
20140347265 Aimone Nov 2014 A1
20140368412 Jacobsen et al. Dec 2014 A1
20140369541 Miskin et al. Dec 2014 A1
20140379251 Tolstedt Dec 2014 A1
20140379336 Bhatnager Dec 2014 A1
20150002808 Rizzo, III et al. Jan 2015 A1
20150016035 Tussy Jan 2015 A1
20150058237 Bailey Feb 2015 A1
20150063661 Lee Mar 2015 A1
20150081884 Maguire Mar 2015 A1
20150099946 Sahin Apr 2015 A1
20150109107 Gomez et al. Apr 2015 A1
20150120186 Heikes Apr 2015 A1
20150135310 Lee May 2015 A1
20150141085 Nuovo et al. May 2015 A1
20150142891 Haque et al. May 2015 A1
20150154643 Artman et al. Jun 2015 A1
20150125831 Chandrashekhar Nair et al. Jul 2015 A1
20150196101 Dayal et al. Jul 2015 A1
20150198454 Moore et al. Jul 2015 A1
20150198455 Chen et al. Jul 2015 A1
20150199566 Moore et al. Jul 2015 A1
20150201181 Moore et al. Jul 2015 A1
20150211858 Jerauld Jul 2015 A1
20150219757 Boelter et al. Aug 2015 A1
20150223355 Fleck Aug 2015 A1
20150256977 Huang Sep 2015 A1
20150257555 Wong Sep 2015 A1
20150260474 Rublowsky et al. Sep 2015 A1
20150262509 Labbe Sep 2015 A1
20150279172 Hyde Oct 2015 A1
20150324646 Kimia Nov 2015 A1
20150330787 Cioffi et al. Nov 2015 A1
20150336276 Song et al. Nov 2015 A1
20150338917 Steiner et al. Nov 2015 A1
20150341591 Kelder et al. Nov 2015 A1
20150346496 Haddick et al. Dec 2015 A1
20150356345 Velozo Dec 2015 A1
20150356837 Pajestka et al. Dec 2015 A1
20150364943 Vick et al. Dec 2015 A1
20150367176 Bejestan Dec 2015 A1
20150375395 Kwon et al. Dec 2015 A1
20160007158 Venkatraman Jan 2016 A1
20160028917 Wexler Jan 2016 A1
20160042228 Opalka Feb 2016 A1
20160078289 Michel Mar 2016 A1
20160098138 Park Apr 2016 A1
20160156850 Werblin et al. Jun 2016 A1
20160173982 Anderson Jun 2016 A1
20160198319 Huang Jul 2016 A1
20160350514 Rajendran Dec 2016 A1
Foreign Referenced Citations (62)
Number Date Country
201260746 Jun 2009 CN
101527093 Sep 2009 CN
201440733 Apr 2010 CN
101803988 Aug 2010 CN
101647745 Jan 2011 CN
102316193 Jan 2012 CN
102631280 Aug 2012 CN
202547659 Nov 2012 CN
202722736 Feb 2013 CN
102323819 Jun 2013 CN
103445920 Dec 2013 CN
102011080056 Jan 2013 DE
102012000587 Jul 2013 DE
102012202614 Aug 2013 DE
1174049 Sep 2004 EP
1721237 Nov 2006 EP
2368455 Sep 2011 EP
2371339 Oct 2011 EP
2127033 Aug 2012 EP
2581856 Apr 2013 EP
2751775 Jul 2016 EP
2885251 Nov 2006 FR
2401752 Nov 2004 GB
1069539 Mar 1998 JP
2001304908 Oct 2001 JP
2010012529 Jan 2010 JP
2010182193 Aug 2010 JP
4727352 Jul 2011 JP
2013169611 Sep 2013 JP
100405636 Nov 2003 KR
20080080688 Sep 2008 KR
20120020212 Mar 2012 KR
1250929 Apr 2013 KR
WO 1995004440 Feb 1995 WO
WO 9949656 Sep 1999 WO
WO 0010073 Feb 2000 WO
WO 0038393 Jun 2000 WO
WO 179956 Oct 2001 WO
WO 2004076974 Sep 2004 WO
WO 2006028354 Mar 2006 WO
WO 2006045819 May 2006 WO
WO 2007031782 Mar 2007 WO
WO 2008015375 Feb 2008 WO
WO 2008035993 Mar 2008 WO
WO 2008008791 Apr 2008 WO
WO 2008096134 Aug 2008 WO
WO 2008127316 Oct 2008 WO
WO 2010062481 Jun 2010 WO
WO 2010109313 Sep 2010 WO
WO 2012040703 Mar 2012 WO
WO 2012163675 Dec 2012 WO
WO 2013045557 Apr 2013 WO
WO 2013054257 Apr 2013 WO
WO 2013067539 May 2013 WO
WO 2013147704 Oct 2013 WO
WO 2014104531 Jul 2014 WO
WO 2014138123 Sep 2014 WO
WO 2014172378 Oct 2014 WO
WO 2015065418 May 2015 WO
WO 2015092533 Jun 2015 WO
WO 2015108882 Jul 2015 WO
WO 2015127062 Aug 2015 WO
Non-Patent Literature Citations (94)
Entry
AlZuhair et al.; “NFC Based Applications for Visually Impaired People—A Review”; IEEE International Conference on Multimedia and Expo Workshops (ICMEW), Jul. 14, 2014; 7 pages.
“Light Detector” EveryWare Technologies; 2 pages; Jun. 18, 2016.
Aggarwal et al.; “All-in-One Companion for Visually Impaired;” International Journal of Computer Applications; vol. 79, No. 14; pp. 37-40; Oct. 2013.
AppleVis; An Introduction to Braille Screen Input on iOS 8; http://www.applevis.com/guides/braille-ios/introduction-braille-screen-input-ios-8, Nov. 16, 2014; 7 pages.
Arati et al. “Object Recognition in Mobile Phone Application for Visually Impaired Users;” IOSR Journal of Computer Engineering (IOSR-JCE); vol. 17, No. 1; pp. 30-33; Jan. 2015.
Bharathi et al.; “Effective Navigation for Visually Impaired by Wearable Obstacle Avoidance System;” 2012 International Conference on Computing, Electronics and Electrical Technologies (ICCEET); pp. 956-958; 2012.
Bhatlawande et al.; “Way-finding Electronic Bracelet for Visually Impaired People”; IEEE Point-of-Care Healthcare Technologies (PHT), Jan. 16-18, 2013; 4 pages.
Bigham et al.; “VizWiz: Nearly Real-Time Answers to Visual Questions” Proceedings of the 23nd annual ACM symposium on User interface software and technology; 2010; 2 pages.
Blaze Engineering; “Visually Impaired Resource Guide: Assistive Technology for Students who use Braille”; Braille 'n Speak Manual; http://www.blaize.com; Nov. 17, 2014; 5 pages.
Blenkhorn et al.; “An Ultrasonic Mobility Device with Minimal Audio Feedback”; Center on Disabilities Technology and Persons with Disabilities Conference; Nov. 22, 1997; 5 pages.
Borenstein et al.; “The GuideCane—A Computerized Travel Aid for the Active Guidance of Blind Pedestrians”; IEEE International Conference on Robotics and Automation; Apr. 21-27, 1997; 6 pages.
Bujacz et al.; “Remote Guidance for the Blind—A Proposed Teleassistance System and Navigation Trials”; Conference on Human System Interactions; May 25-27, 2008; 6 pages.
Burbey et al.; “Human Information Processing with the Personal Memex”; ISE 5604 Fall 2005; Dec. 6, 2005; 88 pages.
Campos et al.; “Design and Evaluation of a Spoken-Feedback Keyboard”; Department of Information Systems and Computer Science, INESC-ID/IST/Universidade Tecnica de Lisboa, Jul. 2004, 6 pages.
Caperna et al.; “A Navigation and Object Location Device for the Blind”; Tech. rep. University of Maryland College Park; May 2009; 129 pages.
Cardonha et al.; “A Crowdsourcing Platform for the Construction of Accessibility Maps”; W4A'13 Proceedings of the 10th International Cross-Disciplinary Conference on Web Accessibility; Article No. 26; 2013; 5 pages.
Chaudary et al.; “Alternative Navigation Assistance Aids for Visually Impaired Blind Persons”; Proceedings of ICEAPVI; Feb. 12-14, 2015; 5 pages.
Coughlan et al.; “Crosswatch: A System for Providing Guidance to Visually Impaired Travelers at Traffic Intersections”; Journal of Assistive Technologies 7.2; 2013; 17 pages.
D'Andrea, Frances Mary; “More than a Perkins Brailler: A Review of the Mountbatten Brailler, Part 1”; AFB AccessWorld Magazine; vol. 6, No. 1, Jan. 2005; 9 pages.
Dias et al.; “Enhancing an Automated Braille Writing Tutor”; IEEE/RSJ International Conference on Intelligent Robots and Systems; Oct. 11-15, 2009; 7 pages.
Dowling et al.; “Intelligent Image Processing Constraints for Blind Mobility Facilitated Through Artificial Vision”; 8th Australian and NewZealand Intelligent Information Systems Conference (ANZIIS); Dec. 10-12, 2003; 7 pages.
Ebay; Matin (Made in Korea) Neoprene Canon DSLR Camera Curved Neck Strap #6782; http://www.ebay.com/itm/MATIN-Made-in-Korea-Neoprene-Canon-DSLR-Camera-Curved-Neck-Strap-6782-/281608526018?hash=item41912d18c2:g:˜pMAAOSwe-FU6zDa ; 4 pages.
Eccles, Lisa; “Smart Walker Detects Obstacles”; Electronic Design; http://electronicdesign.com/electromechanical/smart-walker-detects-obstacles; Aug. 20, 2001; 2 pages.
Frizera et al.; “The Smart Walkers as Geriatric Assistive Device. The SIMBIOSIS Purpose”; Gerontechnology, vol. 7, No. 2; Jan. 30, 2008; 6 pages.
Garaj et al.; “A System for Remote Sighted Guidance of Visually Impaired Pedestrians”; The British Journal of Visual Impairment; vol. 21, No. 2, 2003; 9 pages.
Ghiani, et al.; “Vibrotactile Feedback to Aid Blind Users of Mobile Guides”; Journal of Visual Languages and Computing 20; 2009; 13 pages.
Glover et al.; “A Robotically-Augmented Walker for Older Adults”; Carnegie Mellon University, School of Computer Science; Aug. 1, 2003; 13 pages.
Graf, Christian; “Verbally Annotated Tactile Maps—Challenges and Approaches”; Spatial Cognition VII, vol. 6222; Aug. 15-19, 2010; 16 pages.
Graft, Birgit; “An Adaptive Guidance System for Robotic Walking Aids”; Journal of Computing and Information Technology—CIT 17; 2009; 12 pages.
Greenberg et al.; “Finding Your Way: A Curriculum for Teaching and Using the Braillenote with Sendero GPS 2011”; California School for the Blind; 2011; 190 pages.
Guerrero et al.; “An Indoor Navigation System for the Visually Impaired”; Sensors vol. 12, Issue 6; Jun. 13, 2012; 23 pages.
Guy et al; “CrossingGuard: Exploring Information Content in Navigation Aids for Visually Impaired Pedestrians” Proceedings of the SIGCHI Conference on Human Factors in Computing Systems; May 5-10, 2012; 10 pages.
Hamid, Nazatul Naquiah Abd; “Facilitating Route Learning Using Interactive Audio-Tactile Maps for Blind and Visually Impaired People”; CHI 2013 Extended Abstracts; Apr. 27, 2013; 6 pages.
Helal et al.; “Drishti: An Integrated Navigation System for Visually Impaired and Disabled”; Fifth International Symposium on Wearable Computers; Oct. 8-9, 2001; 8 pages.
Hesch et al.; “Design and Analysis of a Portable Indoor Localization Aid for the Visually Impaired”; International Journal of Robotics Research; vol. 29; Issue 11; Sep. 2010; 15 pgs.
Heyes, Tony; “The Sonic Pathfinder an Electronic Travel Aid for the Vision Impaired”; http://members.optuszoo.com.au/aheyew40/pa/pf_blerf.html; Dec. 11, 2014; 7 pages.
Joseph et al.; “Visual Semantic Parameterization—To Enhance Blind User Perception for Indoor Navigation”; Multimedia and Expo Workshops (ICMEW), 2013 IEEE International Conference; Jul. 15, 2013; 7 pages.
Kalra et al.; “A Braille Writing Tutor to Combat Illiteracy in Developing Communities”; Carnegie Mellon University Research Showcase, Robotics Institute; 2007; 10 pages.
Kammoun et al.; “Towards a Geographic Information System Facilitating Navigation of Visually Impaired Users”; Springer Berlin Heidelberg; 2012; 8 pages.
Katz et al; “NAVIG: Augmented Reality Guidance System for the Visually Impaired”; Virtual Reality (2012) vol. 16; 2012; 17 pages.
Kayama et al.; “Outdoor Environment Recognition and Semi-Autonomous Mobile Vehicle for Supporting Mobility of the Elderly and Disabled People”; National Institute of Information and Communications Technology, vol. 54, No. 3; Aug. 2007; 11 pages.
Kirinic et al.; “Computers in Education of Children with Intellectual and Related Developmental Disorders”; International Journal of Emerging Technologies in Learning, vol. 5, 2010, 5 pages.
Krishna et al.; “A Systematic Requirements Analysis and Development of an Assistive Device to Enhance the Social Interaction of People Who are Blind or Visually Impaired”; Workshop on Computer Vision Applications for the Visually Impaired; Marseille, France; 2008; 12 pages.
Kumar et al.; “An Electronic Travel Aid for Navigation of Visually Impaired Persons”; Communications Systems and Networks (COMSNETS), 2011 Third International Conference; Jan. 2011; 5 pages.
Lee et al.; “Adaptive Power Control of Obstacle Avoidance System Using Via Motion Context for Visually Impaired Person.” International Conference on Cloud Computing and Social Networking (ICCCSN), Apr. 26-27, 2012 4 pages.
Lee et al.; “A Walking Guidance System for the Visually Impaired”; International Journal of Pattern Recognition and Artificial Intelligence; vol. 22; No. 6; 2008; 16 pages.
Mann et al.; “Blind Navigation with a Wearable Range Camera and Vibrotactile Helmet”; 19th ACM International Conference on Multimedia; Nov. 28, 2011; 4 pages.
Mau et al.; “BlindAid: An Electronic Travel Aid for the Blind;” The Robotics Institute Carnegie Mellon University; 27 pages; May 2008.
Meijer, Dr. Peter B.L.; “Mobile OCR, Face and Object Recognition for the Blind”; The vOICe, www.seeingwithsound.corn/ocr.htm; Apr. 18, 2014; 7 pages.
Merino-Garcia, et al.; “A Head-Mounted Device for Recognizing Text in Natural Sciences”; CBDAR'11 Proceedings of the 4th International Conference on Camera-Based Document Analysis and Recognition; Sep. 22, 2011; 7 pages.
Merri et al.; “The Instruments for a Blind Teacher of English: The challenge of the board”; European Journal of Psychology of Education, vol. 20, No. 4 (Dec. 2005), 15 pages.
Newegg; Motorola Behind the Neck Stereo Bluetooth Headphone Black/Red Bulk (S9)—OEM; http://www.newegg.com/Product/Product.aspx?Item=N82E16875982212&Tpk=n82e16875982212 3 pages.
Newegg; Motorola S10-HD Bluetooth Stereo Headphone w/ Comfortable Sweat Proof Design; http://www.newegg.com/Product/Product.aspx?Item=9SIA0NW2G39901&Tpk=9sia0nw2g39901; 4 pages.
Nordin et al.; “Indoor Navigation and Localization for Visually Impaired People Using Weighted Topological Map”; Journal of Computer Science vol. 5, Issue 11; 2009; 7 pages.
OMRON; Optical Character Recognition Sensor User's Manual; 2012; 450 pages.
OrCam; www.orcam.com; Jul. 22, 2014; 3 pages.
Pagliarini et al.; “Robotic Art for Wearable”; Proceedings of EUROSIAM: European Conference for the Applied Mathematics and Informatics 2010; 10 pages.
Paladugu et al.; “GoingEasy® with Crowdsourcing in the Web 2.0 World for Visually Impaired Users: Design and User Study”; Arizona State University; 8 pages.
Park, Sungwoo; “Voice Stick”; www.yankodesign.com/2008/08/21/voice-stick; Aug. 21, 2008; 4 pages.
Parkes, Don; “Audio Tactile Systems for Designing and Learning Complex Environments as a Vision Impaired Person: Static and Dynamic Spatial Information Access”; EdTech-94 Proceedings; 1994; 8 pages.
Pawar et al.; “Multitasking Stick for Indicating Safe Path to Visually Disable People”; IOSR Journal of Electronics and Communication Engineering (IOSR-JECE), vol. 10, Issue 3, Ver. II; May-Jun. 2015; 5 pages.
Pawar et al.; “Review Paper on Multitasking Stick for Guiding Safe Path for Visually Disable People;” IJPRET; vol. 3, No. 9; pp. 929-936; 2015.
Ram et al.; “The People Sensor: A Mobility Aid for the Visually Impaired;” 2012 16th International Symposium on Wearable Computers; pp. 166-167; 2012.
Ramya, et al.; “Voice Assisted Embedded Navigation System for the Visually Impaired”; International Journal of Computer Applications; vol. 64, No. 13, Feb. 2013; 7 pages.
Ran et al.; “Drishti: An Integrated Indoor/Outdoor Blind Navigation System and Service”; Proceeding PERCOM '04 Proceedings of the Second IEEE International Conference on Pervasive Computing and Communications (PerCom'04); 2004; 9 pages.
Rentschler et al.; “Intelligent Walkers for the Elderly: Performance and Safety Testing of VA-PAMAID Robotic Walker”; Department of Veterans Affairs Journal of Rehabilitation Research and Development; vol. 40, No. 5; Sep./Oct. 2013; 9pages.
Rodríguez et al.; “Assisting the Visually Impaired: Obstacle Detection and Warning System by Acoustic Feedback”; Sensors 2012; vol. 12; 21 pages.
Rodriguez et al; “CrowdSight: Rapidly Prototyping Intelligent Visual Processing Apps”; AAAI Human Computation Workshop (HCOMP); 2011; 6 pages.
Rodriquez-Losada et al.; “Guido, The Robotic Smart Walker for the Frail Visually Impaired”; IEEE International Conference on Robotics and Automation (ICRA); Apr. 18-22, 2005; 15 pages.
Science Daily; “Intelligent Walker Designed to Assist the Elderly and People Undergoing Medical Rehabilitation”; http://www.sciencedaily.com/releases/2008/11/081107072015.htm; Jul. 22, 2014; 4 pages.
Shoval et al.; “Navbelt and the Guidecane—Robotics-Based Obstacle-Avoidance Systems for the Blind and Visually Impaired”; IEEE Robotics & Automation Magazine, vol. 10, Issue 1; Mar. 2003; 12 pages.
Shoval et al.; “The Navbelt—A Computerized Travel Aid for the Blind”; RESNA Conference, Jun. 12-17, 1993; 6 pages.
Singhal; “The Development of an Intelligent Aid for Blind and Old People;” Emerging Trends and Applications in Computer Science (ICETACS), 2013 1st International Conference; pp. 182-185; Sep. 13, 2013.
Sudol et al.; “LookTel—A Comprehensive Platform for Computer-Aided Visual Assistance”; Computer Vision and Pattern Recognition Workshops (CVPRW), 2010 IEEE Computer Society Conference; Jun. 13-18, 2010; 8 pages.
The Nex Band; http://www.mightycast.com/#faq; May 19, 2015; 4 pages.
Treuillet; “Outdoor/Indoor Vision-Based Localization for Blind Pedestrian Navigation Assistance”; WSPC/Instruction File; May 23, 2010; 16 pages.
Trinh et al.; “Phoneme-based Predictive Text Entry Interface”; Proceedings of the 16th International ACM SIGACCESS Conference on Computers & Accessibility; Oct. 2014; 2 pgs.
Wang, et al.; “Camera-Based Signage Detection and Recognition for Blind Persons”; 13th International Conference (ICCHP) Part 2 Proceedings; Jul. 11-13, 2012; 9 pages.
Ward et al.; “Visual Experiences in the Blind Induced by an Auditory Sensory Substitution Device”; Journal of Consciousness and Cognition; Oct. 2009; 30 pages.
Wilson, Jeff, et al. “Swan: System for Wearable Audio Navigation”; 11th IEEE International Symposium on Wearable Computers; Oct. 11-13, 2007; 8 pages.
Yabu et al.; “Development of a Wearable Haptic Tactile Interface as an Aid for the Hearing and/or Visually Impaired;” NTUT Education of Disabilities; vol. 13; pp. 5-12; 2015.
Yang, et al.; “Towards Automatic Sign Translation”; The Interactive Systems Lab, Carnegie Mellon University; 2001; 5 pages.
Yi, Chucai; “Assistive Text Reading from Complex Background for Blind Persons”; CBDAR'11 Proceedings of the 4th International Conference on Camera-Based Document Analysis and Recognition; Sep. 22, 2011; 7 pages.
Zeng et al.; “Audio-Haptic Browser for a Geographical Information System”; ICCHP 2010, Part II, LNCS 6180; Jul. 14-16, 2010; 8 pages.
Zhang et al.; “A Multiple Sensor-Based Shoe-Mounted User Interface Designed for Navigation Systems for the Visually Impaired”; 5th Annual ICST Wireless Internet Conference (WICON); Mar. 1-3, 2010; 9 pages.
Shidujaman et al.; “Design and navigation Prospective for Wireless Power Transmission Robot;” IEEE; Jun. 2015.
Wu et al. “Fusing Multi-Modal Features for Gesture Recognition”, Proceedings of the 15th ACM on International Conference on Multimodal Interaction, Dec. 9, 2013, ACM, pp. 453-459.
Pitsikalis et al. “Multimodal Gesture Recognition via Multiple Hypotheses Rescoring”, Journal of Machine Learning Research, Feb. 2015, pp. 255-284.
Shen et al. “Walkie-Markie: Indoor Pathway Mapping Made Easy” 10th USENIX Symposium on Networked Systems Design and Implementation (NSDI'13); pp. 85-98, 2013.
Tu et al. “Crowdsourced Routing II D2.6” 34 pages; 2012.
De Choudhury et al. “Automatic Construction of Travel Itineraries Using Social Breadcrumbs” pp. 35-44; Jun. 2010.
Zhang, Shanjun; Yoshino, Kazuyoshi; A Braille Recognition System by the Mobile Phone with Embedded Camera; 2007; IEEE.
Diallo, Amadou; Sep. 18, 2014; Apple iOS8: Top New Features, Forbes Magazine.
N. Kalar, T. Lawers, D. Dewey, T. Stepleton, M.B. Dias; Iterative Design of a Braille Writing Tutor to Combat Illiteracy; Aug. 30, 2007; IEEE.
Related Publications (1)
Number Date Country
20170343354 A1 Nov 2017 US