DETERMINATION OF OPTIMIZED LOCATION FOR SERVICES AND DATA

• US 20080080497A1
• Filed: 12/20/2006
• Published: 04/03/2008
• Est. Priority Date: 09/28/2006
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Cheng, Lili, MacLaurin, Matthew B., Meijer, Henricus Johannes Maria, Flake, Gary W., Bolosky, William J., Larus, James R., Blinn, Arnold N., Gounares, Alexander G., Snyder, Ira L., Mital, Amit, Mishra, Debi P., Connolly, Michael, Treadwell, David R.
• Granted Patent: US 8,719,143 B2
• Time in Patent Office: Days
• US Class Current: 370/389
• CPC Class Codes: G06F 11/202 where processing functionality is redundant redundant communication control functionality G06F11/2005, redundant storage control functionality G06F11/2089
• CPC Class Codes: G06F 16/214 Database migration support
• CPC Class Codes: G06Q 30/0611 Request for offers or quotes
• CPC Class Codes: G06Q 30/08 Auctions
• CPC Class Codes: G06Q 40/00 Finance; Insurance; Tax strategies; Processing of corporate or income taxes

Abstract

The claimed subject matter provides a system and/or a method that facilitates preserving and maintaining data and/or services associated with a network service. The network service can be any collection of resources that are maintained by a party (e.g., third-party, off-site, etc.) and accessible by an identified user over a network (e.g., WAN, Internet, etc.). An interface component can receive a termination notification related to the network service. An executor component can relocate at least a portion of one of data and a service associated with the terminated network service to a disparate replacement network service in order to preserve any services and/or data related therewith.

Claims

1. A system that facilitates maintaining data associated with a network service, comprising:

an interface that receives a request to migrate a portion of data associated with a network service; and

an executor component that transfers the portion of data associated with the network service to a disparate entity.

2. The system of claim 1, the portion of data is at least one of metadata related to the network service, code, a service provided by the network service, a portion of service provided by the network service, service replication, service transfer, a module for adapting data from the network service to the disparate entity, and a portion of code for transforming data to the disparate entity.

3. The system of claim 1, the executor component employs data insurance for the portion of data, the data insurance protects insured portions of data in event of a termination of the network service.

4. The system of claim 3, the termination of the network service is based on at least one of a retirement, a bankruptcy, a buy-out, a dissolution, the network service dissolving, the network service terminated, the network service terminating, the network service dissolving, filing bankruptcy, a closing, a shut down, a strike, a buyout, the network service ceases to exist, a planned dissolution, a termination of services based on geography, a re-structuring, a user wanting a cheaper rate, a user desiring a better service, a machine deterioration, a virus infections, and a replacement of at least one of a machine and a service.

5. The system of claim 3, the insured portion of data is placed in a data service escrow upon the termination of the network service.

6. The system of claim 5, the executor component solicits at least one offer from at least one of an entity, a company, a disparate network service, a participant, and a user for a right to the insured portion of data in the data service escrow.

7. The system of claim 5, the solicited offer is approved by an owner of the insured portion of data.

8. The system of claim 3, further comprising at least one ownership policy associated with the portion of data between users, companies, entities, network services, and participants, wherein ownership is based at least in part upon a service agreement with an end user.

9. The system of claim 8, the ownership policy corresponds to at least one of a log on name, user identification, and an account.

10. The system of claim 1, further comprising a data transformation component that adapts data to the disparate entity for implementation.

11. The system of claim 10, the data transformation component manipulates at least one of proprietary data and an algorithm underlying the network service to the disparate entity for seamless integration.

12. The system of claim 11, the executor component is extensible allowing the data transformation component to be pluggable thereto.

13. The system of claim 1, the executor component employs at least one of encryption and key management such that the system is traversed by at least one of RSA encryption, and a sequence of decryption and encryption operations securing the portion of data.

14. The system of claim 1, the web application is implemented within the network service and retains state within the network service;

the network service is a resource that is maintained by a party and accessible by an identified user over a network.

15. The system of claim 14, the party is at least one of a third-party, a second-party, and an off-site party.

16. The system of claim 1, the portion of data corresponds to a group, the group can include a user, a machine, a computer, an individual, employees, and a delinquent user.

17. A computer-implemented method that facilitates transporting data related to a network service, comprising:

receiving a request to migrate a portion of data associated with a network service; and

transferring the portion of data associated with the network service to a disparate entity.

18. The method of claim 17, further comprising:

implementing data insurance in case of a termination of the network service;

placing the insured portion of data in a data escrow service;

soliciting an offer from a plurality of companies for a right to the insured portion of data;

approving at least one of the offer and the company who receives the right to the insured portion of data;

migrating the insured portion of data to the approved company who received the right to the insured portion of data;

transforming at least one of an algorithm and proprietary data related to the network service to the approved company; and

providing an analogous service in comparison to the terminated network service.

19. The method of claim 17, the portion of data is at least one of metadata related to the network service, code, a service provided by the network service, a portion of service provided by the network service, service replication, service transfer, a module for adapting data from the network service to the disparate entity, and a portion of code for transforming data to the disparate entity.

20. A computer-implemented system that facilitates maintaining data associated with a network service, comprising:

means for receiving a request to migrate a portion of data associated with a network service;

means for transferring the portion of data associated with the network service to a disparate entity;

means for implementing data insurance in case of a termination of the network service;

means for employing a data escrow service; and

means for soliciting an offer from a plurality of companies for a right to the insured portion of data.