Application software installation method, application operating system, electronic equipment and vehicle

Abstract

The invention discloses an application software installation method, an application operating system, electronic equipment and a vehicle. The application software installation method comprises the following steps: determining that an application state attribute of application software meets a resident software attribute condition of the application operating system; and in response to the installation request of the application software, the application software is controlled to be allowed to be installed, so that the application software is installed, by adopting the method, the requirement of a user for updating the resident software can be met, and the user experience is improved.

Description

Technical Field

[0001] The present invention relates to the technical field of electronic equipment, and in particular to an application software installation method, an application operating system, an electronic equipment and a vehicle. Background Art

[0002] In the related art, the existing operating system can only implement the installation and update of non-resident software, but cannot implement the installation and update of resident software, thereby failing to meet the user's demand for resident software update and reducing the user experience. Summary of the invention

[0003] The present invention aims to solve at least one of the technical problems existing in the prior art. To this end, one object of the present invention is to provide an application software installation method, which can meet the user's demand for resident software updates and improve user experience.

[0004] A second objective of the present invention is to provide an application operating system.

[0005] A third object of the present invention is to provide a computer storage medium.

[0006] A fourth objective of the present invention is to provide an electronic device.

[0007] A fifth object of the present invention is to provide a vehicle.

[0008] In order to solve the above problems, an embodiment of the first aspect of the present invention provides an application software installation method, comprising: determining that the application status attribute of the application software satisfies the resident software attribute condition of the application operating system; in response to the installation request of the application software, controlling the application software to allow installation so as to install the application software.

[0009] According to the application software installation method of the embodiment of the present invention, when it is determined that the application software is resident software and a request for installation of the resident software is received, the resident software is controlled to allow installation so as to install and update the resident software, thereby satisfying the user's demand for resident software updates and improving the user experience.

[0010] In some embodiments, the resident software attribute condition is that the state attribute flag of the application software is that the persistent attribute is true.

[0011] In some embodiments, the installation method further includes: during the installation of the application software, executing an operation of killing the application software process; and when it is determined that the application software meets the installation completion condition, starting the application software.

[0012] In some embodiments, during the process of killing the application software process, a preset flag is set for the application software process so that after killing the application software process, the application software is not restarted.

[0013] In some embodiments, during the process of killing the application software process, setting a preset flag bit for the application software process includes: during the process of killing the application software process, setting the preset flag bit of the application software process to false.

[0014] In some embodiments, the method further includes: when a preset flag bit of the application software process is false, after killing the application software process, performing a cleanup operation on the application software.

[0015] In some embodiments, the installation completion condition includes: the installation file of the application software has been cleared.

[0016] In some embodiments, the installation method further includes: registering a death monitor for the application software, wherein the death monitor is used to monitor the process of the application software and restart the process of the application software when the process of the application software is in a killed state.

[0017] In some embodiments, the installation method further includes: installing the application software by using install installation, silent installation or third-party installation.

[0018] The second aspect of the present invention provides an application operating system, comprising: at least one processor; a memory communicatively connected to at least one of the processors; wherein the memory stores a computer program executable by at least one of the processors, and when at least one of the processors executes the computer program, the application software installation method described in the above embodiment is implemented.

[0019] The application operating system according to the embodiment of the present invention can meet the user's demand for resident software updates and improve the user experience by executing the application software installation method of the above embodiment.

[0020] A third aspect of the present invention provides a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the application software installation method described in the above embodiment.

[0021] A fourth aspect of the present invention provides an electronic device, comprising the application operating system described in the above embodiment.

[0022] The electronic device according to the embodiment of the present invention can meet the user's demand for resident software update and improve the user experience through the application operating system of the above embodiment.

[0023] A fifth aspect of the present invention provides a vehicle, comprising the application operating system described in the above embodiment.

[0024] The vehicle according to the embodiment of the present invention can meet the user's demand for resident software updates and improve the user experience through the application operating system of the above embodiment.

[0025] Additional aspects and advantages of the present invention will be given in part in the following description and in part will be obvious from the following description, or will be learned through practice of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The above and / or additional aspects and advantages of the present invention will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0027] Figure 1 is a flow chart of an application software installation method according to an embodiment of the present invention;

[0028] Figure 2 is a flow chart of an application software installation method according to another embodiment of the present invention;

[0029] Figure 3 is a structural block diagram of an application operating system according to an embodiment of the present invention;

[0030] Figure 4 is a structural block diagram of an electronic device according to an embodiment of the present invention;

[0031] Figure 5 is a structural block diagram of a vehicle according to an embodiment of the present invention.

[0032] Reference numerals:

[0033] Application operating system 10; electronic device 20; vehicle 30;

[0034] Processor 1; Memory 2. DETAILED DESCRIPTION

[0035] Embodiments of the present invention are described in detail below. The embodiments described with reference to the accompanying drawings are exemplary. Embodiments of the present invention are described in detail below.

[0036] In the prior art, the application operating system prohibits the installation of resident software (software persistent attribute is true). The purpose is to assume that since the software is chosen to be resident, it cannot be actively updated in the intermediate stage to ensure security. It can also reduce the necessity of setting system applications as resident and ensure system performance.

[0037] In order to solve the above problems, a first aspect of the present invention provides an application software installation method, which can meet the user's demand for resident software updates and improve the user experience.

[0038] Reference below Figure 1 Describe the application software installation method according to the embodiment of the present invention. Figure 1 As shown, the method includes steps S1 and S2.

[0039] Step S1, determining whether the application state attribute of the application software satisfies the resident software attribute condition of the application operating system.

[0040] Specifically, the application software is a package file, which stores the application status attributes of the application software, wherein the application status attributes are written and packaged into an application software package during the development stage, and a process of the application software is created when the application software is packaged into an operating system and run. When the process of the application software is created, the application status attributes are read from the application software package, and then it is determined whether the application status attributes of the application software meet the resident software attribute conditions of the application operating system. If it is determined that the application status attributes of the application software meet the resident software attribute conditions of the application operating system, that is, the application status attributes of the application software are application status attributes of resident software, then the application software is determined to be resident software, wherein the resident software can be software pre-installed in the system such as setting software or Launcher (desktop launcher) software, and there is no restriction on this.

[0041] Step S2, in response to the installation request of the application software, controlling the application software to allow installation, so as to install the application software.

[0042] Specifically, the existing operating system can only implement the installation and update of non-resident software, but cannot implement the installation and update of resident software, thereby failing to meet the user's demand for resident software update, reducing the user experience. In order to solve this problem, if it is determined that the application state attribute of the application software meets the resident software attribute condition of the application operating system, in response to the installation request of the application software, the application software is controlled to allow installation, so as to install the application software. That is to say, if the application state attribute of the application software is the application state attribute of the resident software, the application software is determined to be resident software, and the application operating system controls the resident software to allow installation in response to the installation request of the application software, that is, the conditional restriction that the resident software is not allowed to be installed is removed, so as to install and update the resident software, thereby meeting the user's demand for resident software update and improving the user experience. In addition, the application software installation method in the present application can also realize the installation of non-resident software.

[0043] According to the application software installation method of the embodiment of the present invention, when it is determined that the application software is resident software and a request for installation of the resident software is received, the resident software is controlled to allow installation so as to install and update the resident software, thereby satisfying the user's demand for resident software updates and improving the user experience.

[0044] In some embodiments, the resident software attribute condition is that the application state attribute flag is that the persistent attribute is true.

[0045] Specifically, the application operating system includes resident software and non-resident software. The application state attribute flag of the resident software configuration in the application operating system is that the persistent attribute is true, wherein the persistent attribute is a flag of whether the application is resident, and is used to keep the resident software alive. It is effective only when the resident software in the system is in effect. The application state attribute flag of the resident software is represented by persistent = "true" attribute, and the application state attribute flag of the non-resident software configuration in the application operating system is that the persistent attribute is false, and the application state attribute flag of the non-resident software is represented by persistent = "false" attribute. Therefore, if it is determined that the application state attribute of the application software satisfies the application state attribute flag that the persistent attribute is true, then the application software is determined to be resident software. In addition, if the application state attribute of the application software is that the persistent attribute is false, then the application software is determined to be non-resident software.

[0046] In an embodiment, the application state attribute of the resident software is marked as having a persistent attribute that is true so as to be sequentially transmitted in different classes.

[0047] In some embodiments, during the application software installation process, an operation of killing the application software process is performed; when it is determined that the application software meets the installation completion condition, the application software is started.

[0048] Specifically, during the installation of the application software, in order to ensure the effective use of system resources and avoid conflicts between old and new application software, it is necessary to kill the running application software process first. At the same time, after killing the running application software process, it is necessary to still be able to maintain the feature of restarting the application software to maintain the active functions of the application. As for the timing of restarting the application software, the present application determines through the early debugging and testing phase that the application software meets the installation completion conditions as the appropriate time, thereby avoiding affecting the operation of existing programs. That is to say, when it is determined that the application software meets the installation completion conditions, the installation completion conditions can be obtaining information on deleting the installation file of the application software and starting the application software, thereby maintaining the active functions of the application while avoiding problems in program development.

[0049] In some embodiments, during the process of killing the application software process, a preset flag is set for the application software process so that the application software is not restarted after the application software process is killed.

[0050] Specifically, during the installation of application software, in order to ensure the effective use of system resources and avoid conflicts between old and new application software, it is necessary to kill the process of the running application software first. That is, the application operating system responds to the installation request, obtains the installation file of the application software, and needs to kill the process of the application software when updating the application software through the installation file of the application software, and the application software process remains in the killed state, that is, it does not restart. Therefore, during the process of killing the application software process, the AMS (Activity Manager Service) of the application operating system needs to control the application software process not to restart. ManagerService) needs to control the application software process not to restart during the process of killing the application software process. Among them, AMS is the core service of the application operating system and is mainly responsible for the startup, communication, and partial life cycle management of the four major components in the system, as well as processing activities, processes, and services. AMS is also used to manage the application software process. AMS starts the process of killing the application software process by calling the AMS.KillApplication method, which is the instruction to kill the application software process. In the process of killing the application software process, a preset flag is set for the application software process so that the application software will not restart after the application software process is killed. Therefore, in this application, the application software process is killed and the killed state is maintained by setting a preset flag for the application software process, and the original properties of the application are not modified.

[0051] In some embodiments, during the process of killing the application software process, setting a preset flag bit for the application software process includes: during the process of killing the application software process, setting the preset flag bit of the application software process to false.

[0052] Specifically, during the installation of the application software, in order to ensure the effective use of system resources and avoid conflicts between old and new application software, it is necessary to kill the process of the running application software first. Therefore, the AMS of the application operating system sets the preset flag of the application software to false in the process of killing the application software process to control the process of the application software from being restarted. That is to say, the AMS starts the process of killing the application software process by calling the AMS.KillApplication method, which is the instruction to kill the application software process, and sets the preset flag of the application software process to false during the execution of killing the application software process, which can be represented by the persistent attribute of the application software process being false, so as to kill the process of the application software and force the application software to stop. Based on the preset flag of the application software process being false, it is ensured that the process of the application software is killed, and then the application software is installed according to the installation file. In addition, if the preset flag of the application software process is true, the application software process is restarted. Therefore, in the present application, the application software process is killed and the killed state is maintained by modifying the preset flag of the application software process, and the original attributes of the application program are not modified. In addition, after the application software process attributes are modified, the application software process attributes will not be modified in other programs, and after determining whether the application software process is restarted, it will no longer have other uses.

[0053] Exemplarily, the application software is resident software. When the resident software is installed, the process of the resident software needs to be killed, and the process of the resident software remains in the killed state, that is, it is not restarted. AMS starts the process of killing the resident software process by calling the AMS.KillApplication method, which is the instruction to kill the resident software process. In the process of killing the application software process, the preset flag of the application software process is set to false, which can be represented by the persistent attribute of the resident software process being false, that is, the preset flag of the resident software process, that is, the attribute is set to a non-resident software process, so as to execute the process of killing the non-resident software process, thereby no longer executing the process of restarting the resident software process. When the death monitor of the commonly used software monitors and cleans the process of the resident software, since the preset flag of the resident software is set from true to false, the process of the resident software is cleaned as a non-resident software process, and the process of the resident software is no longer restarted, thereby ensuring that the resident software can be installed.

[0054] In some embodiments, if the preset flag of the application software process is true, the application software process is restarted and the death monitor of the application software process is re-registered.

[0055] In some embodiments, when the electronic device is powered on, a death monitor of the application software process is registered to manage and monitor the application software process.

[0056] In some embodiments, when the preset flag of the application software process is false, after killing the application software process, a cleanup operation is performed on the application software. Exemplarily, when the preset flag of the resident software process is false, after killing the resident software process, a cleanup operation is performed on the resident software.

[0057] In some embodiments, after the application software process is killed, the application software process object is removed from the memory, thereby ensuring the security of process modification.

[0058] In some embodiments, the installation completion condition includes: the installation files of the application software have been cleared. Exemplarily, after the installation of the application software is complete, the installation files of the application software will be deleted through the PMS (Package Manager Service) of the application operating system, where PMS is the core service of the application operating system, used for installation and uninstallation of application software packages. The installation files of the application software, i.e., the application software package, can be deleted by calling the method for deleting the application software package in the PMS. Therefore, if it is determined that the installation files of the application software have been cleared, it is determined that the installation of the application software is complete.

[0059] In some embodiments, in response to an installation request, an installation file of the application software is obtained; a kill process attribute of the application software is set to false; and based on the kill process attribute of the application software being false, the application software is installed according to the installation file.

[0060] In some embodiments, it is determined that the application software meets the installation completion conditions; in response to the start-up and run instructions of the application software, a death monitor for the application software is registered according to the application status attributes of the application software, and the death monitor is used to monitor the process of the application software and restart the process of the application software when the process of the application software is in a killed state.

[0061] Specifically, the death monitor of the application software is registered through the application status attribute of the application software. For example, if the application status attribute of the application software is persistent and the attribute is true, the death monitor of the resident software is registered; if the application status attribute of the application software is persistent and the attribute is false, the death monitor of the non-resident software is registered.

[0062] For example, if the application software is resident software, since the process of the resident software is in a killed state when the resident software is in an installation state, if it is determined that the resident software meets the installation completion conditions, the process of the resident software is restarted when the process of the resident software is in a killed state, thereby realizing the keep-alive function of the resident software, and the process of the resident software is restarted again after the resident software is installed, thereby avoiding restarting the process during the installation of the resident software.

[0063] In an embodiment, various methods are used for debugging during the development and testing phase, including adding hundreds of log information to determine the timing of restarting the application software process when the application software process is in a killed state, so as to avoid problems in program development.

[0064] In addition, if the PMS broadcasts information that the installation file of the application software has been deleted, it is determined that the installation of the application software is completed.

[0065] In an embodiment, in order to maintain the keep-alive function of the system resident software, the resident software process will be actively started. Since the persistent attribute of the resident software has not been modified and is still true, the death monitor will still be registered after the resident software process is started. When the death monitor detects that the resident software process is accidentally killed, the resident software process can be automatically restarted.

[0066] In some embodiments, the resident software in the prior art relies on OTA (Over-the-Air Technology) updates, which has a long update cycle and cannot meet the requirements for quick updates of the system-preset resident software. In the present application, when the application software is resident software, when the resident software is updated, the application software can be installed by install, silent installation or third-party installation, which improves the convenience and speed of resident software installation.

[0067] Among them, install installation refers to the installation by correctly copying the files, libraries and configuration information of the application software or operating system to the computer's storage device; silent installation is the installation directly according to the default settings without any user intervention. There are two main ways of silent installation: one is to use the silent parameters of the software to compile batch processing for installation, and the other is to install the software by compiling scripts that simulate mouse and keyboard operations; third-party installation is to install application software through third-party applications in the system.

[0068] In an embodiment, when performing installation methods such as install, silent installation or third-party installation, the application software is installed through the PMS (Package Manager Service) of the application operating system, wherein the PMS is a service responsible for managing the installation, uninstallation and update of the software package in the application operating system, and the PMS.PreparePackageLI method is executed during the installation process, wherein the PMS.PreparePackageLI method is a method in the PMS, which is used to prepare to install an application software. In the PMS.PreparePackageLI method, it is first determined whether the application software to be installed needs to be replaced, that is, it is determined whether the application software to be installed is installed for the first time. If the application software to be installed is set with a replace flag, it means that the application software to be installed needs to be replaced, and then the original application software package is uninstalled in the PMS.PreparePackageLI method, and then the new application software package is installed to avoid problems caused by the impact of the new and old versions of the application software package; if the application software to be installed does not set the replace flag, it means that the application software to be installed does not need to be replaced or is installed for the first time, and the PMS.PreparePackageLI method will directly install the new application software package.

[0069] In the embodiment, during the development stage, the present application uses system resident software and non-resident software and third-party applications for comparative verification, and verifies adb install installation, silent installation, third-party installation methods, etc., verifies the installation of application software in a folder, the installation of application software in an IDE (Integrated Development Environment), uninstallation of application software, active killing of application software processes, accidental killing of manufacturing processes, restoration of the application operating system to factory settings or OTA upgrade, etc., to verify abnormal situations such as continuous installation, excessive application software packages, application software package errors, and sudden power failures of electronic devices, thereby verifying that the installation methods in the present application can realize the complete operation of new functions and do not affect the original functions. Among them, the application software is installed in a folder by clicking the application software package in the system folder to install the application software.

[0070] In an embodiment, if it is determined that the device carrying the application operating system is running in a safe mode or in low-power mode, the application software is prohibited from being installed, or is installed in a silent installation manner.

[0071] In an embodiment, the application software installation method of the present invention supports the business requirements of convenient debugging and online updating.

[0072] In the embodiment, the installation location of the application software of the present invention is not limited.

[0073] In the embodiment, AMS and PMS run the service code in the service process. Since the system stability is involved, the location and method of code modification are extremely demanding. Therefore, the insertion and location of the relevant code for the timing of restarting the application software, controlling the installation of the application software, and not restarting after killing the process during the application software installation process in this application will not affect the original program operation and improve the stability of the system.

[0074] Reference below Figure 2 The application software installation method according to the embodiment of the present invention is described by way of example, and the specific contents are as follows.

[0075] Step S3, application software.

[0076] Step S4, when the application operating system is started, the process of controlling the application software is started, and steps S5 and S6 are executed.

[0077] Step S5: If it is determined that the persistent attribute of the application software is true, execute step S7.

[0078] Step S6: if it is determined that the persistent attribute of the application software is false.

[0079] In step S7, the death monitor of the resident software is registered, and step S25 is executed.

[0080] Step S8, the application software is installed using the install command, and step S11 is executed.

[0081] Step S9: The application software is installed using silent installation, and step S12 is executed.

[0082] Step S10, the application software is installed using a third-party installation, and step S12 is executed.

[0083] Step S11, the PMS enters the stage of processing the installation of the application software and executes step S13.

[0084] Step S12, the PMS controls the application software to install the existing application software as the user, and executes step S13.

[0085] Step S13, the PMS prepares to install application software.

[0086] Step S14, replace and install the application software, and execute steps S15 and S16.

[0087] Step S15: If the persistent attribute of the application software is false, execute step S17.

[0088] Step S16: If the persistent attribute of the application software is true, execute step S17.

[0089] Step S17, controlling the application software to continue installation.

[0090] Step S18, the PMS enters the process of killing the application software process and executes steps S23 and S19.

[0091] Step S19, the PMS broadcasts the application software installation completion information, and executes steps S20 and S21.

[0092] Step S20: the application software installation is completed.

[0093] Step S21: The AMS deletes the application software package, and then executes step S22.

[0094] Step S22, actively restart the application software whose persistent attribute is true and which has not been started, and execute step S7.

[0095] Step S23: AMS enters the process of killing the application software process.

[0096] Step S24, the kill process attribute of the application software is set to false.

[0097] Step S25: AMS calls the death monitor to restart or clean up the process.

[0098] Step S26: If the persistent attribute of the application software is false, or the persistent attribute of the application software process is true, execute step S27.

[0099] Step S27, controlling the application software to continue cleaning.

[0100] Step S28: If the persistent attribute of the application software is true, or the persistent attribute of the application software process is true, execute step S29.

[0101] Step S29, controlling the process of the application software to restart, or controlling the application software to restart.

[0102] A second aspect of the present invention provides an application operating system 10, such as Figure 3 As shown, the application operating system 10 includes: at least one processor 1 and a memory 2 communicatively connected to the at least one processor 1 .

[0103] The memory 2 stores a computer program that can be executed by at least one processor 1 , and when the at least one processor 1 executes the computer program, the application software installation method of the above embodiment is implemented.

[0104] In an embodiment, the application operating system may be an Android system, an Apple system, a Hongmeng system or other operating systems, without limitation.

[0105] It should be noted that the specific implementation method of the application operating system 10 of the embodiment of the present invention is similar to the specific implementation method of the application software installation method of any of the above-mentioned embodiments of the present invention. Please refer to the description of the method part for details. In order to reduce redundancy, it will not be repeated here.

[0106] The application operating system 10 according to the embodiment of the present invention can meet the user's demand for resident software updates and improve the user experience by executing the application software installation method of the above embodiment.

[0107] A third aspect of the present invention provides a computer storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the application software installation method of the above embodiment.

[0108] A fourth aspect of the present invention provides an electronic device 20, such as Figure 4 As shown, the electronic device 20 includes the application operating system 10 of the above embodiment.

[0109] In an embodiment, the electronic device may be a central control host, a vehicle host equipped with a ROM (Read-Only Memory) type operating system, a mobile terminal, a mobile phone, a computer, a television, a TV box, a projector, an AR (Augmented Reality) device, a tablet computer and other smart devices equipped with an application operating system, without limitation.

[0110] It should be noted that the specific implementation method of the electronic device 20 in the embodiment of the present invention is similar to the specific implementation method of the application software installation method in any of the above embodiments of the present invention. Please refer to the description of the method part for details. In order to reduce redundancy, it will not be repeated here.

[0111] The electronic device according to the embodiment of the present invention can meet the user's demand for resident software update and improve the user experience through the application operating system of the above embodiment.

[0112] A fifth aspect of the present invention provides a vehicle 30, such as Figure 5 As shown, the vehicle includes the application operating system 10 of the above embodiment.

[0113] It should be noted that the specific implementation method of the vehicle 30 of the embodiment of the present invention is similar to the specific implementation method of the application software installation method of any of the above-mentioned embodiments of the present invention. Please refer to the description of the method part for details. In order to reduce redundancy, it will not be repeated here.

[0114] The vehicle according to the embodiment of the present invention can meet the user's demand for resident software updates and improve the user experience through the application operating system of the above embodiment.

[0115] In the description of this specification, any process or method description in a flowchart or otherwise described herein may be understood to represent a module, fragment or portion of code including one or more executable instructions for implementing the steps of a custom logical function or process, and the scope of the preferred embodiments of the present invention includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in reverse order depending on the functions involved, which should be understood by technicians in the technical field to which the embodiments of the present invention belong.

[0116] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processor, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute the instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purpose of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (electronic device), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or processing in other suitable ways if necessary, and then stored in a computer memory.

[0117] It should be understood that the various parts of the present invention can be implemented by hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, a plurality of steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0118] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0119] In addition, each functional unit in each embodiment of the present invention may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0120] The storage medium mentioned above may be a read-only memory, a magnetic disk or an optical disk, etc. Although the embodiments of the present invention have been shown and described above, it can be understood that the above embodiments are exemplary and cannot be understood as limiting the present invention. A person of ordinary skill in the art may change, modify, replace and modify the above embodiments within the scope of the present invention.

[0121] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples", or "some examples" means that the specific features, structures, materials, or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present invention. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example.

[0122] Although the embodiments of the present invention have been shown and described, it will be appreciated by those skilled in the art that various changes, modifications, substitutions and variations may be made to the embodiments without departing from the principles and spirit of the present invention, and that the scope of the present invention is defined by the claims and their equivalents.

Claims

1. A method for installing application software, characterized in that: include: Determining that the application state attribute of the application software satisfies the resident software attribute condition of the application operating system; In response to the installation request of the application software, the application software is controlled to allow installation, so as to install the application software.

2. The application software installation method according to claim 1, characterized in that: The resident software attribute condition is that the state attribute flag of the application software is that the persistent attribute is true.

3. The application software installation method according to claim 1, characterized in that: The installation method further comprises: During the installation of the application software, executing an operation of killing the application software process; When it is determined that the application software meets the installation completion condition, the application software is started.

4. The application software installation method according to claim 3, characterized in that: In the process of killing the application software process, a preset flag is set for the application software process so that after killing the application software process, the application software is not restarted.

5. The application software installation method according to claim 4, characterized in that: In the process of killing the application software process, setting a preset flag bit for the application software process includes: In the process of killing the application software process, the preset flag bit of the application software process is set to false.

6. The application software installation method according to claim 5, characterized in that: The method further comprises: When the preset flag bit of the application software process is false, after killing the application software process, a cleanup operation is performed on the application software.

7. The application software installation method according to claim 3, characterized in that: The installation completion condition includes: the installation file of the application software has been cleared.

8. The application software installation method according to claim 1, characterized in that: The installation method further comprises: A death monitor for the application software is registered, where the death monitor is used to monitor the process of the application software and restart the process of the application software when the process of the application software is in a killed state.

9. The application software installation method according to any one of claims 1 to 8, characterized in that: The installation method further comprises: The application software is installed by using the install installation, silent installation or third-party installation method.

10. An application operating system, characterized in that: include: at least one processor; a memory communicatively coupled to at least one of the processors; The memory stores a computer program executable by at least one of the processors, and when at least one of the processors executes the computer program, the application software installation method according to any one of claims 1 to 9 is implemented.

11. A computer storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the application software installation method according to any one of claims 1 to 9 is implemented.

12. An electronic device, characterized in that: Includes the application operating system as described in claim 10.

13. A vehicle, characterized in that: Includes the application operating system as described in claim 10.

Images