Microsoft Technology Licensing, LLC

Jorge I Raastroem

Abolade Gbadegesin

Peter J Torr

Darin Miller

Rachel Jiang

Vishal Vikram Ghotge

Megan Galbraith Donahue

Yasser Elsayed Shaaban

Timothy Daniel Noonan

Chittur Padmanabhan Subbaraman

Adrian Dragomir

Marc David McClure

Jianping Yin

Gregory Arthur De Souza

Pavan Rajamohan Hullumane

Rashid Qureshi

Kristofer Noel Iverson

Soemin Tjong

Shai Herzog

Scott Michael Bragg

Jimmy Yu Wu

Xuemei Bao

Qian Zhang

Rajeev Bansal

Shawn Patrick Burke

Jason William Fuller

Anand Muthurajan

Randal James Ramig

Kunal Gandhi

Jithendra K Veeramachaneni

Vijayendra Gopalrao Vasu

Timothy Michael Kurtzman

Alper Selcuk

Marc David Mcclure

Peter John Torr

A device endpoint is accessed through an off-premise communications network relative to the device endpoint. The device endpoint is registered to a virtual device object in data storage of a device service, the device service and the device endpoint communicating across the off-premise communications network, the virtual device object storing a secure device endpoint identifier of the device endpoint. A virtual device identifier associated with the secure device endpoint identifier of the device endpoint is stored in the virtual device object. A request to access the device endpoint using the virtual device identifier is received. The secure device endpoint identifier associated with the virtual device identifier in the virtual device object is read. The device endpoint is notified of a pending job associated with the secure device endpoint identifier. The pending job is communicated to the device endpoint identified by the secure device endpoint identifier.

Secure device endpoint assignment and job communication

Secure device endpoint assignment

The subject disclosure is directed towards a background transfer service that provides platform-level support for third party applications to queue data transfers to run in the background, including when the application is not running in the foreground. Applications may thus perform downloading and uploading tasks in the background; however the background transfer service manages the data transfer requests so as to limit each background application's ability to interfere with foreground application operations, that is, by controlling resource usage according to one or more policies.

Background transfer service for applications on mobile devices

Systems and methods for use in communication between a client and a server, via a networking device, are provided. The method may include sending a request to establish a data connection from the client to the server via the networking device, setting a data connection keep-alive interval for the data connection to a predetermined safe value, and sending a request to establish a test connection between the client and the server. The method may further include determining an efficient keep-alive interval for communication between the client and server via the networking device, using the test connection, setting the data connection keep-alive interval to the efficient keep-alive interval determined using the test connection, and uploading the efficient keep-alive interval from the client to the server in an efficient keep-alive interval notification message, for communication to other clients connected to the server.

Determining an efficient keep-alive interval for a network connection

The subject disclosure is directed towards a technology by which background application code (e.g., provided by third-party developers) runs on a mobile device in a way that is constrained with respect to resource usage. A resource manager processes a resource reservation request for background code, to determine whether the requested resources meet constraint criteria for that type of background code. If the criteria are met and the resources are available, the resources are reserved, whereby the background code is ensured priority access to its reserved resources. As a result, a properly coded background application that executes within its constraints will not experience glitches or other problems (e.g., unexpected termination) and thereby provide a good user experience.

Constrained execution of background application code on mobile devices

Techniques and tools for flexible authentication and authorization of services on a push framework. For example, a push notification framework allows services (social networking web services, etc.) to use either an authenticated access mode or an unauthenticated access mode, in order to push information to client devices (e.g., mobile devices). In the authenticated mode, the push framework requires registration of the service with the push framework before allowing the service to push notifications to client devices. Different authenticated modes are provided for third-party and first-party services. In the unauthenticated mode, registration is not required, but notifications are throttled, thereby limiting risk of abuse by unauthenticated services. This allows flexibility for services that use the push framework.

Flexible authentication and authorization mechanism

Growing community of inventors

Issaquah, WA, United States of America

Jorge I Raastroem