Microsoft Technology Licensing, LLC

Other

Brian D Remick

Jianfeng Gao

Ye-Yi Wang

Chenlei Guo

Xinying Song

Yelong Shen

Divya Jetley

Cynthia M Hagan

Byungki Byun

Adedeji Olumuyiwa Akinyemi

Stephen Friesen

Okacey Chidinma Abaraoha

Edward Thiele

Marcus Gois

Mohammed Aatif Ali

Xiaodong He

Scott Robert Ramsby

Marcus Jon Jager

Jianshu Chen

Marc Andrew Power

Dejan Subotic

Francisco Jose Garcia-Ascanio

Mariana Stepp

Marcus Vinicius Silva Gois

Vaibhav Khandelwal

Rong Guo

Michael F Palermiti

Sejal Kiran Shinde

Yang Zou

Kacey Abaraoha

Sharanya Chinnusamy

Arpan Jugalkishor Asawa

Ritesh Kumar Sinha

Sidi Lin

Ryan Lee Jobse

A graph tracks the lineage of customer data, including when it was originally extracted from a customer computing system, and any transformation results indicating transformations that were performed on the customer data. The graph is traversed to identify nodes in the graph that have expired based upon data removal policies. The customer data represented by the expired nodes in the graph is deleted and the graph is modified to delete the expired nodes. The modified graph is then stored in persistent memory until data removal is next triggered.

Tracking data lineage and applying data removal to enforce data removal policies

Techniques for providing a people recommendation system for predicting and recommending relevant people (or other entities) to include in a conversation based on contextual indicators. In an exemplary embodiment, email recipient recommendations may be suggested based on contextual signals, e.g., project names, body text, existing recipients, current date and time, etc. In an aspect, a plurality of properties including ranked key phrases are associated with profiles corresponding to personal entities. Aggregated profiles are analyzed using first- and second-layer processing techniques. The recommendations may be provided to the user reactively, e.g., in response to a specific query by the user to the people recommendation system, or proactively, e.g., based on the context of what the user is currently working on, in the absence of a specific query by the user.

Contextual people recommendations

Techniques for providing a people recommendation system for predicting and recommending relevant people (or other entities) to include in a conversation. In an exemplary embodiment, a plurality of conversation boxes associated with communications between a user and target recipients, or between other users and recipients, are collected and stored as user history. During a training phase, the user history is used to train encoder and decoder blocks in a de-noising auto-encoder model. During a prediction phase, the trained encoder and decoder are used to predict one or more recipients for a current conversation box composed by the user, based on contextual and other signals extracted from the current conversation box. The predicted recipients are ranked using a scoring function, and the top-ranked individuals or entities may be recommended to the user.

Relevance group suggestions

In one embodiment, a predecessor version of a client software application may execute a runtime handover to a successor version of the client software application. A client side devicemay execute a predecessor versionof a client software application while installing a successor versionof the client software application. The client side devicemay execute an update handshake between the successor versionand the predecessor versionThe client side devicemay execute a runtime validation of the successor version

Auto-update while running client interface with handshake

A computing device detects a synchronization conflict between two versions of a file. In particular, the file may comprise a digital photo. The computing device may characterize a nature of a difference between metadata fields as immutable, mergeable, or subsumable. Core metadata fields may be defined such that a nature of a difference, or conflict, is categorized as immutable. Non-core metadata fields may be defined such that a nature of a difference, or conflict, is characterized as either mergeable or subsumable. A conflict between corresponding mergeable non-core metadata fields may be resolved by merging values of the corresponding non-core metadata fields. A conflict between corresponding subsumable non-core metadata fields may be resolved by replacing a value of a non-core metadata field of an older of the two versions of the file with a value of a corresponding non-core metadata field of a younger of the two versions of the file.

Conflict resolution via metadata examination

A determination is made at a first computing device of whether there is a synchronization conflict between a change to a first synchronized item at the first computing device and a change to a second synchronized item at a second computing device. If a synchronization conflict exists, rule-based conflict resolution is performed to automatically resolve the synchronization conflict. The rule-based conflict resolution is based at least in part on a type of the change made to the first synchronized item, a type of the change made to the second synchronized item, and a set of multiple rules. A notification of the resolution is then sent to the second computing device.

Automatic synchronization conflict resolution

Both an edited version of a first image and an original version of the first image are stored at a first computing device. In response to a user request to synchronize images across multiple computing devices, both the edited version of the first image and the original version of the first image are synchronized with a second computing device. A user is allowed to revert to the original version of the first image regardless of on which of the multiple computing devices the edited version was changed.

Supporting media content revert functionality across multiple devices

A provided computing device detects a synchronization conflict between two versions of a file and may examine corresponding metadata fields. The computing device may characterize a nature of a difference between metadata fields as immutable, mergeable, or subsumable. Core metadata fields may be defined such that a nature of a difference, or conflict, is categorized as immutable. Non-core metadata fields may be defined such that a nature of a difference, or conflict, is characterized as either mergeable or subsumable. A conflict between corresponding mergeable non-core metadata fields may be resolved by merging values of the corresponding non-core metadata fields. A conflict between corresponding subsumable non-core metadata fields may be resolved by replacing a value of a non-core metadata field of an older of the two versions of the file with a value of a corresponding non-core metadata field of a younger of the two versions of the file.

Growing community of inventors

Morgan Hill, CA, United States of America

Brian D Remick