Microsoft Technology Licensing, LLC

Sergii Viktorovych Liashenko

Sathyanarayanan Karivaradaswamy

Robert E Harris, Jr

Sanjana Ramakrishnan Sunder

Michael Jeffrey Ajax

Sanjeev Chandra Reddy

Ugan Sivagnanenthirarajah

Rajesh Bangalore Gururaj

Sayak Chatterjee

Sarah Anne Barnette

Augustus Javier Tertzakian

Augustus Tertzakian

Rajesh Gururaj

A computer system receives a sensor payload from a human presence sensor that is associated with the computer system. The computer system determines, based on an arbitration policy, that the computer system is enabled to perform a particular action based on the priority of the human presence sensor. The arbitration policy determines the priority of the human presence sensor among a plurality of human presence sensors that are associated with the computer system. The computer system triggers the particular action based on the computer system being enabled to perform the particular action based on the content of the sensor payload.

Method for prioritizing human presence sensors in a computer system based on arbitration policies

A device receives a sensor payload at a sensor service. The sensor payload includes a data field that comprises a first value that corresponds to a reading by a sensor device. The device sends the sensor payload to a broker process that is separate from the sensor service and that hosts plug-in logic. The device receives a sensor payload update from the broker process. The sensor payload update includes a second value for the data field that is different from the first value. The second value was determined by the plug-in logic. The device creates a modified sensor payload from the sensor payload, including updating the data field to comprise the second value. The device initiates an operating system action based on the modified sensor payload.

Sensor broker for plug-ins

A method for objective code branch verification executes code branch annotations to assess developer-specified pass conditions for each code branch that are indicative of whether or not the code branch is functioning as originally intended by the author of the code. The method includes maintaining and dynamically updating both a counter value and a pass indicator status in association with each of multiple annotated code branches defined within a code body during execution of the code body. The counter value for each annotated code branch represents a number of times the annotated code branch has executed within a current run-time environment, and the pass indicator status indicates satisfaction or non-satisfaction of a pass condition identified within the code branch that is determined based on the counter value for the associated code branch.

Executable code branch annotations for objective branch verification

Growing community of inventors

Edmonds, WA, United States of America

Sergii Viktorovych Liashenko