Microsoft Technology Licensing, LLC

Gregory Bolles

Shivakumar Seetharaman

John Allen Atwood

Juan Vicente Esteve Balducci

Selvaraj Nalliah

Kevin Daniel Resnick

Patrick Tousignant

Salman Zafar

Michael Anthony Faoro

Jason Andrew Cook

Vanessa C Feliberti

Danilo Landucci Benzatti

Andrew Winslow Brough

Gustavo Varo

Yeelin Tan

David Paul Limont

Samuel Neely

Massimiliano Ciccotosto

Adrian Dragomir

Russell L Simpson, Jr

Katy Chia-wen Chen

Andrew S Moss

Radhesh Mohandas

Jonathan Kent

Michael Hamler

Techniques to apply and share remote policies on personal devices are described. In an embodiment, a technique includes contacting an enterprise server from an enterprise application operating on a personal device. The enterprise application may receive policies from the enterprise server. The policies may be applied to the enterprise application. When a second enterprise application on the personal device is launched, the policies may also be applied to the second enterprise application. When a policy is changed on the enterprise server, notification is pushed to the personal device and all related enterprise applications on the personal device may be updated to enforce the policy change. Other embodiments are described and claimed.

Techniques to apply and share remote policies on mobile devices

Enhanced input field features and techniques for displaying and resolving location information in meeting items are provided. In response to a user's interaction with a place name displayed in the location field of a user interface for a meeting item, up to date information is retrieved about the location associated with the place name from a web service and displayed. The display can include a map image tile. In addition to enabling the displaying of up to date information, during creation of the meeting item, the location input field of a meeting item can present location suggestions from within the location input field, for example, as a drop-down listing of possible locations. The suggestions for completing a user's input text string to the location input field can be obtained from sources such as a web service, a mailbox, a managed database/directory service, a history cache/database or a combination thereof.

Location context, supplemental information, and suggestions for meeting locations

The embodiments described herein generally relate to a method and system for synchronizing multiple classes with disparate schemas in a single collection through the use of the same synchronization request and/or synchronization key. A collection of different types of items may be synchronized while using the unique schema for each class. Further, different synchronization options, e.g., filtering, truncation, and body settings, may be applied to each class. In a synchronization request, an option block within a synchronization command notifies the server to synchronize the class specified in the option block. The option block may also specify the options, or settings, if any, to apply to the class. Multiple option blocks may be included in the synchronization command to specify the synchronization of multiple classes. Where multiple classes are specified, the server responds with the synchronized items of all such classes while maintaining each class's unique schema.

Synchronizing multiple classes with disparate schemas in the same collection

In embodiments, mobile devices request and utilize recipient caches. Recipient caches store information regarding previous recipients of communications. The information on recipients includes when the recipient was last contacted and the frequency with which a recipient is contacted. In embodiments, a mobile device requests a recipient cache from a server. When a user types a string of text, the mobile device then uses the recipient cache as well as the contacts and emails on the mobile device and resolves a recipient list. In other embodiments, a recipient cache on a server is updated when a mobile device sends a message with new recipient information. In another embodiment, a server resolves conflicting messages by using recipient information.

Auto-resolve recipients cache

Embodiments are provided for synchronizing data retrieval with multiple data sources on a mobile computing device while maintaining a predetermined quality of service and optimizing resource usage. A connection is established between the mobile computing device and the multiple data sources for a first synchronization interval. A synchronization request is sent over the connection during the first interval. A response to the request including data is received from a data source during the first interval to synchronize the data. After the data is received, the connection to the data source is severed. The connection between the mobile computing device and the data source is then re-established for a second synchronization interval based on quality of service parameters associated with the data source and a pending connection status associated with one or more additional data sources. Another synchronization request is then sent by the mobile computing device over the re-established connection.

Optimizing mobile device synchronization with multiple data sources

Example embodiments provide for authenticating a device to multiple servers without using delegation or having to have a password stored on the device. Multiple certificates that are typically non-delegable are used to authenticate the device to each server. One certificate is used to authenticate the client with the front-end server and a second certificate is used to authenticate the client against a back-end server. Rather than having both certificates reside with the device, however, the second certificate is originally stored by the client in the back-end. It is then retrieved 'on-the-fly' by the front-end upon authentication of the client and used to authenticate itself as the client in order to act on behalf of the client when retrieving data from the back-end server.

Client authentication using multiple user certificates

A method and system for managing one or more web requests provided to a web application from a client computer. An application is responsive to a web request to generate verification data. The application sends a reply to the client to calculate a stamp as a function of the generated verification data. The application is responsive to an additional request from the client including the calculated stamp to determine if it corresponds to the generated verification data. If the calculated stamp corresponds to the generated verification data, the additional web request is submitted to the web application for processing. A Web server subject to a DOS attack will be able to distinguish between genuine users(who generate stamps) and malicious users(who will not generate stamps) and over a period of time be able to restore service to the former and deny to the latter.

Source throttling using CPU stamping

Growing community of inventors

Snohomish, WA, United States of America

Gregory Bolles