Microsoft Technology Licensing, LLC

Cisco Technology, Inc.

Alex Hopmann

Brian J Deen

Joel Mathew Soderberg

Sean O Lyndersay

Matthew Tebbs

Nick Holt

Brett Marl

Steven M Bush

Joel Hynoski

Joel Matthew Soderberg

Ashley Colin Yakeley

A tool for managing a network of interconnected devices. The tool may provide a user with an interface that allows the user to view the type and status of each network device (that is, each device connected to the network), and even the status of the network itself. The tool may alternately or additionally provide a user with services related to the network. such as allowing a user to perform one or more tasks associated with devices in the network.

Network administration tool employing a network administration protocol

A network device management tool that allows a client, such as a network management tool or network device setup utility, to reliably obtain information about a network device. Variations of the network device management tool may alternately or additionally allow a client to deliver information to the network device, such as instructions to control the operation of the network device. The network device management tool may be incorporated into the network device.

Network device management

Methods and computer program products for using a front-end server to access content stored on one or more back-end servers. The front-end server receives requests for content from client systems. Back-end servers store the content, but to the client system, it appears as if the front-end server is the content's source. Upon receiving the request, the front-end server checks the validity of the request and examines a global catalog that dynamically maps client system requests to the back-end server or servers that store the requested content. In some circumstances, the content will be stored at a single back-end server and the front-end server directs the request to that server. Alternatively, a list of back-end servers storing the requested content may be generated. If so, the front-end then uses an authentication token as a key to a hash operation that is performed on the list and a single server that is capable of satisfying the request for content is identified. A given request and authentication token always identify the same server if the list of servers available for providing the requested content remains the same. The front-end server provides a single source for content requests so that client systems are not required to alter requests or invalidate local caches when content is moved from one back-end server to another. The front-end server also provides an additional level of security for back-end servers.

Routing client requests to back-end servers

A method for efficiently sending notifications over a network. A client system requests to be notified when an event occurs. A server system receives the requests and monitors for the occurrence of the event. When the event occurs a single packet using a connectionless protocol (such as User Datagram Protocol) is sent to the client to notify the client of the occurrence of the event. Using a connectionless protocol to send notification reduces the overall amount of data on the network and thus reduces network congestion and the processing capacity of the server and client. When the client system receives notification an attempt to establish a connection using as connection-oriented protocol is executed. Additional data associated with the occurrence of the event is transferred over the connection. The server may repeatedly send notification using a connectionless protocol until a connection using a connection-oriented protocol is established. The server may send notification that notifies the client of the occurrence of multiple events simultaneously within a single packet. The server may also notify multiple applications of the occurrence of an event using a single notification.

Efficiently sending event notifications over a computer network

Methods and systems for efficiently sending notification of the occurrence of events through a firewall. A client system operating inside a firewall, attempts to receive notification of the occurrence of events from a server system operating outside the firewall. The client system attempts to receive communication from the server system using a connectionless protocol, such as UDP. If the client system receives communication using the connectionless protocol, the client system requests notification be sent using the connectionless protocol. The server system notifies the client system by sending a packet to the server system, using the connectionless protocol, when events occur. However, if the client does not receive communication using the connectionless protocol, the client requests notifications be sent using a connection-oriented protocol, such as TCP. If the client system requests notification using a connection-oriented protocol, the client system polls the server system to receive notification of the occurrence of events.

Sending notification through a firewall over a computer network

Systems and methods for directing client requests and for selecting a back end server to service client requests. A front end server receives client requests and based on the URI of the requests, directs the request to a back end server. The client request can be for a private or a public folder and each back end server typically stores both private and public folders. If the request is for a private folder, then the front end server determines which server stores that user's private folder and directs the client request to that folder. If the request is for a home public folder, the front end server directs the client request to the server that is associated with the private folders of the users. If the request is for an application public folder, then the front end server selects one of the back end servers to service the client request. Advantageously, the front end server always directs the client request to the same server. If the selected server is unavailable, then the front end server is capable of redirecting the client request to an available server.

Selecting a server to service client requests

Methods and computer program products for transparently redirecting a request for content such that a client system is unaware of the redirection. A client requests content through a front-end server that provides a single point of access for content stored on one or more back-end servers. The single point of access makes it so the client does not know and does not care which particular back-end server stores the requested content. When a back-end server provides a redirect response for content that the back-end server does not store, the front-end server receives the redirect response and reissues the request to a server identified in the redirect response. A front-end server indicator is added to requests so that the back-end server knows the request is from a front-end server. This allows the back-end server to provide a list of servers in the redirect response without causing errors in clients making direct requests to back-end servers when the clients are unable to process a list of servers contained in a redirect response.

System and method for transparently redirecting client requests for content using a front-end indicator to preserve the validity of local caching at the client system

Growing community of inventors

Seattle, WA, United States of America

Alex Hopmann