US20150067668A1 - Installation engine and package format - Google Patents
Installation engine and package format Download PDFInfo
- Publication number
- US20150067668A1 US20150067668A1 US14/535,262 US201414535262A US2015067668A1 US 20150067668 A1 US20150067668 A1 US 20150067668A1 US 201414535262 A US201414535262 A US 201414535262A US 2015067668 A1 US2015067668 A1 US 2015067668A1
- Authority
- US
- United States
- Prior art keywords
- version
- successor
- computer application
- predecessor
- executing
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/629—Protecting access to data via a platform, e.g. using keys or access control rules to features or functions of an application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/65—Updates
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
Definitions
- a software developer may continually upgrade a computer program on a user device.
- the user device may contact a server administered by the software developer to see if upgrades are available. If an upgrade is available, the user device may download the new sections of software and add those sections to the existing program currently installed on the user device.
- a processor may execute a predecessor version of a computer application.
- the processor may install a successor version of the computer application on a user account level.
- the processor may execute the successor version of the computer application.
- FIG. 1 illustrates, in a block diagram, one embodiment of a computer network.
- FIG. 2 illustrates, in a block diagram, one embodiment of a computing device.
- FIG. 3 illustrates, in a data flow diagram, one embodiment of an update service.
- FIG. 4 illustrates, in a block diagram, one embodiment of an update for a computer application.
- FIG. 5 illustrates, in a block diagram, one embodiment of a data storage layout.
- FIG. 6 illustrates, in a flowchart, one embodiment of a method for upgrading a computer application.
- the implementations may be a machine-implemented method, a tangible machine-readable medium having a set of instructions detailing a method stored thereon for at least one processor, or an application updater for a computing device.
- a computer device may maintain a user account for each user of a computer device.
- the user account may protect certain data files from access by other users of the computer device.
- An application updater may update a computer application on a per-user basis in addition to a traditional per-machine basis.
- the per-user basis may update the computer application for a user account, rather than the other user accounts on the machine.
- a user account may elevate a user privilege of the user account to install on a machine level.
- the application updater may extract the update in a new directory and data storage location, thus eliminating any file-in-use problems causing a reboot of the machine.
- different versions of the computer application may be installed side-by-side without interfering with other versions of the computer application previously installed on the machine, allowing the computer application to update silently, without causing any issues to the smooth performance of the computer application.
- the application updater may install the same version or a newer version of the computer application as part of an install, reinstall, or repair of the computer application without interfering with the current version. If the available version is an older version, the application updater may execute a null operation to prevent downgrading the computer application.
- the application updater may install multiple computer applications in parallel.
- an application updater may cleanly update a computer application without causing a fault or a reboot of either the system or the process.
- a processor may execute a predecessor version of a computer application.
- the processor may install a successor version of the computer application on a user account level.
- the processor may execute the successor version of the computer application.
- FIG. 1 illustrates, in a block diagram, one embodiment of a computer network 100 .
- a user device 110 may be a desktop computer, a laptop computer, a tablet computer, a handheld computer, or other computing device.
- the user device 110 may run a computer application 112 .
- the computer application 112 may be any software program or firmware program executed by the user device 110 .
- the computer application 112 may have a version indicating the iteration of the computer application 112 .
- the computer application 112 may have an updater module 114 that connects to an application server 120 via a data network connection 130 .
- the data network connection 130 may be a local area network connection, an internet connection, a mobile network connection, or other network connection.
- the updater module 114 may query the application server 120 to see if a new version of the computer application 112 is available.
- a predecessor version is the version of the computer application 112 currently being executed on the user device.
- a successor version is the new version of the computer application 112 .
- the updater module 114 may download the successor version to replace the predecessor version.
- FIG. 2 illustrates a block diagram of an exemplary computing device 200 which may act as an application updater.
- the computing device 200 may combine one or more of hardware, software, firmware, and system-on-a-chip technology to implement an application updater.
- the computing device 200 may include a bus 210 , a processor 220 , a memory 230 , a read only memory (ROM) 240 , a storage device 250 , an input device 260 , an output device 270 , and a communication interface 280 .
- the bus 210 may permit communication among the components of the computing device 200 .
- the processor 220 may include at least one conventional processor or microprocessor that interprets and executes a set of instructions.
- the memory 230 may be a random access memory (RAM) or another type of dynamic storage device that stores information and instructions for execution by the processor 220 .
- the memory 230 may also store temporary variables or other intermediate information used during execution of instructions by the processor 220 .
- the ROM 240 may include a conventional ROM device or another type of static storage device that stores static information and instructions for the processor 220 .
- the storage device 250 may include any type of tangible machine-readable medium, such as, for example, magnetic or optical recording media and its corresponding drive.
- a tangible machine-readable medium is a physical medium storing machine-readable code or instructions, as opposed to a transitory medium or signal.
- the storage device 250 may store a set of instructions detailing a method that when executed by one or more processors cause the one or more processors to perform the method.
- the input device 260 may include one or more conventional mechanisms that permit a user to input information to the computing device 200 , such as a keyboard, a mouse, a voice recognition device, a microphone, a headset, etc.
- the output device 270 may include one or more conventional mechanisms that output information to the user, including a display, a printer, one or more speakers, a headset, or a medium, such as a memory, or a magnetic or optical disk and a corresponding disk drive.
- the communication interface 280 may include any transceiver-like mechanism that enables computing device 200 to communicate with other devices or networks.
- the communication interface 280 may include a network interface or a transceiver interface.
- the communication interface 280 may be a wireless, wired, or optical interface.
- the computing device 200 may perform such functions in response to processor 220 executing sequences of instructions contained in a computer-readable medium, such as, for example, the memory 230 , a magnetic disk, or an optical disk. Such instructions may be read into the memory 230 from another computer-readable medium, such as the storage device 250 , or from a separate device via the communication interface 280 .
- a computer-readable medium such as, for example, the memory 230 , a magnetic disk, or an optical disk.
- Such instructions may be read into the memory 230 from another computer-readable medium, such as the storage device 250 , or from a separate device via the communication interface 280 .
- FIG. 3 illustrates, in a data flow diagram, one embodiment of an update service 300 for a computer application 112 .
- the current version 302 of the computer application 112 may direct an updater module 114 to request any updates from an application server 120 .
- the application server 120 may send an update package to the updater module 114 .
- the update package may have an update manifest 304 and a current binary 306 of the computer application 112 .
- the update manifest 304 is a list of the files that get installed.
- the update manifest 304 may describe a file path, a file size, any registry keys, and any error checking mechanisms for each file.
- the update manifest 304 may be in an extensible markup language (XML) format.
- the current binary 306 is an executable file or associated file, such as a digital link library, for the computer application 112 .
- the updater module 114 may use the update package to create the installer module 308 for installation.
- FIG. 4 illustrates, in a block diagram, one embodiment of an update 400 for a computer application.
- An update package 402 sent from an application server 120 may have an installer code 404 , a set of neutral resources 406 , a set of localizable resources 408 , and a payload 410 .
- the installer code 404 instantiates the installer module 308 on the user device 110 .
- the set of neutral resources 406 is a set of general resources used during installation, such as icons, non-localizable strings, and non-localizable images to be shown during installation.
- the set of localizable resources 408 is a set of language specific resources used during installation, such as messages, prompts, and sounds.
- the payload 410 may be the update manifest 304 and the current binary 306 .
- the data storage 250 may store a predecessor version 508 of a computer application 112 in a predecessor location 510 .
- a primary user account 504 may store a primary file name 512 in a primary name data storage location 514 referencing the predecessor version 508 .
- a file name is a hard link to a data file.
- the primary file name 512 may be a hard link to the predecessor version 508 .
- the predecessor version 508 may be immutable unless changed by the administrator account 502 .
- the primary user account 504 may install a user successor version 516 of the computer application 112 on a user account level.
- a user account level installation installs a user successor version 516 for the primary user account 504 but forgoes any update to a secondary user account 506 .
- the primary user account 504 may place the user successor version 516 in a clean user successor data storage location 518 .
- a clean data storage location does not currently have a version of the computer application 112 stored at that location.
- a data storage location may be considered clean even if a version of the computer application 112 was present at the data storage location and then conventionally erased, such as through deregistering.
- the user successor version 516 may be a complete successor version of the computer application 112 .
- a complete successor version is a successor version that has not been compared with the predecessor version and not had any overlapping sections removed.
- the primary file name 512 may be overwritten to be a hard link to the user successor version 516 .
- a secondary user account 506 may store a secondary file name 520 of the computer application 112 at a secondary name data storage location 522 .
- the secondary file name 520 may be a hard link to the predecessor version 508 .
- the secondary file name 520 may maintain the hard link to the predecessor version 508 even as the primary file name 512 becomes a hard link to the user successor version 516 .
- An administrator account 502 may replace the predecessor version 508 with an administrator successor version 524 of the computer application 112 on a machine level.
- the administrator account 502 may place the administrator successor version 524 in a clean administrator successor data storage location 524 .
- the operating system may elevate a user status for a user account to an administrative privilege to make updates at a machine level. Updates on a machine level install a successor version to each user account on the user device 110 .
- the administrator account 502 may reset the primary file name 512 and the secondary file name 520 to be hard links to the administrator successor version 524 .
- FIG. 6 illustrates, in a flowchart, one embodiment of a method 600 for upgrading a computer application 112 .
- the application updater may execute a predecessor version 508 of a computer application 112 (Block 602 ).
- the application updater may execute an updater module 114 invisibly to a user (Block 604 ).
- the application updater may download a complete successor version 516 using the updater module 114 disregarding the predecessor version 508 (Block 606 ). If the installation is on a per machine basis (Block 608 ), the application updater may elevate the user status to an administrative privilege (Block 610 ).
- the application updater may install the complete successor version 524 of the computer application 112 on a machine level (Block 612 ).
- the application updater may install a complete successor version 516 of the computer application on a user account level (Block 614 ).
- the application updater may maintain execution of the predecessor version 508 while installation of the complete successor version 516 occurs (Block 616 ).
- the application updater may place the complete successor version 516 in a clean successor data storage location 518 (Block 618 ).
- the application updater may execute the predecessor version 508 and the complete successor version 516 of the computer application 112 simultaneously (Block 620 ).
- the application updater may execute a switch from the predecessor version 508 to the complete successor version 516 (Block 622 ).
- the application updater may maintain a presentation of a user interface of the computer application 112 during the switch (Block 624 ).
- the application updater may schedule the predecessor version 508 for an uninstall operation (Block 626 ). If the uninstall operation is scheduled during a system reboot (Block 628 ), the application updater may uninstall predecessor version 508 during the system reboot (Block 630 ). Otherwise, the application updater may uninstall the predecessor version 508 while executing the complete successor version 516 (Block 632 ).
- Embodiments within the scope of the present invention may also include non-transitory computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon.
- Such non-transitory computer-readable storage media may be any available media that can be accessed by a general purpose or special purpose computer.
- non-transitory computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures. Combinations of the above should also be included within the scope of the non-transitory computer-readable storage media.
- Embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network.
- Computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions.
- Computer-executable instructions also include program modules that are executed by computers in stand-alone or network environments.
- program modules include routines, programs, objects, components, and data structures, etc. that perform particular tasks or implement particular abstract data types.
- Computer-executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Stored Programmes (AREA)
Abstract
Description
- This patent application is a continuation of U.S. patent application Ser. No. 13/350,810 on Jan. 15, 2012, which is herein incorporated by reference in its entirety.
- A software developer may continually upgrade a computer program on a user device. The user device may contact a server administered by the software developer to see if upgrades are available. If an upgrade is available, the user device may download the new sections of software and add those sections to the existing program currently installed on the user device.
- This Summary is provided to introduce a selection of concepts in a simplified form that is further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
- Embodiments discussed below relate to cleanly updating a computer application without causing a fault or a reboot of either the system or the process. A processor may execute a predecessor version of a computer application. The processor may install a successor version of the computer application on a user account level. The processor may execute the successor version of the computer application.
- In order to describe the manner in which the above-recited and other advantages and features can be obtained, a more particular description is set forth and will be rendered by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only typical embodiments and are not therefore to be considered to be limiting of its scope, implementations will be described and explained with additional specificity and detail through the use of the accompanying drawings.
-
FIG. 1 illustrates, in a block diagram, one embodiment of a computer network. -
FIG. 2 illustrates, in a block diagram, one embodiment of a computing device. -
FIG. 3 illustrates, in a data flow diagram, one embodiment of an update service. -
FIG. 4 illustrates, in a block diagram, one embodiment of an update for a computer application. -
FIG. 5 illustrates, in a block diagram, one embodiment of a data storage layout. -
FIG. 6 illustrates, in a flowchart, one embodiment of a method for upgrading a computer application. - Embodiments are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the subject matter of this disclosure. The implementations may be a machine-implemented method, a tangible machine-readable medium having a set of instructions detailing a method stored thereon for at least one processor, or an application updater for a computing device.
- A computer device may maintain a user account for each user of a computer device. The user account may protect certain data files from access by other users of the computer device. An application updater may update a computer application on a per-user basis in addition to a traditional per-machine basis. The per-user basis may update the computer application for a user account, rather than the other user accounts on the machine. A user account may elevate a user privilege of the user account to install on a machine level.
- Each time the application updater runs, the application updater may extract the update in a new directory and data storage location, thus eliminating any file-in-use problems causing a reboot of the machine. Further, different versions of the computer application may be installed side-by-side without interfering with other versions of the computer application previously installed on the machine, allowing the computer application to update silently, without causing any issues to the smooth performance of the computer application. The application updater may install the same version or a newer version of the computer application as part of an install, reinstall, or repair of the computer application without interfering with the current version. If the available version is an older version, the application updater may execute a null operation to prevent downgrading the computer application. The application updater may install multiple computer applications in parallel.
- Thus, in one embodiment, an application updater may cleanly update a computer application without causing a fault or a reboot of either the system or the process. A processor may execute a predecessor version of a computer application. The processor may install a successor version of the computer application on a user account level. The processor may execute the successor version of the computer application.
-
FIG. 1 illustrates, in a block diagram, one embodiment of acomputer network 100. A user device 110 may be a desktop computer, a laptop computer, a tablet computer, a handheld computer, or other computing device. The user device 110 may run acomputer application 112. Thecomputer application 112 may be any software program or firmware program executed by the user device 110. Thecomputer application 112 may have a version indicating the iteration of thecomputer application 112. Thecomputer application 112 may have anupdater module 114 that connects to anapplication server 120 via adata network connection 130. Thedata network connection 130 may be a local area network connection, an internet connection, a mobile network connection, or other network connection. Theupdater module 114 may query theapplication server 120 to see if a new version of thecomputer application 112 is available. A predecessor version is the version of thecomputer application 112 currently being executed on the user device. A successor version is the new version of thecomputer application 112. Theupdater module 114 may download the successor version to replace the predecessor version. -
FIG. 2 illustrates a block diagram of anexemplary computing device 200 which may act as an application updater. Thecomputing device 200 may combine one or more of hardware, software, firmware, and system-on-a-chip technology to implement an application updater. Thecomputing device 200 may include a bus 210, aprocessor 220, amemory 230, a read only memory (ROM) 240, astorage device 250, aninput device 260, an output device 270, and acommunication interface 280. The bus 210 may permit communication among the components of thecomputing device 200. - The
processor 220 may include at least one conventional processor or microprocessor that interprets and executes a set of instructions. Thememory 230 may be a random access memory (RAM) or another type of dynamic storage device that stores information and instructions for execution by theprocessor 220. Thememory 230 may also store temporary variables or other intermediate information used during execution of instructions by theprocessor 220. TheROM 240 may include a conventional ROM device or another type of static storage device that stores static information and instructions for theprocessor 220. Thestorage device 250 may include any type of tangible machine-readable medium, such as, for example, magnetic or optical recording media and its corresponding drive. A tangible machine-readable medium is a physical medium storing machine-readable code or instructions, as opposed to a transitory medium or signal. Thestorage device 250 may store a set of instructions detailing a method that when executed by one or more processors cause the one or more processors to perform the method. - The
input device 260 may include one or more conventional mechanisms that permit a user to input information to thecomputing device 200, such as a keyboard, a mouse, a voice recognition device, a microphone, a headset, etc. The output device 270 may include one or more conventional mechanisms that output information to the user, including a display, a printer, one or more speakers, a headset, or a medium, such as a memory, or a magnetic or optical disk and a corresponding disk drive. Thecommunication interface 280 may include any transceiver-like mechanism that enablescomputing device 200 to communicate with other devices or networks. Thecommunication interface 280 may include a network interface or a transceiver interface. Thecommunication interface 280 may be a wireless, wired, or optical interface. - The
computing device 200 may perform such functions in response toprocessor 220 executing sequences of instructions contained in a computer-readable medium, such as, for example, thememory 230, a magnetic disk, or an optical disk. Such instructions may be read into thememory 230 from another computer-readable medium, such as thestorage device 250, or from a separate device via thecommunication interface 280. -
FIG. 3 illustrates, in a data flow diagram, one embodiment of anupdate service 300 for acomputer application 112. Upon initiation, thecurrent version 302 of thecomputer application 112 may direct anupdater module 114 to request any updates from anapplication server 120. Theapplication server 120 may send an update package to theupdater module 114. The update package may have anupdate manifest 304 and acurrent binary 306 of thecomputer application 112. Theupdate manifest 304 is a list of the files that get installed. Theupdate manifest 304 may describe a file path, a file size, any registry keys, and any error checking mechanisms for each file. Theupdate manifest 304 may be in an extensible markup language (XML) format. Thecurrent binary 306 is an executable file or associated file, such as a digital link library, for thecomputer application 112. Theupdater module 114 may use the update package to create theinstaller module 308 for installation. -
FIG. 4 illustrates, in a block diagram, one embodiment of anupdate 400 for a computer application. Anupdate package 402 sent from anapplication server 120 may have aninstaller code 404, a set ofneutral resources 406, a set oflocalizable resources 408, and apayload 410. Theinstaller code 404 instantiates theinstaller module 308 on the user device 110. The set ofneutral resources 406 is a set of general resources used during installation, such as icons, non-localizable strings, and non-localizable images to be shown during installation. The set oflocalizable resources 408 is a set of language specific resources used during installation, such as messages, prompts, and sounds. Thepayload 410 may be theupdate manifest 304 and thecurrent binary 306. -
FIG. 5 illustrates, in a block diagram, one embodiment of adata storage layout 500. Auser device 100 may support multiple user accounts for multiple users. A user account may be password protected from other users. Thedata storage device 250 may store multiple application profiles for multiple users. A first user may update acomputer application 112 while a second user may forgo the update. Anadministrator 502 may update thecomputer application 112 for each user account. Aprimary user account 504 is the user account that is executing the update of the computer application. A secondary user account 506 is a user account that is not actively executing an update of the computer application. The secondary user account 506 may be active or dormant. - The
data storage 250 may store apredecessor version 508 of acomputer application 112 in apredecessor location 510. Aprimary user account 504 may store aprimary file name 512 in a primary name data storage location 514 referencing thepredecessor version 508. A file name is a hard link to a data file. Theprimary file name 512 may be a hard link to thepredecessor version 508. Thepredecessor version 508 may be immutable unless changed by theadministrator account 502. Theprimary user account 504 may install auser successor version 516 of thecomputer application 112 on a user account level. A user account level installation installs auser successor version 516 for theprimary user account 504 but forgoes any update to a secondary user account 506. Theprimary user account 504 may place theuser successor version 516 in a clean user successordata storage location 518. A clean data storage location does not currently have a version of thecomputer application 112 stored at that location. A data storage location may be considered clean even if a version of thecomputer application 112 was present at the data storage location and then conventionally erased, such as through deregistering. Theuser successor version 516 may be a complete successor version of thecomputer application 112. A complete successor version is a successor version that has not been compared with the predecessor version and not had any overlapping sections removed. Theprimary file name 512 may be overwritten to be a hard link to theuser successor version 516. - A secondary user account 506 may store a
secondary file name 520 of thecomputer application 112 at a secondary namedata storage location 522. Thesecondary file name 520 may be a hard link to thepredecessor version 508. Thesecondary file name 520 may maintain the hard link to thepredecessor version 508 even as theprimary file name 512 becomes a hard link to theuser successor version 516. - An
administrator account 502 may replace thepredecessor version 508 with anadministrator successor version 524 of thecomputer application 112 on a machine level. Theadministrator account 502 may place theadministrator successor version 524 in a clean administrator successordata storage location 524. The operating system may elevate a user status for a user account to an administrative privilege to make updates at a machine level. Updates on a machine level install a successor version to each user account on the user device 110. Theadministrator account 502 may reset theprimary file name 512 and thesecondary file name 520 to be hard links to theadministrator successor version 524. -
FIG. 6 illustrates, in a flowchart, one embodiment of amethod 600 for upgrading acomputer application 112. The application updater may execute apredecessor version 508 of a computer application 112 (Block 602). The application updater may execute anupdater module 114 invisibly to a user (Block 604). The application updater may download acomplete successor version 516 using theupdater module 114 disregarding the predecessor version 508 (Block 606). If the installation is on a per machine basis (Block 608), the application updater may elevate the user status to an administrative privilege (Block 610). The application updater may install thecomplete successor version 524 of thecomputer application 112 on a machine level (Block 612). If the installation is on a per user basis (Block 608), the application updater may install acomplete successor version 516 of the computer application on a user account level (Block 614). The application updater may maintain execution of thepredecessor version 508 while installation of thecomplete successor version 516 occurs (Block 616). The application updater may place thecomplete successor version 516 in a clean successor data storage location 518 (Block 618). The application updater may execute thepredecessor version 508 and thecomplete successor version 516 of thecomputer application 112 simultaneously (Block 620). The application updater may execute a switch from thepredecessor version 508 to the complete successor version 516 (Block 622). The application updater may maintain a presentation of a user interface of thecomputer application 112 during the switch (Block 624). The application updater may schedule thepredecessor version 508 for an uninstall operation (Block 626). If the uninstall operation is scheduled during a system reboot (Block 628), the application updater may uninstallpredecessor version 508 during the system reboot (Block 630). Otherwise, the application updater may uninstall thepredecessor version 508 while executing the complete successor version 516 (Block 632). - 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 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 for implementing the claims.
- Embodiments within the scope of the present invention may also include non-transitory computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon. Such non-transitory computer-readable storage media may be any available media that can be accessed by a general purpose or special purpose computer. By way of example, and not limitation, such non-transitory computer-readable storage media can comprise RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions or data structures. Combinations of the above should also be included within the scope of the non-transitory computer-readable storage media.
- Embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices that are linked (either by hardwired links, wireless links, or by a combination thereof) through a communications network.
- Computer-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Computer-executable instructions also include program modules that are executed by computers in stand-alone or network environments. Generally, program modules include routines, programs, objects, components, and data structures, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of such executable instructions or associated data structures represents examples of corresponding acts for implementing the functions described in such steps.
- Although the above description may contain specific details, they should not be construed as limiting the claims in any way. Other configurations of the described embodiments are part of the scope of the disclosure. For example, the principles of the disclosure may be applied to each individual user where each user may individually deploy such a system. This enables each user to utilize the benefits of the disclosure even if any one of a large number of possible applications do not use the functionality described herein. Multiple instances of electronic devices each may process the content in various possible ways. Implementations are not necessarily in one system used by all end users. Accordingly, the appended claims and their legal equivalents should only define the invention, rather than any specific examples given.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/535,262 US20150067668A1 (en) | 2012-01-15 | 2014-11-06 | Installation engine and package format |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/350,810 US8893116B2 (en) | 2012-01-15 | 2012-01-15 | Installation engine and package format for parallelizable, reliable installations |
US14/535,262 US20150067668A1 (en) | 2012-01-15 | 2014-11-06 | Installation engine and package format |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/350,810 Continuation US8893116B2 (en) | 2012-01-15 | 2012-01-15 | Installation engine and package format for parallelizable, reliable installations |
Publications (1)
Publication Number | Publication Date |
---|---|
US20150067668A1 true US20150067668A1 (en) | 2015-03-05 |
Family
ID=48780903
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/350,810 Active 2032-03-14 US8893116B2 (en) | 2012-01-15 | 2012-01-15 | Installation engine and package format for parallelizable, reliable installations |
US14/535,262 Abandoned US20150067668A1 (en) | 2012-01-15 | 2014-11-06 | Installation engine and package format |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/350,810 Active 2032-03-14 US8893116B2 (en) | 2012-01-15 | 2012-01-15 | Installation engine and package format for parallelizable, reliable installations |
Country Status (11)
Country | Link |
---|---|
US (2) | US8893116B2 (en) |
EP (1) | EP2805233B1 (en) |
JP (1) | JP6198229B2 (en) |
KR (1) | KR102052776B1 (en) |
CN (1) | CN104040495A (en) |
AU (1) | AU2013208296B2 (en) |
BR (1) | BR112014017283B1 (en) |
CA (1) | CA2860657C (en) |
MX (1) | MX337871B (en) |
RU (1) | RU2635891C2 (en) |
WO (1) | WO2013106276A1 (en) |
Families Citing this family (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2508599A (en) * | 2012-12-04 | 2014-06-11 | Ibm | Software version management when downgrading software |
US9639342B2 (en) * | 2013-05-01 | 2017-05-02 | Starkey Laboratories, Inc. | Unobtrusive firmware updates for hearing assistance devices |
CN103442077A (en) * | 2013-09-04 | 2013-12-11 | 珠海金山网络游戏科技有限公司 | Method and system for updating software client through network |
CN108733517A (en) * | 2018-06-05 | 2018-11-02 | 深圳忆联信息系统有限公司 | SSD firmware upgrades guard method and device |
CN109933465B (en) * | 2019-03-12 | 2021-12-10 | 北京同城必应科技有限公司 | Exception handling method, exception handling device, server and storage medium |
CN111769966B (en) * | 2020-05-08 | 2023-06-23 | 厦门亿联网络技术股份有限公司 | Clone upgrading method, system and application |
WO2024010177A1 (en) * | 2022-07-04 | 2024-01-11 | 삼성전자 주식회사 | Electronic device for updating applet of security circuit and method for operating same |
Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5835911A (en) * | 1994-02-08 | 1998-11-10 | Fujitsu Limited | Software distribution and maintenance system and method |
US5966715A (en) * | 1995-12-29 | 1999-10-12 | Csg Systems, Inc. | Application and database security and integrity system and method |
US20020083083A1 (en) * | 1999-11-12 | 2002-06-27 | Dell Usa, L.P. | System and method for ensuring proper execution of scheduled file updates |
US6463352B1 (en) * | 1999-01-21 | 2002-10-08 | Amada Cutting Technologies, Inc. | System for management of cutting machines |
US20040133606A1 (en) * | 2003-01-02 | 2004-07-08 | Z-Force Communications, Inc. | Directory aggregation for files distributed over a plurality of servers in a switched file system |
US20070006216A1 (en) * | 2002-04-30 | 2007-01-04 | Toshiba Tec Kabushiki Kaisha | Program management apparatus, program management system, and program management method |
US20070022083A1 (en) * | 2005-07-21 | 2007-01-25 | International Business Machines Corporation | Method of graphical display of hierarchical hardlinks to files in a file system |
US20070240148A1 (en) * | 2006-04-11 | 2007-10-11 | Brother Kogyo Kabushiki Kaisha | Information processor with configuration modification function |
US20070240152A1 (en) * | 2006-03-24 | 2007-10-11 | Red. Hat, Inc. | System and method for sharing software certification and process metadata |
US20090259999A1 (en) * | 2008-04-11 | 2009-10-15 | Oracle International Corporation | Method and system for applying a patch during application execution |
US20100017809A1 (en) * | 2008-07-16 | 2010-01-21 | Sandisk Il Ltd. | Methods for enabling software in storage-capable devices |
US20100058321A1 (en) * | 2008-09-04 | 2010-03-04 | Anderson Greg L | Approach for deploying software to network devices |
US20100218177A1 (en) * | 2009-02-25 | 2010-08-26 | Fujitsu Limited | Storage apparatus and software upgrade method |
US20100242037A1 (en) * | 2009-03-17 | 2010-09-23 | Microsoft Corporation | Software Deployment over a Network |
US20100313105A1 (en) * | 2009-06-04 | 2010-12-09 | Abbott Diabetes Care Inc. | Method and System for Updating a Medical Device |
US20110197114A1 (en) * | 2004-12-08 | 2011-08-11 | John Martin | Electronic message response and remediation system and method |
US20110289499A1 (en) * | 2010-05-19 | 2011-11-24 | Microsoft Corporation | Techniques to automatically update software applications |
US20120011496A1 (en) * | 2009-03-30 | 2012-01-12 | Nec Corporation | Service providing apparatus, service providing system, method of processing data in service providing apparatus, and computer program |
US20120137278A1 (en) * | 2010-11-30 | 2012-05-31 | International Business Machines Corporation | Generating a customized set of tasks for migration of a deployed software solution |
US9733921B1 (en) * | 2014-01-23 | 2017-08-15 | NetSuite Inc. | System and methods for management of cloud application extensions |
Family Cites Families (31)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0954734A (en) * | 1995-08-17 | 1997-02-25 | Fujitsu Ltd | System and method for software distribution/maintenance utilizing network |
US5764992A (en) * | 1995-06-06 | 1998-06-09 | Apple Computer, Inc. | Method and apparatus for automatic software replacement |
US5732275A (en) * | 1996-01-11 | 1998-03-24 | Apple Computer, Inc. | Method and apparatus for managing and automatically updating software programs |
GB9623298D0 (en) | 1996-11-08 | 1997-01-08 | Int Computers Ltd | Updating mechanism for software |
JPH1145179A (en) * | 1997-07-25 | 1999-02-16 | Digital Vision Lab:Kk | Program managing method |
US6141683A (en) * | 1998-01-30 | 2000-10-31 | Lucent Technologies, Inc. | Method for remotely and reliably updating of the software on a computer with provision for roll back |
US7287259B2 (en) * | 2000-04-24 | 2007-10-23 | Microsoft Corporation | Isolating assembly versions for binding to application programs |
US6711557B1 (en) * | 2000-08-14 | 2004-03-23 | Adobe Systems Incorporated | Client-based background update monitoring |
US20040003266A1 (en) | 2000-09-22 | 2004-01-01 | Patchlink Corporation | Non-invasive automatic offsite patch fingerprinting and updating system and method |
TW518513B (en) * | 2001-03-28 | 2003-01-21 | Synq Technology Inc | System and method to update an executing application software by modular way |
US20040010786A1 (en) * | 2002-07-11 | 2004-01-15 | Microsoft Corporation | System and method for automatically upgrading a software application |
US7784044B2 (en) * | 2002-12-02 | 2010-08-24 | Microsoft Corporation | Patching of in-use functions on a running computer system |
US20080177994A1 (en) * | 2003-01-12 | 2008-07-24 | Yaron Mayer | System and method for improving the efficiency, comfort, and/or reliability in Operating Systems, such as for example Windows |
US7089548B2 (en) * | 2003-01-13 | 2006-08-08 | Taiwan Semiconductor Manufacturing Company, Ltd. | Method and system for nondisruptive deployment during upgrading of enterprise systems |
US7228541B2 (en) * | 2003-01-17 | 2007-06-05 | National Instruments Corporation | Creation of application system installer |
US7546594B2 (en) * | 2003-12-15 | 2009-06-09 | Microsoft Corporation | System and method for updating installation components using an installation component delta patch in a networked environment |
JP2005301500A (en) * | 2004-04-08 | 2005-10-27 | Fujitsu Ltd | Information processor |
US7664834B2 (en) * | 2004-07-09 | 2010-02-16 | Maxsp Corporation | Distributed operating system management |
US20060075001A1 (en) * | 2004-09-30 | 2006-04-06 | Canning Jeffrey C | System, method and program to distribute program updates |
JP2006119901A (en) | 2004-10-21 | 2006-05-11 | Toshiba Corp | Portable electronic apparatus and application updating method for the portable electronic apparatus |
US7810089B2 (en) | 2004-12-30 | 2010-10-05 | Citrix Systems, Inc. | Systems and methods for automatic installation and execution of a client-side acceleration program |
US7774195B2 (en) * | 2005-03-08 | 2010-08-10 | Microsoft Corporation | Method and system for creating, storing, managing and consuming culture specific data |
JP2006268752A (en) * | 2005-03-25 | 2006-10-05 | Seiko Epson Corp | Activation of module corresponding to a plurality of versions |
US20060271926A1 (en) * | 2005-05-31 | 2006-11-30 | Microsoft Corporation | Split download for electronic software downloads |
SE529676C2 (en) * | 2006-03-02 | 2007-10-23 | Abb Ab | A method for evaluating an application, an automation system and a control unit |
US8769522B2 (en) * | 2006-08-21 | 2014-07-01 | Citrix Systems, Inc. | Systems and methods of installing an application without rebooting |
US20080301660A1 (en) * | 2007-05-30 | 2008-12-04 | Google Inc. | Maintaining Multiple Versions of a Software Application on a Device |
US20090193409A1 (en) * | 2008-01-24 | 2009-07-30 | Microsoft Corporation | Per User Updates |
US20090319740A1 (en) * | 2008-06-18 | 2009-12-24 | Fujitsu Limited | Virtual computer system, information processing device providing virtual computer system, and program thereof |
CN102299940A (en) * | 2010-06-25 | 2011-12-28 | 龚华清 | Software upgrading method of persistent network service |
US8726103B2 (en) | 2010-12-07 | 2014-05-13 | At & T Intellectual Property I, Lp | Visual outage management tool |
-
2012
- 2012-01-15 US US13/350,810 patent/US8893116B2/en active Active
-
2013
- 2013-01-07 MX MX2014008561A patent/MX337871B/en active IP Right Grant
- 2013-01-07 JP JP2014552230A patent/JP6198229B2/en active Active
- 2013-01-07 BR BR112014017283-8A patent/BR112014017283B1/en active IP Right Grant
- 2013-01-07 CA CA2860657A patent/CA2860657C/en active Active
- 2013-01-07 RU RU2014128842A patent/RU2635891C2/en active
- 2013-01-07 EP EP13736340.4A patent/EP2805233B1/en active Active
- 2013-01-07 WO PCT/US2013/020519 patent/WO2013106276A1/en active Application Filing
- 2013-01-07 AU AU2013208296A patent/AU2013208296B2/en active Active
- 2013-01-07 CN CN201380005517.3A patent/CN104040495A/en active Pending
- 2013-01-07 KR KR1020147019519A patent/KR102052776B1/en active IP Right Grant
-
2014
- 2014-11-06 US US14/535,262 patent/US20150067668A1/en not_active Abandoned
Patent Citations (20)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5835911A (en) * | 1994-02-08 | 1998-11-10 | Fujitsu Limited | Software distribution and maintenance system and method |
US5966715A (en) * | 1995-12-29 | 1999-10-12 | Csg Systems, Inc. | Application and database security and integrity system and method |
US6463352B1 (en) * | 1999-01-21 | 2002-10-08 | Amada Cutting Technologies, Inc. | System for management of cutting machines |
US20020083083A1 (en) * | 1999-11-12 | 2002-06-27 | Dell Usa, L.P. | System and method for ensuring proper execution of scheduled file updates |
US20070006216A1 (en) * | 2002-04-30 | 2007-01-04 | Toshiba Tec Kabushiki Kaisha | Program management apparatus, program management system, and program management method |
US20040133606A1 (en) * | 2003-01-02 | 2004-07-08 | Z-Force Communications, Inc. | Directory aggregation for files distributed over a plurality of servers in a switched file system |
US20110197114A1 (en) * | 2004-12-08 | 2011-08-11 | John Martin | Electronic message response and remediation system and method |
US20070022083A1 (en) * | 2005-07-21 | 2007-01-25 | International Business Machines Corporation | Method of graphical display of hierarchical hardlinks to files in a file system |
US20070240152A1 (en) * | 2006-03-24 | 2007-10-11 | Red. Hat, Inc. | System and method for sharing software certification and process metadata |
US20070240148A1 (en) * | 2006-04-11 | 2007-10-11 | Brother Kogyo Kabushiki Kaisha | Information processor with configuration modification function |
US20090259999A1 (en) * | 2008-04-11 | 2009-10-15 | Oracle International Corporation | Method and system for applying a patch during application execution |
US20100017809A1 (en) * | 2008-07-16 | 2010-01-21 | Sandisk Il Ltd. | Methods for enabling software in storage-capable devices |
US20100058321A1 (en) * | 2008-09-04 | 2010-03-04 | Anderson Greg L | Approach for deploying software to network devices |
US20100218177A1 (en) * | 2009-02-25 | 2010-08-26 | Fujitsu Limited | Storage apparatus and software upgrade method |
US20100242037A1 (en) * | 2009-03-17 | 2010-09-23 | Microsoft Corporation | Software Deployment over a Network |
US20120011496A1 (en) * | 2009-03-30 | 2012-01-12 | Nec Corporation | Service providing apparatus, service providing system, method of processing data in service providing apparatus, and computer program |
US20100313105A1 (en) * | 2009-06-04 | 2010-12-09 | Abbott Diabetes Care Inc. | Method and System for Updating a Medical Device |
US20110289499A1 (en) * | 2010-05-19 | 2011-11-24 | Microsoft Corporation | Techniques to automatically update software applications |
US20120137278A1 (en) * | 2010-11-30 | 2012-05-31 | International Business Machines Corporation | Generating a customized set of tasks for migration of a deployed software solution |
US9733921B1 (en) * | 2014-01-23 | 2017-08-15 | NetSuite Inc. | System and methods for management of cloud application extensions |
Also Published As
Publication number | Publication date |
---|---|
RU2014128842A (en) | 2016-02-10 |
AU2013208296B2 (en) | 2018-03-15 |
JP6198229B2 (en) | 2017-09-20 |
CA2860657A1 (en) | 2013-07-18 |
EP2805233A4 (en) | 2015-08-26 |
CN104040495A (en) | 2014-09-10 |
EP2805233B1 (en) | 2022-11-16 |
MX337871B (en) | 2016-03-22 |
BR112014017283A2 (en) | 2017-06-13 |
BR112014017283B1 (en) | 2021-08-17 |
JP2015503812A (en) | 2015-02-02 |
AU2013208296A1 (en) | 2014-07-31 |
WO2013106276A1 (en) | 2013-07-18 |
RU2635891C2 (en) | 2017-11-16 |
CA2860657C (en) | 2020-10-13 |
EP2805233A1 (en) | 2014-11-26 |
KR20140113685A (en) | 2014-09-24 |
MX2014008561A (en) | 2014-09-26 |
US8893116B2 (en) | 2014-11-18 |
KR102052776B1 (en) | 2019-12-05 |
BR112014017283A8 (en) | 2017-12-12 |
US20130185709A1 (en) | 2013-07-18 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20150067668A1 (en) | Installation engine and package format | |
US8584115B2 (en) | Automated operating system device driver updating system | |
US9032052B2 (en) | Deployment of a driver or an application on a client device having a write-filter | |
US9146729B2 (en) | Deployment and updating of applications and drivers on a client device using an extensible markup language (XML) configuration file | |
US7310801B2 (en) | Servicing a component-based software product throughout the software product lifecycle | |
US7590599B2 (en) | System and method of automatically maintaining and recycling software components | |
US20130139139A1 (en) | Automatic updating of an application or a driver on a client device using a deployment configuration file | |
US20130139183A1 (en) | Creation or installation of a disk image for a target device having one of a plurality of hardware platforms | |
US8769521B2 (en) | Calendar aware adaptive patching of a computer program | |
CN103677937A (en) | Method and device for upgrading and running software | |
CN106293790B (en) | application program upgrading method and device based on Firefox operating system | |
CN116069366A (en) | Client application program updating method and device, storage medium and electronic equipment | |
CN105912352A (en) | Method and terminal for upgrading in mobile terminal | |
CN108733426B (en) | Method and device for running application by electronic equipment and electronic equipment | |
JP2014002600A (en) | Program, communication device, and installation method | |
KR20070071758A (en) | Mobile communication terminal enable to upgrade and its operating method | |
WO2011087352A1 (en) | A profiling remote management system and a method of profiling remote management |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: MICROSOFT CORPORATION, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:HAUBOLD, JEREMY;PACCIARINI, CLAUDIO;REEL/FRAME:034122/0463 Effective date: 20141105 |
|
AS | Assignment |
Owner name: MICROSOFT TECHNOLOGY LICENSING, LLC, WASHINGTON Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MICROSOFT CORPORATION;REEL/FRAME:034819/0001 Effective date: 20150123 |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: FINAL REJECTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: NON FINAL ACTION MAILED |
|
STPP | Information on status: patent application and granting procedure in general |
Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |