Methods, systems, architectures and data structures for delivering software via a network

• US 6,883,168 B1
• Filed: 06/21/2000
• Issued: 04/19/2005
• Est. Priority Date: 06/21/2000
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Raman, Suryanarayanan V., Sanchez, Lawrence M., Licata, John A., Syme, Brian J., James, Sarita M.
• Primary Examiner(s): Zhen, Wei Y.
• Application Number:
  US09/599,299
• Time in Patent Office: 1,763 Days
• Field of Search: 717168-178
• US Class Current: 717/178
• CPC Class Codes: G06F 8/60 Software deployment
• CPC Class Codes: G06F 9/44526 Plug-ins; Add-ons

Abstract

Methods and systems for network-based or Internet-based software delivery are described. In one embodiment, an application program or software platform resides on a client. The program or platform is configured so that it is extensible based on software extensions that are deliverable over a network such as the Internet. Various extensions can be developed by third party developers for incorporation into the program or platform. In the described embodiment, extension files that comprise a software extension are hosted on an Internet server. Additional files are also hosted on the Internet server and describe aspects of the software extension. These additional files include files that describe a logical attachment of the extension to the program or platform, as well as files that describe the location of the extension files. Extensions are incorporated on a client by navigating to a particular Internet site through which the extensions can be accessed. The files describing the extension files are downloaded on the client. These files tell the client where the particular extension is to be plugged in, as well as where to find the appropriate extension files and how to download them. The extension files are then downloaded and incorporated into the program or platform.

Claims

1. A method for delivering software via a network comprising:

describing one or more software extensions using a hierarchical language, the extensions being configured for incorporation on a client, said describing defining one or more manifests containing at least one list of files comprising an extension; and

delivering the one or more manifests to the client via the network, the one or more manifests being configured for use in downloading the software extensions via the network, at least some of the extensions being downloadable by streaming extension files to the client in a manner that enables a user to begin to interact with the extension sooner than if the user had to wait for the entire extension to load, said manner being developed based on scenario runs in which files that are more likely to be first used by the user are downloaded before files that are less likely to be first used, and wherein files that are less likely to be used first can be downloaded via a background download process.

2. The method of claim 1, wherein the one or more manifests are configured to assist in organizing delivery of individual files listed in the one or more manifests.

3. The method of claim 1, wherein the one or more manifests are configured to assist in validating individual files listed in the one or more manifests.

4. The method of claim 1, wherein the one or more manifests are configured to assist in updating individual files listed in the one or more manifests.

5. The method of claim 1, wherein the one or more manifests describe individual file locations.

6. The method of claim 1, wherein the one or more manifests contain individual hashes for one or more of the listed files.

7. The method of claim 1, wherein the one or more manifests contain download directives for downloading the listed files.

8. The method of claim 1, wherein the one or more manifests are defined in a tag-based language.

9. The method of claim 1, wherein the one or more manifests are defined in extensible markup language (XML).

10. The method of claim 1, wherein the network comprises the Internet.

11. One or more computer-readable media comprising computer-readable instructions thereon which, when executed by a computer, cause the computer to implement the method of claim 1.

12. A computer programmed with instructions which, when executed by the computer, implemented the method of claim 1.

13. One or more computer-readable media comprising computer-readable instructions thereon which, when executed by a computer, cause the computer to:

describe one or more software extensions using extensible markup language (XML), the extensions being configured for incorporation on a client, said describing defining a manifest containing at least one list of files comprising an extension, the manifest being configured to assist in one or more of the following;

organizing delivery of individual files listed in the manifest, validating individual files listed in the manifest, and updating individual files listed in the manifest; and

deliver the manifest to the client via the network, at least some of the extensions being downloadable by streaming extension files to the client in a manner that enables a user to begin to interact with the extension sooner than if the user had to wait for the entire extension to load, said manner being developed based on scenario runs in which files that are more likely to be first used by the user are downloaded before files that are less likely to be first used, and wherein files that are less likely to be used first can be downloaded via a background download process.

14. A method for receiving software via a network comprising:

receiving a manifest that contains at least one list of files comprising a software extension that is to be downloaded via a network and incorporated on a client, the manifest being defined in extensible markup language (XML), the manifest being configured to assist in;

organizing delivery of the files,

validating individual files listed in the manifest, and

updating individual files listed in the manifest; and

downloading files from the list of files contained in the manifest;

wherein the extension is downloadable by streaming extension files to the client in a manner that enables a user to begin to interact with the extension sooner than if the user had to wait for the entire extension to load, said manner being developed based on scenario runs in which files that are more likely to be first used by the user are downloaded before files that are less likely to be first used, and wherein files that are less likely to be used first can be downloaded via a background download process.

15. The method of claim 14, wherein the software extension is to be incorporated into a software platform executing on the client.

16. The method of claim 14, wherein the downloading of the files takes place by downloading the files in an order that is described in the manifest.

17. The method of claim 14 further comprising validating one or more downloaded files using the manifest.

18. The method of claim 14 further comprising updating one or more files using the manifest.

19. One or more computer-readable media comprising computer-readable instructions thereon which, when executed by a computer, cause the computer to implement the method of claim 14.

20. A computer programmed with instructions which, when executed by the computer, implement the method of claim 14.

21. A method of providing software via a network comprising:

describing one or more software extensions using one or more extensible markup language (XML) files, the extensions being configured for incorporation in a software program executing on a client, individual XML files providing individual manifests that contain a list of files that comprise an extension; and

storing the XML files in a Web-accessible location;

wherein at least some of the extensions are downloadable by streaming extension files to the client in a manner that enables a user to begin to interact with the extension sooner than if the user had to wait for the entire extension to load, said manner being developed based on scenario runs in which files that are more likely to be first used by the user are downloaded before files that are less likely to be first used, and wherein files that are less likely to be used first can be downloaded via a background download process.

22. The method of claim 21 further comprising storing extension files associated with the XML files in a Web-accessible location.

23. The method of claim 21 further comprising:

storing extension files associated with the XML files in a Web-accessible location; and

providing one or more XML files and one or more associated extension files to a client via the network.

24. The method of claim 21, wherein individual manifests can contain one or more file bashes that can be used for file security.

25. The method of claim 21, wherein individual manifests can contain one or more file hashes that can be used for versioning.

26. The method of claim 21, wherein individual manifests comprise one or more file groups that determine when particular files are downloaded to the client.

27. The method of claim 26, wherein the file groups determine where files are stored on the client.

28. The method of claim 26, wherein the file groups determine how files are packaged.

29. The method of claim 26, wherein the file groups determine where files are stored on the client and how files are packaged.

30. One or more computer-readable media having computer-readable instructions thereon which, when executed by a computer, cause the computer to implement the method of claim 21.

31. An automated software tool comprising a package manifest creation tool configured to:

receive one or more input parameters pertaining to a package manifest that is to describe a software extension that is configured to extend a software application executing on a client; and

generate a package manifest that describes the extension, the package manifest being generated using a hierarchical language;

wherein the extension is downloadable by streaming extension files to the client in a manner that enables a user to begin to interact with the extension sooner than if the user had to wait for the entire extension to load, said manner being developed based on scenario runs in which files that are more likely to be first used by the user are downloaded before files that are less likely to be first used, and wherein files that are less likely to be used first can be downloaded via a background download process.

32. The automated software tool of claim 31, wherein the hierarchical language comprises a tag-based language.

33. The automated software tool of claim 31, wherein the hierarchical language comprises extensible markup language (XML).

34. The automated software tool of claim 31, wherein one input parameter specifies a directory containing files that are to be described in the package manifest.

35. The automated software tool of claim 31, wherein one input parameter comprises file group information and load dependencies.

36. The automated software tool of claim 31, wherein one input parameter comprises file usage statistics.

37. The automated software tool of claim 36, wherein the file usage statistics are ascertained from scenario runs.

38. The automated software tool of claim 37, wherein individual scenarios have individual priorities.

39. The automated software tool of claim 36, wherein the file usage statistics are ascertained from scenario runs that are collected by running logs on various scenarios.

40. The automated software tool of claim 36, wherein the file usage statistics are ascertained from scenario runs that are collected by running logs on various scenarios, the scenarios having individual checkpoints that separate one scenario from another.

41. The automated software tool of claim 36, wherein the file usage statistics are ascertained dynamically by building a knowledge base that describes tasks that users typically accomplish.