Microsoft Technology Licensing, LLC

Ashutosh Tewari

Baskaran Dharmarajan

Gandhi Vaithilingam

David Bruce Lindsay

Geoffrey M Clark

Adrian Dragomir

Steven Kafka

Aby John

Richard Craddock

Krish Vitaldevara

Variety of approaches to manage an asynchronous analytics operation based on a communication exchange are described. A communication service initiates operation(s) to manage an asynchronous analytics operation upon receiving a request communication to start the asynchronous analytics operation. The request communication is detected as an intent to start the asynchronous analytics operation based on of a sender identification, a destination address, a subject, and/or a content of the request communication. The request communication is parsed to identify an analytics query associated with the asynchronous analytics operation. Next, the analytics query is executed. Upon receiving a result for the analytics query, the result is transmitted in a reply communication.

Managing asynchronous analytics operation based on communication exchange

One or more techniques and/or systems are disclosed for facilitating synchronizing of data between one or more servers and a mobile device. The mobile device can establish which servers comprise data that is to be synchronized, and inform the servers that a push notification gateway should be used to send notifications of a data state change. A connection can be opened between the mobile device and the push notification gateway so that when a data state change is detected by a server the server can send the notification to the gateway, which can forward it to the mobile device. The mobile device may then choose to initiate a data synchronization with the server. In this manner, an open connection is merely maintained between the mobile device and the gateway, as opposed to multiple resource intensive connections between the mobile device and multiple servers.

Data synch notification using a notification gateway

An application using one version of a schematized XML protocol communicates with another application using a different version of the schematized XML protocol. The different versions may correspond to different deployments or releases of the protocol. Each application generates messages to be sent using two data sets. A first data set is incorporated into the message using elements available in a standard XML protocol schema. A second data set is incorporated into the message using XML annotation elements. The receiving application processes the message using the schematized XML protocol to parse out the first data set. The receiving application further parses the message to identify the second data set that is carried by enhanced XML annotation elements. Extension or annotations are flexibly added to the XML protocol without requiring the client application to request&#x2014;or the server application to respond to&#x2014;a pre-negotiated number or type of annotations.

Extension of schematized XML protocols

Items of an item set may be stored by an item server (e.g., mail messages comprising a mailbox stored by a mail server) that supports the application of actions, but only within a constraint (e.g., a maximum duration or computational resources consumed by the action). The application of complex actions to large item sets may exceed the constraint if performed in one request. Moreover, the request may be made by a user interface of a user device, but the user interface may stall while interoperating with the item server to perform the action. Instead, a background process may issue a sequence of requests applying the action to respective batches of items within the constraint. This architecture may enable the user interface to remain responsive to the user while the action is performed, and even to be terminated without jeopardizing the completion of the action upon the item set.

Applying actions to item sets within a constraint

In embodiments of global email identity preferences, a default outgoing email address that is designated by a user is maintained at an email server. The user can also be associated with multiple email addresses that are correlated at the email server. When an outgoing email is received at the email server for delivery to a designated recipient, the outgoing email can be identified as being from one of the multiple email addresses that are associated with the user. A determination is made as to whether to update the outgoing email with the default outgoing email address that is associated with the user, such as if the outgoing email is received from an email client that does not allow user selection of a default client email address. The outgoing email is then routed to the designated recipient for display as being from the default outgoing email address.

Global email identity preferences

An authentication process receives information identifying a user, a device used by the user and a location in which the device is being used. That authentication process determines whether the location is among a set of familiar locations stored about the user for a service being accessed. If the location is not among the set of familiar locations, then the user is not authenticated. A desirable user experience can be obtained by using information about any existing relationship, such as a synchronization relationship, between the device and the service established at a prior familiar location. Instead of challenging a user whose device is in an unfamiliar location, the authentication process determines whether the device has a relationship established with the service. If the device has a relationship established with the service, then the set of familiar locations is updated to include the location in which the device is being used.

Growing community of inventors

Fremont, CA, United States of America

Ashutosh Tewari