Microsoft Technology Licensing, LLC

Edward Wu

Yingfeng Oh

Dominic Law

Xiaokang Zhang

Murli D Satagopan

Xiang Yu

Sanjay Sureshchandra Dubey

Hao Liu

Cameron Stillion

Anandhi Somasekaran

Erik R Ashby

Hardik Bati

Yawen Wei

Lihong Pei

Qi Liu

David Paul Harris Gorbet

Robert Charles Ward

Ananda Sinha

Kevin Kuan Wang

Waitat Peter Poon

Vijaysundar R Srirangam

Vineeth Madhusudanan

Thane David Peterson

Richard William Meadows

Generally discussed herein are methods, systems, and apparatuses for tracking user interaction with sponsored and/or unsponsored content. A method can include receiving a tracking event packet including data fields comprising a packet identification, a tracking event identifier, a content identifier, a cost, a campaign identifier, and/or an advertiser identifier, determining whether the tracking event packet is a duplicate based on the packet identification, aggregating non-duplicate tracking event packets by advertiser identification such that packets with advertiser identifications that hash to a same value are aggregated together, and transferring aggregated tracking event packets to a first database and a second database, the first database includes data stored for analytics and the second database includes data stored for billing and campaign performance monitoring.

Tracking interaction with sponsored and unsponsored content

Techniques for handling the dynamic reassignment of entities among multiple data centers are provided. In one technique, for each task of a plurality of tasks that are associated with a first data center of a plurality of data centers, an entity identifier that is associated with the task is identified. A call to an entity routing service is initiated, where the call includes the entity A response to the call is received from the entity routing service, where the response indicates a particular data center. An entity processor that is different than the entity routing service processes the task only if the particular data center is the first data center. If the particular data center is different than the first data center, then a data structure that stores the task is updated to indicate the particular data center and the task is eventually processed in the particular data center.

Dynamic adjustment of entity assignment in a multi-data center environment

Techniques for rotating leadership among processes in multiple data centers are provided. A first process of a program in a first data center determines whether the first process is a leader process among multiple processes of the program. Each process of the multiple processes executes in a different data center of the multiple data centers. In response to determining that the first process is the leader process, the first process performs a particular task. After performing the particular task, the first process causes leadership data to be updated to indicate that the first process is no longer the leader process. After the leadership data is updated, a second process (of the multiple processes) in a second data center determines whether the second process is the leader process. The second process performs the particular task only if the second process determines that the second process is the leader process.

Automatic cross-data center rotation of active processes

Coexistence tools are described for synchronizing properties between on-premises customer locations and remote hosting services. These tools may provide methods that send the tools for installation onto on-premises infrastructure located at customer sites, execute the tools to manage the customer infrastructure remotely via a hosted service, and synchronize properties at the customer site with the hosted service. Other methods may include receiving the tools from the hosted service, communicating configuration parameters related to operating the tools, and executing the tools in response to the configuration parameters. The tools may also provide systems that include on-premises servers associated with the customer infrastructure, with the on-premises servers including on-premises coexistence components for maintaining the property at the customer site. These systems may also include administrative servers associated with the hosted service. The administrative servers may include hosted-side coexistence components for maintaining and synchronizing counterparts of the on-premises properties.

Coexistence tools for synchronizing properties between on-premises customer locations and remote hosting services

This description provides tools related to layered architectures for remote dynamic administration of distributed client configurations. These tools provide methods that may include subscribing to have online configuration services remotely manage applications installed on client systems. The methods may also include receiving dynamically-updated lists from the online configuration services, with these lists including the installed applications. The methods may also receive configuration payloads that specify how to configure the installed applications, and may configure the installed applications based on these configuration payloads. The methods may also present user interfaces on the client systems, with the user interfaces including the configured applications. The tools also provide methods that may include receiving subscription information from the customer sites, with the subscription information indicating that the customer sites have subscribed to the online configuration services. The methods may also include sending the dynamically-updated lists and the configuration payloads to the customer sites.

Layered architectures for remote dynamic administration of distributed client configurations

Growing community of inventors

Fremont, CA, United States of America

Edward Wu