Distributed computing services platform

• US 7,454,462 B2
• Filed: 01/31/2005
• Issued: 11/18/2008
• Est. Priority Date: 06/22/2000
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Campbell, David G., Mital, Amit, Short, Keith W., Capps, Steve, Lucovsky, Mark H., Singh, Kaviraj, Spiro, Peter M., Cellini, Steven M., Rudder, Eric D., Maritz, Paul A., Vaskevitch, David, Fitzgerald, Charles T., Trower, Tandy W., Belfiore, Joseph D., Gundotra, Vivek
• Primary Examiner(s): BARQADLE, YASIN M
• Application Number:
  US11/047,209
• Publication Number:
  US 20050246415A1
• Time in Patent Office: 1,387 Days
• Field of Search: 709 17-219, 709227-231, 709238-241, 709/245
• US Class Current: 709/203
• CPC Class Codes: G06F 16/256 in federated or virtual databases
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 9/451 Execution arrangements for user interfaces
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1029 using data related to the state of servers by a load balancer
• CPC Class Codes: H04L 67/1031 Controlling of the operation of servers by a load balancer, e.g. adding or removing servers that serve requests
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms

Abstract

A server federation cooperatively interacts to fulfill service requests by communicating using data structures that follow a schema in which the meaning of the communicated data is implied by the schema. Thus, in addition to the data being communicated, the meaning of the data is also communication allowing for intelligent decisions and inferences to be made based on the meaning of the data. Cooperative interaction is facilitated over a wide variety of networks by messaging through a common API that supports multiple transport mechanisms. Also, mid-session transfer between client devices is facilitated by schema and the transport-independent messaging structure. The user interfaces of the client devices will appear consistent even if the client devices have different user interface capabilities.

Claims

1. In a network that includes a plurality of servers that communicate with a plurality of client devices including a first client device and a second client device, a method for facilitating a mid-session transition between the first client device and the second client device, the method comprising the following:

retrieving state information stored on at least one server;

interacting in a session with the first client device resulting in an update of the state information;

storing the updated information on the at least one server, wherein the state information is stored on the at least one server utilizing a data structure that follows a schema recognized by the plurality of servers and the first and second client devices, wherein the meaning of the state information is implied by the schema;

retrieving the updated state information when the session is continued on the second client device; and

interacting in the continued session with the second client device based on the updated state information,

wherein the plurality of servers comprises a server federation, wherein the acts of retrieving state information, interacting in a session with the first client device, storing the updated information, retrieving the updated state information, and interacting in the continued session are cooperatively performed by two or more servers of the server federation.

2. A method in accordance with claim 1, further comprising the following:

authenticating a user of the first client device before allowing the state information to be updated in response to interacting in the session with the first client device.

3. A method in accordance with claim 2, further comprising the following:

authenticating a user of the second client device as being the same user as the user of the first client device before interacting in the continued session with the second client device.

4. A method in accordance with claim 1, wherein the data structure is structured in accordance with an extensible Markup Language (XML).

5. A method in accordance with claim 1, wherein at least a portion of the state information includes user interface information, wherein interacting in a session with the first client device comprises the following:

determining first user interface characteristics of the first client device; and

providing a first set of the user interface information to the first client device, the first set of the user interface information tailored towards the first user interface characteristics.

6. A method in accordance with claim 5, wherein interacting in the continued session with the second client device comprises the following:

determining second user interface characteristics of the second client device; and

providing a second set of the user interface information to the second client device, the second set of user interface information tailored towards the second user interface characteristics.

7. A method in accordance with claim 6, wherein the first and second client devices have the same user interface capabilities, wherein the first and second sets of state information comprise substantially the same user interface information thereby allowing the first and second client devices to display the same information.

8. A method in accordance with claim 6, wherein the first and second client devices have different user interface capabilities, wherein the first and second sets of user interface information are different.

9. A method in accordance with claim 8, wherein interacting in a session with the first client device comprises the following:

interacting in the session with a personal computer.

10. A method in accordance with claim 9, wherein the personal computer comprises a first personal computer, wherein interacting in the continued session with the second client device comprises the following:

interacting in the continued session with a second personal computer.

11. A method in accordance with claim 9, wherein interacting in the continued session with the second client device comprises the following:

interacting in the continued session with a mobile telephone.

12. A method in accordance with claim 8, wherein interacting in a session with the first client device comprises the following:

interacting in the session with a mobile telephone.

13. A method in accordance with claim 12, wherein the mobile telephone comprises a first mobile telephone, wherein interacting in the continued session with the second client device comprises the following:

interacting in the continued session with a second mobile telephone.

14. A method in accordance with claim 12, wherein interacting in the continued session with the second client device comprises the following:

interacting in the continued session with a personal computer.

15. A method in accordance with claim 1, further comprising the following:

at least temporarily ceasing interacting in the session with the first client device, wherein interacting in the continued session with the second client device occurs after at least temporarily ceasing interaction in the session with the first client device.

16. A method in accordance with claim 1, wherein retrieving state information stored on at least one server comprises the following:

retrieving preference information stored on the at least one server.

17. A method in accordance with claim 1, wherein storing the updated information on the at least one server comprises the following:

storing session status information for the session on the at least one server.

18. A computer program product for use in a network that includes a plurality of servers that communicate with a plurality of client devices including a first client device and a second client device, the computer program product for implementing a method for facilitating a mid-session transition between the first client device and the second client device, the computer program product comprising a physical computer-readable storage medium having stored thereon the following:

computer-executable instructions for detecting the receipt of state information stored on at least one server;

computer-executable instructions for causing interaction in a session with the first client device;

computer-executable instructions for causing the state information to be updated in response to interaction in the session with the first client device;

computer-executable instructions for causing the updated information to be stored on the at least one server, wherein the state information is stored on the at least one server utilizing a data structure that follows a schema recognized by the plurality of servers and the first and second client devices, wherein the meaning of the state information is implied by the schema;

computer-executable instructions for detecting the receipt of the updated state information when the session is continued on the second client device; and

computer-executable instructions for causing interaction in the continued session with the second client device based on the updated state information,

wherein the plurality of servers comprises a server federation, wherein the acts of retrieving state information, interacting in a session with the first client device, storing the updated information, retrieving the updated state information, and interacting in the continued session are cooperatively performed by two or more servers of the server federation.