Mechanism for downloading software components from a remote source for use by a local software application

• US 20040003389A1
• Filed: 06/05/2002
• Published: 01/01/2004
• Est. Priority Date: 06/05/2002
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Broman, Paul, Jones, Brian, Little, Robert, Reynar, Jeff
• Granted Patent: US 7,281,245 B2
• Time in Patent Office: Days
• US Class Current: 717/178
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57

Abstract

A method and system are provided for downloading software components from a remote source to a software application for providing updates or additions to the application'"'"'s functionality. All components and files that may be utilized to update or add to functionality available to the application are identified and are assembled on a manifest that may be located on a remote web server accessible by the application. If components of the application should be updated, or corrections or improvements to existing components are available, or new functionality is available that will transform the user'"'"'s existing application and document into a “smart” application and “smart” document, the application may connect to the web server to download the required components.

Claims

1. A method of downloading software components from a remote source to a software application for providing updates or additions to application and document functionality, comprising the steps of:

attaching a schema to a document defining permissible data content, data type and data structure for the document;

structuring the document to associate the document with the schema;

associating a solution with the document structure;

assembling a plurality of software components comprising the solution at a location remote from the document;

enabling the document to call the solution to obtain functionality provided by the plurality of software components; and

downloading the plurality of software components to the application for provision of the functionality to the document.

2. The method of claim 1, whereby the step of enabling the document to call the solution to obtain functionality provided by the plurality of software components includes:

attaching a solution property to the document for pointing the document to the solution; and

attaching a solution location to the document for enabling the document to locate the solution at the remote location.

3. The method of claim 2, whereby the solution location includes a uniform resource locator (URL) for the solution.

4. The method of claim 2, whereby the step of attaching a solution property to the document further comprises attaching a plurality of solution properties to the document to associate a plurality of subsets of the solution with particular portions of the document.

5. The method of claim 4, further comprising the steps of:

listing the solution and the plurality of software components in a manifest of software components; and

storing the manifest in a remote library of software components on a remote server accessible by the document.

6. The method of claim 5, further comprising the step of:

attaching a schema to the manifest for defining permissible data content, data type and data structure of the manifest and for associating the solution with the document.

17. The method of claim 5, prior to the step of downloading the software components to the application, receiving at the remote server a command from the application to download the software components to the application.

7. The method of claim 7, prior to the step of downloading the software components to the application, further comprising the steps of:

determining whether the plurality of software components for providing the solution is present in a local library of software components; and

if the plurality of software components is not present in the local library of software components, calling the manifest at the remote library of software components for obtaining the solution.

8. The method of claim 7, prior to the step of determining whether the plurality of software components for providing the solution is present in a local library of software components, further comprising determining whether the document includes solution properties pointing to more than one solution.

9. The method of claim 8, whereby if the document includes solution properties pointing to more than one solution, selecting for downloading from the remote server software components associated with one of the more than one solutions.

10. The method of claim 7, prior to the step of downloading the software components to the application, receiving a query to determine whether the plurality of software components should be downloaded.

11. The method of claim 10, whereby the step of receiving a query to determine whether the plurality of software components should be downloaded, includes receiving a notification that the plurality of software components have been updated at the remote server.

12. The method of claim 11, further comprising:

causing the notification to be sent from the manifest upon the occurrence of an update to any of the plurality of software components.

13. The method of claim 12, further comprising:

causing the notification to be sent from the manifest at a prescribed frequency.

14. The method of claim 13, whereby the prescribed frequency is set by the creator of the manifest.

15. The method of claim 11, whereby the step of receiving a query to determine whether the plurality of software components should be downloaded, includes receiving a notification that additional software components have been added to the plurality of software components stored at the remote server.

16. The method of claim 11, whereby the step of receiving a query to determine whether the plurality of software components should be downloaded, includes receiving a notification that a set amount of time has elapsed since the last download of the plurality of software components to the application.

18. The method of claim 10, whereby the command from the application to download the software components to the application is initiated by a user of the application.

19. The method of claim 7, whereby prior to the step of downloading the software components to the application, connecting the software application to the remote server.

20. The method of claim 19, whereby the step of connecting the software application to the remote server includes connecting the software application to the remote server via the Internet.

21. The method of claim 19, whereby the step of connecting the software application to the remote server includes connecting the software application to the remote server via an intranet.

22. The method of claim 19, whereby the step of connecting the software application to the remote server includes connecting the software application to the remote server via a distributed computing environment.

23. The method of claim 22, whereby the distributed computing environment includes a wireline telecommunications network.

24. The method of claim 22, whereby the distributed computing environment includes a wireless telecommunications network.

25. The method of claim 19, whereby the step of connecting the software application to the remote server includes connecting the software application to the remote server via a local area network.

26. The method of claim 7, prior to downloading the software components to the document, checking the security of the manifest.

27. The method of claim 26, whereby if the security of the manifest cannot be checked, preventing the step of downloading the software components to the document.

28. The method of claim 27, whereby the step of checking the security of the manifest includes determining whether the manifest is located at a trusted remote site.

29. The method of claim 27, whereby the step of checking the security of the manifest includes determining whether the manifest is from a trusted intranet.

30. The method of claim 27, whereby the step of checking the security of the manifest includes determining whether digital signature applied to the manifest matches a trusted digital signature.

31. The method of claim 30, whereby the digital signature applied to the manifest includes a particular digital signature applied to each of a plurality of files included on the manifest.

32. The method of claim 19, after the step of connecting the software application to the remote server, further comprising:

obtaining a checksum value representing the contents of the manifest;

comparing the checksum value representing the contents of the manifest with a checksum value representing the contents of the manifest after the contents of the manifest have been received by the application, but before the contents of the manifest have been installed for use by the application; and

if the checksum value representing the contents of the manifest differs from the checksum value representing the manifest after the manifest has been received by the application, preventing the step of downloading the software components to the document.

33. The method of claim 19, after connecting the software application to the remote server, and before downloading the plurality of software components to the application for provision of the functionality to the document, determining which components of the plurality of components are required by the application to provide a solution pointed to by the solution property.

34. The method of claim 33, after the step of determining which components of the plurality of components are required by the application, further comprising:

comparing the components present in the manifest that are required by the application with components that are present in the local library of software components;

if the components present in the manifest that are required by the application are in addition to the components present in the local library, downloading the software components to the application; and

if the components present in the manifest that are required by the document are the same as the components that are present in the local library, but the components that are present in the manifest that are required by the document are of a newer version than the components that are present in the local library, downloading the software components to the application.

35. The method of claim 7, after downloading the software components to the application, installing the downloaded components for use by the application for providing functionality to the document.

36. A method of downloading software components from a remote source to a software application for providing updates or additions to application and document functionality, comprising the steps of:

attaching an Extensible Markup Language (XML) schema to the document defining permissible data content, data types and data structures for the document;

annotating particular portions of the document with XML structure associated with the permissible data content, the permissible data types, and permissible data structures for the particular portions of the document as defined by the schema;

associating a solution with XML elements comprising the XML structure;

assembling a plurality of software components comprising the solution at a location remote from the document;

enabling the document to call the solution to obtain functionality provided by the plurality of software components; and

downloading the plurality of software components to the application for provision of the functionality to the document.

37. The method of claim 36, whereby the step of enabling the document to call the solution to obtain functionality provided by the plurality of software components includes:

attaching a solution property to the document for pointing the document to the solution; and

attaching a solution location to the document for enabling the document to locate the solution at the remote location.

38. The method of claim 37, whereby the solution location includes a uniform resource locator (URL) for the solution.

39. The method of claim 36, whereby the solution comprises a plurality of software components providing help content and document actions to the document via the application.

40. The method of claim 36, whereby enabling the document to call the solution to obtain functionality provided by the plurality of software components includes enabling the document to call the plurality of software components upon initiation of editing the document within an XML element associated with a particular solution.

41. The method of claim 37, further comprising the steps of:

listing the solution and the plurality of software components in a manifest of software components; and

storing the manifest in a remote library of software components on a remote server accessible by the document.

42. The method of claim 41, prior to the step of downloading the software components to the application, querying a user of the document to determine whether the plurality of software components should be downloaded.

43. The method of claim 41, prior to downloading the software components to the document, further comprising:

determining whether the manifest is located at a trusted remote site; and

if the manifest is not located at a trusted remote site, preventing the step of downloading the plurality of software components to the application.

44. The method of claim 41, before downloading the plurality of software components to the application for provision of the functionality to the document, further comprising:

connecting the software application to the remote server;

determining which components of the plurality of components are required by the application to provide a solution pointed to by the solution property;

comparing the components present in the manifest that are required by the application with components that are present in the local library of software components;

if the components present in the manifest that are required by the application are in addition to the components present in the local library, downloading the software components to the application; and

if the components present in the manifest that are required by the document are the same as the components that are present in the local library, but the components that are present in the manifest that are required by the document are of a newer version than the components that are present in the local library, downloading the software components to the application.

45. A computer readable medium having stored thereon computer-executable instructions which when executed by a computer, perform the steps of:

attaching an Extensible Markup Language (XML) schema to the document defining permissible data content, data types and data structures for the document;

annotating particular portions of the document with XML structure associated with the permissible data content, the permissible data types, and permissible data structures for the particular portions of the document as defined by the schema;

associating a solution with XML elements comprising the XML structure;

assembling a plurality of software components comprising the solution at a location remote from the document;

enabling the document to call the solution to obtain functionality provided by the plurality of software components; and

downloading the plurality of software components to the application for provision of the functionality to the document.

46. The computer readable medium of claim 45 having stored thereon computer-executable instructions which when executed by a computer, further perform the step of:

whereby the step of enabling the document to call the solution to obtain functionality provided by the plurality of software components includes attaching a solution property to the document for pointing the document to the solution; and

attaching a solution location to the document for enabling the document to locate the solution at the remote location.

47. The computer readable medium of claim 46, whereby the solution location includes a uniform resource locator (URL) for the solution.

48. The computer readable medium of claim 45, whereby the solution comprises a plurality of software components providing help content and document actions to the document via the application.

49. The computer readable medium of claim 45, whereby enabling the document to call the solution to obtain functionality provided by the plurality of software components includes enabling the document to call the plurality of software components upon initiation of editing the document within an XML element associated with a particular solution.

50. The computer readable medium of claim 46 having stored thereon computer-executable instructions which when executed by a computer, further perform the step of:

listing the solution and the plurality of software components in a manifest of software components; and

storing the manifest in a remote library of software components on a remote server accessible by the document.

51. The computer readable medium of claim 49 having stored thereon computer-executable instructions which when executed by a computer, prior to the step of downloading the software components to the application, further performs the steps of:

opening the document;

placing a computer cursor in a particular portion of the document;

generating a list of XML elements enclosing a position of the cursor;

determining whether a solution property pointing the document to the solution is associated with the list of XML elements; and

determining whether the plurality of software components for providing the solution is present in a local library of software components; and

if the plurality of software components is not present in the local library of software components, calling the manifest at the remote library of software components for obtaining the solution.

52. The computer readable medium of claim 51, whereby the step of determining whether a solution property pointing the document to the solution is associated with the list of XML elements, further comprises the step of parsing a look-up table of solutions to determine if any available help content or document actions are associated with any XML element in the list of XML elements.

53. The computer readable medium of claim 50, prior to the step of downloading the software components to the application, querying a user of the document to determine whether the plurality of software components should be downloaded.

54. The computer readable medium of claim 50, prior to downloading the software components to the document, further comprising:

determining whether the manifest is located at a trusted remote site; and

if the manifest is not located at a trusted remote site, preventing the step of downloading the plurality of software components to the application.

55. The computer readable medium of claim 50, before downloading the plurality of software components to the application for provision of the functionality to the document, further comprising:

connecting the software application to the remote server;

determining which components of the plurality of components are required by the application to provide a solution pointed to by the solution property;

comparing the components present in the manifest that are required by the application with components that are present in the local library of software components;

if the components present in the manifest that are required by the application are in addition to the components present in the local library, downloading the software components to the application; and

if the components present in the manifest that are required by the document are the same as the components that are present in the local library, but the components that are present in the manifest that are required by the document are of a newer version than the components that are present in the local library, downloading the software components to the application.