Resource connection monitor utility

• US 20090109857A1
• Filed: 10/31/2007
• Published: 04/30/2009
• Est. Priority Date: 10/31/2007
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Statia, Jeromy S., Engdahl, Christopher J.
• Application Number:
  US11/980,865
• Publication Number:
  US 20090109857A1
• Time in Patent Office: Days
• US Class Current: 370/241
• CPC Class Codes: G06F 11/324 Display of status information
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3476 Data logging G06F11/14, G06F11/2205 take precedence
• CPC Class Codes: G06F 11/349 for interfaces, buses

Abstract

A connection monitor utility may monitor the availability of various resources, display a status, and provide various optimization functions for each resource. Performance data may be collected and displayed, and the performance data may be used to optimize, troubleshoot, and notify administrators or users for each connection. Some embodiments may store optimized parameters for connections from different locations. In one use model, the monitor utility may be used with a secure connection to a private network to provide visual feedback of connectivity to various resources and simple optimization of the connections.

Claims

1. A method comprising:

collecting performance data between a client device and a plurality of remote services, said remote services being application layer services;

for each of said plurality of remote services, performing a method comprising;

storing said performance data;

changing at least one communication variable from a first value to a second value;

determining if said first value or said second value resulted in better performance to determine a preferred value; and

saving said preferred value;

determining a summarized status for each of said remote services; and

displaying at least a portion of said summarized status.

2. The method of claim 1 further comprising:

defining a set of optimized connection settings, said set of optimized connection settings being individual settings associated with each of said plurality of remote services; and

storing said set of optimized connection settings.

3. The method of claim 2 further comprising:

defining a location for said set of optimized connection settings; and

storing said location with said set of optimized connection settings.

4. The method of claim 3 further comprising:

storing a first of said set of optimized connection settings for a first location; and

storing a second of said set of optimized connection settings for a second location.

5. The method of claim 4 further comprising:

determining a current location;

selecting one of said sets of optimized connection settings corresponding to said current location; and

operate said plurality of remote services using said one of said sets of optimized connection settings.

6. The method of claim 5, said current location being determined at least in part by a network address.

7. The method of claim 1, said collecting performance data comprising executing a ping command to one of said remote services.

8. The method of claim 1, said collecting performance data comprising executing an LDAP query to one of said remote services.

9. A computer readable medium comprising computer executable instructions adapted to perform the method of claim 1.

10. A device comprising:

a data collection engine having a connection test mechanism adapted to transmit a communication to a remote service, receive a communication from said remote service, and determine at least one performance parameter for a connection to said remote service;

a data analyzer adapted to summarize said at least one performance parameter into a summary parameter; and

a display adapted to show at least one of said summary parameters.

11. The device of claim 10 further comprising:

a connection optimizer adapted to perform at least one optimization of said connection to said remote service to determine an optimized setting for said connection to a remote service.

12. The device of claim 11 further comprising:

a configuration manager adapted to store said set of configuration parameters for each of said remote services.

13. The device of claim 12 further comprising:

a location identifier adapted to determine a location for said device;

said configuration manager further adapted to store said location with said set of configuration parameters.

14. The device of claim 13, said location being a network location.

15. The device of claim 13, said location being a geographical location.

16. The device of claim 13, said configuration manager further adapted to:

store a first set of configuration parameters for a first location; and

store a second set of configuration parameters for a second location.

17. The device of claim 16, said configuration manager further adapted to:

receive a location designator;

retrieve one of a plurality of sets of configuration parameters corresponding to said location designator; and

operate said remote service using said one of a plurality of sets of configuration parameters.

18. The device of claim 17, said location designator being determined at least in part by a network address.

19. The device of claim 10, at least one of said performance parameters being determined as a result of a ping command.

20. The device of claim 10, at least one of said performance parameters being determined as a result of an LDAP query.