Application installation method and device and storage medium

Abstract

The invention relates to an application installation method and device and a storage medium. The application installation method comprises the following steps: acquiring a first path for downloading an application installation file; the first path is mapped to a second path, the application installation file is downloaded to the second path, and the second path and a system installation path are located in the same data partition; and moving the application installation file under the second path to the system installation path, and installing the application installation file based on the system installation path. According to the method and the device, the downloading path, namely the first path, of the application installation file is mounted to the second path in the same data partition as the system installation path, and redundant copies in the downloading and installation process of the application installation file are replaced with movement, so that the downloading and installation time of the application installation file is saved, and the user experience is improved.

Description

Technical Field

[0001] The present disclosure relates to the field of terminal technology, and in particular to an application installation method, device and storage medium. Background Art

[0002] Since its birth, mobile terminal devices have received widespread attention and attracted researchers from all walks of life. Their convenience, portability and ever-evolving technology have made mobile devices an indispensable part of people's lives, ranging from communication and entertainment to work and study. With the continuous advancement of technology, mobile devices will continue to play an important role and bring more convenience and possibilities to people's lives.

[0003] On the one hand, due to the portability of mobile terminal devices and their many unique features, they have been well received by users and widely used. Therefore, the number of applications installed on mobile terminal devices is increasing day by day.

[0004] On the other hand, as more and more applications are installed on mobile devices, some hidden problems are increasingly exposed. For example, when a user needs to download and install a large installation file, it needs to be copied multiple times from the download of the installation file to the installation path specified by the system. This copying takes a long time, resulting in slow installation speed and poor user experience. Summary of the invention

[0005] In order to overcome the problems existing in the related art, the present disclosure provides an application installation method, device and storage medium.

[0006] According to a first aspect of an embodiment of the present disclosure, there is provided an application installation method, comprising: obtaining a first path for downloading an application installation file; mapping the first path to a second path, and downloading the application installation file to the second path, wherein the second path and a system installation path are in the same data partition; moving the application installation file under the second path to the system installation path, and installing the application installation file based on the system installation path.

[0007] In one implementation, mapping the first path to the second path includes: mounting the first path to the second path based on a mount function.

[0008] In one embodiment, the method further includes: storing and maintaining mount information, the mount information including the first path information, the second path information, and information for mounting the first path to the second path; in response to an exception occurring in the download process of the application installation file, continuing to execute the mount operation based on the mount information.

[0009] In one implementation, after mounting the first path to the second path, the method further includes: changing the owner of the downloaded application installation file to the system.

[0010] In one implementation, after the application installation file is moved to the system installation path, the steps include: removing first path information in the first path; and clearing data of the first path stored in the second path.

[0011] In one implementation, the method further includes: if the installation of the application based on the mount function fails, executing a general application installation method to install the application.

[0012] According to a second aspect of an embodiment of the present disclosure, an application installation device is provided, including: an acquisition unit, used to acquire a first path for downloading an application installation file; an execution unit, used to map the first path to a second path, and download the application installation file to the second path, wherein the second path and a system installation path are in the same data partition; an installation unit, used to move the application installation file under the second path to the system installation path, and install the application installation file based on the system installation path.

[0013] In one implementation, the execution unit maps the first path to the second path in the following manner: based on a mount function, the first path is mounted to the second path.

[0014] In one embodiment, the execution unit is also used to: store and maintain mount information, the mount information including the first path information, the second path information, and information for mounting the first path to the second path; in response to an exception occurring in the application installation file download process, continue to execute the mount operation based on the mount information.

[0015] In one implementation, after the execution unit mounts the first path to the second path in the following manner, it is further configured to: change the owner of the downloaded application installation file to the system.

[0016] In one implementation, the installation unit moves the application installation file to the system installation path in the following manner: removing first path information in the first path; and clearing data of the first path stored in the second path.

[0017] In one implementation, the installation unit is further configured to: if installation of the application based on the mount function fails, execute a general application installation method to install the application.

[0018] According to a third aspect of an embodiment of the present disclosure, there is provided an application installation device, comprising: a processor; a memory for storing processor executable instructions; wherein the processor is configured to: execute the application installation method described in the first aspect or any one of the implementations of the first aspect.

[0019] According to a fourth aspect of an embodiment of the present disclosure, a storage medium is provided, in which instructions are stored. When the instructions in the storage medium are executed by a processor of a terminal, the terminal is enabled to execute the application installation method described in the first aspect or any one of the embodiments of the first aspect.

[0020] The technical solution provided by the embodiment of the present disclosure may include the following beneficial effects: obtaining a first path for downloading application installation files, mapping the first path to a second path in the same data partition as the system installation path, downloading the application installation files to the second path, moving the application installation files under the second path to the system installation path, and installing the application installation files based on the system installation path. This download and installation process reduces the number of times the application installation files are copied in the related art, shortens the average time consumed for downloading and installing, saves the time of users downloading and installing applications, and improves the user experience.

[0021] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.

[0023] Figure 1 The diagram is a schematic diagram showing a conventional application installation method according to an exemplary embodiment.

[0024] Figure 2 The figure is a flowchart of a method for installing an application according to an exemplary embodiment.

[0025] Figure 3 The diagram is a schematic diagram of an application installation method according to an exemplary embodiment.

[0026] Figure 4 The figure is a flowchart of a method for installing an application according to an exemplary embodiment.

[0027] Figure 5 The figure is a flowchart of a method for installing an application according to an exemplary embodiment.

[0028] Figure 6 The diagram is a schematic diagram showing an application installation implementation logic according to an exemplary embodiment.

[0029] Figure 7 is a timing diagram showing an application installation method according to an exemplary embodiment.

[0030] Figure 8 The figure is a block diagram showing an application installation device according to an exemplary embodiment.

[0031] Fig. 9 The figure is a block diagram showing an application installation device according to an exemplary embodiment.

[0032] Fig.10 The figure is a block diagram showing an application installation device according to an exemplary embodiment. DETAILED DESCRIPTION

[0033] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0034] In the related art, during the application (Application, App) installation process, the Android (Android) installer needs to first copy (copy) the Android application package (Android application package, apk) to a specified path, or needs to first download (download) to the terminal locally, and finally copy it to the system-specified installation path under the data partition ( / data). For large apk files, this copying will take a long time, resulting in a slow installation speed.

[0035] In the embodiment of the present disclosure, an Android installer is taken as an example, and the present disclosure is not limited to any system. Since an Android installer is taken as an example, in the embodiment of the present disclosure, the application installation file can be described as an apk file.

[0036] Figure 1 is a schematic diagram showing a conventional application installation method according to an exemplary embodiment. Figure 1 As shown, the apk file is downloaded to the terminal external storage card (Sdcard, SD card) or the internal storage path of the terminal through a browser, an application store or other download software. Among them, the apk file is the original apk file, and the above two paths can both be the storage paths of the original apk file.

[0037] In the installation preparation stage, the installer first copies the apk file from the original apk file storage path to the path under the installer, that is, the PackageInstaller cache path, which is the first copy (copy 1), and parses the apk file (package) information. Determine whether it needs to be installed from the application store, whether it is a whitelisted app, etc., and submit the apk file to the game center for detection. Then submit the apk file to the security detection software (GuardProvider) for virus scanning. This process requires copying the apk file under the installer path to the security detection software cache (GuardProvidercache) path for virus scanning, which is the second copy (copy 2), thereby obtaining PackageInstaller, creating an installation process dialogue, opening the installation process dialogue, copying the apk file that has passed the virus scan to the system installation path under different data partitions, which is the third copy (copy 3), and submitting the apk file to the installation process.

[0038] Among them, starting from Android 7.0 (N), in order to improve security, file sharing (FileProvider) is used to transfer files between apps to solve the permission problem when sharing files between apps. It allows apps to share private files while protecting these files from being accessed by other apps. At the same time, FileProvider also provides a safe way to access the files of an app so that other apps can use these files. Files are passed through content URIs, and the target app cannot obtain the file path and cannot access it directly. If the target app needs to parse the file, it can only copy the file to the local through the corresponding interface. Figure 1 Contains copy1 and copy 2.

[0039] Based on this, an embodiment of the present disclosure provides an application installation method to improve the time-consuming problem of multiple copies during the application installation process.

[0040] Through the present disclosure, the problem of redundant copying of apk files during terminal download and installation is improved. For the installer, a path is created in the / data partition, and the installer can directly copy / download the apk file to the path. During installation, the apk file is directly moved (move) to the system-specified installation path. This saves the time of copying apk files, shortens the average installation time, achieves the purpose of fast installation, and saves the user's waiting time for installing the APP. In order to ensure security, the path is protected by Security-Enhanced Linux (SELinux) and security detection code to ensure that only platform applications (platform app) and privileged applications (privilege app) can access it. This function is designed to achieve both efficient and secure installation.

[0041] Figure 2 is a flowchart of an application installation method according to an exemplary embodiment. Figure 2 As shown, the method includes the following steps.

[0042] In step S11, a first path for downloading an application installation file is obtained.

[0043] In the disclosed embodiment, the path where the downloaded application installation file, ie, the original apk file is stored, is obtained.

[0044] Exemplarily, the apk file is downloaded to the terminal external storage card (SD card) or the internal storage path of the terminal through download software such as a browser or an application store. Among them, the apk file is the original apk file, and the above two paths can both be the storage paths of the original apk file.

[0045] Exemplarily, the installer (Installer) is used to call the interface getSpeedInstallExternalFilePath to obtain the first path for downloading the application installation file.

[0046] In step S12, the first path is mapped to the second path, and the application installation file is downloaded to the second path.

[0047] In the disclosed embodiment, the first path is mounted to the second path, that is, the path where the original apk file is stored is mounted to the newly created second path, and the application installation file is downloaded to the second path, and the second path and the system installation path are in the same data partition.

[0048] In step S13, the application installation file in the second path is moved to the system installation path, and the application installation file is installed based on the system installation path.

[0049] Figure 3 is a schematic diagram showing an application installation method according to an exemplary embodiment. Figure 3 As shown, the apk file is downloaded to the terminal external storage card (Sdcard, SD card) or the internal storage path of the terminal through a browser, an application store or other download software. Among them, the apk file is the original apk file, and the above two paths can both be the storage paths of the original apk file.

[0050] In the installation preparation stage, the installer first copies the apk file from the original apk file storage path to the newly created second path in the same partition as the system installation path, that is, the speedinstall path / data / apk-tmp, completes a copy, and parses the apk file (package) information. Determine whether it needs to be installed from the application store, whether it is a whitelisted app, etc., and submit the apk file to the game center for detection. Then the security detection software (GuardProvider) directly reads the apk file under the speed install path / data / apk-tmp for virus scanning, obtains PackageInstaller, creates an installation process dialog, opens the installation process dialog, moves the apk file that has passed the virus scan to the system installation path in the same data partition, and installs the application installation file based on the system installation path.

[0051] In the disclosed embodiment, the second path is a newly created high-speed installation path, and the second path and the system installation path are in the same data partition. Files in different paths of the same data partition can be moved to each other, while files in paths of different data partitions need to be copied. Replacing the copying that takes a long time with the moving that takes a shorter time saves the time of file copying and improves the user experience.

[0052] In the embodiment of the present disclosure, the first path is mounted to the second path based on the mount function.

[0053] Exemplarily, the installer (Installer) calls the interface getSpeedInstallExternalFilePath to obtain the first path for downloading the application installation file, and performs a mount operation based on speedInstallRedirectDir to mount the first path to the second path.

[0054] In the disclosed embodiment, by mounting the first path to the second path in the same data partition as the system installation path, the application installation files in the second path can be moved to the system installation path, thereby reducing the copying time of the application installation files and improving the user experience.

[0055] Figure 4 is a flowchart of an application installation method according to an exemplary embodiment. Figure 4 As shown, the method includes the following steps.

[0056] In step S21, the mounting information is stored and maintained.

[0057] In the disclosed embodiment, the mount information includes the first path information, the second path information, and the information of mounting the first path to the second path. The mount information is stored and maintained, so that when an exception occurs during the download and installation process, the mount operation can still be continued based on the mount information to complete the download and installation of the application installation file.

[0058] In step S22, in response to an exception occurring during the download process of the application installation file, the mounting operation is continued based on the mounting information.

[0059] In the embodiment of the present disclosure, the first path information, the second path information and the information of mounting the first path to the second path are stored, and the mounting information is restored when the computer is turned on again.

[0060] For example, the path information of the original apk file storage, the information of the express installation path, and the information of mounting the path storing the original apk file to the express installation path are stored. During the download and installation process of the application file, if the mobile phone is turned off or the application is unresponsive, resulting in the failure of the express installation process, when the phone is turned on again, the mounting operation will continue based on the stored mounting information to complete the installation of the application.

[0061] In the disclosed embodiment, the owner of the downloaded application installation file is changed to the system.

[0062] In the disclosed embodiment, after downloading the application installation software, an installation session is created and opened, the downloaded application installation file is submitted to the quick installation process, the downloaded application installation file is obtained, and the permission of the application installation file is modified, for example, the file can be accessed by the system installer, and the owner of the application installation file is changed to the system, etc., so that the file has the subsequent installation and use permissions.

[0063] Figure 5 is a flowchart of an application installation method according to an exemplary embodiment. Figure 5 As shown, the method includes the following steps.

[0064] In step S31, the first path information in the first path is removed.

[0065] In step S32, the data of the first path stored in the second path is cleared.

[0066] In the disclosed embodiment, after the application installation file is moved to the system installation path, the original apk file information in the path where the original apk file is stored is removed, and the apk file information stored in the express installation path is cleared to save the user's device memory.

[0067] In the embodiment of the present disclosure, if the installation of the application based on the mount function fails, a general application installation method is executed to install the application.

[0068] For example, if the submission of the speed installation file fails, that is, if session.submitSpeedInstallFile returns false, the installer can use the original openwrite interface to continue the installation. If there is an exception, an unrecoverable error occurs and the installation is terminated.

[0069] In the disclosed embodiment, if the installation of the application fails by mounting the first path to the second path, the installer calls the common installation interface and executes the common application installation method to install the application file. That is, if the fast installation fails, the common installation method is used to install the application installation file successfully.

[0070] Figure 6 is a schematic diagram showing an application installation implementation logic according to an exemplary embodiment. Figure 6 As shown, the schematic diagram of the application installation implementation logic is divided into three parts: application layer, framework layer and kernel layer.

[0071] The application layer calls the speedinstall client interface for the installer (Installer App), namely the API interface: PackageInstaller and PackageInstallerSession, to achieve fast installation of apk. That is, the application layer provides an API interface for the installer to call and communicate with the server. It realizes obtaining the storage and download path of apk, submitting apk to the package manager (packagemanager, PM) for installation, and obtaining the download path from the server.

[0072] The framework layer includes three interfaces, namely PakagelnstallerService, PackagelnstallerSession and PackageManagerService. The installer calls the PackageInstaller interface of the application layer, and the PackageInstaller interface of the application layer calls the PackagelnstallerSession interface of the framework layer to provide the address of speedinstall on the external storage, that is, the first path, remove the information of speedinstall on the external storage, maintain the speedinstall path mount information, and read / write the mount information file. The installer calls the PackagelnstallerSession interface of the application layer, and the PackagelnstallerSession interface of the application layer calls the PackagelnstallerSession interface of the framework layer to move the apk file under the speedinstall path, that is, the second path, to the system installation path. PackageManagerService is used to perform the mount operation at startup and clear the data of the Installer under the speedinstall path according to the stored speedinstall mount information. That is, it is mainly used to maintain and manage the speedinstall download path, call InstallD to mount / umount the speedinstall path to sdcard, maintain related data, and move the apk file to the system-specified installation path for installation. The methods in the PackagelnstallerSession interface and the PackageManagerService interface of the framework layer are implemented based on the methods in the PackagelnstallerSession interface.

[0073] The framework layer also includes Installld: with root permissions, executes speedinstall-related path mount / umount functions, is used to actually mount / umount the speedinstall download path to sdcard, and modify the file owner under the path. When the Installer chooses to clear application data, delete the files under the speedintall path, that is, umount the corresponding speedinstall path and delete related content (Installer uninstallation, clear installer data, clear user data).

[0074] The kernel layer includes: speedinstall path Selinux permission control and creation of speedinstall path at boot time, among which, Selinux configuration: configure the selinux security context of the speedinstall path and set permissions.

[0075] Figure 7 is a timing diagram of an application installation method according to an exemplary embodiment. Figure 7 As shown, before downloading the application installation file, the installer (Installer) calls the application layer interface PackageInstaller, and the PackageInstaller interface then calls the framework layer PackageInstaller.Service interface, and obtains the first path for downloading the application installation file through the getSpeedInstallExternalFilePath method of the PackageInstaller.Service interface. The PackageInstaller.Service interface continues to call the speedInstallRedirectDir method to perform the mount operation, mount the first path for downloading the application installation file to the second path, and store the mount information through the WriteSpeedInstallFileLocked method, and store the path mount information to the file / data / system / speed_install_redirect.json to restore the mount information when the computer is turned on again.

[0076] The installer (Installer) downloads the application installation file to the second path, namely Download apk file tospeedinstall path.

[0077] After downloading the application installation file, the installer (Installer) calls the application layer interface PackageInstaller, and PackageInstaller calls the method to create a super-speed installation session and open the super-speed installation session. The installer (Installer) calls the application layer's PackageInstaller.Session interface, and the application layer's PackageInstaller.Session interface calls the framework layer's PackageInstaller.Session interface, and submits the downloaded application installation file to the super-speed installation process through the submitSpeedInstallFile method of the framework layer's PackageInstaller.Session interface, that is, the application installation file under the second path is moved to the system installation path. The Installd interface calls the changeSpeedInstallFileOwner method to modify the owner of the application installation file and modifies the permissions of the application installation file through the SELinux.restoreconRecursive method and the Os.chmod(file,0644) method, so that it has subsequent installation permissions.

[0078] If the installer (Installer) calls the application layer interface PackageInstaller.Session, and the application layer interface PackageInstaller.Session calls the framework layer interface PackageInstaller.Session, and submits the downloaded application installation file to the fast installation process through the submitSpeedInstallFile method of the framework layer PackageInstaller.Session interface, if false is returned, the installer can use the original openwrite interface to continue the installation. If there is an exception, an unrecoverable error occurs and the installation is terminated.

[0079] In the disclosed embodiment, by mounting the storage path of the original apk file, i.e., the first path, to the newly created second path under the same data partition as the system installation path, it is possible to convert a time-consuming copy into a time-consuming move, thereby saving download and installation time and improving the user experience.

[0080] Based on the same concept, an embodiment of the present disclosure also provides an application installation device.

[0081] It is understandable that in order to realize the above functions, the application installation device provided by the embodiment of the present disclosure includes hardware structures and / or software modules corresponding to the execution of each function. In combination with the units and algorithm steps of each example disclosed in the embodiment of the present disclosure, the embodiment of the present disclosure can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiment of the present disclosure.

[0082] Figure 8 FIG. 1 is a block diagram of an application installation device 100 according to an exemplary embodiment. Figure 8 The device 100 includes an acquisition unit 101, an execution unit 102 and an installation unit 103.

[0083] The acquisition unit 101 is used to acquire a first path for downloading an application installation file; the execution unit 102 is used to map the first path to a second path and download the application installation file to the second path, where the second path and the system installation path are in the same data partition; the installation unit 103 is used to move the application installation file under the second path to the system installation path and install the application installation file based on the system installation path.

[0084] In one implementation, the execution unit 102 maps the first path to the second path in the following manner: based on a mount function, the first path is mounted to the second path.

[0085] In one embodiment, the execution unit 102 is also used to: store and maintain mount information, the mount information including first path information, second path information and information for mounting the first path to the second path; in response to an exception occurring during the download process of the application installation file, continue to execute the mount operation based on the mount information.

[0086] In one implementation, after the execution unit 102 mounts the first path to the second path in the following manner, it is further configured to: change the owner of the downloaded application installation file to the system.

[0087] In one implementation, the installation unit 103 moves the application installation file to the system installation path in the following manner: remove the first path information in the first path; and clear the data of the first path stored in the second path.

[0088] In one implementation, the installation unit 103 is further configured to: if the installation of the application based on the mount function fails, execute a general application installation method to install the application.

[0089] Regarding the device in the above embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.

[0090] Fig. 9 2 is a block diagram of a device 200 for application installation according to an exemplary embodiment. The device 200 may be provided as a terminal. For example, the device 200 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0091] Reference Fig. 9 , the device 200 may include one or more of the following components: a processing component 202 , a memory 204 , a power component 206 , a multimedia component 208 , an audio component 210 , an input / output (I / O) interface 212 , a sensor component 214 , and a communication component 216 .

[0092] The processing component 202 generally controls the overall operation of the device 200, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 202 may include one or more processors 220 to execute instructions to perform all or part of the steps of the above-described method. In addition, the processing component 202 may include one or more modules to facilitate interaction between the processing component 202 and other components. For example, the processing component 202 may include a multimedia module to facilitate interaction between the multimedia component 208 and the processing component 202.

[0093] The memory 204 is configured to store various types of data to support operations on the device 200. Examples of such data include instructions for any application or method operating on the device 200, contact data, phone book data, messages, pictures, videos, etc. The memory 204 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0094] The power component 206 provides power to the various components of the device 200. The power component 206 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 200.

[0095] The multimedia component 208 includes a screen that provides an output interface between the device 200 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 208 includes a front camera and / or a rear camera. When the device 200 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0096] The audio component 210 is configured to output and / or input audio signals. For example, the audio component 210 includes a microphone (MIC), and when the device 200 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 204 or sent via the communication component 216. In some embodiments, the audio component 210 also includes a speaker for outputting audio signals.

[0097] I / O interface 212 provides an interface between processing component 202 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: a home button, a volume button, a start button, and a lock button.

[0098] The sensor assembly 214 includes one or more sensors for providing various aspects of the status assessment of the device 200. For example, the sensor assembly 214 can detect the open / closed state of the device 200, the relative positioning of components, such as the display and keypad of the device 200, the sensor assembly 214 can also detect the position change of the device 200 or a component of the device 200, the presence or absence of user contact with the device 200, the orientation or acceleration / deceleration of the device 200 and the temperature change of the device 200. The sensor assembly 214 can include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 214 can also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 214 can also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

[0099] The communication component 216 is configured to facilitate wired or wireless communication between the device 200 and other devices. The device 200 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 216 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 216 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0100] In an exemplary embodiment, the apparatus 200 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0101] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 204 including instructions, and the instructions can be executed by the processor 220 of the device 200 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0102] Fig.10 is a block diagram of a device 300 for application installation according to an exemplary embodiment. For example, the device 300 may be provided as a server. Fig.10 , the apparatus 300 includes a processing component 322, which further includes one or more processors, and a memory resource represented by a memory 332 for storing instructions, such as an application, that can be executed by the processing component 322. The application stored in the memory 332 may include one or more modules, each corresponding to a set of instructions. In addition, the processing component 322 is configured to execute the instructions to perform the above method.

[0103] The device 300 may also include a power supply component 326 configured to perform power management of the device 300, a wired or wireless network interface 350 configured to connect the device 300 to a network, and an input / output (I / O) interface 358. The device 300 may operate based on an operating system stored in the memory 332, such as Windows Server™, Mac OS X™, Unix™, Linux™, FreeBSD™, or the like.

[0104] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 332 including instructions, which can be executed by the processing component 322 of the device 300 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0105] It is to be understood that in the present disclosure, "plurality" refers to two or more than two, and other quantifiers are similar. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. The singular forms "a", "the" and "the" are also intended to include plural forms, unless the context clearly indicates other meanings.

[0106] It is further understood that the terms "first", "second", etc. are used to describe various information, but such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other, and do not indicate a specific order or degree of importance. In fact, the expressions "first", "second", etc. can be used interchangeably. For example, without departing from the scope of the present disclosure, the first information can also be referred to as the second information, and similarly, the second information can also be referred to as the first information.

[0107] It will be further understood that the terms “center”, “longitudinal”, “lateral”, “front”, “back”, “up”, “down”, “left”, “right”, “vertical”, “horizontal”, “top”, “bottom”, “inside”, “outside”, etc., indicating orientations or positional relationships based on the orientations or positional relationships shown in the accompanying drawings, are only for the convenience of describing the present embodiment and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation.

[0108] It can be further understood that, unless otherwise specified, “connection” includes a direct connection without other components between the two, and also includes an indirect connection with other components between the two.

[0109] It is further understood that, although the operations are described in a specific order in the drawings in the embodiments of the present disclosure, it should not be understood as requiring the operations to be performed in the specific order shown or in a serial order, or requiring the execution of all the operations shown to obtain the desired results. In certain environments, multitasking and parallel processing may be advantageous.

[0110] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any modifications, uses or adaptations of the present disclosure, which follow the general principles of the present disclosure and include common knowledge or customary technical means in the art that are not disclosed in the present disclosure.

[0111] It should be understood that the present disclosure is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the scope of the appended claims.

Claims

1. An application installation method, characterized in that: include: Get the first path for downloading application installation files; Mapping the first path to a second path, and downloading the application installation file to the second path, wherein the second path and the system installation path are in the same data partition; Move the application installation file in the second path to the system installation path, and install the application installation file based on the system installation path.

2. The application installation method according to claim 1, characterized in that: Mapping the first path to the second path includes: Based on the mount function, the first path is mounted to the second path.

3. The application installation method according to claim 2, characterized in that: The method further comprises: Storing and maintaining mounting information, the mounting information including the first path information, the second path information, and information for mounting the first path to the second path; In response to an exception occurring during the downloading process of the application installation file, the mounting operation is continued based on the mounting information.

4. The application installation method according to claim 2, characterized in that: After mounting the first path to the second path, the method further includes: Change the owner of the downloaded application installation file to system.

5. The application installation method according to claim 1, characterized in that: After the application installation file is moved to the system installation path, the method includes: removing the first path information in the first path; Clear the data of the first path stored in the second path.

6. The application installation method according to claim 1, characterized in that: The method further comprises: If the installation of the application based on the mount function fails, a general application installation method is executed to install the application.

7. An application installation device, characterized in that: include: An acquisition unit, used to acquire a first path for downloading an application installation file; An execution unit, configured to map the first path to a second path, and download the application installation file to the second path, wherein the second path and the system installation path are in the same data partition; The installation unit is configured to move the application installation file in the second path to the system installation path, and install the application installation file based on the system installation path.

8. The application installation device according to claim 7, characterized in that: The execution unit maps the first path to the second path in the following manner: Based on the mount function, the first path is mounted to the second path.

9. The application installation device according to claim 8, characterized in that: The execution unit is also used for: Storing and maintaining mounting information, the mounting information including the first path information, the second path information, and information for mounting the first path to the second path; In response to an exception occurring during the downloading process of the application installation file, the mounting operation is continued based on the mounting information.

10. The application installation device according to claim 8, characterized in that: After the execution unit mounts the first path to the second path in the following manner, the execution unit is further configured to: Change the owner of the downloaded application installation file to system.

11. The application installation device according to claim 7, characterized in that: The installation unit moves the application installation file to the system installation path in the following manner: removing the first path information in the first path; Clear the data of the first path stored in the second path.

12. The application installation device according to claim 7, characterized in that: The installation unit is also used for: If the installation of the application based on the mount function fails, a general application installation method is executed to install the application.

13. An application installation device, characterized in that: include: processor; a memory for storing processor-executable instructions; Wherein, the processor is configured to: execute the application installation method described in any one of claims 1 to 6.

14. A non-transitory computer-readable storage medium, when instructions in the storage medium are executed by a processor of a mobile terminal, enables the mobile terminal to execute the application installation method according to any one of claims 1 to 6.

Images