Patent Grant
12217240
This disclosure relates generally to bar code technology and contactless transaction systems and methods.
Modern mobile devices (e.g., smart phones, tablet computers, wearable computers) include an embedded camera that allows a user to capture digital images. These devices include bar code readers and applications for electronic payment using Near Field Communications (NFC) technology. Such applications require the user to manually invoke a payment application to display a bar code (e.g., a bar code, quick response (QR) code) on a hardware display of the device (e.g., a smartphone liquid crystal display (LCD)), and then place the display with the bar code in proximity to the bar code reader at the point of sale (POS) to initiate and complete a payment transaction.
Systems, methods, devices and non-transitory, computer-readable storage mediums are disclosed for bar code detection and authentication for contactless transactions using a wearable multimedia device.
In an embodiment, a wearable multimedia device, comprises: a housing configured to attach to clothing of a user; a wide field-of-view camera embedded in the housing; one or more processors; memory storing instructions that when executed by the one or more processors, causes the one or more processors to perform operations comprising: capturing, using the camera, an image of a scene that includes a bar code displayed by a terminal device; determining an intent of the user to read the bar code; in accordance with the user's intent to read the barcode: cropping the barcode from the image of the scene; establishing, using the bar code, a communication channel with the terminal device; receiving, using the communication channel, transaction data from the terminal device; and responsive to the transaction data, sending, using the communication channel, authentication credentials to the terminal device.
Particular embodiments disclosed herein provide one or more of the following advantages. A wearable multimedia device that includes an embedded camera with a wide field-of-view (FOV) and no physical hardware display, can quickly capture an image of a bar code (e.g., bar code, QR code) from a contactless display and authenticate the wearable multimedia device with another device or system for payment or access transactions, or any other contactless transaction. Moreover, the user is not required to manually invoke a payment application to display a bar code on a hardware display of the device or place the display with the bar code in proximity to the bar code reader at the POS to initiate and complete a payment transaction.
The details of the disclosed embodiments are set forth in the accompanying drawings and the description below. Other features, objects and advantages are apparent from the description, drawings and claims.
The same reference symbol used in various drawings indicates like elements.
Example Wearable Multimedia Device
The features and processes described herein can be implemented on a wearable multimedia device. In an embodiment, the wearable multimedia device is a lightweight, small form factor, battery-powered device that can be attached to a user's clothing or an object using a tension clasp, interlocking pin back, magnet or any other attachment mechanism. The wearable multimedia device includes a digital image capture device (e.g., 120° FOV with optical image stabilizer (OIS)) that allows a user to spontaneously capture multimedia data (e.g., video, audio, depth data) of life events and document transactions with minimal user interaction or device set-up.
The multimedia data captured by the wireless multimedia device is processed locally or uploaded to a cloud computing platform with an application ecosystem that allows the context data to be processed, edited and formatted by one or more applications (e.g., Artificial Intelligence (AI) applications) into any desired presentation format (e.g., single image, image stream, video clip, audio clip, multimedia presentation, image gallery) that can be downloaded and replayed on the wearable multimedia device and/or any other playback device.
In an embodiment, the user can start and stop a context data capture session on the wearable multimedia device with a simple touch gesture (e.g., a tap or swipe), by speaking a command or any other input mechanism. All or portions of the wearable multimedia device can automatically power down when it detects that it is not being worn by the user using one or more sensors (e.g., proximity sensor, optical sensor, accelerometers, gyroscopes). In an embodiment, the device can include photovoltaic surface technology to sustain battery life and inductive charging circuitry (e.g., Qi) to allow for inductive charging on charge mats and wireless over-the-air (OTA) charging.
In an embodiment, the wearable multimedia device can also include one or more environmental sensors, including but not limited to: an ambient light sensor, magnetometer, pressure sensor, voice activity detector, etc.
In an embodiment, the wearable multimedia device can include one or more biometric sensors, such as a heart rate sensor, fingerprint scanner, etc. Biometric sensor data can be included in the context data to document a transaction or to indicate the emotional state or health of the user during the moment (e.g., elevated heart rate could indicate excitement or fear).
In an embodiment, the wearable multimedia device includes a headphone jack connecting a headset or earbuds, and one or more microphones for receiving voice command and capturing ambient audio. In an alternative embodiment, the wearable multimedia device includes short range communication technology, including but not limited to Bluetooth, IEEE 802.15.4 (ZigBee™) and near field communications (NFC). The short range communication technology can be used to wirelessly connect to a wireless headset or earbuds in addition to, or in place of the headphone jack, and/or can wirelessly connect to any other external device (e.g., a computer, printer, projector, television, contactless payment/access terminal, other wearable devices).
In an embodiment, the wearable multimedia device includes a wireless transceiver and communication protocol stacks for a variety of communication technologies, including WiFi, 3G, 4G and 5G communication technologies. In an embodiment, the headset or earbuds also include sensors (e.g., biometric sensors, inertial sensors) that provide information about the direction the user is facing, to provide commands with head gestures, etc.
In an embodiment, the wearable multimedia device includes a projector (e.g., a laser projector, LCoS, DLP, LCD), or can be wired or wirelessly coupled to an external projector, that allows the user to replay a moment on a surface such as a wall, table top or the palm of the user's hand.
In an embodiment, the wearable multimedia device includes a touch surface responsive to touch gestures (e.g., a tap, multi-tap or swipe gesture). The wearable multimedia device may include a small display for presenting information and one or more light indicators to indicate on/off status, power conditions or any other desired status.
In an embodiment, the wearable multimedia device does not include a hardware display and utilizes the camera and a depth sensor for gesture recognition and control, where the camera can detect and recognize hand and finger poses (e.g., finger pointing direction in 3D space). The camera image is processed using computer vision and/or machine learning models to estimate or predict/classify/annotate 2D bounding boxes of detected objects in the image.
In an embodiment, the image is sent to a network-based server computer that has one or more machine learning models trained to predict labels for 2D bounding boxes for the objects and confidence scores. An example of a machine learning model that performs instance segmentation is the Mask Regional Convolutional Neural Network (R-CNN). The framework of the Mask R-CNN is based on two stages: first, it scans the image to generate proposals; which are areas with a high likelihood to contain an object. Second, it classifies these proposals and creates bounding boxes and masks. Other instance image segmentation algorithms can also be used.
To protect user and third party privacy, in an embodiment semantic segmentation is first performed on the device to predict object masks but not label the objects. Then only the object data (pixel data within mask) is sent to the server for instance segmentation rather than the entire image frame. In an embodiment, the outbound unlabeled objects and the inbound labeled objects are encrypted before leaving the device or server.
In an embodiment, known 3D object detection deep learning networks, such as PointRNN or VoxelNet can be used to detect and label 3D objects in a point cloud either on the device or on a network-based server computer.
In an embodiment, the wearable multimedia device performs sensor fusion of 3D depth data an 2D image data, where the 3D depth data (e.g., 2D or 3D bounding box coordinates and dimensions) are projected into the 2D image (using extrinsic and intrinsic calibration matrices), so that user gestures can be associated with labeled objects in the 2D image.
System Overview
In an example use case, when user 100 approaches payment terminal 103, embedded camera 108 captures a wide FOV image that includes bar code 105. In the example shown, bar code 105 can be a one-dimensional or two-dimensional bar code, such as Code 39, Code 128, interleaved 2 of 5, QR, UPC, EAN, PDF417, Data Matrix, and any other barcode type. Hereinafter, the 1D and 2D bar codes described above are collectively referred to as “bar codes.”
Inference engine 110 running on device 102 (see
During the authentication process, wearable multimedia device 102 receives transaction details from contactless payment terminal 103 and responds by sending authentication credentials. Contactless payment terminal 103 uses the authentication credentials to authenticate the wearable multimedia device 102 using, for example, a third party network authentication server. In an embodiment, the publicly known NFC protocol (e.g., ISO/IEC 18092) can be used for authentication and implementing the steps of the payment transaction in a secure manner. Other communication protocols can also be used (e.g., WiFi and Bluetooth protocols).
In an embodiment, inference engine 110 uses a variety of sensor data to infer the intent of user 100 to perform a payment transaction, including but not limited to: images from the embedded camera 108, GNSS position coordinates of wearable multimedia device 102 (e.g., provided by a GNSS receiver), motion data from inertial sensors (e.g., accelerometer, gyro, magnetometer, altimeter) and depth data from a depth sensor (e.g., TOF sensor). For example, camera images and/or depth data can be used to determine a user's hand/finger gestures, such as pointing to a contactless transaction terminal 103.
In an embodiment, the user speech captured by one or more microphones of wearable multimedia device 102 is parsed and converted to text which is used to infer user intent. For example, the user could say, “I want to buy a pass.” Inference engine 110 interprets the phrase with other context data, such as a pointing gesture, to infer the user's intent to engage in a payment transaction with contactless payment terminal 103. In an embodiment, the authentication process uses a variety of sensor data to perform authentication. For example, a fingerprint scanner or camera (e.g., Face ID) of wearable multimedia device 102 can be used as a primary or secondary factor in a two-factor authentication process.
Although the example use case described above was for a payment transaction, the disclosed embodiments can be used in any application where wireless short-range communication and authentication is desired, including any application where NFC, Bluetooth or WiFi is used. Some example applications include but are not limited to: contactless token applications where information is obtained from tags that can be attached to an object, such as movie posters, grocery store specials, etc., ticketing/micropayment applications to validate a purchased ticket or make payments in retail stores, pairing the wearable multimedia device with other devices to facilitate further communication using a higher bandwidth/longer range communication technology, such as WiFi, Bluetooth, etc., secure authentication where the wearable multimedia device establishes a secure communication channel with another device to grant access to a user in a secure access control system or when logging onto a computer terminal, and to control of other devices, such as control of media playback devices (e.g., a television, computer), as described below in reference to
An advantage of the bar code detection and authentication system over conventional bar code scanning technology, is that the transaction terminal displays the bar code, and the wearable multimedia device operates as a bar code reader. Sensors and location technology on the wearable multimedia device are used to infer user intent. If the inferred user intent is related to a particular transaction terminal, the bar code displayed by the transaction terminal is automatically cropped from the image and decoded to obtain the bar code data. The wearable multimedia device then uses the barcode data to automatically authenticate the wearable multimedia device and perform a transaction with the transaction terminal. The technology is not only easier to use but will facilitate faster transactions and access to structures, making the technology equally advantageous for businesses and government entities.
Another advantage of the bar code detection and authentication system over conventional bar code scanning technology, is that detection and authentication occurs over longer distances (e.g., 6 feet) versus other contactless systems like NFC that require the user to be closer to people or devices with readers. This increased detection and authentication distance is useful for social distancing that may occur during health emergencies (e.g., a pandemic), and also allows users with physical disabilities (e.g., wheelchair bound users, visually impaired) to enjoy the benefits of contactless transactions.
Communication Authentication with Media Playback Device
In this use case, the media playback device (e.g., a television, set-top box, digital media receiver) displays a bar code, which is captured in an image by embedded camera 108. After a successful authentication process using decoded bar code data (See description for
In an embodiment, the rate of swiping influences how fast the content changes: faster swiping results in faster content change (e.g., faster channel surfing) and vice-versa. Touchless swiping gestures can be made in any desired direction or pattern, including horizontally, vertically and diagonally. In addition to swiping gestures, any other touchless input can be used to control the media playback device, including but not limited to: tapping, double tapping, flicking, dragging, pinch open, pinch close, touch and hold, two-fingers scroll, pan, rotate, scroll, and any gesture that could be used on a touch screen or surface.
In an embodiment, swiping is detected by projecting each pixel in a depth image captured by a depth sensor (e.g., TOF camera) into 3D space using camera intrinsic parameters (e.g., optical center, focal length, skew coefficient) to generate a point cloud of 3D data points (e.g., x, y, z coordinates), reducing the point cloud to make the 3D data points more spatially uniform, merging all 3D data points that correspond to the same voxel into one voxel, dividing the 3D points into clusters (e.g., using a Euclidian cluster extraction algorithm), deleting clusters with too few points (e.g., less than 200 points) to remove noise and outlier points, identifying for each remaining cluster if the cluster includes a left hand or right hand by checking from which side the arm enters the frame. This is done by counting the number of points in the left and right third of the image frame, and whichever side has more points determines if the hand cluster is a left or right hand.
Next, arm points are removed from the hand cluster to form a new hand point cloud. In an embodiment, this is accomplished by starting from the furthest 3D data point from the camera, and adding up the visible surface area until a specified surface area dimension is reached (e.g., 140 cm2). A dominant axis of the hand point cloud is then determined that represents the hand direction. In an embodiment, the dominant axis of the hand point cloud is determined by computing a least squares fit of a line to the 3D data points in the hand point cloud.
After the hand and hand direction are determined, the system monitors for a swipe gesture by measuring the acceleration of the hand and comparing the acceleration to a threshold value that is indicative of a swipe gesture. To distinguish between a double swipe in a single direction from an alternating left/right or right/left swipe, a dwell time between hand movements is measured. Based on the dwell time, a double swipe or a single swipe in the opposite direction is determined.
In an embodiment, the display will present visual feedback to the user regarding the progress of the swiping action and other visual aids to teach the user how to swipe for best results. In other embodiments, audio or force feedback is provided. For example, a haptic engine in the wearable multimedia device can generate a vibration or vibration pattern that indicates progress in scrolling or for any other gesture. Audio can be output from a loudspeaker of the wearable multimedia device that includes a sound effect that is related to the gesture. A different sound effect can be associated with each gesture. The sound effect informs the user that the gesture they intended to trigger was in fact triggered.
Example Process
Process 200 can begin by capturing an image with a barcode displayed by a contactless transaction terminal (201). For example, an embedded camera of the wearable multimedia device can capture a wide FOV image that includes a display screen of a transaction terminal that has a barcode (e.g., QR code) displayed.
Process 200 continues by inferring user intent to engage with the contactless transaction terminal based on context data (202). For example, the camera image and depth sensor data (e.g., captured by a TOF camera) can be used to infer that the user is gesturing in the direction at the contactless transaction terminal, and intends to engage with the contactless transaction terminal. In an embodiment, user speech is also used to infer the user's intent to engage with the contactless transaction terminal.
In an embodiment, the camera image and depth data are also used to determine the type of contactless transaction terminal. For example, if the contactless transaction terminal is an automated teller machine (ATM), the inference engine 110 infers that the user wants to perform a banking transaction. In an embodiment, instance segmentation (e.g., Mask R-CNN) is used to identify the type of contactless transaction terminal from a camera image and/or depth data.
Other context data, such as the location, speed and heading of the user with respect to the contactless transaction terminal can be used to infer user intent. For example, if the user has stopped or slowed down when in front of the transaction terminal, inference engine 110 infers that the user intends to engage with the transaction terminal. If the heading of the user suggests that she is approaching the contactless transaction terminal, an inference is made that she intends to engage the contactless transaction terminal. In an embodiment, past history of transactions at the transaction terminal by the user are used to infer the intent of the user to engage the transaction terminal. For example, if the user has used the ATM machine in the past, inference engine 111 can use that information to infer that the user intends to use the ATM machine.
Process 200 continues by cropping the barcode from the image (203), decoding the barcode data from the barcode and using the barcode data to establish a wireless communication session with the contactless transaction terminal (204). For example, data encoded in the cropped bar code (e.g., a QR code) can identify a mode of communication with the terminal, such as a Uniform Resource Locator (URL) or NFC, Bluetooth or WiFi protocol.
Process 200 continues by receiving transaction details from the contactless transaction terminal (205), sending authentication credentials to the contactless transaction terminal (206) and completing the transaction and terminating the session (207). For example, standardized communication protocols (e.g., NFC, Bluetooth, WiFi protocols) can be used to establish the session, authenticate the wearable multimedia device, complete the transaction and terminate the session.
Example Mobile Device Architecture
Sensors, devices, and subsystems may be coupled to peripherals interface 306 to facilitate multiple functions. For example, laser projector 317, motion sensor(s) 310, biometric sensor(s) 312, depth sensor 314 may be coupled to peripherals interface 306 to facilitate motion, orientation, biometric and depth detection functions. In some implementations, motion sensor(s) 310 (e.g., an accelerometer, rate gyroscope) may be utilized to detect movement and orientation of the wearable multimedia device.
Other sensors may also be connected to peripherals interface 306, such as environmental sensor(s) (e.g., temperature sensor, barometer, ambient light) to facilitate environment sensing functions. For example, a biometric sensor 312 can detect fingerprints, face recognition, heart rate and other fitness parameters. In an embodiment, a haptic motor (not shown) can be coupled to the peripheral interface, which can provide vibration patterns as haptic feedback to the user.
Location processor 315 (e.g., GNSS receiver chip) may be connected to peripherals interface 306 to provide geo-referencing. Electronic magnetometer 316 (e.g., an integrated circuit chip) may also be connected to peripherals interface 306 to provide data that may be used to determine the direction of magnetic North. Thus, electronic magnetometer 316 may be used by an electronic compass application.
Camera subsystem 320 and an optical sensor 322, e.g., a charged coupled device (CCD) or a complementary metal-oxide semiconductor (CMOS) optical sensor, may be utilized to facilitate camera functions, such as recording photographs and video clips, and detecting bar codes, as described in reference to
Communication functions may be facilitated through one or more communication subsystems 324. Communication subsystem(s) 324 may include one or more wireless communication subsystems. Wireless communication subsystems 324 may include radio frequency receivers and transmitters and/or optical (e.g., infrared) receivers and transmitters. Wired communication systems may include a port device, e.g., a Universal Serial Bus (USB) port or some other wired port connection that may be used to establish a wired connection to other computing devices, such as other communication devices, network access devices, a personal computer, a printer, a display screen, or other processing devices capable of receiving or transmitting data (e.g., a projector).
The specific design and implementation of the communication subsystem 324 may depend on the communication network(s) or medium(s) over which the device is intended to operate. For example, a device may include wireless communication subsystems designed to operate over a global system for mobile communications (GSM) network, a GPRS network, an enhanced data GSM environment (EDGE) network, IEEE802.xx communication networks (e.g., WiFi, WiMax, ZigBee™), 3G, 4G, 4G LTE, code division multiple access (CDMA) networks, near field communication (NFC), Wi-Fi Direct and a Bluetooth™ network. Wireless communication subsystems 324 may include hosting protocols such that the device may be configured as a base station for other wireless devices. As another example, the communication subsystems may allow the device to synchronize with a host device using one or more protocols or communication technologies, such as, for example, TCP/IP protocol, HTTP protocol, UDP protocol, ICMP protocol, POP protocol, FTP protocol, IMAP protocol, DCOM protocol, DDE protocol, SOAP protocol, HTTP Live Streaming, MPEG Dash and any other known communication protocol or technology.
Audio subsystem 326 may be coupled to a loudspeaker 328 and one or more microphones 330 to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, telephony functions and beamforming.
I/O subsystem 340 may include touch controller 342 and/or another input controller(s) 344. Touch controller 342 may be coupled to a touch surface 346. Touch surface 346 and touch controller 342 may, for example, detect contact and movement or break thereof using any of a number of touch sensitivity technologies, including but not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with touch surface 346. In one implementation, touch surface 346 may display virtual or soft buttons, which may be used as an input/output device by the user.
Other input controller(s) 344 may be coupled to other input/control devices 348, such as one or more buttons, rocker switches, thumb-wheel, infrared port, USB port, and/or a pointer device such as a stylus. The one or more buttons (not shown) may include an up/down button for volume control of speaker 328 and/or microphone 330.
In some implementations, device 300 plays back to a user recorded audio and/or video files, such as MP3, AAC, and MPEG video files. In some implementations, device 300 may include the functionality of an MP3 player and may include a pin connector or other port for tethering to other devices. Other input/output and control devices may be used. In an embodiment, device 300 may include an audio processing unit for streaming audio to an accessory device over a direct or indirect communication link.
Memory interface 302 may be coupled to memory 350. Memory 350 may include high-speed random access memory or non-volatile memory, such as one or more magnetic disk storage devices, one or more optical storage devices, or flash memory (e.g., NAND, NOR). Memory 350 may store operating system 352, such as Darwin, RTXC, LINUX, UNIX, OS X, IOS, WINDOWS, or an embedded operating system such as VxWorks. Operating system 352 may include instructions for handling basic system services and for performing hardware dependent tasks. In some implementations, operating system 352 may include a kernel (e.g., UNIX kernel).
Memory 350 may also store communication instructions 354 to facilitate communicating with one or more additional devices, one or more computers or servers, including peer-to-peer communications with wireless accessory devices, as described in reference to
Memory 350 may include sensor processing instructions 358 to facilitate sensor-related processing and functions and application instructions 360 to facilitate the features and processes, described in reference to
Each of the above identified instructions and applications may correspond to a set of instructions for performing one or more functions described above. These instructions need not be implemented as separate software programs, procedures, or modules. Memory 350 may include additional instructions or fewer instructions. Furthermore, various functions of the device may be implemented in hardware and/or in software, including in one or more signal processing and/or application specific integrated circuits (ASICs).
The features described may be implemented in digital electronic circuitry or in computer hardware, firmware, software, or in combinations of them. The features may be implemented in a computer program product tangibly embodied in an information carrier, e.g., in a machine-readable storage device, for execution by a programmable processor. Method steps may be performed by a programmable processor executing a program of instructions to perform functions of the described implementations by operating on input data and generating output.
The described features may be implemented advantageously in one or more computer programs that are executable on a programmable system including at least one programmable processor coupled to receive data and instructions from, and to transmit data and instructions to, a data storage system, at least one input device, and at least one output device. A computer program is a set of instructions that may be used, directly or indirectly, in a computer to perform a certain activity or bring about a certain result. A computer program may be written in any form of programming language (e.g., Objective-C, Java, SWIFT), including compiled or interpreted languages, and it may be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.
Suitable processors for the execution of a program of instructions include, by way of example, both general and special purpose microprocessors, and the sole processor or one of multiple processors or cores, of any kind of computer. Generally, a processor will receive instructions and data from a read-only memory or a random-access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memories for storing instructions and data. Generally, a computer may communicate with mass storage devices for storing data files. These mass storage devices may include magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; and optical disks. Storage devices suitable for tangibly embodying computer program instructions and data include all forms of non-volatile memory, including by way of example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory may be supplemented by, or incorporated in, ASICs (application-specific integrated circuits). To provide for interaction with a user the features may be implemented on a computer having a display device such as a CRT (cathode ray tube), LED (light emitting diode) or LCD (liquid crystal display) display or monitor for displaying information to the author, a keyboard and a pointing device, such as a mouse or a trackball by which the author may provide input to the computer.
One or more features or steps of the disclosed embodiments may be implemented using an Application Programming Interface (API). An API may define on or more parameters that are passed between a calling application and other software code (e.g., an operating system, library routine, function) that provides a service, that provides data, or that performs an operation or a computation. The API may be implemented as one or more calls in program code that send or receive one or more parameters through a parameter list or other structure based on a call convention defined in an API specification document. A parameter may be a constant, a key, a data structure, an object, an object class, a variable, a data type, a pointer, an array, a list, or another call. API calls and parameters may be implemented in any programming language. The programming language may define the vocabulary and calling convention that a programmer will employ to access functions supporting the API. In some implementations, an API call may report to an application the capabilities of a device running the application, such as input capability, output capability, processing capability, power capability, communications capability, etc.
A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made. Elements of one or more implementations may be combined, deleted, modified, or supplemented to form further implementations. In yet another example, the logic flows depicted in the figures do not require the particular order shown, or sequential order, to achieve desirable results. In addition, other steps may be provided, or steps may be eliminated, from the described flows, and other components may be added to, or removed from, the described systems. Accordingly, other implementations are within the scope of the following claims.
This application claims priority to U.S. Provisional Patent Application No. 63/032,520, filed May 29, 2020, the entire contents of which are incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 9760871 | Pourfallah | Sep 2017 | B1 |
| 10332096 | Tilahun | Jun 2019 | B2 |
| 10600060 | Schiffman | Mar 2020 | B1 |
| 11048977 | Ulbricht | Jun 2021 | B1 |
| 20190180270 | Ericson | Jun 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| WO-2016183508 | Nov 2016 | WO |
| WO-2019003074 | Jan 2019 | WO |
| Entry |
|---|
| S. Lin, H. F. Cheng, W. Li, Z. Huang, P. Hui and C. Peylo, “Ubii: Physical World Interaction Through Augmented Reality,” in IEEE Transactions on Mobile Computing, vol. 16, No. 3, pp. 872-885, Mar. 1, 2017. (Year: 2017). |
| S. Seneviratne et al., “A Survey of Wearable Devices and Challenges,” in IEEE Communications Surveys & Tutorials, vol. 19, No. 4, pp. 2573-2620, Fourthquarter 2017. (Year: 2017). |
| E. A. Bernal et al., “Deep Temporal Multimodal Fusion for Medical Procedure Monitoring Using Wearable Sensors,” in IEEE Transactions on Multimedia, vol. 20, No. 1, pp. 107-118, Jan. 2018. (Year: 2018). |
| G. Peng, G. Zhou, D. T. Nguyen, X. Qi, Q. Yang and S. Wang, “Continuous Authentication With Touch Behavioral Biometrics and Voice on Wearable Glasses,” in IEEE Transactions on Human-Machine Systems, vol. 47, No. 3, pp. 404-416, Jun. 2017. (Year: 2017). |
| Kanel, “Sixth Sense Technology,” Thesis for the Bachelor Degree of Engineering in Information and Technology, Centria University of Applied Sciences, May 2014, 46 pages. |
| Mann et al., “Telepointer: Hands-Free Completely Self Contained Wearable Visual Augmented Reality without Headwear and without any Infrastructural Reliance”, IEEE Fourth International Symposium on Wearable Computers, Atlanta, Ga, USA, Oct. 16-17, 2000, 4 pages. |
| Mann, “Wearable Computing: A First Step Toward Personal Imaging,” IEEE Computer, Feb. 1997, 30(2):25-32. |
| Mann, “Wearable, tetherless computer-mediated reality,” American Association of Artificial Intelligence Technical Report, Feb. 1996, 62-69, 8 pages. |
| Metavision.com [online], “Sensularity with a Sixth Sense,” available on or before Apr. 7, 2015, via Internet Archive: Wayback Machine URL <http://web.archive.org/web/20170901072037/https://blog.metavision.com/professor-steve-mann-society-of-sensularity-with-a-sixth-sense/> retrieved on Apr. 25, 2023, URL <https://blog.metavision.com/professor-steve-mann-society-of-sensularity-with-a-sixth-sense/>, 4 pages. |
| Mistry et al., “WUW—wear Ur world: a wearable gestural interface”, Proceedings of the 27th international conference Extended Abstracts on Human Factors in Computing Systems—CHI EA '09, Boston, MA, USA, Apr. 4-9, 2009, 6 pages. |
| Shetty et al., “Sixth Sense Technology,” International Journal of Science and Research, Dec. 2014, 3(12):1068-1073. |
| Number | Date | Country | |
|---|---|---|---|
| 63032520 | May 2020 | US |
