Microsoft Technology Licensing, LLC

Steve Lunsman

Sean Gary Nordberg

Matt Pisut

Jeremy Corley

Rahul Dhar

Tal Goldbloom

J Sage Schreiner

Zhangwei Xu

Patrick Joseph Derks

Matthias Baer

Xiaofeng Gao

Cary L Mitchell

David Manci Gardner

Ori Bar-Niv

Derrick Tan

James Oleinik

Tony V Perez

Arvind Narasimhan

Ashish Virmani

Yoav Sion

Gene Michael DeClark

Nancy Sedora

Anubhav Kale

Example aspects include techniques for employing cross-service diagnostics for cloud service providers. These techniques may include dynamically generating a workflow of one or more diagnostic modules based on relationship information between an origin service experiencing an incident and one or more related services that the origin service depends on, and executing the workflow of one or more diagnostic modules to determine a root cause of the incident, each of the one or more diagnostic modules implemented by an individual service of the one or more related services in accordance with a schema. In addition, the techniques may include determining a diagnostic action based on the root cause, and transmitting, based on the diagnostic action, an engagement notification to a responsible entity.

Automated cross-service diagnostics for large scale infrastructure cloud service providers

A method of payment using a client device is disclosed. The payment can be made through a payment method service that can control the payment flow and options available to the user of a client device. Using the payment method service, new payment options with new data schemas and/or new process flows can be used by the client device, but without any need to update software stored on the client device. The payment method service can utilize the look and feel of the client device, such that the user views payment options in the native UI of the client device.

Payment processing for client devices

A mobile device can send a mobile operator identification request to a mobile operator identification server to determine the mobile network operator for a mobile device. The request comprises mobile operator identifier data, which can include data stored at mobile device smart cards and in mobile device memory. The identification server comprises an identification engine that determines whether the identifier data satisfies one of a plurality of mobile operator rules. If a rule is satisfied, mobile operator identification data is sent to and stored at the mobile device. The mobile device can share the mobile operator identification data with mobile device provider online marketplaces to take advantage of business relationships between the mobile operator and the mobile device provider. Identification of the mobile operator is also useful for determining the appropriate billing methods and ensuring the proper mobile operator branding information is presented at the mobile device.

Mobile network operator identification

Growing community of inventors

Kirkland, WA, United States of America

Steve Lunsman