State replication

• US 7,680,908 B2
• Filed: 09/28/2006
• Issued: 03/16/2010
• Est. Priority Date: 09/28/2006
• Status: Expired due to Fees

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Cheng, Lili, Meijer, Henricus Johannes Maria, Ozzie, Raymond E., Flake, Gary W., Gates, William H. III, Larus, James R., Gounares, Alexander G., Glasser, Daniel S., Mital, Amit, Snyder, Ira L. Jr., Mishra, Debi P., Dani, Nishant V., Thekkath, Chandramohan A.
• Primary Examiner(s): Chan; Wing F
• Assistant Examiner(s): Yi; David
• Application Number:
  US11/536,520
• Publication Number:
  US 20080082652A1
• Time in Patent Office: 1,265 Days
• Field of Search: 709201-203, 709223-228, 709/208
• US Class Current: 709/220
• CPC Class Codes: H04L 67/53 using third party service providers
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

The claimed subject matter provides systems and/or methods that facilitate replicating a state associated with a client, user, service, application, and the like. A third party service provider can support any number of services that can be concurrently requested by several clients without user perception of degraded computing performance as compared to conventional systems/techniques due to improved connectivity and mitigated latencies. A replication component can generate replicas of states associated with requested services. Further, the replicas can facilitate seamlessly interacting with the third party service provider (e.g., while transitioning between client devices). Additionally, by providing replicas of the state related information, differing third party service providers can effectuate services based upon a request from a client without regenerating the state.

Claims

1. A system that facilitates replicating a state associated with a third party service provider, comprising:

a processor;

a memory, on which are stored processor executable instructions, which when executed by the processor cause the system to replicate the state associated with the third party service provider;

a service component that effectuates performing a service supported by the third party service provider in response to a request obtained from a first client device;

a replication component that generates a replica of a state associated with the service, wherein the replica facilitates seamless interaction with the third party service provider; and

a migration component that shifts performance of computational tasks performed by the first client device to a second client device based at least in part by;

recognizing a user ID associated with both the first client device and the second client device;

determining if the second client device is in physical proximity to the first client device;

generating a suggestion to a user of the first client device to transition to the second client device;

receiving input, in response to the suggestion, of a single button click directing transfer of the third party service to the second client device;

transferring the state from the first client device to the second client device via utilizing the replica; and

redistributing a computational split, after shifting performance of computational tasks to the second client, of computational tasks performed by the client device versus computational tasks performed by the third party service provider, wherein the redistributing is based on differences resulting from migration from first client device to second client device; and

a user interface, wherein the user interface presents the service provided by the third party service provider for display on the second client device, and wherein the user interface changes, based on;

a prediction of upcoming data; and

a consideration of characteristics of the second client device, including display size and processor limitations.

2. The system of claim 1, the replication component yields the replica of the state of a computational task.

3. The system of claim 2, the computational task utilizes the replica of its own state.

4. The system of claim 1, the replication component marks a portion of the state to be replicated and generates the replica that corresponds to the portion.

5. The system of claim 1, the replication component enables sharing a portion of the generated replica.

6. The system of claim 1, the replication component generates the replica of the state a plurality of times.

7. The system of claim 1, the replication component replicates a distributed state split between the first client device and at least one disparate client device.

8. The system of claim 1, further comprising a rendering component that outputs data utilized to yield per client device rendering of content.

9. The system of claim 1, further comprising an archive component that retains data provided to the service component and generated by the service component, the data being aggregated from the replicated state of a plurality of services.

10. The system of claim 1, the replica enables resuming the state.

11. A method that facilitates migrating, from a first client device to a second client device, computational tasks performed in connection with a third party service provider, comprising:

storing, in a memory communicatively coupled to a processor, computer-executable instructions for performing the method that facilitates migrating, from the first client device to the second client device, computational tasks performed in connection with a third party service provider;

executing the instructions on the processor;

according to the instructions being executed;

generating a replica of a state associated with a service supported by the third party service provider on the first client device; and

migrating computational tasks associated with the service, from the first client device to the second client device, by employing the replica of the state to provide state continuity, wherein the migrating comprises;

recognizing a user ID associated with both the first client device and the second client device;

determining if the second client device is in physical proximity to the first client device;

generating a suggestion to a user of the first client device to transition to the second client device;

receiving input, in response to the suggestion, of a single button click directing transfer of the third party service to the second client device;

transferring the state from the first client device to the second client device consistent with the replica;

redistributing a computational split, after migrating computational tasks from the first client to the second client, of computational tasks performed by the client device versus computational tasks performed by the third party service provider, wherein the redistribution is based on differences resulting from migration from first client device to second client device; and

changing a user interface, presenting the service provided by the third party service provider to the second client device, based on;

a prediction of upcoming data; and

a consideration of characteristics of the second client device, including display size and processor limitations.

12. The method of claim 11, generating the replica further comprises evaluating data obtained by the third party service provider from one or more client devices requesting the service and data related to the service effectuated by the third party service provider.

13. The method of claim 11, further comprising inferring whether to migrate the computational tasks based upon one or more of a permission, characteristics of the disparate client devices, and an upcoming event.

14. The method of claim 11, further comprising rendering a tailored user interface based upon characteristics of a client utilized for presentation.

15. The method of claim 11, further comprising accessing a consistent set of data by utilizing the replica of the state.

16. A system that facilitates replicating a state associated with at least one of a client, a user, a service, and an application, comprising:

means for processing instructions within a computing environment;

means for storing the instructions on a memory, which when executed by a processor within the computing environment cause the system to replicate a state associated with at least one of a client, a user, a service, and an application;

means for receiving a request to perform a service supported by a third party service provider from a client device;

means for performing the requested service;

means for generating a replica of a state associated with the service on the first client device while performing the service on the first client device; and

means for migrating computational tasks associated with the service, from the first client device to the second client device, by employing the replica of the state to provide state continuity, wherein the migrating comprises;

means for recognizing a user ID associated with both the first client device and the second client device;

means for determining if the second client device is in physical proximity to the first client device;

means for generating a suggestion to a user of the first client device to transition to the second client device;

means for receiving input, in response to the suggestion, of a single button click directing transfer of the third party service to the second client device;

means for transferring the state from the first client device to the second client device consistent with the replica; and

means for redistributing a computational split, after migrating computational tasks to the second client, of computational tasks performed by the client device versus computational tasks performed by third party service provider, wherein the redistributing is based on differences resulting from migration from the first client device to the second client device; and

means for changing a user interface, presenting the service provided by the third party service provider to the second client device, based on;

a prediction of upcoming data; and

a consideration of characteristics of the second client device, including display size and processor limitations.