Patent Grant
10514901
Many computing environments comprise a large and diverse set of objects managed by a set of object systems. For example, a computing environment may comprise a set of files managed by a file system, one or more databases managed by a database system, a set of executable binaries representing applications and managed by an assembly cache, a set of user profiles managed by a user profile component of an operating system, and various data caches managed by data caching components, such as a set of copied items managed by a copy buffer of the operating system, a set of undo actions managed by an undo component of the operating system, and a set of “most recently used” items managed by an item usage tracking component of the operating system. Moreover, such objects may be exchanged among a plurality of devices operated by one or more users, and according to one or more operations (e.g., an object synchronization operation that merges two object sets and an object mirroring operation that adjusts a target object set to match a source object set.) In this manner, the objects are loosely organized through a set of object systems and aggregated to represent the computing environment.
Application management within conventional computing environments often involves considerable user involvement. For example, a user may independently discover a desired application, and may procure an installer package, such as a setup executable or a CD-ROM containing setup files. The user may then utilize an application installer that facilitates the deployment of the application in the computing environment, such as by copying files to specific locations and creating registration information. However, following application deployment, computing environments typically provide little ongoing support for the application, sometimes comprising only an uninstaller application. Common maintenance tasks such as execution, sharing, synchronization, and updating are commonly relegated to the application. Moreover, the deployment of the application on one computer system or device rarely enables or facilitates the deployment of the application on other computer systems or devices, even if operated by the same user and utilized for a common purpose on two or more such platforms.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key factors or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
The organization of objects within a computing system as a disjointed, loosely aggregated set of object systems may create several problems. For example, it may be difficult to present a consistent computing environment to the user through various devices, especially if the devices vary in capabilities (e.g., a high-performance personal workstation, a browser-based public terminal, and a low-performance cellphone device.) As another example, applying services to the objects, such as synchronization and backup, may involve interfacing with each object system to affect the objects managed thereby, and such interfacing may vary among object systems. As a third example, relating a diverse set of objects (such as all of the objects comprising an application) may be difficult due to the incomplete cooperation of the managing object systems.
An alternative technique for representing the objects comprising the computing environment involves organizing the objects in an object hierarchy, which may be hosted by a computing environment host. If the objects are represented in a uniform manner and managed in a consistent way by an object system, a set of services may be devised to apply to all of the objects of the computing environment. Moreover, the object hierarchy may be delivered to various devices to represent the same computing environment (including the same user profiles, applications, data files, etc.), and each device may render the computing environment in a consistent manner but customized based on the capabilities of the device (e.g., a hard keyboard interface for receiving data entry from a keyboard device attached to a workstation, and a touchscreen software keyboard interface for receiving data entry from a cellphone device.)
Within an object hierarchy of this nature, application management tasks may be performed. The computing environment host may facilitate the acquisition of the application, the association of the application with a device, and the deployment of the application on the device. The representation of the application as a set of objects in the deployable object hierarchy may facilitate common application management tasks. As a first example, the application may be readily deployed, and in many scenarios automatically deployed, on a plurality of computer systems and devices that are represented in the object hierarchy. For instance, a first version of the application may be deployed to a workstation; a second version of the application may be deployed as a web or web-enabled application for use with a public terminal; and a third version of the application may be deployed as a reduced-functionality application for use on a low-power cellphone device. As a second example, the computing environment host may facilitate the updating of the application (e.g., patching of application resources with updated versions, or deployment of new content for use with the application) by accordingly adjusting the object hierarchy and deploying the adjustments to the devices by synchronizing the hosted and deployed versions of the object hierarchy.
Moreover, the representation of the application as a set of objects in the deployable object hierarchy may also enable new features. As a first example, the computing environment may enable a user to share an application with a second user, or an aspect of an application session, by deploying a specific portion of the object hierarchy to the second user's device, computer system, or computing environment host. For instance, a first user may choose a set of song objects to play on a first computer through a media player application, and may choose to share the media player application session with a second user (e.g., by streaming the audio of the media player application to the second user.) As a second example, the configuration of the application may be synchronized across devices and computer systems as part of the object hierarchy. Device-independent application properties (e.g., custom words added to a spell-check dictionary) may be automatically propagated to all such devices and computer systems, while device-specific application properties may be specified for respective devices by the computing environment host. In this manner, the application management service of the computing environment host may support the discovery, deployment, use, and removal of applications on various computer systems and devices operated by one or more user.
To the accomplishment of the foregoing and related ends, the following description and annexed drawings set forth certain illustrative aspects and implementations. These are indicative of but a few of the various ways in which one or more aspects may be employed. Other aspects, advantages, and novel features of the disclosure will become apparent from the following detailed description when considered in conjunction with the annexed drawings.
The claimed subject matter is now described with reference to the drawings, wherein like reference numerals are used to refer to like elements throughout. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the claimed subject matter. It may be evident, however, that the claimed subject matter may be practiced without these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing the claimed subject matter.
A conventional computing environment typically includes a large and varied array of applications, ranging from small tools with a simple purpose, such as clocks and calculators, to large suites of complex and interrelated applications, such as software integrated development environments and productivity suites. Applications may also comprise media, such as a multimedia player and the media objects rendered thereby (e.g., one or more electronic books to be rendered by a reader application), games, screen savers, device drivers for managing various types of hardware, etc. Applications may be deployed locally (e.g., through executable binaries and resources deployed to the user's device), remotely (e.g., web applications that run on a remote server and communicate with a user through a web browser), or a combination thereof (e.g., locally installed applications that utilize remote resources, such as email clients configured to access network-accessible email archives.) An operating system is usually provided to host and maintain the applications and to provide user access to the applications through an application launcher and associations with data objects related thereto.
After or concurrent with procurement 12, the application life cycle 10 often involves installation 18, wherein the local computing environment is configured to provide access to the program. Installation 18 sometimes involves mapping 20, wherein a particular device is configured to use the application. Mapping 20 may involve a user designation of a particular device for accessing the software (e.g., selecting a cellphone device on which an application is to be deployed), and/or authorization of a device for using the software (e.g., through product activation.) Installation 18 also involves deployment 22, wherein the resources comprising the application are deployed on one or more mapped device (e.g., creating application folders, placing application binaries in such folders, registering code libraries, and writing configuration information to system registries and configuration files.) Deployment 22 may also involve configuring the computing environment to provide access to the application, such as by registering the application with an application launcher, associating the application with data objects related thereto (e.g., identifying a media application as a media player for certain types of media objects), and/or configuring the computing environment to launch the application spontaneously upon system initialization or in response to particular events. Deployment 22 may also involve displaying documentation to assist the user in using the application. In some scenarios, installation 18 may involve the configuration of remote resources, such as registering a device with a network server or configuring a network server to host the application for the device. In other scenarios, installation 18 may be reduced or omitted; e.g., a locally deployed application may comprise an executable binary that runs without configuration or installation, and a web application may not involve any type of installation on a local device.
After procurement 12 and installation 18, the application may be ready for use 24 by one or more users. Use 24 typically involves execution 26, which may begin, e.g., by launching the application or activating a data object associated with the application. Execution 26 may also include the acquisition of additional content, such as new media objects that may be rendered by a media player. Use 24 also involves updating 28, which includes ongoing changes to the application, such as patching to provide new versions of the application or the maintenance of resources utilized thereby (e.g., an antivirus package that receives and incorporates information for detecting and addressing new forms of malware.) Such updating 28 may sometimes be performed on remote resources by an application server; e.g., a webmail provider may update its back-end software frequently without involving the user or user devices, and even without the awareness of the user.
The application life cycle 10 may also involve uninstallation 30, wherein the application is removed from one or more devices. Uninstallation 30 may include unmapping 32, wherein one or more devices are deauthorized for use of the application. For instance, a web application may be accessible only on certain devices, and a device may be unmapped by removing it from the authorized devices list stored on the application server. Uninstallation 30 may also include decommissioning 34, wherein the resources of an application may be removed from one or more devices. Decommissioning 34 may be requested by the user, or may be spontaneously invoked (e.g., an application may be licensed to the user only for a limited duration, and the computing environment may be configured to decommission the application automatically upon expiration of the license term.)
Although the application life cycle has been widely utilized for a large variety of applications, many conventional computing environments are configured such that the application life cycle exhibits several disadvantages. As one example, convention computing environments may entail a significant amount of user participation in conducting this application life cycle. During procurement 12, a computing environment may provide little or no support for discovering or acquiring applications, and a user may be tasked with finding useful applications through research (e.g., web searches) and downloading application installation packages. Procurement 12 may also involve user acceptance of a license, but this may sometimes be abrogated (e.g., a user may preauthorize any application offered under a particular boilerplate end-user license agreement.) Modern computing environments typically provide little or no support for mapping 20, and users may have to arrange for individual deployment of an application on an array of devices. Many conventional computing environments provide some support for deployment 22, such as automated installer tool. However, such installer tools may still delegate to the user a considerable amount of interaction that may be otherwise avoidable, such as inputting user information (name, email address, etc.) while creating a user account in a web application, providing credit card information to purchase a license, and inputting a serial key included with physical media, such as an installation CD. Conventional computing environments may also provide inadequate support for updating 28, which is often delegated to applications, or even to the user-initiated discovery, downloading, and application of software patches. Finally, unmapping 34 and decommissioning 34 may be facilitated by the installer app, but may be limited to per-device management; e.g., the user may have to initiate uninstallation on each device, and centrally managed deployment among all such devices may be difficult.
These disadvantages may be exacerbated and other disadvantages may arise in the context of modern computing environment use, which is often extended across an array of devices. A user of a computing environment may cooperatively manage and utilize a workstation, a portable computer system such as a notebook or tablet, a game console, a cellphone, and a media player. Moreover, the user may wish to access all or part of the computing environment on a public workstation, or to grant access to part or all of the computing environment to other users (e.g., to allow a guest to utilize the computing environment or to access data objects managed therein.) Despite the continued proliferation of devices that a user may operate in the context of a computing environment, conventional operating systems may provide little support for the consistent presentation of a computing environment among such devices, and for promoting the distribution, access, and synchronization of data objects thereby. This limited support is particularly apparent with regard to applications. In general, users often perform many aspects of the application life cycle 10 manually on each device, independently of the configuration of any other device. For instance, a user may configure a particular application according to the user's preferences, but configuring each device on which the application in a similar manner often involves a manual configuration of each application deployment. In addition, the use of multiple devices in a cooperative manner may create new problems; e.g., a user may have a set of contact information for a person on a first device that is inconsistent with a set of contact information for the same person on a second device, and may be unable to ascertain which set of contact information is more current.
Recent attempts have been made to develop techniques for providing access to a computing environment among an array of devices in a consistent, deployable, and extensible manner. These techniques also seek to provide a common set of applications among the cooperating devices, and a centralized service for managing the procuring, installing, using, and uninstalling of applications among such devices. The application set is not necessarily identical among various devices; e.g., a workstation may contain high-performance applications (e.g., photo editing software and graphically intensive games) that may not run well on a cellphone device, and the cellphone device may include portability applications (e.g., a GPS-based mapping software) that is not relevant to a non-portable workstation. However, many applications and data objects related thereto may be shared among such devices (e.g., a calendar application configured to manage a user calendar object), and the computing environment may be adapted to enable the distribution and synchronization of the application and data objects among such devices. The application may also be adapted for each such device; e.g., a first version or configuration of the application may be oriented to high-performance devices such as a workstation, while a second version or configuration of the application may be oriented to low-performance devices with limited screen size and input capabilities. However, other portions of the application configuration (e.g., user preferences, such as a visual style) of the same application may be shared among the devices, and may promote the consistency of the user experience with the computing environment among the various devices.
It may therefore be appreciated that a computer system may be advantageously represented in a manner that enables the deployment of the computing environment, including the application set, among a set of devices. In one such technique, the computing environment—including a set of applications, the application resources, and data objects used thereby—is represented in a manner that may be delivered to devices for rendering according to the capabilities of the device. The representation comprises a set of objects organized according to an object hierarchy and represented according to a common grammar. The objects include the data objects of the computer system, such as the user files and data created by the user. The objects also include the executable binaries and class libraries comprising the operating system components, such as the shell, and the applications offered therein. The object also include the information specifying the user interface of a computing environment, including shell preferences (e.g., visual themes, application launch menu, and double-click threshold), user accounts and privileges, security information (e.g., passwords, security tokens, and certificates), application binaries and configuration information, user data and metadata (e.g., file sharing information), and data caches (e.g., most-recently-used file lists and browser history.) Despite the various nature and uses of these objects, the objects are represented in a common manner in the object hierarchy, and may be arbitrarily organized in the hierarchy. Thus, in contrast with conventional computer systems comprising a set of isolated data stores, each containing one type of object (e.g., a file system containing files, a registry containing configuration information, and a data cache containing the browser history), the object hierarchy in this approach organizes all such objects in a common manner in the object hierarchy.
A computing environment represented in this manner may be delivered to any device and rendered in a manner suitable for the capabilities of the device. For instance, a workstation may render the information as a robust and general-purpose computing environment, while a public workstation may render a different computing environment experience through a web browser (e.g., as a virtual machine that may be discarded at the end of the user's session), and a cellphone may provide a leaner interface with quicker access to cellphone-related information (e.g., contacts, calendar, and navigation data.) Moreover, updates to the information set (e.g., preference changes and updates to data files contained therein) may be applied to the canonical source of the information set, and thereby propagated to all other devices to which the information set is delivered. Also, the devices sharing the computing environment may be integrated through the shared information set, such that one device may interact with others that are identified in the information set; e.g., data stored on a first device may be accessed by a second device, and a first device may be controlled by a second device through a communications conduit. The information set may therefore identify the collection of devices that share the computing environment, along with the roles, capabilities, and resources of each device, to provide an integrated computing experience across a potentially large number and variety of devices.
In furtherance of these ends, an object hierarchy schema may be devised for organizing the objects of the object hierarchy in a particular manner. For instance, objects may be devised and structured to represent data objects (such as files), users and user accounts, devices, and events arising with the computing environment, as well as derivation, ownership, and interrelationships therebetween. The manner of organizing the objects may give rise to particular advantages and/or reduce disadvantages with respect to other organizations of the objects. Accordingly, the object hierarchy schema according to which the objects may be organized is devised in view of the uses of such objects and of the computing environment. For instance, security permissions may be modeled by associating respective objects with one or more user accounts having various sets of permissions (e.g., a first user account having read/write permissions to an object, a second user account having read-only permissions to the object, and a third user account having no permissions to the object.) The computing environment may be configured to utilize the objects of an object hierarchy according to the structure and semantics of the object hierarchy schema, thereby enabling the presentation of a deployable computing environment across a plurality of devices in a manner that is appropriate for the configuration and capabilities of each device, but otherwise consistent among all such devices.
Within an object hierarchy of this nature, a set of applications may be managed in a manner consistent with the application life cycle of each application. For instance, the computing environment host 42 may facilitate the acquisition of the application, the association of the application with one or more devices, and the deployment of the application on each device. The representation of the application as a set of objects in the object hierarchy 44 may facilitate common application management tasks. As a first example, the application may be readily deployed, and in many scenarios automatically deployed, on a plurality of computer systems and devices that are represented in the object hierarchy 44. For instance, a first version of the application may be deployed to a personal notebook computer 50; a second version of the application may be deployed as a web or web-enabled application for use with a public workstation 54; and a third version of the application may be deployed as a reduced-functionality application for use on a low-powered cellphone device 46. As a second example, the computing environment host 42 may facilitate the updating of an application (e.g., patching of application resources with updated versions, or deployment of new content for use with the application) by accordingly adjusting the object hierarchy 44 and deploying the adjustments to the devices by synchronizing the hosted and deployed versions of the object hierarchy 44.
The representation of an application set as a set of objects in a deployable object hierarchy 44 may also enable new features. As a first example, the computing environment may enable a user to share an application with a second user, or an aspect of an application session, by deploying a specific portion of the object hierarchy 44 to the second user's device, computer system, or computing environment host 42. For instance, a first user may choose a set of song objects to play on a first computer through a media player application, and may choose to share the media player application session with a second user (e.g., by streaming the audio of the media player application to the second user.) As a second example, the configuration of the application may be synchronized across devices and computer systems as part of the object hierarchy. Device-independent application properties (e.g., custom words added to a spell-check dictionary) may be automatically propagated to all such devices and computer systems, while device-specific application properties may be specified for respective devices by the computing environment host 42. In this manner, the application management service of the computing environment host 42 may support the discovery, deployment, use, and removal of applications on various computer systems and devices operated by one or more user. Many portions of these tasks may be performed by adjusting the object hierarchy 44 and synchronizing its deployment to the various devices represented therein, which, as an automated process, may provide a significant improvement in the consistency of the computing environment and the overall user experience.
The exemplary method 60 of
Within this scenario 80, the application management system 86 may operate to achieve the deployment of one or more applications within the object hierarchy. The exemplary system 86 comprises an application acquisition component 88, which is configured to receive a request to install an application, and to acquire the application from the application store 84. The application acquisition component 88 may also determine whether the request satisfies any prerequisites (e.g., whether the application can run on the requested device; whether the user is permitted to install and run the application, in view of various security privileges of the user and licensing issues; etc.) The exemplary system 86 of
The techniques described herein may be implemented with variations in many aspects, and some variations may present additional advantages and/or reduce disadvantages with respect to other variations of these and other techniques. These variations may be included in various embodiments, such as the exemplary method 60 of
A first aspect that may vary among implementations of these techniques relates to the architecture of the application management server through which the application management service is provided. As illustrated in
A second aspect that may vary among implementations of these techniques relates to variations in the basic components of the application management, including acquisition, mapping, and deployment. As a first variation of this aspect, the acquiring application typically entails receiving a request to deploy the application and acquiring the application to be deployed to the object hierarchy with respect to a particular device. However, the acquiring may also include presenting an application license to a user through the device, such as displaying the terms and conditions of an end-user license agreement for the application. The acquiring may also include requesting the user to accept the application license as a prerequisite of deployment; and upon receiving an acceptance of the application license, the acquiring may include recording the acceptance of the application license, such as by notifying an application license server. This acceptance might be received as an acknowledgment from the user, or as an automated acceptance, e.g., where the user has preauthorized the acceptance of any application under a particular application license (e.g., any application provided under a particular version of the GNU Public License.) The acquiring may also include brokering an acquisition transaction with a user of the at least one device, such as an e-commerce purchase of a license to the application. The acquiring may also include generating a user account representing a user of the application, which may be particularly advantageous for acquiring access to a web application, such as a webmail application that is entirely hosted on a webmail server and provided through a browser in the computing environment.
As a second variation of this second aspect, the mapping of an application typically involves associating the application with one or more devices represented in the object hierarchy. However, the mapping may also include an examination of device-specific conditions, such as whether the application is available in a version that is compatible with the device, and whether the application or a variant thereof (such as an earlier version) is already available on the device. The mapping may also involve acquiring additional resources in order to promote the mapping of the application to a new device, such as a new version of the application binary that may be compatible with the device, or additional components on which the application depends that may be deployed to the device (e.g., a supporting runtime that may be retrieved from another server.) The mapping may also involve an activation of the application through an application activation server, which may authorize the execution of the application on a particular device, such as by providing an authenticated certificate that is validated by the application on the device upon launching.
As a third variation of this second aspect, the deploying of an application typically involves deploying the application within the object hierarchy, such as by inserting a representation of the components of the application in the object hierarchy. Even typically organized applications may be structured in numerous ways. A small utility may comprise a single executable binary, which may be wholly or partially compiled, or may be included as source code that is compiled locally on each device. This executable binary may be represented, e.g., as source code module, a parse tree, intermediate language instructions representing a partially compiled binary, a wholly compiled binary, etc. A larger utility might comprise a set of resources, such as one or more executable binaries; shared assemblies that may be registered in a global assembly cache; application resources such as icons, sound objects, pictures, documents, and video; help files; data resources stored in one or more structured data stores, such as a relational database; ancillary application resources, such as a language dictionary file for a spell-checking tool in a word processing application; an application manifest that serves as an index of the resources specified therein; etc. Moreover, an application may include several versions of an executable binary, each of which may be targeted to a particular platform; for instance, an application might include a full-featured version for use on a more powerful device such as a notebook computer 50 and a reduced functionality version for use on a low-powered cellphone device 46. The application may also include several sets of configuration information, each targeting a specific platform. The application may be presented as a standalone installer package, or as an installable archive that may be deployed by a device-based installer, or as a set of one or more resources that may be utilized in any location, etc.
The object hierarchy may also include applications of a less conventional structure. For example, a game application might include a large number of graphics resources, such as bitmap textures and meshes for constructing complex three-dimensional environments and objects represented therein. A web-enabled application may include a set of web pages, which may contain portions of inline code or may reference external code resources, such as Java objects included in source code or compiled form. Such an application might also be represented simply as a reference to a website where such resources are available. A web-enabled application might also be structured through a markup language, such as the Extensible Application Markup Language (XAML), which may be compiled or interpretively executed on a device either as an application or an applet hosted in a web browser. Finally, a web application might be represented simply as one or more URLs referencing one or more websites on which part or all of the application is deployed, which may be accessed on the device through a web browser; alternatively or additionally, some resources may be included for device deployment, such as cookies that may locally stored to persist the state of a web application between sessions.
Because the resources comprising an application may be diverse, the deployment of the application in the object hierarchy may be similarly robust. For example, text resources may be included as plaintext, or may be compressed with a general or special-purpose compression utility. Binary resources may be presented as serialized binary code, may be compressed with a binary compression utility, may be transcoded (e.g., via Uuencode or MIME), etc. Hierarchically organized objects may be structured according to a hierarchical formatting, such as XML, or may be serialized as a single hierarchical object. Large objects may be included as atomic units, compressed, transcoded (e.g., a movie file may be reencoded at a lower bitrate to conserve space), segmented into portions that may be individually transmitted to a device over time or on an ad hoc basis, etc. Resources may be included in the object hierarchy, or may be inserted as a reference to a server hosting the resource that may be accessed as needed. Large sets of numerous objects may be included as an archive (e.g., a compressed file containing several thousand objects.) Web-based applications may be represented as one or more URLs where the components of the application are available; alternatively or additionally, a snapshot of the web application may be captured and included in the object hierarchy to provide a cached version of the application or to enable offline access to the application. Those of ordinary skill in the art may be able to devise many techniques for representing an application in an object hierarchy while implementing the techniques discussed herein.
In addition to representing the application in the object hierarchy, the deploying may also include configuring the application with respect to the device and/or with respect to the user. For instance, a new set of configuration information may be formulated for the device, or an appropriate set of configuration information in a library of configuration sets may be designated for use by the device.
In deploying the application within the object hierarchy 82 for these devices, the application deployment component 92 may configure the application for particular use on each device. For instance, the calendar application may be deployed for the cellphone device 46 by associating it with the client-side browser script executable binary, which may run within a web browser application of the cellphone device 46, and with the portable configuration set for low-power devices. Similarly, the calendar application may be deployed for the notebook computer 50 by associating it with the compiled executable binary, and with the full functionality configuration set that may provide computationally intensive features that the notebook computer 50 is capable of rendering. However, both devices may incorporate the device-independent configuration set to present a consistent set of device-independent features, thereby promoting a consistent computing environment among all such devices of the computing mesh. Those of ordinary skill in the art may be able to devise additional variations in the acquisition, mapping, and deployment of applications in the object hierarchy 82 while implementing the techniques discussed herein.
A third aspect that may vary among implementations of these techniques relates to additional features that may be added to the basic components of such embodiments. In addition to the basic management services (acquisition, mapping, and deployment), additional services may be provided for application management, which may facilitate the user and the computer system in the management of the application life cycle.
As a first variation of this third aspect, the application management service may also serve as the computing environment host, such as illustrated in the third exemplary architecture 110 of
As a second variation of this third aspect, the application management service may also facilitate the discovery of applications that may be of interest to the user. For instance, a method of managing the deployment of applications to an object hierarchy (such as the exemplary method 60 of
As a third variation of this third aspect, the application management service may also facilitate the launching of the application. For instance, an exemplary system embodying the application management service may include an application launching component, which may be configured to launch the application on the at least one device. The application launching component may comprise, e.g., a runtime configured to provide a platform for the device and to facilitate the execution of the application thereupon. For instance, an application may be deployed in the service as a client-side browser script, and the application management service may include with the object hierarchy a browser runtime within which the browser script may be interpretively executed. As another example, the application may be represented as source code, and the application launching component may comprise a device-specific compiler that, upon launching the application on the device, compiles the source code into an executable binary that may be executed on the device. Moreover, the application launching component may also store the compiled executable binary, such as in an assembly cache, and may respond to subsequent requests to launch the application by fetching the stored executable binary instead of recompiling the application. As a third example, a web-enabled application may comprise a client-side front end configured to access a remote resource, and the application launching component may attempt to connect to the remote resource and to verify its availability to the device upon launching the application. Those of ordinary skill in the art may be able to devise many ways of facilitating application launching on a device while implementing the techniques discussed herein.
As a fourth variation of this third aspect, the application management service may also facilitate the sharing of aspects of the application with other users. Such application sharing may occur in many scenarios. As a first example, the sharing may involve sharing of the full application (including all resources and data objects associated therewith.) As a second example, the sharing may involve sharing a version of the application with another user; e.g., the first user may have purchased a license to use the application, and may share with the second user a reduced functionality version of the application that may demonstrate some features of the application to encourage the second user to license the application. As a third example, the sharing may involve sharing one or more data objects associated with the application, such as media objects created with the application. The second user may then use the same application or another application to render the media objects within the second user's computing environment. As a fourth example, the sharing may involve sharing a configuration of the application with another user; e.g., several members of a software development team may utilize a particular configuration of an integrated development environment while working as a team in the development of the software. As a fifth example, the sharing may involve sharing a session of the application with another user; e.g., two users may collaborate in the preparation of a text document, and a first user may share a session of a word processing application with the second user to promote live interaction between the users. These sharing scenarios may also arise among several users of a computing environment (represented by a single object hierarchy), or among users of two or more computing environments (represented by multiple object hierarchies), or may arise when sharing a portion of an object hierarchy representing a computing environment with users of computing environments represented in unknown manners by providing data objects of the shared computing environment through a common communications protocol, such as the File Transfer Protocol (FTP.) These and other sharing scenarios may be devised by those of ordinary skill in the art while implementing the techniques discussed herein.
As a fifth variation of this third aspect, the application management service may facilitate the updating of applications with new content. Applications are often updated to new versions and with new content by patching binaries, inserting new resources, and altering or removing existing resources. Such updating may be performed by the application management service by obtaining application updates and deploying the updates to applications represented in the object hierarchy (e.g., by updating application resources contained in the object hierarchy, and/or inserting new resources as new objects in the object hierarchy.) The updates may be applied at the request of a user, who may have acquired new content to be exposed by the application; or may be retrieved by the application management service through a query to an application store; or may be pushed to the application management service b by an application store or an administration server; etc. The updated object hierarchy may then be transmitted to one or more devices, and may thereby achieve an updating of the applications of the computing environment with reduced reliance on the involvement of the user. Those of ordinary skill in the art may be able to devise many ways of updating the applications represented in the object hierarchy while implementing the techniques discussed herein.
As a sixth variation of this third aspect, the application management service may also permit the revocation of applications from the computing environment. This revocation may involve many scenarios, such as removing a mapping of an application to a device, de-authorizing a device in an authorized devices list of an application activation server, removing application resources from a device (e.g., by withholding from the device a portion of the object hierarchy containing the application resources), and completely decommissioning the application by removing all of the application resources from the object hierarchy and from all mapped devices. The revocation may be at the request of a user who wishes to uninstall the application from one or more devices, or upon expiration of a limited duration software license, or upon removing a device from the computing mesh, etc.
As an exemplary embodiment of this variation, an application management system may include an application revocation component configured to revoke the application from at least one device in any of these manners. Those of ordinary skill in the art may be able to devise many ways of revoking applications from within computing environments represented by object hierarchies while implementing the techniques discussed herein.
These variations of these aspects may be included in many embodiments of the techniques discussed herein, including the exemplary method 60 of
The exemplary system 160 of
The exemplary system 160 of
The exemplary system 160 of
Finally, the exemplary system 160 also includes an object hierarchy transmission component 170, which is configured to transmit at least a portion of the object hierarchy 44 to the at least one device. The object hierarchy 44 may be modified by many of the components of the application management system 160, and the modifications of the object hierarchy 44 may be synchronized with the one or more devices represented therein to effectuate the updating of the application set of the computing environment. By combining these many variations of the techniques discussed herein, the exemplary system 160 thereby provides comprehensive application management services for administrating a large set of applications through the typical application life cycle among many devices comprising a computing mesh.
Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
As used in this application, the terms “component,” “module,” “system”, “interface”, and the like are generally intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a controller and the controller can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.
Furthermore, the claimed subject matter may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.
Although not required, embodiments are described in the general context of “computer readable instructions” being executed by one or more computing devices. Computer readable instructions may be distributed via computer readable media (discussed below). Computer readable instructions may be implemented as program modules, such as functions, objects, Application Programming Interfaces (APIs), data structures, and the like, that perform particular tasks or implement particular abstract data types. Typically, the functionality of the computer readable instructions may be combined or distributed as desired in various environments.
In other embodiments, device 182 may include additional features and/or functionality. For example, device 182 may also include additional storage (e.g., removable and/or non-removable) including, but not limited to, magnetic storage, optical storage, and the like. Such additional storage is illustrated in
The term “computer readable media” as used herein includes computer storage media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions or other data. Memory 188 and storage 190 are examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disks (DVDs) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by device 182. Any such computer storage media may be part of device 182.
Device 182 may also include communication connection(s) 196 that allows device 182 to communicate with other devices. Communication connection(s) 196 may include, but is not limited to, a modem, a Network Interface Card (NIC), an integrated network interface, a radio frequency transmitter/receiver, an infrared port, a USB connection, or other interfaces for connecting computing device 182 to other computing devices. Communication connection(s) 196 may include a wired connection or a wireless connection. Communication connection(s) 196 may transmit and/or receive communication media.
The term “computer readable media” may include communication media. Communication media typically embodies computer readable instructions or other data in a “modulated data signal” such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” may include a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
Device 182 may include input device(s) 194 such as keyboard, mouse, pen, voice input device, touch input device, infrared cameras, video input devices, and/or any other input device. Output device(s) 192 such as one or more displays, speakers, printers, and/or any other output device may also be included in device 182. Input device(s) 194 and output device(s) 192 may be connected to device 182 via a wired connection, wireless connection, or any combination thereof. In one embodiment, an input device or an output device from another computing device may be used as input device(s) 194 or output device(s) 192 for computing device 182.
Components of computing device 182 may be connected by various interconnects, such as a bus. Such interconnects may include a Peripheral Component Interconnect (PCI), such as PCI Express, a Universal Serial Bus (USB), firewire (IEEE 1394), an optical bus structure, and the like. In another embodiment, components of computing device 182 may be interconnected by a network. For example, memory 188 may be comprised of multiple physical memory units located in different physical locations interconnected by a network.
Those skilled in the art will realize that storage devices utilized to store computer readable instructions may be distributed across a network. For example, a computing device 200 accessible via network 198 may store computer readable instructions to implement one or more embodiments provided herein. Computing device 182 may access computing device 100 and download a part or all of the computer readable instructions for execution. Alternatively, computing device 182 may download pieces of the computer readable instructions, as needed, or some instructions may be executed at computing device 182 and some at computing device 200.
Various operations of embodiments are provided herein. In one embodiment, one or more of the operations described may constitute computer readable instructions stored on one or more computer readable media, which if executed by a computing device, will cause the computing device to perform the operations described. The order in which some or all of the operations are described should not be construed as to imply that these operations are necessarily order dependent. Alternative ordering will be appreciated by one skilled in the art having the benefit of this description. Further, it will be understood that not all operations are necessarily present in each embodiment provided herein.
Moreover, the word “exemplary” is used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as advantageous over other aspects or designs. Rather, use of the word exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise, or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims may generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.
Also, although the disclosure has been shown and described with respect to one or more implementations, equivalent alterations and modifications will occur to others skilled in the art based upon a reading and understanding of this specification and the annexed drawings. The disclosure includes all such modifications and alterations and is limited only by the scope of the following claims. In particular regard to the various functions performed by the above described components (e.g., elements, resources, etc.), the terms used to describe such components are intended to correspond, unless otherwise indicated, to any component which performs the specified function of the described component (e.g., that is functionally equivalent), even though not structurally equivalent to the disclosed structure which performs the function in the herein illustrated exemplary implementations of the disclosure. In addition, while a particular feature of the disclosure may have been disclosed with respect to only one of several implementations, such feature may be combined with one or more other features of the other implementations as may be desired and advantageous for any given or particular application. Furthermore, to the extent that the terms “includes”, “having”, “has”, “with”, or variants thereof are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising.”
This application is a continuation of, and claims priority under 35 U.S.C. § 120 to, U.S. patent application Ser. No. 12/052,550, entitled “Application Management Within Deployable Object Hierarchy,” filed on Mar. 20, 2008, the entirety of which is hereby incorporated by reference as if fully rewritten herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5437025 | Bale et al. | Jul 1995 | A |
| 5504852 | Thompson-Rohrlich | Apr 1996 | A |
| 5548726 | Pettus | Aug 1996 | A |
| 5850090 | Oashi et al. | Dec 1998 | A |
| 5930156 | Kennedy | Jul 1999 | A |
| 6105062 | Andrews et al. | Aug 2000 | A |
| 6137493 | Kamimura et al. | Oct 2000 | A |
| 6209029 | Epstein et al. | Mar 2001 | B1 |
| 6243746 | Sondur et al. | Jun 2001 | B1 |
| 6286138 | Purcell | Sep 2001 | B1 |
| 6330717 | Raverdy et al. | Dec 2001 | B1 |
| 6374252 | Althoff et al. | Apr 2002 | B1 |
| 6546554 | Schmidt et al. | Apr 2003 | B1 |
| 6553375 | Huang et al. | Apr 2003 | B1 |
| 6573907 | Madrane | Jun 2003 | B1 |
| 6594664 | Estrada et al. | Jul 2003 | B1 |
| 6662192 | Rebane | Dec 2003 | B1 |
| 6678724 | Nakajima et al. | Jan 2004 | B2 |
| 6685090 | Nishigaya et al. | Feb 2004 | B2 |
| 6732172 | House et al. | May 2004 | B1 |
| 6834301 | Hanchett | Dec 2004 | B1 |
| 6836842 | Guccione et al. | Dec 2004 | B1 |
| 6865737 | Lucas | Mar 2005 | B1 |
| 6907451 | Mukundan et al. | Jun 2005 | B1 |
| 6909721 | Ekberg et al. | Jun 2005 | B2 |
| 6941306 | Kim | Sep 2005 | B2 |
| 6952714 | Peart | Oct 2005 | B2 |
| 6968535 | Stelting et al. | Nov 2005 | B2 |
| 7013340 | Burd et al. | Mar 2006 | B1 |
| 7054927 | Ulrich et al. | May 2006 | B2 |
| 7088995 | Rao | Aug 2006 | B2 |
| 7089295 | Christfort et al. | Aug 2006 | B2 |
| 7099888 | Gollapudi et al. | Aug 2006 | B2 |
| 7117243 | Peart | Oct 2006 | B2 |
| 7117495 | Blaser et al. | Oct 2006 | B2 |
| 7146524 | Patel et al. | Dec 2006 | B2 |
| 7149959 | Jones et al. | Dec 2006 | B1 |
| 7203485 | Coppinger et al. | Apr 2007 | B2 |
| 7240327 | Singh et al. | Jul 2007 | B2 |
| 7266370 | Paddon et al. | Sep 2007 | B2 |
| 7266563 | Morris et al. | Sep 2007 | B2 |
| 7284196 | Skeen et al. | Oct 2007 | B2 |
| 7330872 | Peart et al. | Feb 2008 | B2 |
| 7353259 | Bakke et al. | Apr 2008 | B1 |
| 7383541 | Banks et al. | Jun 2008 | B1 |
| 7406542 | Erlingsson | Jul 2008 | B2 |
| 7480699 | Alam | Jan 2009 | B2 |
| 7483978 | Esfahany et al. | Jan 2009 | B2 |
| 7577681 | Rozenman et al. | Aug 2009 | B1 |
| 7739680 | Thakur et al. | Jun 2010 | B1 |
| 7836458 | Gwozdz et al. | Nov 2010 | B1 |
| 7890543 | Hunt et al. | Feb 2011 | B2 |
| 8132166 | DeHaan | Mar 2012 | B2 |
| 8185891 | DeHaan | May 2012 | B2 |
| 8290762 | Kodosky et al. | Oct 2012 | B2 |
| 8321538 | Ford et al. | Nov 2012 | B2 |
| 8387037 | Henseler | Feb 2013 | B2 |
| 8484174 | Shukla et al. | Jul 2013 | B2 |
| 8572033 | Shukla | Oct 2013 | B2 |
| 9152404 | Reeves | Oct 2015 | B2 |
| 9298747 | Shukla et al. | Mar 2016 | B2 |
| 20010044801 | Senn et al. | Nov 2001 | A1 |
| 20020010807 | Multer et al. | Jan 2002 | A1 |
| 20020029227 | Multer et al. | Mar 2002 | A1 |
| 20020040368 | Schreiber | Apr 2002 | A1 |
| 20020103811 | Fankhauser et al. | Aug 2002 | A1 |
| 20020133669 | Devireddy et al. | Sep 2002 | A1 |
| 20020138617 | Christfort et al. | Sep 2002 | A1 |
| 20030004746 | Kheirolomoom et al. | Jan 2003 | A1 |
| 20030033308 | Patel et al. | Feb 2003 | A1 |
| 20030063134 | Lord et al. | Apr 2003 | A1 |
| 20030074393 | Peart | Apr 2003 | A1 |
| 20030177121 | Moona et al. | Sep 2003 | A1 |
| 20030225851 | Fanshier et al. | Dec 2003 | A1 |
| 20030233376 | Bussler et al. | Dec 2003 | A1 |
| 20040006566 | Taylor et al. | Jan 2004 | A1 |
| 20040031029 | Lee et al. | Feb 2004 | A1 |
| 20040085947 | Ekberg et al. | May 2004 | A1 |
| 20040103071 | Kalia et al. | May 2004 | A1 |
| 20040111515 | Manion et al. | Jun 2004 | A1 |
| 20040133589 | Kiessig et al. | Jul 2004 | A1 |
| 20040148525 | Aida et al. | Jul 2004 | A1 |
| 20040153568 | Ho et al. | Aug 2004 | A1 |
| 20040199572 | Hunt et al. | Oct 2004 | A1 |
| 20040201604 | Kraenzel et al. | Oct 2004 | A1 |
| 20040236801 | Borden et al. | Nov 2004 | A1 |
| 20040251568 | Chao et al. | Dec 2004 | A1 |
| 20050004978 | Reed et al. | Jan 2005 | A1 |
| 20050004985 | Stochosky | Jan 2005 | A1 |
| 20050021847 | Rothman et al. | Jan 2005 | A1 |
| 20050060315 | Sanin | Mar 2005 | A1 |
| 20050060581 | Chebolu et al. | Mar 2005 | A1 |
| 20050062581 | Koyama | Mar 2005 | A1 |
| 20050091348 | Ferri | Apr 2005 | A1 |
| 20050091575 | Relyea et al. | Apr 2005 | A1 |
| 20050102678 | Hunt et al. | May 2005 | A1 |
| 20050125771 | Vitanov et al. | Jun 2005 | A1 |
| 20050138156 | Gebhart et al. | Jun 2005 | A1 |
| 20050177600 | Eilam et al. | Aug 2005 | A1 |
| 20050192962 | Furrer et al. | Sep 2005 | A1 |
| 20050203931 | Pingree et al. | Sep 2005 | A1 |
| 20050251786 | Citron et al. | Nov 2005 | A1 |
| 20050251812 | Hayward | Nov 2005 | A1 |
| 20050289454 | Donelson et al. | Dec 2005 | A1 |
| 20060015538 | LeTourneau | Jan 2006 | A1 |
| 20060015936 | Illowsky et al. | Jan 2006 | A1 |
| 20060036602 | Unangst et al. | Feb 2006 | A1 |
| 20060037007 | Snyder et al. | Feb 2006 | A1 |
| 20060080353 | Miloushev et al. | Apr 2006 | A1 |
| 20060089965 | Fontes et al. | Apr 2006 | A1 |
| 20060117073 | Bosworth et al. | Jun 2006 | A1 |
| 20060123010 | Landry et al. | Jun 2006 | A1 |
| 20060129972 | Tyburski et al. | Jun 2006 | A1 |
| 20060130050 | Betts et al. | Jun 2006 | A1 |
| 20060143435 | Kwon | Jun 2006 | A1 |
| 20060143601 | Concha et al. | Jun 2006 | A1 |
| 20060173895 | Engquist | Aug 2006 | A1 |
| 20060173993 | Henseler | Aug 2006 | A1 |
| 20060200494 | Sparks | Sep 2006 | A1 |
| 20060206533 | MacLaurin et al. | Sep 2006 | A1 |
| 20060242327 | Knight et al. | Oct 2006 | A1 |
| 20060253849 | Avram et al. | Nov 2006 | A1 |
| 20070005613 | Singh et al. | Jan 2007 | A1 |
| 20070028175 | Moore et al. | Feb 2007 | A1 |
| 20070038642 | Durgin et al. | Feb 2007 | A1 |
| 20070061349 | Morgan et al. | Mar 2007 | A1 |
| 20070073770 | Morris et al. | Mar 2007 | A1 |
| 20070100834 | Landry et al. | May 2007 | A1 |
| 20070106650 | Moore | May 2007 | A1 |
| 20070118560 | Bornhoevd et al. | May 2007 | A1 |
| 20070150480 | Hwang et al. | Jun 2007 | A1 |
| 20070169049 | Gingell | Jul 2007 | A1 |
| 20070169083 | Penubolu et al. | Jul 2007 | A1 |
| 20070180043 | Vernal et al. | Aug 2007 | A1 |
| 20070209066 | Timmerman | Sep 2007 | A1 |
| 20070233698 | Sundar | Oct 2007 | A1 |
| 20070266136 | Esfahany et al. | Nov 2007 | A1 |
| 20070280165 | Doshi et al. | Dec 2007 | A1 |
| 20070294366 | Ozzie et al. | Dec 2007 | A1 |
| 20080016505 | Bucklew et al. | Jan 2008 | A1 |
| 20080040511 | Messer et al. | Feb 2008 | A1 |
| 20080057992 | Griffin | Mar 2008 | A1 |
| 20080059912 | Scherpa et al. | Mar 2008 | A1 |
| 20080092109 | Kinnucan et al. | Apr 2008 | A1 |
| 20080130639 | Costa-Requena et al. | Jun 2008 | A1 |
| 20080155523 | Kornmann | Jun 2008 | A1 |
| 20080201453 | Assenmacher | Aug 2008 | A1 |
| 20080249994 | Passmore | Oct 2008 | A1 |
| 20080276181 | Moromisato | Nov 2008 | A1 |
| 20090083425 | Bozak et al. | Mar 2009 | A1 |
| 20090094592 | Alam | Apr 2009 | A1 |
| 20090164987 | Scholz et al. | Jun 2009 | A1 |
| 20090172637 | Parikh | Jul 2009 | A1 |
| 20090240698 | Shukla et al. | Sep 2009 | A1 |
| 20090240935 | Shukla | Sep 2009 | A1 |
| 20140325502 | Zarifis | Oct 2014 | A1 |
| Number | Date | Country |
|---|---|---|
| 1599901 | Mar 2005 | CN |
| 1801086 | Jul 2006 | CN |
| 2000163269 | Jun 2000 | JP |
| 2001005648 | Jan 2001 | JP |
| 2002229902 | Aug 2002 | JP |
| 2003186782 | Jul 2003 | JP |
| 2005251167 | Sep 2005 | JP |
| 1020000035005 | Jun 2000 | KR |
| 200515175 | May 2005 | TW |
| 200620129 | Jun 2006 | TW |
| 0067112 | Nov 2000 | WO |
| 2004097759 | Nov 2004 | WO |
| 2005072114 | Aug 2005 | WO |
| 2005124573 | Dec 2005 | WO |
| 2007083299 | Jul 2007 | WO |
| 2008018051 | Feb 2008 | WO |
| Entry |
|---|
| “Office Action Issued in Korean Patent Application No. 10-2010-7020791”, dated Jan. 8, 2017, 3 Pages. |
| “Reply Non-Final Office Action Issued in U.S. Appl. No. 12/057,000”, dated Nov. 4, 2010, 19 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/910,757”, dated Dec. 2, 2011, 18 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 12/910,757”, dated Jun. 21, 2012, 30 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 12/910,757”, dated Sep. 26, 2012, 38 Pages. |
| “Reply Non-Final Office Action Issued in U.S. Appl. No. 12/910,757”, dated Feb. 27, 2012, 12 Pages. |
| “Australian Office Action Issued in Australian Patent Application No. 2008247683”, dated Mar. 12, 2012, 3 Pages. |
| “Notice of Allowance Issued in Australian Patent Application No. 2008247683”, dated Apr. 18, 2012, 3 Pages. |
| “Reply Australian Office Action Issued in Australian Patent Application No. 2008247683”, dated Apr. 12, 2012, 18 Pages. |
| “First Chinese Office Action Issued in Chinese Patent Application No. 200880014431.6”, dated Mar. 22, 2011,10 Pages. |
| “Fourth Office Action Issued in Chinese Patent Application No. 200880014431.6”, dated Oct. 29, 2012,9 Pages. |
| “Reply First Chinese Office Action Issued in Chinese Patent Application No. 200880014431.6”, dated Jun. 29, 2011, 15 Pages. |
| “Reply fourth Chinese Office Action Issued in Chinese Patent Application No. 200880014431.6”, dated Nov. 20, 2012,13 Pages. |
| “Reply third Chinese Office Action Issued in Chinese Patent Application No. 200880014431.6”, dated Jul. 24, 2012, 13 Pages. |
| “Third Office Action Issued in Chinese Patent Application No. 200880014431.6”, dated Jul. 6, 2012, 9 Pages. |
| “Notice of Allowance Issued in Russian Patent Application No. 2009140733”, dated Dec. 20, 2012, 15 Pages. |
| “Office Action Issued in Russian Patent Application No. 2009140733”, dated May 5, 2012, 4 Pages. (W/o English Translation). |
| “Office Action Issued in Russian Patent Application No. 2009140733”, dated Aug. 29, 2012, 4 Pages. (W/o English Translation). |
| “First Office Action Issued in Chinese Patent Application No. 200980110662.1”, dated Apr. 6, 2012, 6 Pages. |
| “Notice of Allowance Issued in Chinese Patent Application No. 200980110662.1”, dated Jul. 31, 2013, 6 Pages. |
| “Reply First Chinese Office Action Issued in Chinese Application No. 200980110662.1”, dated Aug. 16, 2012, 6 Pages. |
| “Reply Second Office Action Issued in Chinese Application No. 200980110662.1”, dated Feb. 28, 2013, 13 Pages. |
| “Second Office Action and Search Report Issued in Chinese Patent Application No. 200980110662.1”, dated Dec. 18, 2012, 9 Pages. |
| “First Office Action Issued in Chinese Patent Application No. 200980112183.3”, dated Apr. 12, 2012, 6 Pages. |
| “Reply First Chinese Office Action Issued in Chinese Patent Application No. 200980112183.3”, dated Aug. 17, 2012, 40 Pages. |
| “Second Office Action Issued in Chinese Patent Application No. 200980112183.3”, dated Dec. 18, 2012, 6 Pages. |
| “First Chinese Office Action Issued in Chinese Patent Application No. 20098011676.3”, dated Jun. 5, 2012, 7 Pages. |
| “Reply First Chinese Office Action Issued in Chinese Patent Application No. 20098011676.3”, dated Oct. 23, 2012, 28 Pages. |
| Valavanis, et al., “MobiShare: Sharing Context-Dependent Data & Services from Mobile Sources”, In Proceedings of the IEEE/WIC International Conference on Web Intelligence, Oct. 13, 2003, 8 Pages. |
| VeriSign, “VeriSign® Unified Authentication Service”, 3 Pages. |
| Bickmore, et al., “Digestor: Device-independent Access to the World Wide Web”, In Journal of the Computer Networks and ISDN Systems, vol. 29, Issue 8-13, Sep. 1, 1997, pp. 1075-1082. |
| Chen, et al., “Providing Web Services to Mobile Users: the Architecture Design of an M-Service Portal”, International Journal of Mobile Communications, vol. 3, Issue 1, May 1, 2005, pp. 1-18. |
| Foley, Mary Jo., “Can Microsoft's ‘Harmonica’ Create P2P Harmony Across All Devices?”, Retrieved from <<http://blogs.zdnet.com/microsoft/?>>, Dec. 18, 2006, 2 Pages. |
| Gribble, et al., “The Ninja Architecture for Robust Internet-scale Systems and Services”, In the International Journal of Computer and Telecommunications Networking, Computer Networks—Pervasive Vomputing, vol. 35, Issue 4, Mar. 2001, pp. 473-497. |
| Han, et al., “Websplitter: A Unified XML Framework for Multi-Device Collaborative Web Browsing”, In Proceedings of the ACM Conference on Computer Supported Cooperative Work, Dec. 1, 2000, 10 Pages. |
| Hejtmánek, Lukas, “Distributed Data Storage Based on Web Access and IBP Intrastructure”, In Data Processing and Storage Networking: Towards Grid Computing, Technical Proceedings. Third IFIP-TC6 Networking Conference., May 14, 2004. |
| Hoschek, et al., “Grid Enabled Relational Database Middleware”, In Global Grid Forum ,vol. 3, Oct. 7, 2001, 6 Pages. |
| Miller, Tim, “PCI Express and Advanced Switching: Data Movement Protocols”, In Journal of COTS, Oct. 2003, pp. 76-79. |
| Mukhi, et al., “Multi-protocol Web Services for Enterprises and the Grid”, In Proceedings of the 2002 international conference on EuroWeb, Dec. 17, 2002, 10 Pages. |
| Nathan, et al., “Convert XML to JSON in PHP”, Retrieved From <<http://www.ibm.com/developerworks/xml/library/x-xml2jsonphp/>>, Jan. 16, 2007, 10 Pages. |
| “International Preliminary Report Issued in PCT Application No. PCT/US2008/062191”, dated Nov. 10, 2009, 8 Pages. |
| “International Search Report Issued in PCT Application No. PCT/US2008/062191”, dated Oct. 21, 2008, 10 Pages. |
| “International Preliminary Report Issued in PCT Application No. PCT/US2009/034442”, dated Sep. 21, 2010, 4 Pages. |
| “International Search Report Issued in PCT Application No. PCT/US2009/034442”, dated Sep. 30, 2009, 12 Pages. |
| “International Preliminary Report Issued in PCT Application No. PCT/US2009/034601”, dated Sep. 21, 2010, 5 Pages. |
| “International Search Report and Written Opinion Issued in PCT Application No. PCT/US2009/034601”, dated Aug. 28, 2009, 3 Pages. |
| “International Preliminary Report Issued in PCT Application No. PCT/US2009/035602”, dated Sep. 28, 2010, 6 Pages. |
| “International Search Report & Written Opinion Issued in PCT Application No. PCT/US2009/035602”, dated Oct. 1, 2009, 10 Pages. |
| Scurrell, Mark, “Synchronizing Data between WinFS Stores”, Retrieved from <<http://blogs.msdn.com/b/winfs/archive/2006/01/25/517674.aspx>>, Jan. 25, 2006, 4 Pages. |
| “Office Action Issued in Japanese Patent Application No. 2011500835”, dated Apr. 2, 2013, 13 Pages. |
| “Notice of Allowance Issued in Japanese Patent Application No. 2011500835”, dated Oct. 7, 2013, 6 Pages. |
| “Amazon Simple Storage Service (Amazon S3)”, Retrieved from <<http://www.amazon.com/gp/browse,html?node=16427261>>, Oct. 9, 2007, 6 Pages. |
| “Mapping Between JSON and XML”, Retrieved from <<http://msdn.microsoft.com/en-us/library/bb924435.aspx>>, Feb. 6, 2008, 1 Page. |
| “Reply EP Communication Issued in EP Patent Application No. 08747323.7”, dated Jan. 22, 2010, 8 Pages. |
| “Communication Issued in EP Patent Application No. 08747323.7-1225”, dated Dec. 14, 2009. |
| “EP Communication Issued in EP Patent Application No. 09723161.7”, dated Oct. 21, 2011, 1 Page. |
| “Reply Non-Final Office Action Issued in U.S. Appl. No. 12/057,000”, dated Nov. 5, 2012, 17 Pages. |
| “Reply Final Office Action Issued in U.S. Appl. No. 12/057,000”, dated Mar. 24, 2011, 26 Pages. |
| “Notice of Allowance Issued in European Patent Application No. 09723161.7”, dated May 25, 2014, 7 Pages. |
| “Office Action Issued in European Patent Application No. 09723161.7”, dated Mar. 8, 2012, 5 Pages. |
| “Reply EP Communication Issued in EP Patent Application No. 09723161.7”, dated Jul. 6, 2012, 13 Pages. |
| “Reply EP Communication Issued in EP Patent Application No. 09723161.7”, dated Dec. 23, 2011, 15 Pages. |
| “Supplementary European Search Report Issued in European Patent Application No. 09723161.7”, dated Oct. 4, 2011, 8 Pages. |
| “Notice of Allowance Issued in Taiwan Patent Application No. 098105022”, dated Oct. 17, 2014, 4 Pages. |
| “Office Action and Search Report Issued in Taiwan Patent Application No. 098105022”, dated May 2, 2014, 8 Pages. |
| Zhao, et al., “Grid Metadata Catalog Service-Based OGC Web Registry Service”, In Proceedings of the 12th Annual ACM International Workshop on Geographic Information Systems, Nov. 12, 2004, pp. 22-30. |
| “Office Action Issued in Korean Patent Application No. 10-2010-7020791”, dated Aug. 21, 2015, 4 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 11/744,777”, dated Mar. 10, 2010, 9 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 11/744,777”, dated Aug. 17, 2010, 7 Pages. |
| “Reply Non-Final Office Action Issued in U.S. Appl. No. 11/744,777”, dated Jun. 10, 2010, 15 Pages. |
| “Reply Restriction/Election Issued in U.S. Appl. No. 11/744,777”, dated Dec. 22, 2009, 10 Pages. |
| “Restriction/Election Office Action Issued in U.S. Appl. No. 11/744,777”, dated Dec. 1, 2009, 6 Pages. |
| “Final Office Action Issued in U.S. Appl. No. 12/052,534”, dated Aug. 16, 2011, 20 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/052,534”, dated May 25, 2011, 32 Pages. |
| “Reply Final Office Action Issued in U.S. Appl. No. 12/052,534”, dated Nov. 16, 2011, 18 Pages. |
| “Reply Non-Final Office Action Issued in U.S. Appl. No. 12/052,534”, dated Jun. 30, 2011, 20 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/052,544”, dated Aug. 6, 2010, 10 Pages. |
| “Final Office Action Issued in U.S. Appl. No. 12/052,550”, dated Mar. 2, 2012, 21 Pages. |
| “Final Office Action Issued in U.S. Appl. No. 12/052,550”, dated Jun. 19, 2013, 46 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/052,550”, dated Nov. 22, 2016, 6 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/052,550”, dated Dec. 21, 2012, 40 Pages. |
| “Non-final Office Action Issued in U.S. Appl. No. 12/052,550”, dated Aug. 8, 2011, 17 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 12/052,550”, dated Apr. 21, 2017, 9 Pages. |
| “Amendment after Final Issued in U.S. Appl. No. 12/052,554”, dated Jul. 2, 2012, 16 Pages. |
| “Final Office Action Issued in U.S. Appl. No. 12/052,554”, dated Jan. 25, 2011, 43 Pages. |
| “Final Office Action Issued in U.S. Appl. No. 12/052,554”, dated Mar. 30, 2012, 44 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/052,554”, dated Aug. 5, 2010, 27 Pages. |
| “Notice of Allowance Issued in U.S. Appl. No. 12/052,554”, dated Aug. 6, 2012, 22 Pages. |
| “Reply Final Office Action Issued in U.S. Appl. No. 12/052,554”, dated Apr. 7, 2011, 31 Pages. |
| “Reply Non-Final Office Action Issued in U.S. Appl. No. 12/052,554”, dated Nov. 4, 2010, 25 Pages. |
| “Final Office Action Issued in U.S. Appl. No. 12/052,556”, dated Aug. 5, 2011, 23 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/052,556”, dated Feb. 17, 2011, 23 Pages. |
| “Reply Final Office Action Issued in U.S. Appl. No. 12/052,556”, dated Nov. 7, 2011, 22 Pages. |
| “Reply Non-Final Office Action Issued in U.S. Appl. No. 12/052,556”, dated May 16, 2011, 21 Pages. |
| “Final Office Action Issued in U.S. Appl. No. 12/057,000”, dated Jan. 21, 2011, 26 Pages. |
| “Final Office Action Issued in U.S. Appl. No. 12/057,000”, dated Jul. 19, 2013, 16 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/057,000”, dated Jul. 5, 2012, 9 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/057,000”, dated Jan. 16, 2013, 13 Pages. |
| “Non-Final Office Action Issued in U.S. Appl. No. 12/057,000”, dated Aug. 4, 2010, 14 Pages. |
| Vaas, Lisa, “Microsoft Aims to Mesh Disparate Calendars, Contacts”, Retrieved from <<http://www.eweek.com/c/a/Messaging-and-Collaboration/Microsoft-Aims-to-Mesh-Disparate-Calendars-Contacts>>, Nov. 21, 2005, 4 Pages. |
| Sollins, et al., “Linking in a Global information Architecture”, Retrieved from <<http://www.ana.lcs.mit.edu/people/sollins/links.html>>, Feb. 8, 2008, 18 Pages. |
| “Office Action Issued in Indian Patent Application No. 05480/CHENP/2010”, dated Mar. 7, 2018, 6 Pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170357498 A1 | Dec 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12052550 | Mar 2008 | US |
| Child | 15666145 | US |
