Microsoft Technology Licensing, LLC

Frank Gorgenyi

Justin Allen Hutchings

Michael P Fenelon

Sanjib Saha

Fernando Gonzalez

Matthew Thomas Beaver

Guillermo Eduardo Guillen

Herman Richard Forrest, Iii

Janet Lynn Schneider

Feng Yue

Peter Dawoud Shenouda Dawoud

Arvind Muthukrishnan

Jared Enoch Henderson

Bartosz Henryk Paliswiat

Mark A Inderhees

Shaun C Hedrick

Aidan George Purdy-Say

Brian Andrew Bowman

Stuart J Harper

Uri Ron

Oliver H Foehr

Arie Yehuda Gur

Alain L Michaud

Darren Ray Davis

Parmjeet Singh

Adrian F Maxa

J Adrian Lannin

Heming Wen

Ashish Vijay Gadre

Rahul Ramadas

Jay Gilbert

Max Glenn Morris

J Robert Sims, Iii

Joshua A Dersch

Kaustav Mukherjee

Cristina Del Amo Casado

Erik O Peterson

Steven Mathew Ilami

Daniel Estrada Alva

Maxim Kudryavtsev

Lanny D Natucci, Jr

Neha Motghare

Artur Moura Aguiar

Shawn E Maloney

Sylvester Tate, Ii

Sebastian Perez Juarez

Daryl M Wilson

Robert Zi Long Zhao

Lanny D Natucci Jr

Sylvester Ii Tate

J Robert Iii Sims

Jr Natucci Lanny D

Janet L Schneider

The present disclosure relates to systems, methods, and computer-readable media for securely verifying an identity of a user of a client device based on a signal transmitted by the client device. For example, systems disclosed herein include registering a client device and facility device via a cloud computing system to enable the client device and facility device to securely communicate a signal via a wireless connection. The systems disclosed herein additionally include determining whether a trigger condition applies based on a position of the client device relative to the facility device. The systems disclosed herein further include maintaining and updating a subset of user verification information to include personal verification of a registered user of the client device. Using the subset of user verification information, a biometric scanning device may efficiently and accurately verify an identity of an individual associated with the client device.

Secure verification of an individual using wireless broadcasts

A computing device including a wireless communication device, an electrostatic interface, and a processor. The processor may be configured to, via the electrostatic interface, detect a peripheral device proximate the surface. In response to detecting the peripheral device, the processor may be further configured to establish wireless pairing with the peripheral device at least in part by performing an identifier exchange via the electrostatic interface. Subsequently to performing the identifier exchange, establishing wireless pairing may further include generating a temporary key and transmitting the temporary key to the peripheral device via the electrostatic interface. Subsequently to transmitting the temporary key, establishing wireless pairing may further include receiving a first wireless pairing signal from the peripheral device via the wireless communication device. Subsequently to receiving the first wireless pairing signal, establishing wireless pairing may further include transmitting a second wireless pairing signal to the peripheral device via the wireless communication device.

Establishing wireless pairing via electrostatic interface using temporary key

Techniques are described for receiving annotations in a fixed digital document on a first computing device and streaming them to multiple other computing devices that are connected to the first computing device using a peer-to-peer network. For example, a session may be established between the first computing device and a plurality of the other computing devices. Annotations may be received at the first computing device and streamed to the multiple other computing devices using the peer-to-peer network. For example, the annotations may include highlighting text in the fixed digital document, or electronic ink annotations made at a given location within the fixed digital document. These annotations may be streamed to the other computing devices in real-time, or at regular intervals, without requiring a cloud connection and without the need to save, close, and/or reopen the fixed digital document for the annotations to be received by the other computing devices.

Synchronized annotations in fixed digital documents

The disclosure herein describes coupling a stylus and a computing device. Based on a tip of a stylus being brought proximate to a display of a computing device configured to communicate in accordance with a wireless protocol, the computing device is configured to receive a stylus wireless protocol identifier and transmit a wireless protocol identifier of the computing device and one or more security keys to the stylus via a communication channel in response, whereby the stylus and computing device are coupled. Based on receiving a signal associated with user input from the coupled stylus using the wireless protocol, the computing device performs an operation based on the signal. The described 'loose coupling' enables streamlined use of styluses with compatible computing devices without requiring full pairing.

Coupling a pen device to a companion device based on pen proximity

A host device, such as a laptop or desktop computer, that supports wireless point-to-point connections with a peripheral device, such as a pair of headphones, mouse, etc., is configured with a proximity platform with which services register to execute particular filters or scenarios upon the host device connecting or attempting to connect with a peripheral device. For example, an advertisement packet transmitted from the peripheral device using Bluetooth may be customized with a particular pattern that corresponds to one or more registered patterns from the registered services, thereby causing the proximity platform to perform particular functions. Peripheral devices can thereby customize their products so that a host computer automatically performs a function upon receiving an advertisement from the peripheral device, such as surface a notification on a user interface of the host device or track the peripheral device's location.

Proximity platform

Electronic devices described herein are configured to use a beaconing capability to enable responders to locate a user of the electronic device. The beacon payload includes an incident identifier, among other data, that enables responders to identify the specific electronic device that was used to place the emergency call. The beacon payload is dynamically updated with refreshed data to enable responders to locate the user of the electronic device that may potentially be in transit from one location to another, and to adapt to changing circumstances associated with the emergency situation.

Location assistance with a dynamically updated beacon payload from an electronic device

The location of a computing device is determined, and the location of an area of interest that is a geographic area referred to as a geo-fence is identified. The accuracy of the determined location of the computing device has an associated uncertainty, so the exact position of the computing device cannot typically be pinpointed. In light of this, the uncertainty associated with the determined location is evaluated relative to the size of the geo-fence in order to determine whether the computing device is inside the geo-fence or outside the geo-fence. Based on this determination, various actions can be taken if the user is entering the geo-fence, exiting the geo-fence, remaining in the geo-fence for at least a threshold amount of time, and so forth.

Detecting geo-fence events using varying confidence levels

A device location is determined, and the location of an area of interest that is a geographic area referred to as a geo-fence is identified. Multiple geo-fences can be identified by the device, and different geo-fences can be associated with different programs on the device. An operating system of the device implements multiple different periods of operation for the device, including a conservation period during which certain programs are not typically scheduled to run, and an execution period during which such programs are typically scheduled to run. A system identifies geo-fence events, which occur when the device enters or exits the geo-fence. The system maintains a record of the geo-fence events for each of multiple geo-fences, and provides to a program selected ones of those geo-fence events at a time when the program is scheduled to run on the device during an execution period of the operating system.

Coalescing geo-fence events

A computing device includes at least one processor and a memory, the memory storing computer-executable instructions for causing the device to be configured to load a subset of geo-fences from secondary storage to primary storage for tracking by the computing device, the subset of geo-fences selected from a set of available geo-fences stored in the secondary storage, based on a selection criteria. The computing device further creates a boundary geo-fence with a radius corresponding to a distance between a current location of the computing device and an edge of a geo-fence in the subset of geo-fences that is furthest from the current location of the computing device. Upon detecting a geo-fence event associated with a new location of the computing device in relation to the boundary geo-fence, a new subset of geo-fences is re-loaded, and a new boundary geo-fence is created based on the new location of the computing device.

Scalability and reliability of hardware geo-fencing with failover support

Platform neutral device protocol techniques are described in which functionality to customize device interactions through communication busses is made accessible through platform independent script-based infrastructure. Functionality provided by an operating system to manipulate standard protocols of a communication bus used to interact with a connected device is exposed as script-based objects. Script-based protocol definition files associated with connected device may be employed to customize device protocols for the communications using the functionality exposed through the script-based objects. A computing device may acquire a protocol definition file for a particular device in various ways and host the protocol definition file via a suitable run-time platform. Requests for interaction with the particular device may then be handled using the custom protocols defined by the hosted protocol definition file.

Platform neutral device protocols

Systems and methods disclosed herein may include tracking one or more geo-fences using a GNSS hardware processor within a computing device. The tracking may use at least one GNSS signal. State changes of the one or more geo-fences during the tracking may be saved in a shared state database. The shared state database may be shared between the GNSS hardware processor and an application processor within the computing device. Upon detecting a deterioration of the at least one GNSS signal, tracking the one or more geo-fences may be switched from using the GNSS hardware processor to using the application processor. After the switching, an initial state of each of the one or more geo-fences may be set by using states currently stored in the shared state database prior to the switching.

Improving scalability and reliability of hardware geo-fencing with failover support

Bidirectional (bidi) extension techniques for USB and/or other similar busses/connections are described in which an interface is provided to enable bidirectional communication with connected devices. The interface may be implemented as an operating system component to handle bidi communication for devices from multiple different independent hardware vendors (IHVs). Device drivers for different devices can be configured to include extension files in accordance with an established schema for bidi communication. The extension files describe supported bidi attributes, capabilities of the device, and how to make calls into the device. The interface operates to detect the extension files and set-up a corresponding device for bidi communication. Applications then interact through the interface to access, retrieve, and set configuration and status data for connected devices. The use of extension files enable creation of architecture independent devices drivers that can be used across different platforms with substantially no changes.

Bidi extension for connected devices

Growing community of inventors

Bremerton, WA, United States of America

Frank Gorgenyi