Microsoft Technology Licensing, LLC

Upshur Parks

Marco Piumatti

Ravi Rao

Pascal Francis Menezes

Amer A Hassan

Shai Guday

Billy R Anders, Jr

Andrew Thomas Baron

Dmitry A Anipko

Pehkeong Teh

Todd R Manion

Jeremy Lee Dewey

Scott A Senkeresty

Brian R Lieuallen

Pallavi Choudhury

Kevin C Ransom

Pritam De

Travis C Luke

Robert D Donner

James R Boldman

Jonathan T Wheeler

Ramakrishnan Peruvemba

Kishore J Prakash

A mobile computing device that supports cost-aware application components for operation over a metered network. A current basis for computing usage charges over one or more networks may be made available to the cost-aware application components through an application programming interface supported by an operating system service. That service may receive a policy for charging for data usage over a network and may also obtain information defining data usage for the mobile computing device. Based on this information, the service may determine a current basis for charging for data usage. With this information, the application component can determine a manner for executing network operations that involve data transmission over the network, such as deferring the operation or selecting an alternative network.

Operating system supporting cost aware applications

An indicator for a device may provide an indication that a threshold associated with a budget for a network resource has or will be reached. When a user requests a network operation that will consume the network resource, an amount of the network resource to be consumed by the operation is predicted, if possible. If the prior use of the network resource and the amount to be used to complete the network operation exceeds a threshold the user may be warned and given an opportunity to cancel the operation or adjust the way in which the operation will be performed. If the amount of network resource a network operation will consume is unknown, a rate of use of the network resource is determined and a time until the budget is reached is estimated.

Network resource management with prediction

Application programming interface (API) for starting and accessing distributed routing table (DRT) functionality. The API facilitates bootstrapping into the DRT by one or more devices of a group of devices (a mesh) seeking to collaborate over a serverless connection, establishing a node of the DRT, where each node is an instance of an application that is participating in the mesh, and node participation by allowing the application to search for keys published by other nodes in the mesh, or by becoming part of the mesh by publishing a key. The API facilitates optimization of the routing table for quickly finding a root of a specific key in the mesh by finding the key directly in a cache or by asking a root node of the key that is in the local routing table that is closest numerically to the key being searched.

Distributed routing table interface

A computing device including an indicator predicting use of a network resource. The indicator may provide an indication that a threshold associated with a budget for the network resource has or will be reached. When a user requests a network operation that will consume the network resource, an amount of the network resource to be consumed by the operation is predicted, if possible. If the prior use of the network resource and the amount to be used to complete the network operation exceeds a threshold the user may be warned and given an opportunity to cancel the operation or adjust the way in which the operation will be performed. If the amount of network resource a network operation will consume is unknown, a rate of use of the network resource is determined and a time until the budget is reached is estimated. An administrative tool is provided for managing network resources and setting budgets for resource consumption by users, devices, or applications.

Application programming interfaces and methods that provide group management in a peer-to-peer (P2P) network are provided. More specifically, new and improved P2P application programming interfaces (APIs) and methods for the creation and access of groups, the retrieval of member and group information, the addition, modification, deletion and management of records (data), the importation and exportation of group data, the direct communication between members, the addition of a security provider to a group, the setting and retrieval of presence information, the registering for event notifications, and other utility and support functions are presented. Each of these interfaces utilize various parameters that are passed in from an application program that uses these interfaces to manage and utilize groups. The interfaces return a value that indicates the success or failure of the function. For failures, the interfaces provide an indication as to the problem resulting in the failure.

Peer-to-peer grouping interfaces and methods

A test framework for testing peer-to-peer applications allocates a test case manager and a plurality of distributed test units for each test case, which has a sequence of actions each to be performed by one of the test units. To enable the test units to perform the test case actions, the test case manager loads dynamic link library files (DDLs) containing the test case to each test unit, and creates on each test unit a test object that can be remotely activated using an object-remoting framework. To execute the test case, the test case manager goes through the sequence of test case actions. For each action, the test case manager calls the test object on a corresponding test unit to perform the action. In this way, the test case manager directs the test units to carry out the test case actions. The results of the test case actions are logged by the distributed test units and then collected for analysis and diagnosis.

System and method for testing peer-to-peer network applications

Growing community of inventors

Bothell, WA, United States of America

Upshur Parks